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: Absolute vs relative pathnames (Read 2903 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Absolute vs relative pathnames

Are there any plans to support absolute pathnames within cue sheets?

What is the "relative" pathname base directory? Is it the directory of the playlist? Is it the directory of foobar2K executable?

Can this "start" directory be set through the foobar2K start command?

Absolute vs relative pathnames

Reply #1
Are there any plans to support absolute pathnames within cue sheets?
I don't think so.
What is the "relative" pathname base directory?
The directory where the .cue file is located.
Is it the directory of the playlist?
No. Cue sheets are not playlists.
Full-quoting makes you scroll past the same junk over and over.

Absolute vs relative pathnames

Reply #2
Are there any plans to support absolute pathnames within cue sheets?
I don't think so.
What is the "relative" pathname base directory?
The directory where the .cue file is located.
Is it the directory of the playlist?
No. Cue sheets are not playlists.


Thanks for that!  Now I know how to deal with them.

Excellent forum.

This all came out when trying to run foobar under cMP.  cPlay is the usual suspect for doing so and it supports absolute path names within cue sheets. 

Is there a cue file creator that will create the relative names that foobar likes?  I used recursive cue creator, but it created absolute paths.  ( I suppose I could modify the jar file....)

Absolute vs relative pathnames

Reply #3
if you create your compressed audio backup of a cd with foobar, you can choose to create single file + cue.