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 files couldn't be found (Read 2019 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Some ogg files couldn't be found

Hi there

Some weeks ago I switched to foobar2000.
Though the player is pretty cool and exactly what i wanted, there's a big minus:
The library scanner doesn't find all of my ogg files in the monitored directories. The fun/strange thing about that is, some of the even decoded ogg files (even from the same album) are recognized. Sadly, the found files are the minority and i have no clue why foobar can't find the others.

Even though foobar doesn't find them, the player has no problems playing them! The files can droped in the playlist and work excellent, also the album/interpreter data are displayed correctly.

This error appears on two of my setups, booth running on win7 64 and foobar2000 1.3.1.
The ogg files are encoded by a cocktail X10.

Can anybody help me or has an idea?
I'll appreciate every hint!

Some ogg files couldn't be found

Reply #1 –
Chances are your files lack proper tags. Right click/properties on the manually dropped ones to see what's missing.

You either fix the tags (which you really should) or you can set whichever library viewer you are using to folder/file structure mode (which ignores tags).

Some ogg files couldn't be found

Reply #2 –
Quote from: Daeron on
Chances are your files lack proper tags. Right click/properties on the manually dropped ones to see what's missing.

You either fix the tags (which you really should) or you can set whichever library viewer you are using to folder/file structure mode (which ignores tags).

The tags all seem to be fine. I checked them with mp3tag and recognized and unregognized files do have the exact same tags filled out. Even foobar accept the tags and shows them, as soon I drop the file in the playlist (from outside the application).

It's really confusing, because I can't see a regularity in failure/success in the files, not in filesize, not duration, not in the name, just nowhere.

Is it possible, nonetheless the files can be played from start to end without hicks or similiar things, that the ogg files ar corrupted? Does someone know how to check the integrity?

Thanks for the media library viewer recommendation, I'll check it out and maybe another one will recognize them

Some ogg files couldn't be found

Reply #4 –
Quote from: Porcus on
Dumb question, but: you have tried rescanning the folders?

Aye, i did, multiple times. In addition i removed the directory and added it again.
I tried it on a other computer, too.

Quote from: Porcus on
As for integrity checking, yeah, http://www.foobar2000.org/components/view/foo_verifier . But I would be very surprised if you saw any differences there.

As you expected: no differences. The files are marked valid, ok and without errors.

BUT i just found out something new (but not less strange ^^):
When I edit the Artist tag to a LONGER name and save it, foobar gets it. After that, I can check the tag back, and the file still shows up, now in the correct place.
If I do the same thing, but to a SHORTER name/value, nothing happens.

So there would be propably a solution in edit all the artist tags twice by a script, but to be honest, I'm still very curious, what's the real matter here.

Some ogg files couldn't be found

Reply #5 –
Feel free to upload a file, possibly somewhere private, and PM Peter with a link. CC: me as well, if you like, but all I can do is examine your file and report anything that looks suspicious in a hex editor.

Some ogg files couldn't be found

Reply #6 –
Quote from: kode54 on
Feel free to upload a file, possibly somewhere private, and PM Peter with a link. CC: me as well, if you like, but all I can do is examine your file and report anything that looks suspicious in a hex editor.

Very kind of you, but this really cranked me up, so i tried it myself just now, and voilà, I found the thing that seems to be the source:

So I downloaded a HEX editor, to take a closer look and found finaly a difference between the files:
All files recognized by foobar do have a gap betwenn the tags and the audio-content (introduced by 'vorbis+BC', all after +/- 00000910)
The files that doesn't end in the library view haven't a empty space (00 00 00 ...) at all, directly after Tracknumber the audio content begins.

Do you guys think, that could cause that behaviour?

@kode54 should this not explain the problem, I would glady take your offer and send peter & you some sampels. Thanks for your effort

Some ogg files couldn't be found

Reply #7 –
According to this official documentation, the comment header should contain at least one more bit (which requires one more byte) after the last comment string, the so-called framing bit. It should be set, to indicate the end of the frame. If it is clear, or the end of the frame has been reached, then the comment is invalid.

I would need to look at the actual Ogg structure of the data, since it may be possible that there is audio data packed into the same frame as the comment header, and I'm not sure if that is valid or not. I'll have to ask #vorbis.