What is a 'Collection' and how does it behave in Traktor Pro 4?

PhynomMusic

Traktor Pro 4

Alright, generically, I know what a collection is, but what I don't understand is what the limitations are as far as moving between computers or having multiple collections, if possible. What exactly is stored in a collection? Is the literal file or is it a link to a file on my local drive such that if I move the file, it cannot be referenced in the collection. In NI's documentation for Traktor Pro 4, it states that a collection automatically sorts your music based on metadata (that's what I gathered); however, is it possible to have multiple collections in the same workspace of the software. I am an Adobe user, and Adobe let's you build your collections based on all sort of criteria (metadata). Adobe also uses what are called catalogs to keep ALL references to content, including local content.

I guess what I am really asking for is a comprehensive understanding of collections without divulging trade secrets.

Is a collection a file?

Is it a collection set of files?

Exactly what is stored in a collection file?

Can multiple collections be created in the same software interface?

If a file's data is changed, i.e. file name or any metadata, does this change affect the collection's ability to track the file?

Does the collection's reference to the music on the local drive get scanned every time the software starts, or does it need to be commanded to rescan by the user if additional files are added?

Other than fancy sorting, why would a one use a collection? What are the benefits of using a collection?

I have currently pointed my local music folder to the collection, and it is 'analyzing' the music. I have what appears to be 8939 files (songs) in my local music folder. According to the little information bar at the bottom, it will take 1 day and 4 hours to complete.

What other information about a file is stored in the collection, for example, cue points?

And the last thing I will say will now turn into a gripe…after letting Traktor sit for a day to process all that music, I have returned to my computer only to find that Traktor Pro 4 closed itself and did not save any of the data I added yesterday. My collection now shows 182 tracks instead. 😒

lord-carlos

The collection is a XML file that gets stored in ~/Documents/Native Instruments/Traktor X.X.X/Collection.nml

It contains playlists and meta data about the tracks. And yes, I think that includes cue points.

In theory you could have multiple collection.nml files, switch them out and only load what you need. But in praxis there is no easy why to handle that from traktor.

The file gets saved and a backup created every time you close traktor. But you can also manually start this process by right clicking on the collection node in the browser.

Yes, if you move a file you have to start the "check concistency" process to "relocate" it again. Same when you update some meta data in the files. It's quick.

You don't have to analyze (finding bpm, key and creating waveform) every song you own, unless you 100% know you want to play them, but it's certainly a good idea to have them in your collection. This allows you to find the tracks in traktor, if you at some point choose to want to play them.

lord-carlos

The collection is a XML file that gets stored in ~/Documents/Native Instruments/Traktor X.X.X/Collection.nml

It contains playlists and meta data about the tracks. And yes, I think that includes cue points.

In theory you could have multiple collection.nml files, switch them out and only load what you need. But in praxis there is no easy why to handle that from traktor.

The file gets saved and a backup created every time you close traktor. But you can also manually start this process by right clicking on the collection node in the browser.

Yes, if you move a file you have to start the "check concistency" process to "relocate" it again. Same when you update some meta data in the files. It's quick.

You don't have to analyze (finding bpm, key and creating waveform) every song you own, unless you 100% know you want to play them, but it's certainly a good idea to have them in your collection. This allows you to find the tracks in traktor, if you at some point choose to want to play them.