Traktor Pro 3.8 still has flashing browser when you load tracks

Options
123457

Comments

  • PZZO
    PZZO Member Posts: 18 Helper
    Options

    Just wanted to add that I also see this issue on my laptop (cpu: i7-1065g7, ram: 16GB) when I load tracks off a USB drive that haven't been analyzed. If I pre-analyze my library and copy the files to the main drive, this isn't an issue.

    My guess it's some combination of the slow USB speeds and the way analyzed data gets written to the files that causes the browser to continuously refresh.

    Also lol at this debate of it being a "feature". If NI intentionally wants the browser to glitch out each time a track loads, then I want my money back 😅

  • T_G
    T_G Member Posts: 8 Member
    edited March 2023
    Options
    https://community.native-instruments.com/discussion/comment/59051#Comment_59051

    What you say is actually so far from reality it is in outer space.

    This is the most basic, most unoptimized code I was able to write in a short time. We are talking way below 0.1s on operations with 100k+ Tracks. In the simplest container possible. 2017 i7 CPU...

    2023-03-21 18:40:18,558 - __main__ - INFO - Parsing collection
2023-03-21 18:40:20,872 - __main__ - INFO - Parsing collection finished, Time : 2313.54 ms
2023-03-21 18:40:20,872 - __main__ - INFO - Loading collection into internal structure
2023-03-21 18:40:21,280 - __main__ - INFO - Loading collection ended, Tracks found : 102722, Time : 407.91 ms
2023-03-21 18:40:21,280 - __main__ - INFO - Sorting by Artist
2023-03-21 18:40:21,321 - __main__ - INFO - Sorting by Artist finished, Time : 41.89 ms
2023-03-21 18:40:21,321 - __main__ - INFO - Sorting by Title
2023-03-21 18:40:21,384 - __main__ - INFO - Sorting by Title finished, Time : 62.83 ms
2023-03-21 18:40:21,384 - __main__ - INFO - Sorting by Label
2023-03-21 18:40:21,436 - __main__ - INFO - Sorting by Label finished, Time : 51.86 ms
2023-03-21 18:40:21,436 - __main__ - INFO - Filtering for keyword : Mix, across all fields
2023-03-21 18:40:21,517 - __main__ - INFO - Finished filtering for : Mix, Results : 50761, Time : 81.29 ms
2023-03-21 18:40:21,517 - __main__ - INFO - Filtering for keyword : Mix, across title
2023-03-21 18:40:21,535 - __main__ - INFO - Finished filtering for : Mix, Results : 33511, Time : 17.97 ms
2023-03-21 18:40:21,535 - __main__ - INFO - Filtering for keywords : Shiva Drums, across all fields
2023-03-21 18:40:21,615 - __main__ - INFO - Finished filtering for : Shiva Drums, Results : 6, Time : 79.77 ms

    With a small change we are at 0.05s maximum for filtering across all fields with 2 keywords, which is roughly 30% faster again. This is still using the dumbest container possible, no indexing/optimizations whatsoever.

    2023-03-21 20:50:49,668 - collection - INFO - Parsing collection finished, Time : 2298.70 ms
2023-03-21 20:50:49,668 - collection - INFO - Loading collection into internal structure
2023-03-21 20:50:50,005 - collection - INFO - Loading collection ended, Tracks found : 102722, Time : 337.05 ms
2023-03-21 20:50:50,005 - collection - INFO - Sorting by Artist
2023-03-21 20:50:50,045 - collection - INFO - Sorting by Artist finished, Time : 39.89 ms
2023-03-21 20:50:50,045 - collection - INFO - Sorting by Title
2023-03-21 20:50:50,104 - collection - INFO - Sorting by Title finished, Time : 57.88 ms
2023-03-21 20:50:50,104 - collection - INFO - Sorting by Label
2023-03-21 20:50:50,150 - collection - INFO - Sorting by Label finished, Time : 46.88 ms
2023-03-21 20:50:50,150 - collection - INFO - Filtering for keyword : Mix, across all fields
2023-03-21 20:50:50,208 - collection - INFO - Finished filtering for : Mix, Results : 50761, Time : 57.87 ms
2023-03-21 20:50:50,208 - collection - INFO - Filtering for keyword : Mix, across title
2023-03-21 20:50:50,222 - collection - INFO - Finished filtering for : Mix, Results : 33511, Time : 13.97 ms
2023-03-21 20:50:50,222 - collection - INFO - Filtering for keywords : Shiva Drums, across all fields
2023-03-21 20:50:50,279 - collection - INFO - Finished filtering for : Shiva Drums, Results : 6, Time : 55.86 ms

    The times given for filtering here include not only finding but also the generation of a finished result subset of the collection

  • T_G
    T_G Member Posts: 8 Member
    Options
    https://community.native-instruments.com/discussion/comment/59146#Comment_59146

    In my case this made a day/night difference. I had blackouts of several seconds with it enabled, depending on filtering etc!

  • Oxy
    Oxy Member Posts: 88 Helper
    Options
    https://community.native-instruments.com/discussion/comment/58909#Comment_58909

    Don't be rediculous. Using Traktor on multiple PC's so I thought to share my observation. Sorry that you feel I'm bragging. On my laptop an i7 10th gen the problem is very much prevalent. Thanks and have a nice day.

  • Kubrak
    Kubrak Member Posts: 2,789 Expert
    Options

    @T_G

    The whole sorting takes several seconds in your example... If collection is parsed every time.... Which may be the case with editable fields enabled. For example. And I havent said, db handling in Traktor does not ask for improvements...

    Still, I do not have any problems with 2-3k Traktor database. If I really focus, than yes there is very short blink taking tiny fraction of second. I haven't noticed it before hitting this thread.

  • T_G
    T_G Member Posts: 8 Member
    Options


    https://community.native-instruments.com/discussion/comment/59666#Comment_59666

    What are you even talking about, again? This is the parsing of the file. It is a one-time operation. Why should someone parse the collection file and rewrite it into an internal structure on every single operation? This is insane. Maybe also reassemble and rewrite the whole collection file on every change of a character to disk... Dude...

    If someone did that, or does that - and honestly such an idea did not even come to my mind, because it is severely disturbing - the suspect should be fired immediately and look for a job outside of IT.

  • Kubrak
    Kubrak Member Posts: 2,789 Expert
    Options

    Many things happen... Maybe they did not want to keep it all the time in RAM. The code is old and there used to be much less RAM in computers 10-15 years ago. And it might work well for small databases. There is many explanations...

    It may be so, that if fields are editable, db is not in RAM. For example. It would explain behaviour you have described... But it is just my wild guess.

  • Alex Dutch
    Alex Dutch Member Posts: 27 Member
    Options

    +1 And still not fixed in 3.9. What happen? Why.

  • Sûlherokhh
    Sûlherokhh Member, Traktor Mapping Mod Posts: 1,747 mod
    Options
    https://community.native-instruments.com/discussion/comment/73913#Comment_73913

    Why are you asking this question in three different threads? Why do you think anybody has any idea what the answer is? Why do you think anybody who knows is free of an NDA and can talk about it?

  • Alex Dutch
    Alex Dutch Member Posts: 27 Member
    Options

    @Sûlherokhh Good question. Sorry for my enthusiasm. I would like to see concrete action. Most users are really not crazy and understand quite a lot about technology. Sometimes we are treated like little children. You don't want to know how many calls and test reports I have already made. We all want only 1 thing. A reliable, friendly, stable and fine software.

    In my company i learn my employees: A complaint is free advice. 😃

    I notice that some threads are dead so thats why i posted in some threads. If that is not good, i will remove it, no problem.

    Love. Peace and beats from Amsterdam bro.

  • Sûlherokhh
    Sûlherokhh Member, Traktor Mapping Mod Posts: 1,747 mod
    Options

    @Alex Dutch Posting in several threads at the same time without much of a content to interact with just comes across as shouting and ranting. If you have read all the posts about Traktor's shortcomings, you have probably realized that many of us share your grievance.

    'We all want only 1 thing. A reliable, friendly, stable and fine software.'

    All the progress that has been made so far is the result of hard work of those that are in a position to maintain the software and constructive feedback from the community of die-hard Traktor users. Stating the obvious, a sign of frustration on your part surely, has been done many times before. If i were a community manager, and i am glad that i'm not, that sort of feedback would just make my stomach churn and force me to prioritize other things just to keep my sanity. It is obvious your anger finds a target, but it most certainly is the wrong one.

    Keep the hope up things get done, even if it's slow. Things have kind of picked up in the last half year. Personally i just use the version of Traktor with the smallest number of failings. Downgrading doesn't cost a thing, unless you need a computer running an older OS, but those can be had for less than back in the day.

    @Jeremy_NI , @Jonas_NI , @Kaiwan_NI and colleagues: Just wanna point out that you are doing a good job handling all of this; and keeping your cool taking it from two sides at once. 🦋

  • wayfinder
    wayfinder Member Posts: 365 Guru
    edited May 2023
    Options

    If i were a community manager, and i am glad that i'm not, that sort of feedback would just make my stomach churn and force me to prioritize other things just to keep my sanity.

    Am I misreading that or are you saying you would deliberately keep a frustrating bug that makes people desperate if that desperation unloads itself as five posts in a support forum? I MUST be misreading that, surely

  • Sûlherokhh
    Sûlherokhh Member, Traktor Mapping Mod Posts: 1,747 mod
    Options
    https://community.native-instruments.com/discussion/comment/74016#Comment_74016

    Not deliberately, no. But i know myself well enough that i would not be a community manager for long, being really no ace at juggling. 😵

  • Kubrak
    Kubrak Member Posts: 2,789 Expert
    Options

    @wayfinder is most probably right, that at least some cases of flickering could be solved pretty easily. I have suggested the same thing like he some time ago...

    Show the user info that sorting is in progress only if sorting takes more than 0.5-1 second. Or something like that. Or make the displaying that warning user configurable/switchable off.

    But it looks to me to solve it completely, it probably needs much more work....

    Most probably it is on schedule, as browser improvements are....

  • vsound
    vsound Member Posts: 4 Newcomer
    edited July 2023
    Options

    Just bought a new Win11 Pro laptop with an Intel N95 processor with 16gb RAM 512GB SSD), which is much faster and double the RAM and fasted hard drive than my 12 yr old i3 1st gen processor and can't get any version of Traktor to work properly. I'm getting that "please wait while refreshing" message and browser flashing every time I click on a track and it takes several seconds to refresh. Makes the app almost unusable. Also, I notice how buggy Traktor Pro 3.9.0 is when is comes to the transport and pitch bend and syncing. I've uninstalled and reinstalled and run into the same issues.

    I have a large collection (over 400k tracks). The original Traktor Pro (version 1.27) works fine on my 12 year old Toshiba i3 1st gen laptop running win7. The only issue is it takes about 20+ minutes to load my collection when I open Traktor, very rarely I get that "please wait while refreshing" message or browser flashing.

    Does anyone have any tips on how to fix these issues or how to rollback to a version that doesn't have these issues? I can't go back to Traktor Pro 1.27 since the app crashes every time I try to import my collection and can't get Traktor Pro 2 to open after multiple installs. Been using Traktor for 12 yrs and never had issues like this. Any help is greatly appreciated.

Back To Top

Categories