NML doesn't want to import
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.
The same question 
Almost 50 gb of RAM & swap?
Almost 50 gb of RAM & swap?
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.
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.
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
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
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.
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.
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.
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.
Hey
We've just released an update to fix this!
Make sure that check for updates is switched on in settings:
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.
Hey
We've just released an update to fix this!
Make sure that check for updates is switched on in settings:
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Replies have been locked on this page!