I've not noticed this problem myself, but I may not have encountered the situation in the first place. The auto-detect mode of a receiver will work by looking for magic numbers in the data stream which tell it what sort of data is being sent. If those magic numbers disappear, the receiver has to decide what to do -- in your case, I guess it thinks it's having difficulty re-syncing with a DTS stream and elects not to just push that digital data out to the speakers (where it would sound awful).
I presume that the SB3 could interrupt its output stream to force the receiver to reconsider what it was receiving, but I suppose that could ruin gapless playback between ordinary PCM tracks. I've proposed in 'Bug 3047' (http://bugs.slimdevices.com/show_bug.cgi?id=3047) that it would be useful if the SB2/3 could provide certain special behaviour if it knows it's handling a non-PCM digital stream (such as disabling analogue outputs). It seems to me that another useful effect might be to force a stream interruption of some sort if a DTS track is followed by a PCM track. I've added that idea to the bug. (Identification of such tracks in the above scenario is another matter, but might be through a custom tag or the presence of certain values (DTS, Dolby Digital, etc) in a genre list.) -- smst ------------------------------------------------------------------------ smst's Profile: http://forums.slimdevices.com/member.php?userid=752 View this thread: http://forums.slimdevices.com/showthread.php?t=23590 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
