github-actions[bot]
commented
1 week ago 👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
To help make it easier for us to investigate your issue, please follow the contributing instructions.
My apologies in advance if this request is not entirely representative of a Whipper related issue and more attributable to user ignorance..
For the first time ever since using Whipper, I recently set about burning files ripped from a CD with Whipper, by using cdrdao and referencing the generated .toc file, given Brasero/k3b bork.
I was unsuccessful, receiving a notification re cdrdao only expecting to find one toc file, but what struck me as interesting was that the tracks listed in the .toc were each named 'data', rather than the name of the tracks that were identified during the rip.
I had converted these to .wav from .flac post-rip but I'm curious whether I may be correct in thinking that a) cdrdao will only reconcile/burn a single image file as opposed to individual tracks, and b) may refuse to accept to files that reflect 'non-compliant'/Red Book gaps?
Again apologies that this doesn't in any sense represent any issue in regard to Whipper, I'm posting chiefly as I'm curious as to how one typically would burn ripped files using the toc file produced to help with that purpose.
Many thanks.