NML doesn't want to import

decat shared this question 2 months ago
Answered

Hi,


Just received the beta to test, thanks!

Doesn't go well at the moment. When importing the NML it says that some tracks (all of them) cannot be imported because too large, corrupt or...

I enabled logging but couldn't find something useful or readable.

Comments (11)

photo
1

Almost 50 gb of RAM & swap?

photo
1

Hey


How many tracks are in the NML you're importing and what file type?

Try importing around 50 tracks directly to MIXO:

https://support.mixo.dj/guide/import-songs-mp3-etc

When was the RAM usage going that high?

Please send the computer specs that it's happening on.

photo
1

The NML contains about 4000 tracks. I succeeded importing them as mp3 and did it per 1000 orso.

Size of library is about 140gb, 30% MP3 & 70% AIFF. The RAM usage went bonkers while trying to import the whole music folder as tracks.


My system is an 9700k with 16gb of RAM running Windows & Mojave each on it's own NVME drive. Mostly used in MacOS.

With the strange behaviour I tried installing the app in WIndows 10. Got some Java errors & couldn't do much. I think it's related to the music folder not being on it's usual/default location. In MacOS I noticed that the app created a folder in default Music folder. On Windows I moved that one to a third mechanical drive. If it's related it would be a good idea to let the user choose this folder while installing.


While typing the folder problem above it came to my mind that the NML file is not on it's usual location either but on a third NVME drive. The music & Traktor folder on that drive are synced between this system, an older iMac and a NAS. The filepaths on the two MacOS'es are the same so I can use / change on one system, sync and later continue or use on the other

photo
1

That's really useful info, thanks.

I've created an idea to choose the default folder and subscribed you:

https://support.mixo.dj/t/choose-default-music-folder-on-installation

How big are each of the AIFF files?

Importing a large amount of those could be what's causing the large RAM usage.

Can you try importing around 20 of your AIFF files and let us know how that affects RAM.

The location of the NML file or the music shouldn't have an effect, as long as MIXO has access to that music it will be able to play it locally.

photo
1

Sorry for the delay.

Those tracks are between 50 to 150 mb. Importing around 20 of them doesn't affect RAM much.

Importing a batch of 200 tracks mixed aiff & mp3 does. RAM & swap went up to about 15 gb.


btw: my nml error seems to be the same as josegfv mentioned.

photo
1

Hey

We've just released an update to fix this!

Make sure that check for updates is switched on in settings:

/866428249d6f098312d793b48ef04832

You'll get a prompt to download and install the update in the app, this may take a few minutes.


Let us know if you get the same problem after the update.

photo
1

Yes, installed it last night but after the import I did.

What I did notice is when enabling the 'check for updates' switch last night it was switched off again moments later.

Now in 0.3 it's still on.


Will do some more testing in the next couple of days.

photo
1

Hi Decat, we're currently on 0.9.0, how has the app been working for you? Have you had any further issues with your NML files?

photo
1

Well, didn't use the app till today because didn't had the necessary cloud storage.

Got a 1TB OneDrive account but it's not supported yet. Yesterday my mate gave me a Google Drive account from the school where he works. I picked up today. Sync doesn't seem to sync anymore, it did some tracks though. Analysis queue seems to hang to. Will have to catch up reading the support page to check what it could be.

photo
1

No problem!

Try a couple of things:

1. Make sure MIXO is up-to-date (0.9.0)


2. Reset Mixo by going to Settings > Debug > Reset MIXO and then clear the cache as well - this may whitescreen in which case just close the app and reopen. Then try syncing again.

3. Try reinstalling the app

We are aware of some issues with syncing large libraries, sometimes they can hang for quite a while or fail, so you can also try adding smaller libraries. We are working on this.


Let me know how you get on!

Thanks decat!

photo
photo
1

Hola, apenas voy a importar mi ¨coleccion¨ de Traktor DJ, pero creo tardara mas de 1 dia, lleva casi 6 horas importando 9978 archivos MP3 y contando, entiendo que es mucha la colleccion que tengo en mi disco duro, pero tardo menos el MIXED IN KEY en importar y analizar, lo que quiero tratar es exportar mis ¨cue¨ a la coleccion en Recordbox, queria importar el XML de Virtual Dj pero me dio error al cargar xml. (virtual) esperare a tratar de hacer la exportacion del xml a Recordbox.

photo
1

Thanks for the feedback!

We are looking into improving the performance of large libraries:

https://support.mixo.dj/t/importing-large-libraries

I've subscribed you to the idea.

photo
photo
1

Tried the app a couple of times but had to give up. Constant crashes, not possible to import, even when it's small batch of tracks.

Removed and reinstalled the app but no luck. And it's sluggish. My system is quite performant (9700k, 16gb ram, NVME drives)


Just removed 0,9 and installed 0,10 = same, constant crashes.


My mate tried the app too last weekend, same stuff. Really sluggish performance and constant crashes.

If in the future you want people to pay for this you gotta make it alot better.

photo
1

It just crashed, tried to reopen the app and it asks to log in again.

When entering the credentials it says the user is already logged in.

photo
1

Hi Decat, sorry for the issues you're having, we are currently prioritising CPU and RAM optimisation and will hopefully have an update for this in the coming weeks!

For the 'user is already logged in error', try resetting your password:

https://go.mixo.dj/sso/request-reset-password/

Could you send us a full spec list of your setup? I agree that it shouldn't be crashing like that on your system based on what you've said so it would be interesting to see. Does it crash when you just add one track for example?


Please know that we really appreciate all the feedback, it helps us massively!

photo
1

I'm running:


9700k

16 GB RAM

Gigabyte Z390 Aorus Master

Samsung EVO 970 NVME with MacOS / Mojave / main use

Samsung EVO 960 NVME with Windows

Crucial P1 NVME with music

RX580

Just resetted the password, removed the app by using appcleaner and rebooter.

Reinstalled 0.10. / tried 1 track = ok, tried 10 tracks = ok, tried 20 tracks = ok, tried 50 tracks = ok, tried 100 tracks = ok.

System seems to be handling the work much better than before. With the previous versions cpu temp rose up to 70° & fans started spinning like mad.

Now temps jump between idle = 32° & around 50°.


The temps really jump from 30>50>30>60>30>60. Feels like the app is being throtlled orso?

CPU voltage is constantly jumping between 0,7 & 1,3. like ping pong

photo
2

Thank you Decat! I'm going to send this over to our developers and I'm pleased that importing works to a degree - although obviously we want this to be a lot higher for you!


We have also noticed the jumping around and high usage of CPU and temperature and it's also a part of our testing.


I've added you to this idea, so you'll get an update once this is completed -


https://support.mixo.dj/t/multithreaded-tasks

photo
1

I cant import my traktor collection

all time mixo chrashes


i have a master race pc

photo
1

To help us, could you follow this guide to turn on logs and then import again to repeat the error

https://support.mixo.dj/guide/how-to-turn-on-logs

Then go to: Music > MIXO > Logs - and send us the files there.

photo
photo
1

I've tried a batch of 300 tracks and they got imported. Seconds ago I dropped a 600 track dump and it was succesful too.

0.10 seems to be workable.

With the previous versions I also noticed nvme reads around 1,2 Gbit. In 0.10 the reads seem to hang around the 200 Mbit mark. Not meaning higher speeds are needed for me.