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: Cue File cockup (Read 3172 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Cue File cockup

I have a cue file which once imported into Foobar gives the first 13 tracks the length of 3 - 7 seconds but the 14th track is basically the whole album I have looked at the cue file and I can not see anything wrong but that does not mean there isn't something wrong.

http://pastebin.com/eaMppk2Z This is the cue file in question. This is what its like in foobar

On another note I tried to use the CUETool but it just crashes on start up, .net is installed along with the C+ runtimes.

Cue File cockup

Reply #1 –
Quote
INDEX 01 00:02:45


This means 00 min 02 sec 45 frames (1 frame = 1/75 sec). So, nothing wrong with foobar2000.

Cue File cockup

Reply #2 –
Quote from: lvqcl on
Quote
INDEX 01 00:02:45


This means 00 min 02 sec 45 frames (1 frame = 1/75 sec). So, nothing wrong with foobar2000.


Think I got that one sorted now thanks to greynol. Just have another couple of issues with another cue file now.
http://pastebin.com/2CKMpucG again no idea why its playing up.

Cue File cockup

Reply #4 –
Anyway around it?

Cue File cockup

Reply #5 –
Try a different program, or ask the developer(s) if they can add support for your nonstandard cue file.

Cue File cockup

Reply #6 –
We are talking Foobar2000 devs here  Maybe there is a plugin or something.

-Edit-

In the end I just split the tracks, I know not something I should do but it got the job done.

Cue File cockup

Reply #7 –
foobar2000 opens your second cue without problems if the file has UTF-8 encoding.

Cue File cockup

Reply #8 –
Is foobar2000 still rejecting some cue sheets? IMHO, it's high time this and any other software that treats cue sheets as playlists stops being so half-assed about it. If it's usable as a playlist, use it as a playlist. If I want to put 400 tracks in a 6-hour file and play it with a cue sheet, that should be OK. There's no reason to reject the cue sheet for use as a playlist just because it's not usable for CD-R burning; checking for that is the burning software's job. Nor is there a need to be perfectly compliant with a "spec" defined for one particular piece of CD-R burning software no one uses anymore...for example, cue sheets should be able to be consistently used with ordinary file-per-track rips with gaps appended. /rant

Cue File cockup

Reply #9 –
Quote
for example, cue sheets should be able to be consistently used with ordinary file-per-track rips with gaps appended

You mean noncompliant cue sheets? In this case audio data of a track belong to two different files.
If fb2k core doesn't support such thing (1 track = several files) then support of non-compliant cues simply cannot be added to fb2k.

Cue File cockup

Reply #10 –
Quote from: Enigma776 on
http://pastebin.com/2CKMpucG again no idea why its playing up.

fb2k simply regards cuesheet to be encoded with system locale character set. It can additionally handle UTF-8 only when the file starts with 3 bytes byte order mark (BOM).
If it is actually encoded with different character set, or it is encoded with UTF-8 but doesn't start with BOM, fb2k cannot correctly decode byte sequence in the cuesheet. On some cases, it will simply show wrong characters in title or something. On other cases, it will refuse to open it and you can see something like the following in the console (which is not quite helpful):
Code: [Select]
could not enumerate tracks (Error parsing cuesheet: invalid TITLE syntax (line NN)) on:


In other word, you have to always add BOM to UTF-8 cuesheet if you want fb2k to read it.
Opening it with notepad and saving in UTF-8 will add BOM to the file.