By EnochLight
Wed Feb 10, 2021 12:50 am
Automatically, that is!
User nicethings over at GS found this cool app that scans your sample library (wav's only), and adds Acidized tempo meta data to them so your MPC browser sync/warp actually works. One thing that always irritated me about the MPC's browser is that - unlike Ableton Live - if your samples, clips, loops, etc don't already have tempo metadata in the file, then the MPC browser won't warp them to your project's tempo.
It's a Javascript app that's pretty simple to run. You copy all of your samples into a folder called "wavs" and run the *.bat file. Took less than 10 minutes to process part of my library (I only threw 9 GB at it to start). It does increase your library size, as it creates duplicate files sometimes in half-time for problematic reads. It's also not perfect, and skipped a bunch of files because it claims they exceeded 300 BPM, but it got most of it.
Check it out if not having your sample library content sync/warp in time with your project tempo irritates you:
https://github.com/intelliriffer/WAVAKIER
You'll also need NodeJs on your system from: https://nodejs.org/en/download/
User nicethings over at GS found this cool app that scans your sample library (wav's only), and adds Acidized tempo meta data to them so your MPC browser sync/warp actually works. One thing that always irritated me about the MPC's browser is that - unlike Ableton Live - if your samples, clips, loops, etc don't already have tempo metadata in the file, then the MPC browser won't warp them to your project's tempo.
It's a Javascript app that's pretty simple to run. You copy all of your samples into a folder called "wavs" and run the *.bat file. Took less than 10 minutes to process part of my library (I only threw 9 GB at it to start). It does increase your library size, as it creates duplicate files sometimes in half-time for problematic reads. It's also not perfect, and skipped a bunch of files because it claims they exceeded 300 BPM, but it got most of it.
Check it out if not having your sample library content sync/warp in time with your project tempo irritates you:
https://github.com/intelliriffer/WAVAKIER
You'll also need NodeJs on your system from: https://nodejs.org/en/download/
