I discovered foobar's support for cue sheets by accident the other day, it's great to have support for them natively.
Though one issue I've noticed is that when the track changes, foobar changes position in the file itself, rather than just letting it play, this causes a slight skip in mp3's and for mpc's causes a lockup for half a second or so.
There is another CUE file support issue... Foobar2000 can't play CUE if the FILE directive contains full path to the image file being in different folder.
There is another CUE file support issue... Foobar2000 can't play CUE if the FILE directive contains full path to the image file being in different folder.
Can't reproduce. Works fine as long as path in cue file is correct, no matter if it is full or relative one.
OK. Maybe this issue is OS related... My OS is Windows NT 4 + sp6a, foobar's version is v0.586
Here's foobar's output:
INFO (CORE) : opening file for playback : file://C:\WINNT\Profiles\Administrator\Desktop\Rush - 1976 - 2112.cue
ERROR (CORE) : error opening file for playback : file://C:\WINNT\Profiles\Administrator\Desktop\Rush - 1976 - 2112.cue
3rd line of that CUE:
FILE "G:\Rush - 1976 - 2112.wav" WAVE
And surely there is "Rush - 1976 - 2112.wav" in the root directory of "g" drive.
After mooving the CUE sheet to G:\ and editing FILE directive so that it contains just filename, CUE can be opened by foobar corectly.
keep the paths out of the cues
keep the paths out of the cues
Why? Here's from CUE sheet specification:
...
FILE Command
Description:
This command is used to specify a data/audio file that will be written to the recorder.
Syntax:
FILE <filename> <filetype>
Parameters:
filename - Filename (can include device/directory). If the filename contains any spaces, then it must be enclosed in quotation marks.
...
Absolute paths in cuesheets make no sense.
edit: no too often anyway.
Paths in cue are OK, it was a bug which is fixed in 0.6.