Bugzilla – Bug 4914
Stops playing any source after switching from digital-in to network
Last modified: 2007-04-26 23:29:02 UTC
While playing from the soundcard via optical without pressing stop in the player (Foobar2000) running directly some song from the Slimserver; Transporter goes mute and can not play anything until I unplug it from the power and turn on again. Please let me know if you need any more specific info as I am quite sure in this bug, happened 2 times today but I am not sure if it is 100% repeatable, kinda reluctant to retry because unplugging it makes me edgy. Btw you should really make some power switch. Soundcard is E-mu 1212m, optical out. 44.1khz songs. Toslink sometimes doesn't sync from the first time then I switch inputs and go back then it works. Btw soundcard is fine, I have another DAC (Northstar) which works without locking issues.
please see bug 4834. consider trying the nightly builds (http://www.slimdevices.com/dev_nightly.html) as this includes FW v31
Solution below, first some info. Installed Slimserver 6.5.2, now player firmware is 31 and it seems to me that the Toslink picks up now every time but unfortunately starting some networked song while listening to the digital-in it will still go mute. Additional info: Wired Ethernet, 230V version Transporter. Actually it seems identical issue to the one you pointed me to: bug 4834. But I have some great info this time! If I pause the Toslink before starting play on the networked it works! Please just add automatic pause if the digital input is playing. Let me know if you do it in the nightly or some version aside and I'll try it, I can now repeat this always.
Additional info: it mumbled the Toslink again, this time the situation is reversed. If I'm playing networked song it switches to the digital-in just fine, if I pause the networked digitan-in is corrupted. So to summarize: pause helps when switching from digital-in to networked. play helps in reversed scenario.
I'm going to merge this with bug 4834. you comments will still be saved to this report but you will be added to the cc list of the other bug, and the comments here can be accessed from that report via a link. *** This bug has been marked as a duplicate of 4834 ***