I just tried this. Load Love Is In The Air on deck 1 and start playing. Load Daddy Cool into deck 2 and press sync. Hit play on deck 2, and watch Daddy Cool play perfectly in sync with Love Is In The Air.
This is just perfect, and it is made possible by the revolutionizing beat gridding engine in 5.0. I can’t count the hours I have spent on manually beat gridding tracks on Serato. Luckily this is a thing of the past.
PS: For this to work sync type needs to be set to “BPM and Beats” (Settings / General / Sync Mode / Sync Type)
I really like the new features to DJay Pro 5.0
Room for improvement, lots:
Is there a way to lock the bpm and grid arrangement from my library?
It would be nice to set a default for dynamic or fixed track analysis.
For example: since the upgrade, most of the song I load into the decks, the set bpm gets reanalyzed, hence the grid modified. This is a big advantage problem if you have a DJ gig.
It would be best if I could decide which songs I would like to re analyze or fix.
@djSahid the Fluid Beatgrid system has been redesigned from the ground up and is not compatible with the old system. This is why all tracks need to be reanalyzed the first time they are played. I’m sharing everyone’s input with the dev team. Also we will be releasing an FAQ article soon which will explain in detail how the new system works.
Hi !
I had a stressful GIG 2 days ago and it was stressful with the 5,0… I had a similar BPM issue. I figured the dynamic and straight setting. It was okay at first, but it started switching back to the dynamic mode and I had to manually change it. It there a there any way to lock-it ( dynamic or straight) to your preferences ?
I’ve spent years manually inputting all my beat grids in and now they’re completely wrecked. Random starts, no grids matching, all the bpms changed, can’t set a beatgrid without all the track being thrown out. I’m just devastated and I feel like giving up now. I have thousands of tracks that are ruined and unplayable because of this update and I can’t revert…
That’s crap indeed. Food for thought for the team.
Maybe not assume that every new feature is an improvement for everyone and make upgrading to whatever new feature optional.
E.g. In Live they’ve made tons of tweaks on internal devices over the years, but they’ll never force you to use the latest one as sets will open up with the original / old version and an ‘update’ button.
There needs to be a legacy beatgrid option so I can save my sets on iOS. Other wise I’ll just enter the same information from scratch in rekordbox and ditch this system once and for all…
Crazy. I was about to do a set when I had to update. Now I genuinely have no idea what is going on with the BPM. Simply put it moves on it and a lot of the time is not in sync with the other song. AND it moves without the music playing at all! This is a wilddddd update to make without proper testing. It really messed with my set.
I’ve read this thread and changed the BPM setting to straight and it’s still going haywire. This is a bug not a feature right? I absolutely love this software, and it’s the reason I haven’t learned CDJs…but honestly it looks like I’m going to have to make that a priority.
There needs to be an option to turn this off asap!
If a track consists of two tempos, is there a way to adjust the tempo either side of an anchor separately?
I’ve found a track that the Fluid Beatgrid doesn’t understand. DJay can detect that there are two tempos, but the grid lines in the slower section are in between beats. The grids in the fast section are in the correct place.
I’m finding I can’t correct one section without the grids in the other section moving. I tried placing an anchor at the changeover point but then the grid after the anchor was too slow.
This app was working perfectly before this update. As a matter of fact, that is the only reason I ditched my previous DJ app 2 months ago, and now this. This is unacceptable!
It seems to me after reading this thread, people seem to be misunderstanding how Fluid Beatgrid works.
They’re so used to DJ software incorrectly assigning a single BPM to all tracks that they see any variation as a problem. Actually it’s the other way around. Now we’re able to see the true BPM any any point. If it varies, we see it.