I update this thread every time an old bug that should have been fixed years ago makes life harder
Comments
-
Exactly! 😔
0 -
Today for some reason it's worse than usual: MouseUp events are only recognized a few frames after they have actually happened, by which time I have already moved the mouse away. What this means in practice is that I keep accidentally reordering a playlist after entering a star rating, because Traktor thinks I am dragging when I'm just trying to click once and then move on :(
1 -
I hate to say it, but this is the story of my track prep life. I stopped cursing years ago. Instead i transferred as many of the GUI controls i could to my F1 in order to not use my mouse. Inside, this is driving me mad. Feels like the dinosaur browser-code is of the same species as sharks, scaring the coders to death to even touch it. ^^
I wish they where allowed to talk to us about their attempts to tackle it.
2 -
It struck me today how weird Traktor does dragging block selections of tracks in the browser.
Every normal software will treat those as a block, a single unit that is inserted at a specific place, and when you drag and drop the mouse over any part of the selected block, they will place the whole selection in the place of the whole selection, i.e. do nothing.
In Traktor, you can drag a block of multiple selected tracks between any two of the selected tracks inside the block, and what ends up happening is that Traktor takes the track below where you dropped the block and moves it to the end of the block (still all selected, still in the same place, just now in a different order, with that one single track moved to the end of the selection).
That is really confusing if you don't understand what's happening!
It reminds me a bit of how Traktor also does not treat text selections as a block cursor, so that you can end up with the cursor between the first and second character of the selection when you press the right cursor key, instead of after the last selected character like in any normal app.
2 -
Traktor always forgets the sensitivity setting on the - and + controls next to the key knob in the mixer :( It always defaults to 2 semitones per click - I don't in all honesty know why that setting even exists!
2 -
I have to click on automatic volume adjustment every time I start the program or is this a wrong setting in my configuration?
0 -
I have opened a support ticket since October 2022, the response from native instruments was that they were able to reproduce the problem and will forward it to the developers for resolution. Almost 2 years later this bug unfortunately remains unsolved and I have no information about this.
1 -
I'd be content if they set the default to ONE semitone - two just makes no sense at all!
1
Categories
- All Categories
- 19 Welcome
- 1.5K Hangout
- 65 NI News
- 819 Tech Talks
- 4.2K Native Access
- 17K Komplete
- 2.1K Komplete General
- 4.4K Komplete Kontrol
- 5.9K Kontakt
- 1.6K Reaktor
- 390 Battery 4
- 871 Guitar Rig & FX
- 440 Massive X & Synths
- 1.3K Other Software & Hardware
- 5.9K Maschine
- 7.6K Traktor
- 7.6K 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