Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Burning files copied by cdda2wav fails with error #38

Open
Vidrep opened this issue Dec 14, 2021 · 4 comments
Open

Burning files copied by cdda2wav fails with error #38

Vidrep opened this issue Dec 14, 2021 · 4 comments

Comments

@Vidrep
Copy link
Contributor

Vidrep commented Dec 14, 2021

CompilationCloneView.cpp L#448 files.Append("/.wav");
cdrecord sees the append as part of the cloned files directory, rather than as the files to be burned
cdrecord: No such file or directory. Cannot open '/boot/system/cache/burnitnow_clone_wavs/
.wav'.

CompilationCloneView.cpp L#448 files.Append("/");
If *.wav is removed, the cdrecord seems to find the files, but the error message changes to this:
cdrecord: Track 1 has unknown length.
cdrecord: Use tsize= option in SAO mode to specify track size.
pregap1: -1
Track 01: data unknown length

Opening a terminal and running cdrecord from the command line using the same parameters works correctly.
cdrecord dev=2,0 -v -dao -useinfo -text *.wav

@humdingerb
Copy link
Member

(Github swallows the "*" above to format italics...)

If you remove the "*.wav", I think cdrecord tries to burn the folder /boot/system/cache/burnitnow_clone_wavs. So it's no surprise it doesn't work.
It is surprising that manually doing cdrecord dev=2,0 -v -dao -useinfo -text /boot/system/cache/burnitnow_clone_wavs/*.wav does work, but not when doing it 'inside' BurnItNow.

@Vidrep
Copy link
Contributor Author

Vidrep commented Dec 15, 2021

Using cdda2wav to read the disc and create the .inf and .wav files is working perfectly (after a few changes, which we can discuss later).
However, when trying to burn the disc it fails as if cdrecord is seeing the path as a directory rather than as valid individual files. I suspect something is incorrect in the logic somewhere. Can we get one of the other developers to do a quick review of the code?

@Vidrep
Copy link
Contributor Author

Vidrep commented Dec 19, 2021

After launching BurnItNow from a terminal and observing the log while cloning and burning it appears that problem is not in the BurnItNow code at all, but is somewhere else.
Perhaps a related issue in trac? https://dev.haiku-os.org/ticket/11100
There are several such open tickets about apps not finding path

@Vidrep
Copy link
Contributor Author

Vidrep commented Dec 20, 2021

PulkoMandy fixed the disc burning issue in the glob branch. I've tested it, and it's working. The displayed progress message might need a little tweaking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants