Engine DJ is a step backward in the contextualization of our workflows and separation of our DJ use cases.
Our Collections was where we would store the music, our Playlists would be our selected tracks we “took to gigs”. The separation worked. I could have my Collection untouched, and just drag a track into a Playlist or two or three in Prime 1.6.2… and if I wanted to remove it from any of the Playlists… I could select “Remove from Playlist” and it was taken out, and the song would remain in the Collection and my other “Playlists” where it appeared- alternatively- I could just play out of crates of a sub genre… or what ever- I could either prepare- or go digging in the crate.
Now, with 2.0… they went backwards and made the “Collection Crates” behave like Playlists so we could order our Collection Crates. If you create another “Playlist” in 2.0 you are only creating another “Collection Crate” that can be ordered.
If you are thinking of upgrading, really consider if you want to lose this separation of Collection and Playlist with easier toggling in the interface, versus a long single scrolling list.
Bummer. It will now take a year + for them to sort out all the new issues.