Why is Traktor Pro 3.7 iso slowly by storing the collection?
Answers
-
20 seconds are 3 times less than a minute and 6 times less than 2 minutes... i think your nerves will be fine! 😂
...btw, i also get nervous if some things take longer than was expected, but alas, patience is the doorstep to wisdom! 😉
0 -
Age is already beginning to mellow my perception of time. 😉
...
Next to 'Flag, Quote, Insightful, Like', there really should be a 'Smile' option, don't you think? 🦋
2 -
Maybe not a bug, but a remarkable performance difference. I used both 3.5.3 and 3.8 with the same library and the difference is 4 seconds (3.5.3) vs 30 seconds (3.8).
On the same laptop with the same settings.
I only use 3.5.3 when I play in front of a crowd. There has never been a performance problem or a bug with this version on my laptop. If there ever will be one, I can shut down and restart in 8 seconds.
1 -
It's at least interesting why such a basic function works so differently between Version 3.5.3 and later ones.
0 -
indeed....
i suspect that this delay is because of those integrated stupid services (beatport etc), i can't see any other logical explanation...
they might be fun and convenience for a newbie or an average user but for a pro DJ are an unnecessary burden... 😠
1 -
People who have this problem, have you tried comparing your collection.nml between 3.5 and a version where it takes tens of minutes?
Both size but also content if there is something standing out.
0 -
I totally agree!
1 -
Well, with 10.000 tracks, I can't tell if there is anything extraordinary in it, but in General I can say I have mp3, wave and m4a data in it.
The Support suggested to me to set up a new collection and to re-build it step-by-step to find a possible cause.
Tbh: that will take so long, I will stick to 3.5.3. as long as it runs stable with my Windows.
But as I "only" have a 30 secs delay, that's maybe different for me compared to those 10+ Minutes guys...
0 -
I'm talking about the .nml file itself. The size in MB. Compare one form 3.5 to one form 3.7
In the back of my head some people had trouble with slightly corrupt / verbose xml that made Traktor behave in unexpected ways.
0 -
The size of the .nml file it has to do with how big your collection is, and it is the same size, regardless the version you use.
0 -
That is 100% correct, very observant of you. It should be the case.
In this thread we are trying to find out an anomaly with some specific user. That's why I asked people who have this problem to check, else I could have checked my self.
1 -
Anyone found anything about the problem of the slow storing of the collection since 3.6x so far? Or got any hint from anywhere how this can be fixed (such as from the support)?
0
Categories
- All Categories
- 18 Welcome
- 952 Hangout
- 56 NI News
- 472 Tech Talks
- 2.5K Native Access
- 11.1K Komplete
- 1.3K Komplete General
- 3K Komplete Kontrol
- 4K Kontakt
- 846 Reaktor
- 299 Battery 4
- 616 Guitar Rig & FX
- 325 Massive X & Synths
- 765 Other Software & Hardware
- 4.1K Maschine
- 4.8K Traktor
- 4.8K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators