Bug 13381 - Digital bitstream pre-emphasis bit mis set on fab4?
: Digital bitstream pre-emphasis bit mis set on fab4?
Status: CLOSED FIXED
Product: SB Touch
Classification: Unclassified
Component: Audio
: unspecified
: PC Other
: P1 normal (vote)
: 7.5.0
Assigned To: Richard Titmuss
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-13 07:22 UTC by Caleb Crome
Modified: 2010-04-08 17:26 UTC (History)
2 users (show)

See Also:
Category: Bug


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Caleb Crome 2009-08-13 07:22:04 UTC
toby10 noticed the digital out sounds wrong, and jacobdp seems to have verified that the pre-emphasis bit is set when it shouldn't be.
Comment 1 Caleb Crome 2009-08-13 07:23:39 UTC
Steven, can you check the pre-emphasis bit on the digital out?
Comment 2 Spies Steven 2009-08-13 09:51:04 UTC
Sure, I will grab the digilizer and report back when I get a chance.
Comment 3 Toby 2009-08-14 07:21:45 UTC
Specifically it was Optical out, not tried Coax Digital, if that matters.
I'll try both digital outs when FAB gets (any) audio out back.   :)
Comment 4 Phil Leigh 2009-08-14 09:14:03 UTC
I seem to recall that there are two ways to set pre-emphasis? - in the TOC and in the sub-channel... on some CD's the data can conflict. Probably best to set pre-emph to off as default and then to set on only if p/e bit is set?
Comment 5 Spies Steven 2009-08-17 16:09:37 UTC
Yep, according to the Digilyzer we are indeed setting pre-emphasis to on in error for both toslink and coaxial S/PDIF output.
Comment 6 SVN Bot 2009-10-02 06:41:57 UTC
 == Auto-comment from SVN commit #7829 to the jive repo by richard ==
 == https://svn.slimdevices.com/jive?view=revision&revision=7829 ==

Bug #13381
Turn off spdif pre-emphasis bit.
Comment 7 SVN Bot 2009-10-02 06:43:06 UTC
 == Auto-comment from SVN commit #7830 to the jive repo by richard ==
 == https://svn.slimdevices.com/jive?view=revision&revision=7830 ==

Bug #13381
Turn off spdif pre-emphasis bit.
Comment 8 Chris Owens 2010-04-08 17:26:06 UTC
This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release.

If you are still seeing this issue, please let us know!