Exporting Serato crates to Engine - most up to date meta

Hi all,

I would like some clarity on the topic of exporting my Serato crates into Engine DJ.

I am primarily a Serato DJ Pro user (with a Rane Performer) but I have a Numark Mixstream Pro Go that I take with me as my backup. It’s a perfect little unit as it not only has Engine baked in but is also compatible with Serato.

I do all of my prep in Serato for a gig and before the gig kicks off will open Engine DJ and export my Serato crates for the gig into Engine. What I am finding is that if I have a track that is already in Engine (e.g. is not a brand new track import from my Serato crate(s)), any existing cue points and loops will NOT be overwritten by the Serato crate import. E.g. if I have added some new cue points to a track that exists both in my Serato and Engine Libraries, the existing Engine library cues will remain and I won’t have any new ones that I worked on in Serato.

Is there a way to tell Engine to overwrite cues and loops etc. from each Serato import of an existing track sitting in Engine?

I’m also finding the same thing for comments I make in Serato (I use a lot of functional tags in Serato to get to tracks quickly during gigs).

Cheers!

1 Like

Hi, the import feature in Engine was only ever designed as an initial load for people looking to move into the eco-system, not a way of updating your library form other software.

In order to achieve what you want, you’ll either have to empty and re-load your whole library, purchase some 3rd party software to sync it or manage your collection in Engine only.

Thanks for your reply! Yeah figured that might be the case. I could potentially use Lexicon as a middle man perhaps. Cheers!

1 Like

I use Serato as my main Library.

Workaround is to delete the engine library folder or as you guessed Lexicon

An other option is not to spend money on an other software but use MIXXX

I have as well a Numark Mixstream Pro and a Go that I use in combination with MIXXX Mixxx can export to Engine OS including hotcues / loops etc.

I don’t use Serato personally but I can see that Mixxx can access the Serato library

So you can give it a try to see if Mixxx also can read the track meta data as well.

The workflow for you would than be (if you don’t want to leave Serato) to accees the library in Mixxx and next before the gig you create a CRATE in MIXXX, to export to Engine OS.

Option 2 is that you abandon Serato and switch over to MIXXX completely as audio management system and live performance software.