Hi there,

I have an ogg vorbis file which when played in Foobar 2000 v0.9 sounds bad. The thing is, this file plays fine in other players.
Tested it on 2 computers for confirmation.
Result is the same - It has loud pops/clicks on Foobar v0.9, however the file sounds perfectly fine in Foobar 0.83, Winamp5, MPlayer. When decoded to WAV from Foobar (w/o any DSP) also same pops/clicks.
The file in question is uploaded here:
http://www.sendspace.com/file/0ce7eo (2.07MB)
mirror
These pops in the file seem to be placed at random, unevenly but always in the same place each play.

Before anyone asks, this ogg vorbis file was transcoded with aoTuV -q4 (I think it should be the latest
beta5 - Foobar property page says aoTuV b4b - link
Exact Foobar versions used - 0.9.4.3 and 0.9.4.1 (second computer).
I have to mention that as of now this is only one ogg vorbis file I found with such artifacts at decoding.

Could the devs/people-in-the-know look into it?

Edit: fixed link

I just tested it and I can say that such kind of behavior appears to be very strange to me. Foobar never let me down. Let's hope that it's not a foobar issue .

I also tested it in WMP and it played just fine (using matroshka splitter + ffdshow tryouts for playback).

I know this piece of music - it's the audio track of the Spider-Man 3 trailer. I had various problems converting this video into an iPod campatible format and now that you come up with that I suspect the source is the actual problem.

It happens over here too, with 2 different soundcards:
- Crappy built-in Conexant AC-Link Audio
- Audigy 2 NX

I tested also on 16 and 24 bits output, same pops and clicks.

But then, why is the audio gets mangled only on fb2k 0.9?

Perhaps it has a different vorbis decoder, and that's what is at fault.

Eek, happens here as well. fb2k 0.9 with or without pphs resampler (44.1->48) sb audigy 2 zs notebook.

So either the foobar2000 ogg vorbis decoder is faulty or it is too nit-picking. Any chance of getting a technical characterization (of the problem)?

Confirmed. Apparently something in the file makes foobar2000's Ogg parser trip; whether the problem is with the file or the parser is still undetermined. Peter said he would look into it, but gave no specific information about when.

Edit: Note that the Integrity Verifier tool reports a length mismatch between the decoded data and what the file header contains.

According to how I understand the argumentation of parts of the community (remember the cuesheet discussion or the broken mp3 playback discussion) , the reported behaviour is a feature then. Otherwise fb2k would play noncompliant vorbis files. Peter should make it totally refuse playback and leave a message in the console. SCNR.