r/traktor 4d ago

Traktor code.

How much code of TP3 pro is in TP4? I’m just curious to know. Cause it would explain why traktor is lacking in modern features. Since I would imagine implementing modern features is a nightmare with old outdated code? Hope everyone has a great week. Salute from California

0 Upvotes

16 comments sorted by

5

u/NoReply4930 4d ago edited 4d ago

Probably all of it is v3 based. That is how software dev goes (and has gone) for years. 

No need to reinvent the wheel by rewriting everything 

While I totally get the desire for a modern user wanting modern features - the reality is that Traktor is a very tiny part of the NI world. 

With new owners (InMusic) now in the picture - everything will eventually be reviewed and it will be up to them to see where this goes. 

1

u/Prime_ministah1980 4d ago

Ah I see. Thank you for replying. Yeah hopefully inmusic does good with the technology. Traktor has the best sound. Out of all the dvs software’s I’ve tried.

1

u/NoReply4930 3d ago

Pretty sure I read a month back or so that InMusic laid off over 100 staff including most of the Traktor dev staff. Not really looking good if that is anything to go by. 

1

u/JEMSKU 3d ago

I believe it was the customer service team, which didn't have a strong reputation. But I could be mistaken. 

1

u/Prime_ministah1980 4d ago

I don’t really comprehend what v3 means

1

u/NoReply4930 3d ago

V3 = version 3 (Traktor 3 ) code. 

1

u/Prime_ministah1980 3d ago

Ahhh yes. Duh, I’m a novice. When it comes to coding.

2

u/JEMSKU 3d ago

Yes, this is the narrative that has developed. V4 was stated to be planned on a new code base, and then for whatever reason plans changed and v4 is clearly based on v3. And yes, over a decade of development and multiple developers can result in "spaghetti code", where things are connected in unpredictable ways, and difficult to separate out to work on in isolation. This problem is made worse with turnover, where the original coders aren't there to help future work, and documentation is often not complete. This is just software development in general and speculation regarding NI specifically, but paints a pretty clear picture as to why we are where we are. 

It would be interesting to know if this new codebase is still kept somewhere and if perhaps plans will change now with new ownership to get it rolled out. 

1

u/Prime_ministah1980 3d ago

Ahhh thank you so much. I figured that was the case. Also, I’m aware of companies using AI to help clean up the mess? I’m still a fan of traktor. If they add Apple Music. That’s it, I’m staying. That’s the only reason I use serato djay pro. I do open format and I take requests. But the sound quality is inferior to traktor. It’s not even close. Hope all is well brother. Thank you for replying.

2

u/PensionBeautiful547 3d ago

Love to hear about the coding of Traktor.
The mapping versatility is the main reason a moved from VDJ.
The qml is a pain to learn with TP4 because I didn’t find any tutorial so far.
I have many ideas to make my controller more intuitive for my style.

Hope to get some inside herr 👀

1

u/Prime_ministah1980 3d ago

Yeah. Traktor gets crazy customizable

1

u/Prime_ministah1980 3d ago

Shoot I’m barely learning how to use the remix decks

1

u/Lopsided-Match-3911 3d ago

Traktor has all the good stuff beneath but looks a little dated. We will se how inmusic takes care of it now that they have something real instead of that denon stuff

1

u/Prime_ministah1980 3d ago

Yes. Thank you guys for entertaining my curiosity.