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: Strange behavior involving foobar, monkey audio and mp3tag (Read 3693 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Strange behavior involving foobar, monkey audio and mp3tag

Hi there!

When i saw that some audio formats, like wavpack for example used to store the cuesheet in a tag field called 'CUESHEET' , i thought it was a good idea so i started to do the same with my
monkey audio files.

But then i discovered that many of those files that has the cuesheet embedded where not seen anymore by foobar (BTW before you ask, i use v0.9.8.6).

I did a lot of tests to try to find the exact circonstances but I don't understand it.

Here's a sample of a cuesheet that you can copy and paste in a 'CUESHEET' field of any ape files
with mp3tag. After that, go in foobar and add the folder where the file is and you should see that
the file will not be seen.

Then you go back in mp3tag and remove the last character (the zero) save the tag and go back in foobar to rescan the folder and then the file will be seen.



REM GENRE "Thrash Metal"
REM DATE 2007
REM DISCID 8110CE0A
REM COMMENT "ExactAudioCopy v0.95b4"
PERFORMER "Exodus"
TITLE "The Atrocity Exhibition - Exhibit A"
FILE "01 - Call To Arms.wav" WAVE
TRACK 01 AUDIO
TITLE "Call To Arms"
PERFORMER "Exodus"
INDEX 01 00:00:00
FILE "02 - Riot Act.wav" WAVE
TRACK 02 AUDIO
TITLE "Riot Act"
PERFORMER "Exodus"
INDEX 01 0




Is it related to foobar? to the monkey audio input plugin or to mp3tag? (altough probably not) i
don't know but since many of us use a combination of these 2 great software i thought that it could
be interesting for some.

If someone can or can't reproduce the behavior please let me know.

Thanks
Christian

Strange behavior involving foobar, monkey audio and mp3tag

Reply #1
Context menu - Utils - Edit Cuesheet

I believe this is the correct way as of 0.9.
Sharing delusions since 1991.

Strange behavior involving foobar, monkey audio and mp3tag

Reply #2
Hi slotos,

The Edit embedded cuesheet doesn't seems to work with ape files but i still think that anyway, this is a behavior that is close to a bug.

I'm sending 2 small files as a sample to demonstrate my point. The only difference between these
files, other than their name, is one byte in their tag, but that's enough to make foobar ignore one
of the two.

If someone want to make the test, just unzip'em in a folder, go in foobar and do "Add Folder" to add
the one where the files are, not "Add Files" but "Add Folder". At this point, you should see that the track called "Bad file.ape" will not be displayed.

I'm using foobar v0.9.8.6 and foo_input_monkey v2.1.4 wich are both the latest version i think.

Oopps! just realize that i can't attach a file... i have send it on the mp3tag forum, you can download it there or i can send it to the ones that want to make the test.

Thanks
Christian

Strange behavior involving foobar, monkey audio and mp3tag

Reply #3
There are two issues with what you are trying to do:
1) you are embedding one-file-per-track cue sheet to image
2) your cue sheet is broken (most likely incomplete)

Strange behavior involving foobar, monkey audio and mp3tag

Reply #4
The reason why the cuesheet is broken is because i erase the end of it when i tried to go down to the first character that causes the problem. The same thing was happening with the cuesheet complete.

And Case, you're right, i think i'm mis-using the concept of embedded cuesheet wich is, from what i understand, for peoples who rip a whole album to a single file but still want to be able to skip to individual tracks.

Personnaly, i prefer having the tracks already splitted but i wanted to keep the cuesheet somewhere just in case... So that's why it ended up in the tag of each first track.

I can see now that it's bad practice so what i'll do from now on, is use a field call CUEFILE instead of CUESHEET like some people do.

The only thing is maybe i would have liked that foobar handle the situation differently, perhaps giving me a message that a corrupted cuesheet had been found and offering some options. Instead it let me wonder what was happening.

It's not a critic... I love foobar!

Thanks
Christian