search

Omeya / a2dpvolume

Automatically exported from code.google.com/p/a2dpvolume
0 stars 0 forks source link

Change volume ocurring at the wrong time #89

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Currently, a2dpvolume adjusts the volume up or down before the bluetooth 
connection is established.

This leads to excessive volume for the tiny speaker in the phone.  It can also 
lead to excessive volume if the car radio was left at a high volume the last 
time it was used.  This could be rather startling for the driver.

If the user sets the media volume high before the bluetooth connection is 
established - it could have the same startling effect.  

My suggestion: Change the volume to a reasonable starting level, then ramp the 
volume to the desired setting after the bluetooth connection is established.

Perhaps settings like:
1. set volume to initial volume setting (pre-ramp)
2. final volume setting (post-ramp)
3. volume ramp time (how long should the volume change take)

Original issue reported on code.google.com by tryoung...@gmail.com on 12 Feb 2012 at 1:06

GoogleCodeExporter commented 9 years ago 
We will need to balance the value of additional settings.  I have already had 
complaints that the app has too many settings.  There is no risk to the phone 
speaker as it is perfectly capable of operating at full volume for long 
periods.  The device manufacturer would not install a speaker that you can fail 
by using the volume control at the max.  I often use that setting when showing 
videos in a noisy place for instance.  

I am thinking we should add 2 settings:
1) Make the current volume up delay adjustable.  Today it is hard coded to 5 
seconds.  Apparently that is not long enough for some devices.

2) Make a new ramp in feature.  I am thinking this will be hard coded.  It will 
ramp in at say 1 tick per second.  Generally the volume has 15 ticks from mute 
to max.

Will this meet the requirements?  It should be a decent balance between 
simplicity and usability.  With this 1 setting and a hard coded delay you 
should never get blasted again.  In fact, I question the value of the ramp.  I 
think the delay is enough but in the case where your cars volume is too high I 
can see the use case where ramping would be nice.  Any thoughts or comments?

This issue is related to issue 80 and issue 86 as well.

Original comment by JimR...@gmail.com on 12 Feb 2012 at 2:44

GoogleCodeExporter commented 9 years ago

Original comment by JimR...@gmail.com on 12 Feb 2012 at 2:44

GoogleCodeExporter commented 9 years ago 
I just posted version 2.5.0 here in the downloads section ready for testing.  
See the 2 new preferences at the bottom of the preferences menu.  I added a 
configuration to the volume up delay time (was previously hard coded to 5s) and 
a volume up ramp.  Please test and let me know how this works for you.

Original comment by JimR...@gmail.com on 12 Feb 2012 at 5:30

GoogleCodeExporter commented 9 years ago

Original comment by JimR...@gmail.com on 16 Feb 2012 at 11:55

GoogleCodeExporter commented 9 years ago 
Hi!

Sorry for the delay in getting back to you.

The volume ramping seems to be working.

However I'm having other problems, and I haven't had a chance to investigate 
them further, due to some kitchen reno's I started doing.

I am having problems with WinAMP always starting from the beginning when it 
connects through bluetooth, and I have to tell my head unit to play or pause 
twice in a row to get it to perform that action.

I'm going to go back to the basics - I want to do some more testing with the 
default player.  I'll let you know what I find.

Original comment by tryoung...@gmail.com on 20 Feb 2012 at 9:08

GoogleCodeExporter commented 9 years ago 
Winamp has some issues, especially on ICS.  Most music players will 
automatically pause on Bluetooth disconnect but some like Winamp and Pandora 
don't do this consistently.  I to send a pause command on disconnect as well so 
most music players should pause.  I considered adding a feature that will send 
the play command but that will require that a music player be active.  I also 
found that this causes the default player to play even if another player is 
playing sometimes.  Another problem can be that memory is low and background 
tasks get killed, such as the paused player.

There are 3 music players I would recommend: Google Music, Amazon MP3, and the 
default player.  Those all seem to do as they are told.  Google Music and 
Amazon are both free cloud players as well as being able to play local content.

Original comment by JimR...@gmail.com on 20 Feb 2012 at 12:02