A few recently imported clips won’t time stretch properly. It coincides with an update, could that have smth to do with it?
The clips are all 8 measures long and 120BPM. When I increase the tempo to 128BPM, they jump up one measure, to 9.
I render the clips myself, and they’re always exactly 16 seconds, 480 frames and imported at 120 BPM.
I checked the frame count in Quicktime and in VDMX they end at 16:00secs.
Stopwatch-button for quantisation toggle on, clock synced via Ableton Link.
What’s happening here?
Checked a few more files, incl older ones. Seems persistent: 120BPM clips of 8 bars get bumped up to 9 when tempo set at 128BPM and higher (8 bars still @ 127BPM).
Might have sailed under my radar previously. I’ve made clips often in 128BPM instead of 120BPM (ending at exactly 15 or 16 seconds respectively), and those quantise as expected.
Search engines and AI tell me it’s a rounding error, and that does check in with a threshold (i.e. 128?).
If it is, I really need a workaround that can be done in batch, silently, not applied twice to clips by accident, etc.
I’ll experiment a bit with removing a frame or two from 120BPM clips, setting ‘M’ length via midi etc. Re-rendering @ 128BPM or time stretching in AE would probably be too time consuming.
Also, should I perhaps stick to making 128BPM clips only from now on? That’s about where music I DJ sits, sometimes higher, very rarely below 125.
Thanks!
….Aaaaaaaand I think I might have solved it already! (fingers crossed)
I asked AI to ‘vibe code’ an ffmpeg command to convert 120BPM files to 128, quantized. I don’t trust it entirely, but it actually seems to work! It’s just one command, worth debugging if it doesn’t. And then a simple shell script to batch process. 