Bug 14552 - WAV-PCM Native causing white noise / popping between tracks
: WAV-PCM Native causing white noise / popping between tracks
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Transcoding
: 7.4.0
: PC Windows XP
: -- major with 2 votes (vote)
: 7.4.2
Assigned To: Spies Steven
:
Depends on: 14883
Blocks:
  Show dependency treegraph
 
Reported: 2009-10-03 08:09 UTC by Matt McCulloch
Modified: 2012-02-27 17:33 UTC (History)
5 users (show)

See Also:
Category: ---


Attachments
Track ripped with dbpoweramp containing LIST and ID3 tags (3.92 MB, audio/x-wav)
2009-10-07 18:13 UTC, Jim McAtee
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matt McCulloch 2009-10-03 08:09:41 UTC
In version 7.4, if WAV-FLAC-SOX transcoding is disabled and only WAV-PCM native is enabled, the player creates loud white noise / popping between WAV tracks.  This was not the case in earlier versions where WAV files were transcoded natively, which is how some people prefer to run their WAV files (i.e., not transcoding to FLAC).
Comment 1 Alan Young 2009-10-03 21:56:21 UTC
In previous versions, the raw WAV was sent to the player including the header. The player only actually understands PCM, so it would try to 'play' the WAV header too. This has varied a bit with different versions of SC. With the so-called WAV->PCM transcoding, all that is (supposed to be) happening is that that the server strips off the WAV header and simply sends the raw PCM, avoiding the problem above. Perhaps there is a problem with this mechanism.

I was wondering if your DAC (you said in the forum thread: "I use an outboard DAC (DACMagic for one setup, Music Hall for another)") was somehow expecting a WAV header but I think that would be very odd, and seems even more than likely since you say you are using two different DACs.
Comment 2 Matt McCulloch 2009-10-04 11:25:35 UTC
I agree that it's very unlikely to be a DAC-specific issue because both DACs are experiencing the same problem and neither had any trouble with the native WAV setting in previous versions of SC.  Thanks for looking into this, I hope a fix is possible -- if so, would it available in an upcoming nightly build that I could download?  Much appreciated.
Comment 3 radish 2009-10-06 22:42:39 UTC
It might be worth checking the analog outs from the SB to see if the problem also exists there. If so, it would eliminate the DAC entirely as a suspect.
Comment 4 Matt McCulloch 2009-10-07 06:32:37 UTC
I can confirm that the analog outputs of the SB produce the same noise between WAV tracks (with WAV>FLAC>sox disabled).  I think this eliminates the external DAC as a source of the problem and suggests a transcoding error.  Thanks.
Comment 5 Jim McAtee 2009-10-07 18:13:33 UTC
Created attachment 6060 [details]
Track ripped with dbpoweramp containing LIST and ID3 tags

According to Matt in the forum thread

http://forums.slimdevices.com/showthread.php?t=68932

he's using dbpoweramp to rip to WAV.  dbpoweramp adds LIST and 'ID3' tags to WAV files that it rips.

I've reproduced this bug by using dbpoweramp to rip an album to WAV and scan it into SbS 7.4.x.  Played by SbS through either an SB2 or SB Touch, there's an audible pop at the end of each track.

See the attachment for an example file (23 seconds).  This track plays correctly in Winamp, foobar2000 and Windows Media Player.
Comment 6 Jim McAtee 2009-10-07 18:20:45 UTC
Could this be related in any way to bug 11803, or the fix applied for that bug?
Comment 7 Jim McAtee 2009-10-20 11:22:43 UTC
Alan, any progress on this bug?  The uploaded WAV file contains correctly embedded LIST INFO and id3v2 RIFF chunks at the end of the file.  This is what's causing the noise or pop, as they are apparently not being stripped out in the process of transcoding the WAV to PCM.
Comment 8 Jim McAtee 2009-10-20 13:55:20 UTC
Until this is fixed, a workaround is to stream WAV as WAV, like it used to work.  Instructions here:

http://forums.slimdevices.com/showthread.php?p=475143#post475143
Comment 9 Jim McAtee 2009-10-21 11:18:31 UTC
(In reply to comment #8)
> Until this is fixed, a workaround is to stream WAV as WAV, like it used to
> work.

Forget it.  Doesn't work.  Players can no longer stream WAV.


Why was it necessary to open another bug that addresses this _exact_ problem?
Comment 10 Nossaile 2009-10-23 13:38:16 UTC
I use EAC to rip my WAV-files and I've also these load click noise between every piece of music since the v7.4 update. If it is true that my Duet Receiver no longer have support for WAV then please add it asap, because WAV was included when I bought my Duet.
Comment 11 Jim McAtee 2009-10-26 13:37:54 UTC
This appears to be fixed now.  Should be in tonight's nightly of either 7.5 or 7.4.2.
Comment 12 Nossaile 2009-10-29 15:18:30 UTC
When will the 7.4.2 be released and available through the normal update?
Comment 13 Alan Young 2009-10-29 23:27:04 UTC
A 7.4.2 release is not currently planned.
Comment 14 Pascal Hibon 2009-11-01 10:45:52 UTC
Hi,

I also am using WAV files and have the click at the end of each song. I didn’t notice this before because I had crossfade on. I accidently noticed this yesterday after an iTunes update. Right after the update, iTunes changed something to my database – I guess it moved some files around. Due to this, my SBS database and my actual music files got out of sync. And this is when I noticed the click at the end of a song. Yesterday I was running 7.4.1 –r28904. I read in this bug report that this would be fixed in 7.4.2 current nightly. So I installed 7.4.2 –r29092. I switched off the crossfade and I still experience the click at the end of a song. My WAV files are all tagged with ID3v2.3 tags. My SBS is running on a ReadyNAS NV+ with 1GB of memory.
Is the fix in the release I have installed or do we need to reopen this bug?

Thank you,
Pascal
Comment 15 Pascal Hibon 2009-11-03 06:26:18 UTC
Hello,

Is this bug report still being monitored? Or do I need to file a new bug report?

Thank you,
Pascal
Comment 16 Jim McAtee 2009-11-03 11:36:50 UTC
Try posting to bug 14883.  Could this be an iTunes integration problem, where the audio_size of WAVs isn't being imported properly?
Comment 17 Pascal Hibon 2009-11-03 23:08:55 UTC
I read bug report 14883.  I don’t quite understand why the scanner would work this way. Isn’t it way simpler and better to read the file size from the wave file itself? The file size information would then be provided by the OS and not by the iTunes xml file. 

Also, iTunes is running on my PC (XP), while my wave files reside on the NAS (Linux). Maybe these two OS’s have different ways of calculating file size - or even disk space usage. iTunes would calculate the “file size” based on the XP OS, while SBS would read the wave file stored on a Linux OS. Maybe there is a difference there. 

The streamer engine could even retrieve the length of the data chunk from the wave file itself too. I guess this is the best way to go since the streamer needs to stream the data part of the wav file. See here for details on the chunks inside a wave file: https://ccrma.stanford.edu/courses/422/projects/WaveFormat/
Comment 18 Andy Grundman 2009-11-10 17:16:48 UTC
*** Bug 14561 has been marked as a duplicate of this bug. ***
Comment 19 James Richardson 2012-02-27 17:33:14 UTC
Closing resolved bugs - if you feel this bug still exists please first re-test
with the latest SW/FW version.  If you are able to reproduce then feel free to
reopen and attach new logs / steps to reproduce.