Bugzilla – Bug 10808
Line out setting not followed for during an alarm
Last modified: 2009-06-17 09:36:31 UTC
Have line out set to always on. Powers a second set of speakers in the ensuite. Works fine except when the boom fires up from the alarm. External speaker seems to be off. If I check the audio setting it still shows line out always. If I set this to off and back on during an alarm the external speakers start working?
Max: don't we turn line-out off during an alarm event? I remember a bug about it, but couldn't find it.
We set line-out mode to subwoofer during an alarm if something is plugged into line out. This is done in order to force output through the main speakers on the assumption that headphones are plugged in. See bug 8146. The case of people plugging speakers into the headphone socket wasn't really considered. There's also the additional problem in that during an alarm with headphones plugged in, sub-woofer mode is used, causing the main speakers to lack bass. In summary, this bug should probably be resolved invalid, but there may be another two bugs lurking round the corner. A lot of these details are in bug 8146.
OK that explains why I am actually hearing a very quite muffled sound out if the ensuite speaker as it lacks in the base department. As to the logic I would say the safest setting is Line Out = On that way both outputs are active during an alarm. That is unless you want a alarm specific output selection.
Bug 8146 was really closed too early. Enabling sub mode was the only way at the time of making sound come through the main speakers even though something was plugged into line out. I don't know if it is yet possible to choose in software to have the same output through the main speakers and line out. Is this what Line Out->Always On does? Felix - can you help? If there's now a software setting to do this, I'll change the alarm code.
Hi Max, yes, you should be able to change that from SC and yes, it's the always on option. I believe this can be set from within the player settings page. /* * Mode == 0 -> headphone * Mode == 1 -> sub out * Mode == 2 -> always on * Mode == 3 -> always off */
Max: should I change this to a SC bug?
Change 24893 should fix this. Line out mode is now temporarily set to always on during an alarm, rather than subwoofer. This should force sound to always play through the internal speakers during an alarm. If something is plugged into line out, that should play too. The problem case now is if someone actually has a sub plugged into line out... Could you test please, James?
This would mean the sub gets a full range signal which will sound different but should not be the end of the world as its own roll off should mix OK. But should the logic be: If client has selected "Always on" or "Subwoofer" then set the output to "Always on" or "Subwoofer" as appropriate. If the client has selected "Always off" or "Headphones" the set "Always on"
Gary: good point! I'll add that tomorrow if I get a chance.
(In reply to comment #8) > > If the client has selected "Always off" or "Headphones" the set "Always on" > Did you mean "...then set to 'Always OFF' That would make more sense to me
I'm not sure of the exact operation of each of the settings. But I assumed that becasue the exsisting code tried to force a situation to make sure an output was active that the logic should follow a simalar route. I guess the only issue is when it is set for headphones so maybe the test should be against that only. I leave it you guys to figure. But still first time I have been involved with bug reporting and it is great to see it all working. Keep up the good work!
Change 24919 changes things so that the line out mode is only changed during an alarm if the line out pref is set to headphones. In this case, line out mode is temporarily set to 'always on', which will force output through the main speakers as well as the headphones. This will ensure that someone asleep with headphones in will get woken up, as well as anyone else in the room. People using subs or external speakers won't be affected. Testing needed, but we should be done.
Latest build installed and seems to be working fine from my perspective. So thanks guys! Keep up the good work.
Verified fixed in SC 7.3.3 r25948
This bug has been fixed in the 7.3.3 release version of SqueezeCenter! If you haven't already. please download the new version from http://www.logitechsqueezebox.com/support/download-squeezecenter.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.