N.I ..Any update on the progress of Traktor DJ 2 ?

Buffer: Fair point. But there could be buffering elsewhere. For sure in the MIDI path of the kernel driver.
We can only infer this by measuring.

----
Reagrding collection: I currently edit the file directly to duplicate cues on dupliacted files.
https://github.com/pestrela/music/blob/master/traktor/tools_traktor/cue_merge_cues.py

This is a crucial step of NOT using any DJ folders at all:
https://github.com/pestrela/dj_kb#h...sts-ie-using-only-finder-windows-explorer-etc

SQLite is more scalable and shareable between systems of course.
But I see no reason why flexible beatgrids cannot be done in the current XML file structure.

 

yes you're right, could be anything behind the scenery in kernel too

cool links thanks for sharing, be sure i will walk thru all details. I remember you are the guy behind 'cmdr' .. such a great tool, would be a nightmare not having this .. Traktor Mapping editor is a pain, and mapping hundreds of line manually would make me crazy. I know you moved to BOME but i still hope you will keep (and upgrade your cmdr still sometimes). I miss one detail in cmdr only: having the option to select several items in mapping list and edit them in details dialog togehter with same fields (common fields editable, similar as in e.g. mp3tag), so be so much helpful (INC/DEC batch commands no longer needed). Btw: I am the guy behind Dark Controller (Midi compliant controller), and the 2 minor tools TraCoMerger and TraCoConverter, the last 2 maybe of interest for you (reading you links regarding collection.nml): TraCoCoverter allows to export Traktor meta data into DJ Player Pro .. and TraCoMerger allows to share Traktor meta data between laptops or between TPro and TDJ1, maybe you know them already. Posting this info & links only because i saw in your links you worked with collection.nml too, so maybe of interest.

Correct. The pain why i posted: With the new annoucments on NI (not focusing longer on TDJ) i am afraid this NI dtatabase conzept will get lost too .. so i still have my doubts we will get modern new redesigned concepts in TPro soon, right ?

Question (also back to thread TDJ2): do you (or anybody else) have any technical details about the NI HID protocol ? Any coding libraries/documents ? The reason i ask: I was thinking about in past to build own controller which could be used in TDJ1 or TDJ2. As both do not support midi (but e.g. S4 HID) i was wondering about creating a kind of 'S4' emulator, means creating a 'black box' (or firmware enhancements in my Dark Controller devices) which allows me to add (selfmade) controller communicating in HID with TDJ (simulating a S4 or Z1 HID) So in case you have info, let us know

 

I like your programming discussions. I build and program drones and I can tell you measuring how voltage passes through can make a huge difference.

A loose example would be the jogs on the sc5000/6000 models. If you use a radio transceiver near the jogs you mess up how the how they work. And this is not only for the Denon’s either.

Another thing people don’t realize is what work goes into making direct drive controllers to work. It takes a lot of dynamic modelling to the point that it is the equivalent of programming a drone.

It will be at least $3000 in labour and time lost for NI to work on these things. Time that could have been put into building up the software. But at the same time look how much variety of products are coming out with spinning platters and how companies who worked on it before are now blessed for the investment.

 

Kalo probably you will need to mesh with id vendor which will made those impossible to sell legally.

Wyley Are you talking just about PMW 3 phase motors or that plus something else?

 

Any motor needs some kind of esc to operate usefully. Also it’s clock speed has to be monitored and feedback systems have to be created to monitor and manipulate the data so the platter can function like a turntable.(exactly like receiving telemetric data and making adjustments.). It took serato a while to do this.

The hosting software needs some kind of sdk from the manufacturer to even start.

Modeling static stuff is easy but dynamic stuff is not.

 

N.I just turned aout to be alot of work arounds or flat out no's, was always wiating and hoping but in the end nothing. When the software starts to hold you back its time to say goodbye im afraid and i say that with a heavey heart.

Imagine having ace software but you just refuse to let your users use it with other hardware that they so desire. Traktor like the sulky kid in the park took his ball home for the last time.

 

I’m starting digging into that part for a personal (open source) project and I will appreciate info/collab. Are you interested?

 

Blame Ritchie Hawtin and Ean Golden for this. Traktor was magical until these guys were allowed to speak for all of us.

 

Kalo
thanks for your kind words!
I still use CMDR every day, because the only thing that moved to BOME was the modifier-heavy stuff.

---
regarding common fields editing like mp3tag: i know what you mean but this was harder than I tough in C#.
Because the code is fully generic and auto-generates the exiting common fields automatically.

Workaround was the several other automations I've added. Especially mass-generate channels and pads.

---
TraCoMerger and TraCoConverter were indeed my instpiration for my python tool. Fantastic job.
Your tools are even better by having a GUI, which is a great feature that I personally do not need.
With WSL I hope that other windows persons can easily run them

---
no experience on NHL. if anybody managed to do it would have been MIXXX by now:
https://mixxx.discourse.group/t/native-instruments-kontrol-s4-v0-1/11942/7?u=dj_estrela

@wiley
agree that modelling a direct drive platter is really hard. Harder than DVS, as there you don't have a variable frequency going out you can sample
This is why I'm talking about fixed jogs of DDJ-1000 etc

 

dj_estrela: thank YOU ! yes, as long you keep current CMDR alive, then all is fine

Mutis: i would love to dig into your open source project .. but afraid i am too busy in moment , my new Dark Flame (DFL) needs lot time (just started beta, some fancy 4-deck/multi-layer Traktor mapping with dj_estrelas's CMDR is next step .. and final documentation). But keep me into the loop, happy to help wherever i can ...damn: would be amazing if TDJ would support midi native (my tiny portable DFL would match best). So i go with Traktor Pro (laptop) at home and with DJ Player Pro (iPad) on travel for now.
https://dark-controller.com/darkflame/

 

Sure!

 

I’m to old for this.

I run an outdoor laser tag business with military grade laser rifles (200m+ range). Most of my time now is spent programming games and fine tuning a network for it. What’s cool about the rifles is that you can attach your phone to it and use google maps to have radar, locate virtual re-ups something like an Xbox but real in life. I’m adding drones to the mix this year.

Appreciate the offer though and good luck

 

Seems fun! Thanks anyways mate <3

 

Look like Denon’s new controller is called the Lc6000.

 

Super interesting thread, till you all got really technical

I am a full time event (mobile) DJ, and have used Traktor since 2011. I still find Traktor to be the easiest/best DJ program to use And I do own full versions of Serato and VDJ.

However I now have a major problem with Traktor. I am looking to replace my controller (currently a Denon MC6000mk2), There are almost no suitable controller available for event DJs. While I like the Kontrol S4 and S8, having microphone feed through the channel faders makes them unusable for most, if not all, my events. What I need most in a controller is, great microphone control, and inputs (lost of inputs). I would also prefer a laptop than a totally integrated system.

The only real option for an event DJ is the Roland M707, but Traktor mapping is not available for that controller. So I will need to give up Traktor, or learn to Map!!!

SO my suggestions for Traktor.

And here I agree with Wyley - "Mapping support for all pioneer mixers."

But I would go further. I suggest having NI programmers create mapping for all the most popular controllers on the market. Then offer it to everyone. While this could be seen as detracting from the Kontrol products, I see a bigger picture. Before purchasing a Kontrol product, a DJ needs to be “Sold” on Traktor Pro. One way to get more DJ’s using Traktor Pro, is to make it easy for DJs to use it on their current controller (whatever it is).

 

Running a mic through software is pretty good btw. The s2mk2 lets me use the mic though the software or just though the controller. The Roland’s 707m seems to be the best mobile controller on the market right now and should get a Traktor mapping. I would of bought it if it was class compliant.

 

Does this mean we might actually get A Linux version finally?

 

why should we?
lets focus on much more urgent things please

 

What makes you believe that?
The nearest thing will be NI ditching mostly everything about actual traktor and going S4+... but not seems the way forward IMHO.

 

The one thing i hope is coming would be to connect Traktor and its controllers wirelessly. I have found that this is the biggest thing that puts people off traktor, setting up in clubs having to connect cables and leads for controllers, audio interfaces, laptops etc is a pain.