It would be interesting to have some memory cues for a song in a playlist and other different memory cues for the same song but in another playlist. All this without having to "duplicate" the song.
Rekordbox could ask if you want to import the current hot/memory cues when you drag and drop a song from your collection or from a playlist to another playlist. If not, the song would appear in the playlist without any memory/hot cues but those would be kept in the song at the collection or initial playlist, and viceversa.
Il post è chiuso ai commenti.
I know of one other user who has requested this, and it may have been you if this isn't the first time you've asked, but I can't really figure out why you would want to have that when you already have the ability to store 16 hot cues and 10 memory points on a track as it is...?
I am another requesting this feature. Sometimes some tracks need to be transitioned in a specific way that doesn't work with other tracks and having many ques just makes it confusing since I would have to guess which CUE is the one I wanted to use in that specific playlist. This is definitely a feature to have to keep cues clean and separate between playlists.
Exactly. It is terribly confusing to manage all those cue points for different transitions. Definitely, different cue points for the same song in different playlists would be the solution.
Exactly. It is terribly confusing to manage all those cue points for different transitions. Definitely, different cue points for the same song in different playlists would be the solution.
I know what you mean. It sucks to have to go back in playlists and replay them for the next events to make sure they line up again. I'm on a DDJ-400 so dont have the luxury of a 3rd deck to redo the cue before the next track starts.
I came here to request the exact same thing. I use both memory cues and hot cues as visual indicators where the best mix in/out points are. And that varies per set/playlist. Now I have to manually reposition them for every gig and that takes me hours on large sets. It's a huge waste of time, not to mention if I forget a track, I get wrong info during a set.
This is how I use Hot Cues for example:
Hot Cue A - Start point for the track (everything before Hot Cue A should be skipped). Also, sometimes you don't want to start mixing on the downbeat. That first hot cue shows me that. The first memory cue is always set on this hot cue so when a track is loaded, the needle is automatically positioned at this cue point.
Hot Cue B - Transition point (best point to switch from bass line on playing track, to bass line on new track)
Hot Cue D - Mix in point (where I should start mixing in the next track)
Hot Cue H - Kill point. If set, point where the track should be completely mixed out.
I use memory cues in a similar way.
There are many advantages of setting up your cue points this way. When a track is loaded, I only have to look at the hot cue buttons to see how the track should be mixed in and out. It also gives me a visual clue how to set the EQ knobs before mixing in the track. And like I said, this varies per set/playlist. If I would simply use more hot cues, I would lose all overview.
This is a really good idea. Creative mixing means using tracks in different ways depending on the transition meaning the drops are totally different. You can scatter memory cues at different sections and count back or forward, but having memory cues just for specific drops on specific transitions depending on track order would be a very useful tool in Rekordbox.
EDIT: Forget this post and skip to my next post. The solution given below is way too complicated. The solution in my next post is much, much simpler and will work on any player.
I do understand this brings some potential problems. For instance, as it is now, if you edit the hot/memory cues of a track, it changes in every playlist. Sometimes this is preferable. So if this feature is implemented, how would you go about handling changing cue points?
My idea is that there is a global database where cues etc are stored (as it is now). But when a new playlist is created, a local (to the playlist) empty database is created as well. For each track (in a playlist), you can choose which database to use. The global or local database. By default it's set to use the global database.
But you can only toggle this in the Rekordbox software, not on the player. This has quite a few advantages. On the player's side this simplifies the changes needed to be made to the firmware. All the player has to do is (when a track is loaded) make a choice from which database it needs to load the cue points. But no matter from which database they are loaded, every change you make during a performance will always be stored in the playlist's database. So if you change a cue point mid performance, and the track was originally set to use the global database, a new record in the local database will be created and the new/edited cue points will be stored there. It will also switch the track to use the local database from now on as well (if it wasn't, and of course for this playlist only).
So if you are preparing a new set and you are copying a track from another playlist, it will also copy the track's database choice and record from the playlist's database (if the track was set to use the local database) from that specific playlist. But changes you make to the cue points will again only be applied to the current playlist.
You do have to be aware that on players that don't have this feature (yet), that those will always load the cue points from the global database which might not be the ones you want.
Brilliant approach from the user´s perspective but also the programmer´s. I hope they seriously consider it.
Come to think of it, my earlier solution might actually be unnecessary complicated. In fact, there's a method that will work on all players without needing a firmware upgrade. A change in the Rekordbox software is, of course, inevitable. So the new idea is this:
First of all, I have no idea what Rekordbox's database structure is. But I'm pretty sure when a track is added to the database, it is assigned a unique identifier. This identifier is then used to link the physical file (the mp3) on the storage device (be it the local hard drive, or a USB stick) to the track's other information (like waveform, hot cues, memory cues, play count, etc.). So all the software has to do is to allow multiple identifiers all pointing to the same physical file. And, that's it really. So in Rekordbox, all you have to do is copy over a track to a new playlist as you always do, then right click the track, then choose (for example) "Make Unique". This will create a new record in the database with its own unique identifier but pointing to the same physical file.
I'm a software engineer myself and I know this isn't very difficult to implement.
Hope they will here it :)