The new fluid beat grids are changing the rate of playback if they're played without being pre scanned.
This is on tracks with a clear tempo change.
I'm running the latest released version.
Currently at a gig so this is short.
This is on tracks with a clear tempo change.
I'm running the latest released version.
Currently at a gig so this is short.
Posted 2 days ago @ 11:21 pm
It's happening with tempo transition tracks even if they've been pre-scanned, perhaps not in every case but I can hear it happening on quite a few.
It only happens if sync is pressed (as in BPM match) with the initial values, then it's mangling the track once the tempo changes by slowing down or speeding it up to half or double time.
It only happens if sync is pressed (as in BPM match) with the initial values, then it's mangling the track once the tempo changes by slowing down or speeding it up to half or double time.
Posted 2 days ago @ 11:29 pm
If you loaded a track on the opossite deck and you pressed sync, then bpm_stabilizer automatically turns on.
You should press sync right before you start mixing your song in that case, not right after you load the song.
However I will pass your usage case to the team for further consideration.
You should press sync right before you start mixing your song in that case, not right after you load the song.
However I will pass your usage case to the team for further consideration.
Posted 2 days ago @ 7:36 am
Ok, that's a bit concerning that an update has changed the basic behaviour of BPM match.
I understand that BPM stabiliser may be useful for playing unquantized edits where there's small tempo fluctuations, but having it on by default is problematic, especially if it's attempting to stabilise tracks that have wide and deliberate tempo changes?
I'll be turning this feature off as it's a car crash waiting to happen, but I'd suggest some sort of limitation to its behaviour, such as the ability to set a maximum percentage of allowable change.
Posted 2 days ago @ 12:54 pm
PhantomDeejay wrote :
However I will pass your usage case to the team for further consideration.
However I will pass your usage case to the team for further consideration.
Appreciated, thank you.
Posted 2 days ago @ 1:17 pm
Does the autoBPMStabilizer settings affect this at all?
Posted 2 days ago @ 1:56 pm
DJ VinylTouch wrote :
Does the autoBPMStabilizer settings affect this at all?
Yes, this is the first update I've installed in a very long time that changes the basic behaviour of BPM match/sync by default, surely something like "BPM stabilizer" is more of a niche function and should just have its own button on the skin somewhere, talk about a banana skin.
Posted 16 hours ago
I agree with you on the default behavior . However I was asking about those options in the settings (the new update defaults them to yes), and whether setting them to no restores the old behavior.
Posted 15 hours ago
DJ VinylTouch wrote :
I agree with you on the default behavior . However I was asking about those options in the settings (the new update defaults them to yes), and whether setting them to no restores the old behavior.
Turning it off restores the default behaviour, I wish I knew this at my gig as Thrift shop playing at double time wasn't a good look.
The fluid grids are great though.
Posted 15 hours ago
It's good to know that we can get the default behaviour back 👍🏾.
The Fluid Beatgrids are pretty good indeed - some minor tweaks needed for certain tracks but for the most part it is on point.
The Fluid Beatgrids are pretty good indeed - some minor tweaks needed for certain tracks but for the most part it is on point.
Posted 14 hours ago
Not sure if this is the same issue that I brought up, but at the least, it's very similar. With the way my VDJ is set up, I would have to wait literally until a moment before starting to mix the second song in to load it...otherwise the variable tempo might change, but the second track loaded synced to the original tempo of the first track (I have autobpmmatch enabled).
Posted 8 hours ago





