Open Forage opened 3 years ago
I see now (#335) that you're actually doing the opposite at the moment by removing the caching, the only difference being that the TOC was stored during the rip process instead of info.
Does this make the use-case described above a no go?
@Freso, @MerlijnWajer what's your opinion about this?
An alternative would be to have a 'light' version of info
not doing an extensive analysis but sticking to basic disc and track info like number, length, ISRC, title, MB additions, etc.
Sorry for the late response, but yeah, I'd argue in favour of removing the cache rather than caching more. Yes, it's annoying that it sometimes reads the entire CD again to get an accurate toc, but a (wrong) cache can be much more annoying, at least in my experience.
It can take some time for
whipper cd info
to finish reading the TOC. When startingwhipper cd rip
the same process is repeated. Providing a way to store the TOC when usinginfo
and reusing the same when following up with arip
would speed up the process a bit.While it being just a rough idea, several things come to mind:
info
andrip
to subsequently save the TOC and read the TOC fromIn addition to a speed-up for when you happen to use
info
beforerip
, it would also function as groundwork for a possible Whipper GUI in the future. You'd want to systematically view the disc content before ripping.