Anyone Upgrade to Traktor 4 yet?
You can upgrade through DJTT
I’ll probably do it soon…just wanted to see if anyone else has jumped in…
Anyone Upgrade to Traktor 4 yet?
You can upgrade through DJTT
I’ll probably do it soon…just wanted to see if anyone else has jumped in…
Purchased and installed ![]()
downloaded and fiddled with it. Basic stuff is working as it should be. Flexible beatgrips are a pleasure to finally have. Works great. Tried out a few stems related things, but for now i wouldn’t use it in a live situation. My tracks is beginning to stutter while analysing other tracks at the same time. For now, this feature will only be used at home for preparations. i’m having an 8h gig on staturday and will give T4 a deep dive
From what I’ve read I would not expect to actually be able to analyze stems in a live situation. I would treat stems in T4 the way it was in earlier versions - something to use with pre-separated stem tracks (the difference being you can do the analysis right in T4). But it sounds like it takes almost the length of a song to analyze it, which is absolutely not something I’d want to do in a live situation. It also stores the stems as separate tracks, which has the advantage of requiring no extra processing on subsequent uses, but your disk will fill quickly if you start stem-ifying every track. I could be wrong but I believe other programs figure out the right math to apply when they analyze a track for stems and then save the math rather than saving separate tracks. That’s a higher processor overhead when using them subsequently since it has to reapply the math to the tracks (but nothing compared to analyzing them in the first place); I’m not sure Traktor made the right decision in going to separate tracks but I guess we’ll see.
Disclaimer tho, my opinion is based purely on reading about T4 as I haven’t installed it yet for other reasons unrelated to stems. But I am pretty sure I will, probably after the .1 update.
RE: Anyone Upgrade to Traktor 4 yet?
I have, and I’m having the time of my life!! MAN!! I’m like an Apple zombie in that I would defend Traktor to my last breath, but man!! We FINALLY got manual beatgrids (called flexible beatgrids) for songs that change tempos within them, the converting your party favorites to Stems built-in so you can create loops and one-shot sound FX, the colors, and the seamless compatibility with my Kontrol S4 MK III…I’m like a kid in a candy store!! I’m even watching some of their “What’s New In Traktor 4” tutorials on repeat to make sure I don’t miss that KNOWLEDGE!!
Have they fixed the “Deck Lock” issue?
Some users have reported that it occasionally appears. I always work around it with mappings that duplicate the faulty preference without actually using it.
Care to elaborate?
Wether it’s a midi mapping or an NI controller with a qml mapping, i add the condition ‘Deck Playing = NO’ to the load function.
Also i uncheck ‘load only into stopped deck’ in Preferences → Loading, which is the setting (when checked) that causes the deck being sometimes unloadable, because, for some reason, there are occasions when Traktor thinks the track is ‘doing something’ and disallows loading, whereas my mapping solution only checks if the deck state ‘PLAY’ is ON or OFF.
Somebody at NI should have done this exact thing since forever. I don’t think the problem would be hard to find and solve with the uncompiled code at hand.
The “Load Selected” with a deck play modifier only determens if Track will be loaded or not. The problem happens when a “deck is loading” - sometimes I can produce this issue with a computer mouse but never with a midi controller or Traktor controller.
I made custom mappings to help others solve this issue but had reports that the modifier trick didn’t work.
The 'Deck Lock" issues was the main reason for finally leaving Traktor Pro, I was hoping Traktor 4 would have solved it. Oh well..
Oh well. Happily i find the workaround satisfactory and can enjoy all the rest of the traktor goodies.
Dare I ask what the dreaded “deck lock” issue is?
When you attempt to load a track into a stopped deck only to get the message that the deck must be stopped first, it mainly affects DVS users.
I emailed Native Instruments support, but they suggested turning off the Deck Lock feature, which defeats the purpose of the Deck Lock feature.
This is probably an obvious guess but is it possible the record is still moving a tiny bit when this happens? I have quickly corrected this issue with a baby scratch and stop on the deck. I use DVS more often than not in Traktor and don’t recall encountering this in other situations. Also if the needle gets to the middle of the record traktor switches to internal mode until you move the needle back or stop the record; if you don’t switch it back to relative mode you have to stop the track with the play/pause button. Traktor considers the record to be playing long after the music stops if you don’t do these things. [Apologies if you already know this; I’m just guessing here].
Short answer: Nope.
As I mentioned earlier, I’ve emailed NI support, they are aware but claim to not be able to reproduce the problem.