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

burst mode readout #481

Open
ghost opened this issue Apr 23, 2020 · 6 comments
Open

burst mode readout #481

ghost opened this issue Apr 23, 2020 · 6 comments
Labels
Feature New feature Needed: discussion More discussion needed before anything can be done (or still no agreement has been reached) On Hold Waiting for other actions

Comments

@ghost
Copy link

ghost commented Apr 23, 2020

first off - i hope this subject has not been covered already.

whipper has its focus on accuracy over speed, but this is often also a very time-consuming process. now, how about offering an optional 1pass readout via burst mode (as fast as possible, no test & copy), which switches to secure mode in case of accuraterip discrepancies for problematic tracks only.

this way one could save a lot of time without having to make compromises in terms of accuracy.

@MerlijnWajer
Copy link
Collaborator

I do exactly this in my software that relies on a mix of morituri and whipper. (Started before whipper existed)

It's totally possible. I did it slightly differently though, adding heuristics. If the first X tracks all have to fall back to paranoid mode, maybe there is no reason to try to run track X + 1 in burst mode first.

@ghost
Copy link
Author

ghost commented Apr 23, 2020

that sound great.

i also believe it would make a nice addition to whipper, as the extraction process could be trimmed down drastically in most of the cases, but with no impact on accuracy at all.

@texneus
Copy link

texneus commented Apr 25, 2020

I would also like to add to this that if the accurate rip database is available for the selected CD and track that the track only requires ripping in one pass (could be in burst or accurate mode, perhaps a user selectable option). If the accurate rip database check passes, move on. If it fails or accurate rip data isn't available, then it could fall back to it's current behaviour (multiple passes in accurate mode, etc). Although I'm on definitely all for the accuracy whipper promotes and guarantees, but I've always wondered if it was being unnecessary redundant.

@JoeLametta JoeLametta added Feature New feature Needed: discussion More discussion needed before anything can be done (or still no agreement has been reached) On Hold Waiting for other actions labels May 29, 2020
@stormwatch
Copy link

stormwatch commented Feb 22, 2021

Whipper is awesome and +1 to every previous comment. It's been a long time since I had to rip an audio CD. In the meantime, do you know by any chance of other linux software that is able to rip in burst mode? I mean, besides EAC under wine. what about passing -Z (--disable-pranoia) to cd-paranoia? Is it possible from within whipper or with an env variable?

@JoeLametta
Copy link
Collaborator

Whipper is awesome and +1 to every previous comment.

Thanks!

It's been a long time since I had to rip an audio CD. In the meantime, do you know by any chance of other linux software that is able to rip in burst mode? I mean, besides EAC under wine.

Well, there's abcde which is quite customizable.

what about passing -Z (--disable-pranoia) to cd-paranoia?

I think that is roughly equivalent to what EAC does in burst mode.
You can also try cdda2wav which offers more settings than cdparanoia to tune the accuracy / error detection of the rip.

Is it possible from within whipper or with an env variable?

It isn't currently possible.

@eharris
Copy link

eharris commented Sep 22, 2022

#266 seems to be a similar feature request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature Needed: discussion More discussion needed before anything can be done (or still no agreement has been reached) On Hold Waiting for other actions
Projects
None yet
Development

No branches or pull requests

5 participants