Closed malvarenga123 closed 9 months ago
Currently, the generation of the filenames is based on what you input to the program. It's a result of calling it with explicit full paths, rather than relative. You could maybe change directory before running it?
I could also see about adding some flag if it would improve the user experience. Can you clarify what your workflow looks like?
Just saw your edit -- it could still be an opportunity for improvement. Can you post your batch?
Sorry for the late reply. The batch file was simple
start "" /low %binmerge_path% --split %cue_name% %split_name%
%split_name% had the full path. After changing it to %~dpn1 it worked fine.
You could maybe change directory before running it?
This a good workaround, but not the best solution. How the output files are specified should not change the output CUE content.
Not adding paths to the BIN files in the CUE content is quite a consensus in communities that deal with CUE files, so I believe no additional flag is necessary, and this can be default behavior.
As for implementation, a simple os.path.basename(track_fn)
when creating the CUE content is enough. I can happily provide a PR if you're interested
Yeah, I'm with you on that. Will adjust it.
The issue was with my batch files.