Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Some ogg vorbis files are not playable in foobar2000 v2 (Read 3748 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Some ogg vorbis files are not playable in foobar2000 v2

Some ogg vorbis files are not playable in foobar2000 v2. Tested in foobar2000 v 2 beta 12. Sample -

This file plays fine in 1.6.12.

Re: Some ogg vorbis files are not playable in foobar2000 v2

Reply #1 –
After stripping the tags, File Integrity Verifier in v2 beta 12 64-bit reports:

Warning: Nonsense Ogg granulepos value, file is not properly seekable
Error: Ogg frame decoding failure
Error: Reported length is inaccurate : 4:17.184671 vs 0:00.000000 decoded

In 1.16.12 where it plays fine:

Warning: Reported length is inaccurate : 4:17.184671 vs 4:17.545578 decoded

Re: Some ogg vorbis files are not playable in foobar2000 v2

Reply #2 –
Problem persists in beta 15.

Re: Some ogg vorbis files are not playable in foobar2000 v2

Reply #3 –
Noted, thanks for reporting.
Microsoft Windows: We can't script here, this is bat country.

Re: Some ogg vorbis files are not playable in foobar2000 v2

Reply #4 –
Fixed.
Microsoft Windows: We can't script here, this is bat country.

Re: Some ogg vorbis files are not playable in foobar2000 v2

Reply #5 –
i have the same issue:
"Reported length is inaccurate" in vobis can be fixed with optimize file layout+minimize file size in v.2.2 preview.
"File verification warning: Nonsense Ogg granulepos value, file is not properly seekable" not.
cannot upload it here since too big

Moderator: Please keep audio samples under 30 seconds in length.

it has a tag <BITRATE_NOMINAL> : 519
but bitrate is 610 kbps
2003/2004 possibly created with oggdropXPd V.1.7.6 using GT3b1 based on LibVorbis v1.0 2003-12-13

Re: Some ogg vorbis files are not playable in foobar2000 v2

Reply #6 –
Do you mean it really can't be played, or are you just worried about validator reporting those issues? If it can't be played you can use any file sharing service and send a link to the file to Peter in private message.

If the issue is verifier reporting the granulepos errors, I fear there isn't much you can do. I don't think there is a tool to fix such files losslessly. Oggcleaner doesn't work, remuxing doesn't work. As a workaround granulepos errors can be made to disappear by muxing the audio into Matroska or Webm containers, but as soon as you mux it back into Ogg the granulepos errors are restored.

Re: Some ogg vorbis files are not playable in foobar2000 v2

Reply #7 –
i am just worried rather bothered about validator reporting those issues. Those files play and are seekable here. a link to the file was already sent to Peter by admin.

Matroska or Webm containers are no solution to me, since i.e. they dont play in NI Traktor. Would converting them to Flac be risky? how about modern ogg or mp3 conversion?

Re: Some ogg vorbis files are not playable in foobar2000 v2

Reply #8 –
I was forwarded download links from above that were edited out, sadly neither works - former seems to have been transcoded by the hosting provider, latter shows copyright-related error.
What Case said is valid, we've seen more of these files before, specific old/buggy encoders produced Ogg files with malformed timing information and no other software complained about it at the time.
I recommend just ignoring this error, this issue does not prevent decoding, only causes possibly inaccurate seeking.
Microsoft Windows: We can't script here, this is bat country.

Re: Some ogg vorbis files are not playable in foobar2000 v2

Reply #9 –
@Peter i sent you a new link as PM.
ignoring this error is unconvienient, since the popup window places itself every time in the middle of my screen. now also it seems the error ""Reported length is inaccurate" in vobis can not every time be fixed with "optimize file layout+minimize file size"".
i have hundreds of those files and would prefer having a flawless playback without those error messages.

then i have some files with "Suspiciously large peak". how to deal with this?

Re: Some ogg vorbis files are not playable in foobar2000 v2

Reply #10 –
You can disable the file verification during playback (Preferences -> Advanced -> Playback -> Verify integrity of played tracks and report errors immediately). That way you don't see warnings about the files being faulty.

Converting to FLAC is unwise: FLAC itself is lossless but doesn't support floating point input that Vorbis decoding produces. The files would be rounded to for example 16 bits and potential high peaks would get hard clipped. And using lossless encoder means the file sizes would become much bigger.

Transcoding to other lossy codec is a theoretical option to get rid of the granulepos errors. But that means further quality reduction. Every time a signal is lossy compressed it loses some details. I'd highly recommend against it.

The files with "suspiciously large peak" errors sound like they are corrupted, though Vorbis seems to just drop corrupted frames instead of decoding nonsense. Are they Ogg Vorbis files too?

Re: Some ogg vorbis files are not playable in foobar2000 v2

Reply #11 –
thinking about it now i am quite happy to see the error notice when there is an error. the reason i dont just disable file verification is i want to have flawless audio files. i imagine timing errors can cause beat sync errors in programs like mixxx oder ni traktor. that i cant risk.

so thanx for showing me detailed hurdles just in an proposed conversion process. these days i dont care so much about filesizes. not degrading sound would be important to me. is there a way in an audio editor or else to bring ogg to floating point wave, convert it to fixed point, thereafter in flac?

or is there an floiting point lossless codec usable in traktor/mixxx?

Re: Some ogg vorbis files are not playable in foobar2000 v2

Reply #12 –
If those errors annoy you too much and you really want to do the conversion to get valid data, I'd recommend converting the files back to Vorbis. If you use same or higher bitrate as the originals had, the quality loss will be inaudible and mostly theoretical.

But if you also want to edit the files before this error-clearing operation, for example to try to fix cases of "Suspiciously large peak", you can convert the files to 32-bit WAV with foobar2000 converter. That format is able to losslessly store the output from the decoder and won't clip or change the data in any way. Downside is that the files will be very big as there's no compression.
Once you edit the files and fix any issues you can, you can convert them back to Vorbis to save space and remind yourself where the files originated from.

Traktor and Mixxx both support WAV format, but not sure how well. If they for example handle any metadata.

It's a shame I don't have unlimited time. I would be somewhat curious to see if such nonsensical files could be losslessly fixed by sanely recreating the ogg file. Though in all honesty creating a tool for repairing these files should be the job for whoever is responsible for creating software that produced them.

Re: Some ogg vorbis files are not playable in foobar2000 v2

Reply #13 –
the few cases of "Suspiciously large peak" i just got new.
i also did some conversions and listening to results/codecs again  :P  not finished yet.
doing so i found out, there is 4 Writing libraries involved:
Lavf58.76.100
libVorbis 1.0 (2002-07-17)
libVorbis 1.1 (2004-06-29)
libVorbis 1.0 (GTune 3 Beta 1) (2002-07-17)
note: only some percentage of all the ogg files fail the integrity check. so i wonder if the data/files are not intact because of some earlier harddrive errors, viruses/cleaners ect.

Re: Some ogg vorbis files are not playable in foobar2000 v2

Reply #14 –
"Suspiciously large peak" errors could have been introduced later by failing hardware. But hard to say what has really happened as you haven't shared any more details about such files. But the granulepos errors are introduced during file creation and I don't think hardware error could have caused them.
 

Re: Some ogg vorbis files are not playable in foobar2000 v2

Reply #16 –
ok, i will deal with those ogg/opus errors over time. @Peter will next week have a look at that file i sent.

if there will be no other solution by @Peter, high bitrates (often 48khz) will be converted with fb2k into 32bit float .wav (thanx for the hint @Case) and then reencoded + dithered into 16bit flac. after doing some listening tests, this is my preferred combination. low bitrate files i will probably get new, or transcode them with the latest aotuv encoder. since rarewares.org is down currently, this will have to wait. thanx for your help @all

since i scanned my collection for errors, i found 1096 mp3 files with different errors not repairable by fb2k. one of them crashed mp3tag while loading. few of them can be fixed in the old mp3val.
is there a place where i can upload some examples, maybe for the devs to make fb2k even stronger? should i open a new thread?

Re: Some ogg vorbis files are not playable in foobar2000 v2

Reply #18 –
Quote from: orangefx on
ok, i will deal with those ogg/opus errors over time. @Peter will next week have a look at that file i sent.
since peter did not respond after checking and i would still prefer the corrupted ogg vorbis files to be repaired i found the command line tool OptiVorbis
i am not shure if it works in all situations as advertised. i just tried a few errornous files. "Reported length is inaccurate" was not fixed with their web demo page. but "Nonsense Ogg granulepos value, file is not properly seekable" is.
worth implementing in foobar?!
@Peter @Case hows that sound?

Re: Some ogg vorbis files are not playable in foobar2000 v2

Reply #19 –
i looked further into a solution to losslessly fix ogg vorbis errors and found OptiVorbis
Since i am too unfit to work commandline tools, i ran into some problems with the web interface. this resulted in a bug report, followed by some discussion with the developer Alejandro.

Since i got no feedback here, it might be of interest to the fb2k developers. or other users with broken ogg vorbis files.