when having the CROSFADER FX active, when using HOTCUE it should drop by 1 beat when moving the crossfader, but it goes in time… this is uncomfortable since djay doesn’t always interpret the beat rhythm of the songs… is there some setting I’m missing???
It happens since the new update 5.3.2
Hi @LuisCervants, what Beat sync internal are you using in the djay Settings>General>Sync Mode? Try setting it to 1 Beat.
It’s on 1 beat activated… it shows at the end of the video… I think it’s a mistake… have you tried doing it like in the video?
please help!
How do I go back to version 5.3.1, it was working without any problems
Hi @LuisCervants, thanks for the clarification. Sorry I missed that at the end of your video. I was able to replicate this on my setup and have passed this onto our engineering team for further review.
The only way to rollback to a previous version of djay is if you have a full system backup made to your laptop via the iTunes/Music app.
Hi again @LuisCervants, I checked with the dev team and this is actually expected behavior in the latest version of djay. This change was requested users. However, the team is going to review this further and see if there are some options we can offer to satisfy to both use cases. I’ll report back here when I have more news. Thanks!
Yes as it works well for me.
Thanks for the feedback @Dysfunk_DJ
Do you only mix electronic music? Well, I’m a crossover DJ, so the time signature won’t always be in 1/16… sometimes it will be 4/16… professional DJs will understand.
How very unprofessional of me. FYI I dj at events of all kinds.
Hello again, but I don’t understand the users who were asking for that option… weren’t 1 BEAT and 4 BEAT already in the “BEAT Sync Interval” configuration?
Why the change? I used to mix with Serato and didn’t use the SYNC options because this option bothered me a lot in other software, because I couldn’t enter exactly the “time”, “beat”, “rhythm”, “bar”, “measure”, It’s one thing to see that the BEAT matches on the screen, but another very different and real thing is that, by ear, the BEAT falls somewhere else.
so I switched to Djay, a versatile software… it would be my second year with this magnificent software… I trust their work a lot, but they should give the option to keep both options. Thank you for your time.
Hi again @LuisCervants, I’m not sure of the specific details behind the change, but the team is already looking into making some further adjustments here. I will also pass on your additional comments. Thanks!
NOTE: Please use the search function above before posting to avoid creating duplicate topics.
iPad 10
macbook air 2020
djay 5.3.2
As of this new update 5.3.2,
I cannot synchronize to 1 BEAT as in previous versions.
Let me explain: in this image I have marked with a HOT CUE every 4 MEASURES or 16 BEATS, djay correctly identified the TIME. When mixing with another track the SYNC function will do its job.
Okay, now. The music will not always be square (as I call it) it will not always make a change of PHRASES at 16 BEATS or 8 BEATS, sometimes for dynamics in a drum roll it will enter half MEASURE before starting again the PHRASE of 16 BEATS.
Then Djay will not interpret these small changes and will think that all the music keeps the constant rhythm of 16 BEATS.
This is where the “BEAT SYNC INTERVAL” option came in, to be able to mix correctly in TIME, you could sync to 1 BEAT and those who wanted to could sync to 4 BEATS.
As in the image, the same song, minutes later, when trying to mix here the correct thing to do is to start the first BEAT of the other song, where the green arrow indicates. And not where Djay marked the Bar 85, because if I do that, it will produce the horse gallop effect, that two tracks are synchronized but the Kick of them sounds one after the other, how a delay
Now 1 BEAT does not work and is automatically magnetized to the bar marked by djay
Please fix that bug and really, thank you for being a great software that listens to its users.
Hi @Lacoda, I’ve merged your new topic with this existing one. Our team is aware of this. Please see above for more details. Thanks!
Hi @Lacoda and @LuisCervants, this should now be addressed in the latest 5.3.3 release. Thanks!
