Are you having that issue with the browser snapping continuously? The only way to partly fix it is turn off re indexing for the sample locations, but then any package contents trigger the bug still. It seems like every time I click a sample, it rescans for some reason. Bitwig says it's something on my computer but I can't find anything...I am with Teksonik here...So yes that's sloppy programming. I can say that as someone who has been a beta tester for several major DAWs. None of the 6 other DAWs I currently own has the same issue on the same systems.
...
It´s obvious that Bitwig did implement a system which doesn´t work very well and seem to do really unnecessary work...
And it´s not that we are talking about just having a spinny wheel on the top and a bit more of CPU usage...
We talk about mostly not being able to use the side browser as long as this scan runs as it always jumps back to the last selected file when having finished a part of the scan besides cluttering the system with hundred thousands of tiny files...
As no other DAW behaves this negative way (i.e. FLS supports user tagging and advanced search as well and has finished indexing on startup in about one second parallel to loading the template) there is just one option left...
Call it what you want... bad idea, sloppy programming... whatever... but the issue stays the same...
It got already better though... scanning got faster, excluding of some folders... but i.e. the decision to scan over and over the native packs where nobody knows better than the programm itself if something has changed or not is more than questionable...
Cluttering the drives with that amount of tiny files is questionable as well ...
It´s not the end of the world but as we have all seen with the example of EQ+ and it´s latency, it´s not that the Bitwigs are flawless and not making sometimes at least weird if not simply wrong decisions.
Statistics: Posted by XandY — Fri Dec 29, 2023 4:35 am
