Why is BeatGrid detection so bad on Engine Prime / Prime 4?
Why don’t the Anchor options not work as they should?
Why can’t Denon make a program that makes a good BeatGrid?
Guys, I’m fed up, after 10 days fighting with ENGINE PRIME, I’m going to be forced to return it to the store where I bought it, because of its disastrous BeatGrid detection, in addition to all the problems it has for folders and subfolders.
I leave two videos, first from Traktor, and another from Engine Prime, of the same track, editing the beatgrid.
In this one, with Traktor, you can see how the track is analyzed well, but on the way down it has a speed change downwards, and then it returns to its original speed, which we solve perfectly with an anchor and moving the grid:
Now, let’s go to Engine Prime.
Right off the bat, the track doesn’t analyze it well, we edit pitch and grid, and the beginning looks good, but when we get to the part of the speed down and up, it is impossible to put it evenly:
In the Engine Prime anchor it says the following:
Set a marker at the current playhead position, and locks the beatgrid BEFORE the anchor. This can be used if the track you are editing has tempo fluctuations, but we already see that this is not the case, if you put an anchor, the track is edited completely, not from the anchor.
So I’m about to return the Prime 4 and get back to my Traktor S5, as Denon doesn’t listen to their customers and I honestly highly doubt they are going to fix this.
Bye Bye Denon.