Bugzilla – Bug 2897
Power spike when playing APE with WAV conversion
Last modified: 2009-07-31 10:13:49 UTC
There's a clear audible power spike through the analog output of the SB when playing APE files. This only occurs when the SlimServer is set to convert APE to WAV. When set to APE to convert to FLAC, everything is as smooth as it should be.
Anton - can you attach an APE file that exhibits this problem? Could you also see if it's still an issue with the latest 6.2.2 nightly build with Firmware 43? Thanks.
Subject: Re: Power spike when playing APE with WAV conversion Hello, Thanks for looking into it, although I don't use APE anymore (because of this problem) I will transcode a file to APE, and see if the problem is still there (with the latest), I'll report back to you either today or tomorrow. As for an APE file that will produce this problem; Any will do ...... kind regards, Anton ----- Original Message ----- From: "Slim Devices Bugzilla" <bugs@bugs.slimdevices.com> To: <anton@heimiko.com> Sent: Saturday, April 22, 2006 3:08 AM Subject: [Bug 2897] Power spike when playing APE with WAV conversion > https://bugs-archive.lyrion.org/show_bug.cgi?id=2897 > > > dan@slimdevices.com changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|NEW |ASSIGNED > Target Milestone|--- |6.3 > > > > > ------- Comment #1 from dan@slimdevices.com 2006-04-21 18:08 ------- > Anton - can you attach an APE file that exhibits this problem? > > Could you also see if it's still an issue with the latest 6.2.2 nightly > build > with Firmware 43? > > Thanks. > > > > > ------- You are receiving this mail because: ------- > You are on the CC list for the bug, or are watching someone who is. > You reported the bug, or are watching the reporter. > >
I was about to report this problem myself. I wasn't going to describe it as a power spike on the analog output because I experience it as an audible click on both the analog and digital output. I doubt that a simple voltage spike on the digital side would be audible. The click appears right at the start of every track, even when replayed. This happens with any and every ape file I've tried. I was tearing my hair out for a while trying to figure out what was causing it, but then I remembered changing the file conversion options. Sure enough, enabling the default settings again, i.e. ape to flac transcodes, eliminated the clicks. That increases CPU load needlessly when one has a cable connection.
I forgot to mention that the latest build and firmware doesn't fix it.
Further info as requested by Logitech Customer Support: Squeezebox V3 MAC address 00:04:20:06:A4:A5 Firmware version: 81 SlimServer Version: 6.5.2 - 11763 - Windows XP - EN - cp1252 OS: Windows XP Home SP2
I wonder if this has something to do with a piece of windows code we use called socketwrapper. We'll have a look.
Have you reproduced the problem? Any progress on a solution?
I have not been able to reproduce the problem. Is it possible someone could upload a file the displays the problem? I don't need a whole song. 15-30 seconds would be ideal.
Created attachment 1922 [details] 9 seconds of near-silence. No tags. 9 seconds of near-silence, encoded to Monkey's Audio (.ape) format, version 3.99. No tags.
Any news on this?
None. :( No mention of a fix in version 7 either. It's disappointing that APE->WAV appears to be off the radar. I imagine that some SBs are getting returned as faulty because of this.
Ross, I couldn't play the attached file at all. Could you have a go? If it works for you, try putting several instances in a playlist and see if you can repro this bug. Thanks.
Reproduced this with SC7 - 15998, the click happens 100% of the time with ape -> wav enabled. Let me know if a log or anything is needed.
Ross, can you verify with Release version of SC7 as well as with daily 7.0.1
This bug is still in SC 7.0 - 17793 .
Wanted to mention that I hear the click on Mac OS X as well with SqueezeCenter 7.0. It seems to me that the WAV header is being sent to the Squeezebox and being decoded as audio thus the click.
17793, 17976, both demonstrate the audible click.
Why has it been formally decided not to fix this?
Reduce number of active targets for SC