Traktor 4 bug with beatmarkers

hickbert · 2025-08-05T09:14:35+00:00

There was an error rendering this rich post.

I have a Track that starts at 105bpm, has a small portion acceleration, and then goes on at 150bpm.

Problem is as follows :

The first Gridmarker sets properly at 105, but as soon as i set the 2nd marker at 150 the first 1 gets recalculated to an odd value like 149.025 and the initial grid is f……. up. It seems that the acceleration portion of the Song gets included here.

I CANNOT override this by manually setting the 1st Marker to the desired 105bpm, it still jumps to an odd value by itself!

I cannot use the fine adjustment of the grid for its acting very coarse!

A workaround was setting a sole Beatmarker at the point where the Song accelerates, but this still results in a 105.019 bpm!

That is not satisfying, especially as i was very happy with the function, i have a lot of tracks with odd tempi.

Is this a known bug or imminent to the system?

Find more posts tagged with

Comments

Sûlherokhh

You need three gridmarkers.

First at first beat of 105bpm segment.

Second at last beat of 105bpm segment. If the numbers don't accurately hit 105bpm at this point, you can fine adjust this gridmarker until it does, before setting the third gridmarker.

Third at first beat of 150bpm segment. Once set, you can just plug in 150bpm as a number. The last gridmarker always has this option, while every other gridmarker in front of it will have it's number fixed.

hickbert

Thats what i did in the workaround i described, the result is 105.019 bpm. There is still the portion acceleration between the last 105 marker and the final 150 marker . The calculation includes this part automatically, this cannot be switched off and affects the grid BEFORE the last 105 Marker.

Sonstructure is as follows:

1st 105bpm 64bars / 2nd 105bpm→150bpm 4bars / 3rd 150bpm

Sûlherokhh

Ah, okay i wasn't entirely sure. Does this have an effect on the quantization soundwise over the 64 bars? So far i have switched off my otherwise perfectionist mindset and ignored any 0.01bpm differences. I haven't had any beat-offsets when transitioning or layering multiple tracks. Are you able to hear the offset?

hickbert

thats the track:

Suave by 2DLQTZ, to be found at bandcamp

Sûlherokhh

I'll grid it next time i start up traktor and see if it makes any trouble for me.

But you haven't answered my last questions. 😉

hickbert

Haven't played around with it yet, was trying to nail the Problem last night, i also guess it will work. But just imagine the acceleration would be over 16bars, or the part before it would be only 32bars, then the problem would be more significant.

I just hwonder why i can't manually set the bpm on EVERY marker? that would eliminate the whole issue. especially regarding the fact, that the grid is not in every case set properly automatically

hickbert

Also i wonder why there are no grid markers available anymore in the Cue section. I usually placed 1 at the drop, so i had a countdown towards the drop and a count up from the drop …….

It still seems to exist, there is always set 1 at the first gridmarker, when the track is analized, but i cannot set it manually to a desired position…….

lord-carlos

If you set the second grid marker with snap enabled, or by beatjumping from the first marker, it should result in exactly 105BPM.

But you can also choose to ignore the 0.019, I doubt you can hear the difference.

That is not a workaround, it's how the grid system works.

I just hwonder why i can't manually set the bpm on EVERY marker?

Traktor does not allow half a beat. The distance between two markers gets evenly distributed. But if the second marker is on beat to the first, then it should be a round number.

hickbert

This is not satisfactory, i'll tell you why (actually i already wrote this but again):

In T3 i always set the Gridmarker on the drop, in order to have a countdown of bars and beats to my preferred mixing point. Also i had a WHITE Cuepoint to this important point of the respective Track.

You can simulate this in T4 by setting the first Gridmarker on the drop too, but my cuepoint will stay blue. In this case this means that the offset is worse, 105.026 bpm to be precise, still not much and kinda acceptable. But If the acceleration in the Track would be not only 4 but 8 or even16 Bars long, i'm sure the offset became significantly off! Or imagine more than 1 acceleration and deceleration…….

Don't get me wrong, i actually upgraded especially because of the feature with different beatgrids, BUT almost no Track JUMPS between different timings, they mostly go there gradually so at least for me and the music that i play this long awaited feature is useless for its very purpose. If at least i could override the automatic and set the Grid manually all would be fine. Why is it anyway that Traktor doesn't allow a half beat, a lot of music is written that way!

hickbert

Forget may last Post, or better delete it, the solution was the snap feature , as mentioned above. I had to turn it off for the 150bpm jump and should have turned it on again right afterwards. Problem solved…..

THX for all your answers, and patience :)

Sûlherokhh

Yeah, the SNAP feature constraining gridmarker placement since the last update has irritated many before you, since this was absent in every other Traktor iteration. I didn't even think this could be the issue since i got accustomed to it for a couple of months gridding new tracks. Happy you got it working now. :)

Quick links

Unanswered questions