Where did the auto/default grid marker go?
Comments
-
Letting it create a new 3.11.1 folder let me write cues to any tracks I dropped in there, so it's not a Mac-side permissions issue. I went back to the original 3.11.1 folder and took out just the Traktor Settings.tsi file and that fixed it too! So, is that file somehow corrupt (which would be bad news) or is it simply some bad combination of settings somewhere?
1 -
Sounds like it was a corruption in the TSI file then. It's like it wasn't reading the "set beatgrid" option correctly. Is everything working OK for you now?
0 -
Unfortunately not...maybe...
Traktor on my laptop works fine - I tried copying the TSI and collection over to my desktop, which has the problem, and got the same bad result. I even tried copying the whole Traktor 3.11.1 folder over from the laptop but same problem. Interestingly too, when I copied the whole Traktor 3.11.1 user folder from the desktop (bad) to the laptop (good), it works perfectly well. Which now DOES seem to suggest some kind of permissions issue, although I can't work out what. For some reason it seems like Traktor is preventing itself from writing the tags rather than the files being unwritable. Just for fun, I copied a track over from the desktop to the laptop and can write to it normally, so it doesn't seem to be anything baked into the files either.
0 -
That's weird - probably worth putting in a support ticket, the devs might want to see config files etc.
0 -
Thanks for your help Myke, I opened a ticket.
0 -
Hey Myke....well, after some fairly in-depth elimination and troubleshooting, I've fixed it!
I have 4 controllers listed in my controller manager - an S4, a generic keyboard, a Novation XL, and a Faderfox DJ44 << it was the Faderfox settings! Not that the file was corrupt, but the MIDI port setting itself. After trying various combinations, I connected the DJ44, I assigned the ports to DJ44 in TP, and it worked. I disconnected the cable, and the Traktor setting port went back to n/a instead of all or none....and the cues worked!! I reconnected, retested, restarted but as far as I can see, it's all OK. I'm not sure exactly what triggered it; the only difference midi-wise between my 2 machines is that I have a Stream Deck on my desktop (the one with the TP issue), and it uses the IAC port, so maybe having 'all' selected puts it into some kind of conflict. But WHY that would affect writing cues???? I have NOOO idea. Anyway I'll let my NI support people know, maybe it's an obscure bug?
Thanks again.
1 -
@muthafunka That's a weird problem/solution for sure, no idea why that would affect cues, but at least you're up and working :)
1
Categories
- All Categories
- 19 Welcome
- 1.5K Hangout
- 65 NI News
- 818 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