Mixo 1.75.0 export to Engine DJ 4.0.1 does NOTHING

The smaller part was imported from Rekordbox, the larger part directly into MIXO. The majority of tracks has been analyzed by MIXO and all tracks are working. I've tried exporting to DJXML but I simply get an "Export Failed". The logs do not mention any errors.

I do like the app and its functionality and would be ready to send you 7$ per month but as things are, it does not inspire me the confidence that my collection would be in reliable hands.

Ok sounds like there's an issue in your library.

Please try Settings/Tools/Bad Track Remover and click "Remove Blank Entries In Playlists", then refresh the page click "Check For Bad Tracks". Then try exporting again... maybe this will help?

Failing that, you could try reverse sorting All Tracks via the FilePath column (you need to right-click to add this column) to see if you notice any strange looking tracks in your library.

Remko
MIXO team

I would like to do that but now MIXO is not even letting me log in anymore. I will not tell you how I feel about this.

Here is what I did:

• booted into my Linux where I had originally set up MIXO and uploaded the first 20 tracks
• started MIXO which synchronized fine with the 38,000 tracks I had added on Windows
• removed the 20 tracks that had been missing on Windows to hopefully solve the issue
• booted back into Windows where, since then, I cannot log in anymore, even after re-installing MIXO. I'm logged in in the browser but when I click on "Open MIXO", I go back to the app and the "Waiting for browser" notification simply disappears. When I try logging in with a key, MIXO tells me the key is not valid.

Please logout in the browser first, then restart MIXO and login again. It should work.

Remko
MIXO team

I had tried this already. The problem was that coming back from Linux, the clock was two hours behind. An informative error message would have been useful.

I can now confirm that the problem persists

• without the proviso that a few tracks hadn't been downloaded
• after removing (2) blank entries from playlists
• after checking for bad tracks (of which there were none)

I checked the filepaths and found no strange-looking tracks (whatever that means).

I had tried the DJXML export and it had given me the same unspecified error. However, I re-tried right now and this time it worked! Engine DJ export still not creating any files, however.

P.S.: For matters of completeness I've tried the other exports. Here's the outcome (NO = nothing happened despite the "Export complete" message)

• Playlists YES
• Rekordbox YES
• TRAKTOR YES
• Serato NO
• VirtualDJ YES
• iTunes YES
• Engine DJ NO
  
• DJXML YES
  

Can you please send me your Rekordbox XML so I can try to figure out what's different with your partition vs mine.

Thanks!

Remko
MIXO team

This is the one exported by MIXO.

Additional information: I've installed MIXO on another Windows computer and synchronized the database without downloading any tracks. This time, the warning said (obviously) that none of the tracks has been downloaded yet. This time, the m.db file was modified but only the names of the playlists were exported, no tracks.

Ok I imported your XML and exported it Engine without issues. By design no tracks were exported either, because tracks are saved to the database relative to the track's path.

I then used the Find & replace Tool to change D:\ paths to my local drive and exported again. Now Engine Dj shows everything, including tracks!

This shows that for some reason MIXO cannot find your partitioned drive. Whereas for me it finds the portioned drive without any issues and everything worked.

This type of incident (where it works for some but not for others) is always environment related. In your case it's probably a permissions issue of some kind but I'm not sure how to debug that!

If you have any ideas, that would be great! Presumably you'd have to grant MIXO permission to access files on that drive?

Remko
MIXO team

I can see that it's difficult to debug this but I'm pretty certain your guesses are off the mark considering that

1. the other exports work fine and
2. MIXO is able to play all the tracks.

Also mind that I've tried on three different systems two Windows, one Linux. I think it's safe to say at this point that this is not about incorrect paths, it's not about permissions, it's some bug in the code. There must be some way to monitor what the software is doing during export? Writing some verbose debugging logs?

Also, would you mind sharing that m.db file with me?

Apologies if that didn't make sense. Let me explain the differences.

For most exports MIXO writes the file to MIXO's export folder inside the system Music folder on your local drive. This rarely fails since MIXO created the folder.

For Engine, MIXO tries to write to the (or create a new) m.db file on each drive that it finds tracks on.

So whilst reading permissions might be ok (which is why the tracks play in MIXO) write permissions to that drive/folder might be different. That was the premise of my theory and it's not uncommon.

If there was an actual error, the export would fail, whereas if it can't find the drive for a track, it just moves on to the next one. So in your case it loops through all the tracks until it completes.

To test this theory, create a new playlist and import some tracks on your other windows computer, then export to Engine. The result should be that only those tracks are exported.

You could also check that MIXO has write permission on your D drive and for the Music folder on that drive and test again.

Let me know how it goes!

I'll also see if I can build you a beta version with additional logs and arrange a zoom call to go through it with you. How does that sound?

Oh one last thing - I've extended your free trial by 1 month as a thank you for engaging. We need more people like you to help eliminate these rare anomalies!

Remko

MIXO team

I just used the Find & Replace Tool to change D: to E: (which is my partition) and then exported to Engine DJ on my Windows machine and everything worked.

Here's a brief video of the progress:

https://take.ms/3VCID

And here are the tracks:

Remko

MIXO DJ team

Wow, alright. Thanks for your dedicated, responsive, and accomodating support! That was a very important piece of information which I didn't get when you had hinted at it in an earlier post. It is a bit unintuitive that I select an export path and then files are generated in a totally different and uncontrolled location. I'm sure that's because of how Engine does things but the user needs to know (as we can see)! At least, the success message should list all the locations where files have been written. This could also be the moment to check whether the files have actually been written/modified because this is what's not happening on my system.

I've started MIXO in admin mode and checked Windows app permissions to be on the safe side here. We can safely eliminate the permission problem at this point. Also, such a problem would have raised an error, I think. So how is it that MIXO thinks it's writing data to the disk but actually isn't? I'm afraid without debugging logs we won't get any further. I'll gladly accept any of the solutions that you suggest, e.g. running a custom build.

I have an idea!

There may be some logs available - To get them, please follow these steps:

1. Open a Command Prompt window (search for cmd.exe).

2. Drag MIXO into the window (which should add the path to the app), then hit Enter. MIXO should now open.

3. Then proceed with Export Engine DJ and watch the Command Prompt window for logs.

Please send me any logs you get from the export!

Remko

MIXO DJ team

I would be doing this RN but with the new piece of information I went back to the other Windows computer, plugged in a USB key as drive D:, exported all fine (took way longer than a few seconds, obviously), copied both Engine Library folders (from C: and D:) to the main computer and voilà, now everything is there, even the smart playlists! For some reason, though, Engine DJ set itself the task to re-analyze all tracks. Was that to be expected from your side?

I think we should still do the debugging at some point to find out the cause, and also so I can actually keep using MIXO in the future, which I would like to. But first I'll let it analyze, backup everything, and play around before actually risking anything, I hope you'll understand.

Well that's good news. I just don't know why it can't find your partitioned drive!

USB drives are slow, that's also why it took a while.

Engine DJ might need to analyse but in the next release there will be a beatgrid lock option, which might speed it up:

https://www.mixo.dj/versions

Anyway, feel free to have a good play around for the next month and let me know how it goes.

Thanks!

Remko

MIXO DJ team