You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the catcher settings there is a setting: "Accepted Audio Volume - Many" for the volume of the "caught" notification. Modifying this value does not do anything unless you set it at 0, which makes no noise at all.
Expected Behavior
The setting should increase/decrease the volume of the notification, depending on what value you have it at.
The value should be between 0-100. That may already be the case, but I don't know because it doesn't work.
Current Behavior
Setting the value to any value between 1-100 results in the notification being at full volume.
Possible Solution
Steps to Reproduce (for bugs)
Using Chrome, go to the catcher
Set volume to 1
Force HIT to be caught and note volume
Set volume to 100
Force HIT to be caught and note volume
Context
The default volume is almost deafeningly loud, so when I'm working on HITs like MLDataLabeler which are batch and the notification is constantly pinging, I have to turn down the volume of Chrome.
Your Environment
Version used: 3.3.1
Browser Name and version: Chrome, 92.0.4515.131
Operating System and version (desktop or mobile): Windows 10 Version 2009 (64-bit)
The text was updated successfully, but these errors were encountered:
In the catcher settings there is a setting: "Accepted Audio Volume - Many" for the volume of the "caught" notification. Modifying this value does not do anything unless you set it at 0, which makes no noise at all.
Expected Behavior
The setting should increase/decrease the volume of the notification, depending on what value you have it at.
The value should be between 0-100. That may already be the case, but I don't know because it doesn't work.
Current Behavior
Setting the value to any value between 1-100 results in the notification being at full volume.
Possible Solution
Steps to Reproduce (for bugs)
Context
Your Environment
The text was updated successfully, but these errors were encountered: