Just running through some tracks for an upcoming gig and so far three or four of them have the incorrect BPM. They are all EDM tracks so really not sure why, but one was on the player as 123.1bpm where in fact it is actually 126.
I know I can change the BPM in the editor but that’s no use unless you actualy know what the correct BPM is.
Can the track be selected and rescanned on the player itself to correct the BPM reading?
no
Well, with the editor it is easy to make the change from 123.1 to 126 BPM or to the right value even if it is not known.
Have you got the track name so we can test it on ours to see how it behaves?
It could be that the analysis isnt picking the beat up correctly as DjAj mentioned, and it requires some manual gridding work (that can be done on the device itself).
Thanks for your reply.
Yes I did figure out the way above, but when cueing a track at a gig it would be better to have an instant rescan rather than having to mess about before the playing track ends.
Again it’s another Engine anomoly that is just not an issue in VDJ.
@STU-C Sorry I can’t remember which tracks they were but if it happens again I will provide a link so others can try.
Thank you.
Yes, but if a track analyzed by EDJ has produced a wrong result (it can also happen), then if you force a new analysis of the track it will surely lead to the same wrong result. So it would not solve anything.
Instead, a manual editing solves the problem.
I understand that manual editing is a pain in the ass, but if it is necessary it must be done.
Small note: I also sometimes compare the results obtained from the analysis of the tracks done by EDJ vs. VDJ. Well I have found that I get better results with EDJ. 
Thing is that I put my SD card back in the PC, re-analyzed it in Engine desktop and it then it scanned with the correct BPM …
Ahhhhhhh ok. Probably your track was analyzed by an old version of EDJ Desktop: in the most recent versions we have modified and improved the track analysis algorithm, that’s why with the new analysis you got the right result.
Yes, I understand your request. In this case you could force a new analysis of the track and get the right result. You are right. Unfortunately it is not possible to do it from Engine OS.
@DjAj I’m a new user and got the Prime Go+ under 4 weeks ago. I have only ever used Engine 4.1 on both PC and the unit.
The quickest method ive found of ‘on device’ grid editing is to hold the shift/slip key down to enter the grid edit (not sure if its the same on the go as the Prime 2) then quickly move the platter to align the grid and press the shift button again to exit the edit mode, usually takes less than 10 seconds.
if its music performed by live instruments its an entirely different proposition, but most electronic music is regular beats so should be just a quick back and forward with the platter to align it.
So the reason is this: if your track has a BPM tag with a value in it, then EDJ uses that value to set its grid. However, if you force a reanalysis of the track, then EDJ ignores the BPM tag and performs the analysis with its own algorithm.
On the mixstream pro go just hold the scratch button & it takes you straight to the grid edit of that track on that deck, then press again to return to mixing, couldn’t be any quicker.
Well funnily enough I just found another one that did the same thing. It’s a video file from Xtendamix which is in VDJ at 128bpm but I checked the tag and it reads 125bpm so that’s definitely the issue. Pobssibly tagged incorrectly by them as I don’t add BPM info to the tags myself.
I usually clear the embedded tag info when prepping a file but must have missed these ones.
Next question, is it possible for Engine DJ to ignore the embedded tag BPM info when scanning?
No. When you load the track for the first time in EDJ Desktop it checks if it has the BPM and KEY tag, then it uses that data. Later if you do the new analysis then it understands that you do not want to use the tag data and performs its analysis. All this was done to allow you to import pre-analyzed tracks from other software (VDJ, Serato, Mix in key) without having the risk of losing the results of those software. There are two solutions:
Well now the mystery is solved. I usually do clear the tags on prep but must have just missed some of them.
At least we have a solution so thank you very much.
Buying an Engine unit was always going to be a learning curve, that’s for sure, but I’m impressed with the robustness of the Prime Go+ hardware wise and also how much Engine has come on in recent times. Still a fair bit to do to catch up with PC based solutions however.
The fact it works seamlessly with VDJ is another bonus.
…and more beautiful things are yet to come! 
I think PC software will always have the edge over hardware OS, but the gap has definitely narrowed in recent times.
Not sure if this still works.
REANALYSE on tracks (new or old) used to ignore imported BPM, Grid and Key and do a fresh analysis.
OK, will try next time. Thank you. I have turned auto analysis off so it will remind me to reanalyze them manually from now on.
Maybe explains the difference between the two analyses.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.