pyBlamscamp updated, and it should probably be renamed
Because of the recent shenanigans I’ve been working on pyBlamscamp again.
For now I’ve just been working on refactoring it to make a GUI possible, and improving performance by actually parallelizing execution wherever possible. And it’s a lot faster now! On my Mac studio (with the files hosted on my NAS), it now takes only 13 seconds to do the full encode of Lo-Fi Beats to Grind Coffee To, down from the previous 105. That’s 8 times as fast! (Presumably it’s mostly I/O bound, what with retrieving the .wav files over gigabit Ethernet, and it would be much faster if the source files were on my local volume.)
So, anyway. My next step will, of course, be to make an actual GUI. Because it’s pretty clear that such a thing would be useful.
Also I should probably rename it. It’s caused quite a lot of confusion, and people don’t seem to understand that pyBlamscamp does way more than the original Blamscamp, but isn’t (yet) as user-friendly. It’s also very much diverged at this point.