Filed Common mistakes in saving collection state

I have a big request to make an autosave of the collection, now the collection is working very unreliably, I constantly double-check so that the tracks are not deleted, I'm not talking about dozens of times, when Traktor did not save the library state.
I got into the habit of saving the state of the library with hotkeys while working on the tracks, but sometimes there are situations when the traktor is closed due to an error and I have not saved the state of the library.

To make it easier to understand my indignation, when I used rekordbox, and there, saving occurs after each change in the library, or several times a minute, so for the year that I used the rekordbox, I always knew that the rekordbox library and autosave are very reliable

The lack of autosave leads to the fact that if the traktor is closed due to an error, then the DJ lost all the work that he was doing before, and if we take into account that I do not restart the laptop for months, then I do not tend to close programs at all.
If in the settings is set to save the tag data to a file, in most cases this causes an error in the traktor when closing, and it does not save anything again
I have lost work on the library dozens of times already, and unfortunately I cannot trust Traktor to handle the entire collection.

I heard the version that you are not doing autosave, because it is related to the load on the browser, then I suggest doing a smart save.
Save the library once a minute, while editing tags or hot cues, after the last autosave, if no action has been taken with the library, do not autosave, so as not to load the Traktor and the system. Then, if the DJ has edited any field, autosave turns on again and saves once a minute, then stops again.

Thanks,
Pavel

 

This sounds like a feature request, not a bug report.

And yes, the reason there's no autosave currently is because Traktor has to write the entire collection.nml, which can take quite a while, during which time the entire application is locked.

Traktor DJ 2 does have a modern database and does save changes instantly, but I doubt this feature will make it to Traktor Pro.

 

in this case, as I suggested at the end, smart save that turns on for a while would be a good way as it seems to me. I could switch to DJ2, but as far as can be seen, it does not develop particularly

 

By the way, why do you say that it saves the library for a very long time, it saves my 500 songs in 1 second

 

Some people have tens of thousands of songs in their library. Don't ask me why.

 

Yes, I have more than 15 thousand tracks, and saving the collection takes a lot of time.
If you make AutoSave, it should be in the background and not suspend the functionality.
A couple of workarounds:
1) Close Traktor every time after the event. In addition to saving, this will give you correct auto-playlists in the History Archive. Traktor Pro is not a program that you can live with just by closing your laptop's lead every day.
2) I made cmd+S keyboard shortcut to save the Collection and use this every time I made significant changes.
3) The absence of AutoSave can be used with advantage. For example, when you need to work on an event from which you do not want to save the created playlists and do not want the "Last Played" and "Played Count" marks to apply on the played tracks. Just kill the Traktor after work.

 

should workarounds wven be a thing or should there not be a smartsave or any type of built-in save feature. If thay cant do that then they have no business with selling us this cleary broken program. With how much their stuff is, the lack of care they show towards the users is appaling.

so much lost work and time due the bad design and many overlooked features. Whoever coordinated and oversaw the completion of Traktor 3 should be ashamed they made and sold us on this software version of a hot garbage bag on a summer street.

 

So they care more for their niche app than their proper software. Seems about standard for them.

 

Hey everyone, we appreciate your feedback and have already added an autosave feature to our list for future consideration. In the meantime as radiokrishna mentioned, I would recommend to make a save collection mapping which you manually trigger at any time. This has saved me from losing my work dozens of times.