3 ms·
> this will be at least little bit helpful for those people, wouldn't it Probably not, because they're unlikely to have enough stuff to export that it's releva
by masklinn 2y ago
> this will be at least little bit helpful for those people, wouldn't it
Probably not, because they're unlikely to have enough stuff to export that it's relevant.
> Edit: Just tried turning a ~5 minute .wav into .flac (without multithreading) on a Intel Celeron N4505 (worst CPU I have running atm) and took around 20 seconds, FWIW
Which is basically nothing. It takes more time than that to fix the track's tagging.
- diggan 2y agoI mean, you're again assuming the only use case is "encode and tag a huge music collection", encoding is used for more than that. For example, I have a raspberry pi that is responsible for recording as soon as it powers up. Then I can press a button, and it grabs the last 60 recorded minutes, which happens to be saved as .wav right now, which I'm fine with, the rest of my pipeline works with .wav. But if my pipeline required flac, I would need to turn the wav into flac on the raspberry pi at this point, for 60 minutes of audio, and of course I'd like that to be faster if possible, so I can start editing it right away.