Ok, so I tested this in Traktor Pro, Traktor S4 and Traktor Pro 2, and it only happens in the latter 2.
If you engage the beatmasher on a track and then set a loop of less than 1 beat, it messes with the beatmasher - I can’t seem to see any sort of pattern to it, but if the loop is 1/32 it almost overrides the beatmasher completely (the track seems to play as normal), with a few buzzing noises. Does anyone else have this problem or is it just me? Bug, or working as intended?
I thought it sampled the track for 4 beats, so if you’ve got a 1 beat loop then it will just sound the same (until you turn up the value on the beatmasher to >0.5).
I’m sure this behaviour isn’t working as intended, it’s too weird (especially as it didn’t happen in Traktor Pro 1)
As I recall, it samples 4 beats from what the deck is currently playing. So if you are playing a 1 beat loop it’ll sample that 1 beat loop for 4 beats. Or, if you sample a 1 beat loop for 2 beats and then the next 2 beats that’ll be the 4 beat loop.
Yeah, that’s what I meant. Doesn’t really explain why if you have the beatmasher engaged (on any value) if you THEN drop a loop of less than 1 beat it sounds weird. It shouldn’t sound weird, it should just continue playing what the beatmasher is outputting.
Ok so I tested while playing around with the clock and it only happens when the deck with the loop + beatmasher turned on is the master. Interesting. I am drunk right now though so I might revisit this in the morning
so only happens in s4/2 and not 1? kind of fits my theory…
wat i’m thinking is that anything below 1 beat loop will start to increase the bpm readout, while the grid and clock will still say 128 (for example) at 1/2 loop hits are coming at 256bpm. if that makes sense?
saying this, i use effects on mix outs more often so have already set next deck to master in all versions to make sure things stay locked