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

Button map discussion #42

Open
Spagett1 opened this issue Feb 4, 2023 · 2 comments
Open

Button map discussion #42

Spagett1 opened this issue Feb 4, 2023 · 2 comments

Comments

@Spagett1
Copy link
Contributor

Spagett1 commented Feb 4, 2023

Just making this thread to discuss the button mappings.

@Spagett1
Copy link
Contributor Author

Spagett1 commented Feb 4, 2023

one idea i like is to have volume be mapped to the hold button for a hold and increase design. This gets in the way of a hold for ANC pass-through option though. I wonder if a hold both earbuds at the same time for ANC pass-through would be an option

@sbot50
Copy link

sbot50 commented Mar 18, 2023

Ok so here's my feedback on this:
Keep the controls like they are now but instead of tripple tab to only go up one if you hold after triple tab make it increase every x amount of miliseconds (with a sound)
tbf i think there should be sounds for skipping/going back, turning volume up/down anyways and they should be different, but if you wanna implement what you said above then definitely a sound per step up/down in necessary.

Secondly, your implementation of holding both earbuds at the same time wouldn't work for mono earbud use, this is why i suggest what i stated above.

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