As I explained earlier on Reddit (but clearly you don’t believe me) It’s not possible. This “cue” point is separate to the hotcues and is set with shift+cue.
I can’t find a way for hotcue 1 to be respected when the track is loaded.
I know it’s weird, I’m a VDJ user and it makes no sense to me either.
This is a temporary cue point. You set it by pressing the ‘CUE’ button (next to the play button). You can set this anywhere in a track and will be respected as a load point, even if you unload the track.
@Homeland101 figured I would try multiple forums I appreciate your reply!
@djliquidice@Homeland101 I think the setting that confuses me is the option to load at the start of the track vs. the first ‘cue’ point. If EngineDJ adds a ‘cue’ point at the start of each track, then these settings should do the same thing right?
Well, if the Cue point is at the start of the track and you don’t move it then yes, it’s the same. However, it’s a common practice to place the Cue point just where you want the playhead to be when you load the track, so in that case it’s not the same, because you set the Cue point at any position, and when you load a track, it will load with the playhead at that Cue position, instead of the start of the track (if you enabled the setting for this).
The thing that confuses me with Engine though is that in VDJ you can set the track to load at hotcue 1 and that’s it. No temporary cue set by the software, it just goes to hotcue 1 every time. If no cue is set it goes to the very start of the track.
As I’ve reported several times Engine scanning is not very accurate and that temporary cue can be anywhere, rather than the start of the track (or the first beat for that matter). Sometimes it’s early and sometimes it’s late.
Another thing is that you can enable a loop, play from the temp cue and the loop invokes. If you do the same from a hot cue then the loop is cancelled.
I’ve never worked this out too. I didn’t initially think that it is a bug but more of an inconsistency but the more I think about it, the more I’m starting to think that it could be a bug.
I’m new to EngineDJ so I’m curious on how you would approach it given these funky product quirks.
I am trying to optimize for speed in getting the incoming track to start at my first hot cue point.
With my workflow starting in rekordbox and then exporting to a USB to plug into Denon:
Would you suggest manually setting the ‘Cue’ point to my first hot cue for every track, or, would you simply hit the first hot cue every time you load a track? Or, would you suggest something else?
With the first solution, I’m afraid that the system will not remember me setting the ‘Cue’ point for each song.
If you have used Rekordbox, the menu option that allows you to select that when you load a song, the cue is placed by default in the first Hot Cue, is not available in Denon.
Currently it allows you to set it to the start of the song or to the last cue position, the last time you adjusted it.
As Mufasa says, there is a feature request to vote for.
I have gotten used to when I load a song, I manually press hot cue 1 and then the cue to start playback from there… it is a little more uncomfortable than with the Rekordbox option, but it works the same.
This behavior bugs me as well, I always start from the 1st Hot Cue, hence that temporary Cue point is of no use for me in that case. Voted in that linked topic.
You will find there’s a lot of things that don’t make sense in the engine DJ world. Not sure if the developers just didn’t take the time to work these things out, or they are just depending on the users to request it. My vote is always mimic what rekordbox has done, not sure why they would do anything differently as rekordbox has taken the time to figure out what makes the most sense for djs. Been dealing with little irritating things like this in the software since I changed to engine in 2020, still waiting for streaming services to be sortable and viewable in the software. Wish they would just focus on optimizing workflow over everything. They always make ways for things to work in some way but it’s usually a roundabout ass backwards way. Like “just go set the cue for every single track” when you have already taken the time to set your cues. How about developers fix it on your end and not pass all the tedious work on to our users.
I appreciate your reply!