Smaller updates and root folder copying

saradis

It is so great that the team addresses critical bugs and issues as fast as they can, but I can't help to think that people with large collections dread installing small incremental updates because of the time it will take to copy stripes and transients to a new folder, and less experienced users probably have their hard drives swamped with Traktor root folders from previous updates. I'm pretty sure people hold off updating the smaller ones because "they'll wait for a big one".In such small updates maybe the root folder should stay the same? For example, both 4.0.1 and 4.0.2 could function from the same folder. When I'm bored or don't have time to wait for copying, and when I see in the log that it's just small bugfixes, I just rename the folder to the new version before opening, and everything works fine. Maybe the program should do that on it's own, and smaller updates could run from the same folder, like 4.1.1 and 4.1.7 from a "Traktor 4.1" folder?

lord-carlos

Yes, it's probably from a time with rare but larger updates.

Also all the backups that never get cleaned up.

Heisenberg

I have 26,000 songs and only one cheap SN570 SSD, copying only takes a minute or two.

I also clean up the old folder after the update was successful.

Well, I don't see any problem as devices are so fast these days and storage is so cheap.

For me the most annoying thing is backing up thousands of tiny files to my next cloud, it takes the longest but luckily it can be done in the background.

If you would rather have many fixes at once, you can simply update every second or third time; there are no forced updates.

maniacintosh81

I am glad that it is that way: Even if 4.0.2 maybe contains a critical bug (which may even damages that files); I still have a fully working installation of 4.0.1 and can play on with almost no effort to recover. The copying of that files is really quick for me. Maybe my library is just to small.

But what would be a great idea that Traktor tidies up after some updates (or at least offers to do so).

saradis

4.0.1 and can play on with almost no effort to recover

That would still be the case since they would both be able to run from the 4.0 folder which after all contains mostly stuff about the songs and just a small file for settings which could be different, but still in the same folder. The app/exe files do would not get overwritten since they reside elsewhere.

Well, I don't see any problem as devices are so fast these days and storage is so cheap

Well, you're obviously not a macbook user, because storage is not upgradable, and the price jump for bigger models is not miniscule, so having 20 folders of 10gb each is not very savvy. And as for the time it takes to copy or in your case upload, it doesn't matter if it is two minutes or two hours, it's completely unnecessary to have multiple copies of thousands of stripes and transient files that definitely don't change when you switch versions

Heisenberg

But that's your problem, if you keep twenty versions, why do you do that?

It is enough if you keep the last working version...

saradis

Yeah, I don't even keep the previous version if everything works after a week. I don't even let the program create a new folder most times. Or I just move the Stripes, Transients and Covers folders and the nml file after opening the new version with a blank database, which takes just a few seconds.

IT WAS A SUGGESTION for the developers, because most programs nowdays do the backup housekeeping on their own and are more practical and time/space efficient with updates, and from my experience from helping out dozens of other djs, most of them don't have the slightest clue about the root folder, what it contains, why their hard drive fills up, and lots of other stuff. I was not looking for a solution, I was just sharing my thought that the update procedure has some unnecessary steps.Also, everyone would benefit from seperating the music stuff from the settings.

Let's say you install 4.0.2 today, add 50 new songs to your playlists, and you go to work tomorrow and something isn't right. Of course you go back to 4.0.1. Why go through playlisting again since there really is NO NEED for that, because even in large version jumps, the nml structure and the analysis files don't change.

lord-carlos

https://community.native-instruments.com/discussion/comment/170987#Comment_170987

He also has the knowhow to rename the folder so Traktor does not have to copy it.

Tons of people also have the knowledge how to beatmatch, yet there is sync.

It's an easy of use feature request.