Saving Traktor collection

Luka3

What is traktor doing every time you close the application?

I have a very large database of files and when closing the application with traktor 3, it takes 20 minutes or more to close the application while waiting for "storing collection".

I downloaded a trial version of traktor 4 to see if this behaviour has improved and to my surprise it now eadily takes 12 hours or more to do the same.

I'm editing nothing. Just open T4 and close it again and I have to wait the whole day for it to finish 'storing collection'.

ilove1981

There is something wrong here. How many tracks do you have in your collection and what spec is your computer?

lord-carlos

Are the files on an external disk?

Oxy

Same here. Been complaining about this issue a while now. I'm on the latest version of 4 though.

Toxicaudio

Had similar issues with closing Traktor. It tooks very long to shut down.

Then I realized that some tracks which were stored as a copy/backup on my NAS, are also in my tracklist. One track with storage path C:\xxx…. and others with storage path N:\xxx…..

After deleting all files with N:\xxx… from my collection it works like a charme. I don't think it's a bug. Are you using external Drives? Maybe it would be helpful to post a pic from your file management settings in Traktor.

Oxy

"Network storage", Yes, all my tracks are on my server. Why is this a problem? This problem started somewhere in the later stage of Traktor 3.

Unknown

This content has been removed.

lord-carlos

Someone else mentioned in another thread that Traktor started accessing / touching every single file in the collection on close. And I assume a network / USB connection can't deal with those small ~random~ access fast enough.

But that is just what one community member could dig up.

The silence from Traktor devs are deafening.

Luka3

My tracks are also on network storage but I'm not changing anything. Just opening traktor and closing it again. Nothing should need checking or updating and if it does need updating, it should only update that which has changed. Instead it takes forever just to close the program. My files are on a NAS and mapped as a network drive on my pc. File access is not as fast as the local SSD drive but again, I'm not changing anything, just opening and closing. I also use an open source app called Mixxx and this too has the whole collection indexed and available and guess what, takes seconds to both start and close the app.

Luka3

@ilove1981 core i9, 64Gb RAM, RTX 3060 GPU but when closing traktor the cpu is as good as idle so I doubt this is a performance issue. Collection is huge though, 10s of thousands of files.

@lord-carlos files are on a NAS

@toxicaudio that is interesting but moving my files to a single local disc is not an option for me, neither is keeping copies in 2 places. They are on a NAS for good reason.

@lord-carlos if that is true then it sounds like they want to make it slow by design. Which database does a full DB check every time a file is touched? (or in this case even when nothing is touched at all)

Since they seem to have made it worse in T4, I think I'll save the money for the upgrade and stick to T3 for now (or switch to mixxx al together). Shame on you Native Instruments.

Oxy

https://community.native-instruments.com/discussion/comment/192501#Comment_192501

Yes, I have brought this up on multiple occasions and even once had a dev interaction, when I was asked how big my "colection.nml" is. You where there too Carlos.

Even if you open Traktor, do NOTHING, close it, it starts it's (for me) 20 minutes saving cycle. Again, this behaviour started somewhere in the late cycle of Traktor 3. My work flow has been the same since I'm using Traktor since 2018.

What I typically do now when I'm done playing, close the laptop lid, it goes in stand-by and the next morning resume the session and close Traktor properly to save any changes made.

ilove1981

I currently have 58,453 tracks in my collection running 4.1.0 and it takes 19 seconds to close on my 2019 MacBook Pro 2.4GHz i9/32Gb if I haven't done anything (no tracks loaded, nothing played). It's barely any longer after a 4-5 hour gig. All of my music is on my local drive though, so not external and certainly not on a NAS. We can debate the rights and wrongs of accessing all files on closure, but may I ask, why do you have files on a NAS? Presumably this is not accessible if you are away from home?

Toxicaudio

Maybe they want to have access to their music collection with different devices at home. I would recommend to keep your music files/collection on your internal HDD or an high speed external hard drive and use the NAS only for backups.

Luka3

@ilove1981 I use traktor mainly at home for fun. I'm not a DJ that goes on gigs so having it on the NAS makes the most sense, also because as @Toxicaudio mentioned, it allows me to access my collection from different devices (eg my nvidia shield running kodi). My collection is 750GB. I'll copy it over for fun and see what happens but if this takes seconds and the other takes +12 hours then this is not simply a matter of it being on the network if you ask me.

Toxicaudio

@Luka3 have you (and all the other users) raised a ticket? Did you get an answer?

I can understand your frustration and it is obvious that we cannot help you with this problem.

lord-carlos

Also it used to work. Traktor devs made some changes. Maybe it is an bug, why would Traktor need to touch every file on close?

Kinda fed up with no public response from Traktor devs 🤮 Just say something .. anything. Is it a known bug? Does it work as intended? Do you need help reproducing it? Currently we are just in limbo.

it allows me to access my collection from different devices (eg my nvidia shield running kodi)

I sync my collection from laptop to server with rsync.