Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tick sound is annoying #1

Open
yishayw opened this issue Sep 8, 2012 · 1 comment
Open

Tick sound is annoying #1

yishayw opened this issue Sep 8, 2012 · 1 comment
Assignees

Comments

@yishayw
Copy link
Owner

yishayw commented Sep 8, 2012

Scenario:

  • login
  • Click on 'My turn' button
  • Keep the button down for several seconds

Expected result:

Tick sound should be noticeable but not annoying

Actual result:

Tick sound is both noticeable and annoying

@ghost ghost assigned yishayw Sep 8, 2012
@DavidStodolsky
Copy link

On 8 Sep 2012, at 10:24 PM, yishayw wrote:

Scenario:

login
Click on 'My turn' button
Keep the button down for several seconds
Expected result:

Tick sound should be noticeable but not annoying

Actual result:

Tick sound is both noticeable and annoying

It is likely that a sound designer will be needed to resolve these types of issues. In a fully developed App, the following functions will be needed:

  1. Announcement of the next speaker or of the waiting state.
  2. "Button" activation feedback to compensate for the lack of tactile feedback on touch screen devices.
  3. For best results, people will have to compare the volume of the sound from each phone and then allow the weakest phone to determine the amplitude for all phones.
  4. A network test. The signal could be sent to all phones at the same time. If a phone had a congested network connection or some other problem, it would not sound at the same time as the others.
  5. A connectivity test. Trigger each phone about a quarter of a second after the previous one, until all have sounded. This would also permit the group to ensure that everyone participating was registered and not a lurker/spy.
  6. In more advanced dialogue management models, there are different priority levels. For example, if someone wishes to correct an error in a statement that has just been made, they can be the next speaker even though they would be speaking out-of-turn if they had not been offering a criticism. In a fully developed model, seven or more priority levels would be available. Different sounds for each level would help avoid confusion.

(Vibration of a phone is considered to be a type of sound output. Not all devices, however, have vibratory output. Therefore, sound will be needed for a comprehensive solution. Full privacy protection would require an earphone output on devices lacking vibratory output.)

dss

David Stodolsky Blog: http://cosmism.blogspot.com
dss@secureid.org Skype/Twitter: davidstodolsky

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants