I have encountered a bug with hot cue color synchronization.

If I import from engine DJ with track analysis set to active, and then export again from Mixo to Engine DJ, the hotcue colors in engine DJ will be lost and become the engine DJ default ones.
However, the cue colors in Mixo stay the same.
Even if I import a second time from Engine DJ.

Only after the next export to Engine DJ it will start importing the hotcue colors from engine DJ.

Maybe some of this is intended, but it feels inconsistent.
If it is intended, I would like to request an additional button that disables synchronizing hot cue colors on import or the option to disable "track analysis" per default, because I want Mixo to be the primary source for cues.

I am running the beta 2.11.5

Hi there,

I'm not seeing that - I tested like this:

1. Imported a track with 8 default cue colours from Engine. MIXO imported the colours correctly.
2. I changed the cue colours in Engine so they were all different from the default for the slot. Imported into MIXO and again all looked fine.
3. Exported back to Engine and the cue colours remained the same. They did not revert to the default.
4. Deleted tracks in Engine, then exported from MIXO again. Same result - all cue colours were correct and not the default colours.

See attached result after export.

This happens with tracks that first were imported from Rekordbox to Mixo and then to a clean engine DJ library.
I was able to reproduce it reliably.
Maybe it has to do something with the mapping of cue colors to the restricted set of color options in Engine DJ?

That's more likely then. If you've imported custom cue colours from Rekordbox, MIXO will map them to the closest in Engine. We have a huge conversion table for all the varieties of colours imported from all the different DJ apps. They all have to be mapped into 8 colours in Engine.

I'll be happy to tweak some of the mappings if you can isolate any that don't seem right (like pink getting mapped to orange, for example).

I know that these mappings have drawbacks, but I think the behavior is still inconsistent. I think either the hot cue colors should be reset/imported directly from engine DJ when importing with track analysis, or not at all.

And right now (this is making it inconsistent), the importing creates some changes to the cues that are not visible in Mixo directly:

If you do "import from Engine (track analysis on) -> export to Engine".
Then the hot cue colors are reset in engine, but you can not see any difference in Mixo yet (for that you have to import a second time).
And then you no longer "get what you see" because the cue colors from Mixo can no longer overwrite the ones in Engine on export.
(i noticed this by accident, very confusing)

For my use case I am fine just using it without track analysis to keep the ones in Mixo, or to receive just the changes to the cues.

Track analysis is irrelevant for this because the cue points are stored in the database.

When you import from Engine, MIXO will remove all cue points for existing tracks, then import from the Engine database. So Import should always match Engine DJ.

I think what you're saying, which I can't replicate, is that when exporting to Engine DJ, sometimes the cue colours are reset to the default order (see attached default colour order).

If there any way I can try to replicate this?

Ok I've spotted 1 issue after exporting to Rekordbox then importing back into MIXO, then exporting to Engine -> cues 2,3,4 are all green. See attached before and after my mapping fix.

I am doing the following: 1. Load RB Library into Mixo with mirror mode. Tracks inherit RB cues. 2. Export to fresh Engine DJ library. 3. Import from Engine DJ without track analysis. (Current state: Cues in Mixo stay unchanged, even after multiple imports and opening Engine DJ in between). 4. Export to Engine DJ.

Oh, I've also realised the colour does in fact fall-back to the default if the cue colour in MIXO is unknown.

Please can you export a Rekordbox XML from MIXO with some tracks containing cue colours that get reverted to default in Engine, and I'll add the colour codes.

Okay, wait now the behavior changed for me. I dont think I clicked on track analysis this time, but the cues were still reset in Engine DJ after an export.

Yep, please send me the XML, I'll get the missing colours added. Or if you can tell me how to set these particular colours (eg which colours from the chart you used in Rekordbox) that would be great.

I uploaded a file with two playlists. The colors from 1€ party were mostly preserved, the ones from ein euro playlist V5 were not.

However, I am a bit confused, I could swear I could reliably replicate this behavior (at night tbf), where it would just happen if track analysis was set.

I even had tested changing just one cue on my controller, importing back to Engine and then back to Mixo, and only this one cue was updated. If you are saying it should always overwrite with all hot cue colors from Engine then there is still something fishy going on. Thanks for taking a look at it though.

Okay, sorry for the confusion, it seems like it was importing from C:/ and exporting to an engine library on D:/

All of the cue colours in your XML were included, except Engine's purple. That means any cues in that colour would get converted to the default colour for the slot which might not have been purple!

I've added that one too. So I think with my green adjustments and the addition of purple, it might work better for you. I'll send you a beta to confirm.

Here you go!

https://www.mixo.dj/download/beta-v2/MIXO-2.11.6.exe

Works fine I believe.

Would be cool though, if I could select which information I import. Im my use case I want to use the beatgrids etc. from Rekordbox, and just import any changes to ratings / cue points from Engine. Basically using Mixo as an extended Sync-Manager. Due to the bug, I initially thought it was possible. But thanks for the fix on a short notice!