Traktor API

I like the idea of a basic Traktor API which allows external programs to read the following data:

• Now playing (Deck A..D) + the ID3-Tag of the files
• Tracks which are in the selected playlist + the ID3-Tag of the files

These small features would offer 3rd-party programs many possibilities like:

• statistics
• proposals for the next song
• ....

In special, I would be able to extend my selfmade camelothweel which already suggests harmonic keys

 

I agree on the fact that an API would be very usefull, although it might already be there, I have not read anything about it yet.

the functionality I'm thinking of creating is similar to what you suggested.

Improvement in managing (renaming/organizing/backing up) files / key based suggestions / played state on different remixes of the same tracks / history.

anyway who knows NI might already creating features mentioned above.

 

+1

generally there should very little risk for making it possible to interface with all this meta data, so the "vst plugin's are dangerous and do not work in time" argument doesnt apply here. please please please open up to allow innovation at the edges (aka by end users)

 

Hey Guys,

I would love to see an API for Traktor. Even being able to grab track meta data per deck would open up lots of possibilities for visuals and crowd interaction.

Ableton Live has an unofficial one already, it would be great if you guys took it upon yourselves to be the first to release something official.

Cheers, Tom.

 

+1

 

If you just want to know the name and title of the main-track playing I could modify my Traktor Scrobbler.
Just tell me what you need? An XML-file?

Sadly it's difficult to write 3rd party stuff for Traktor since debugging doesn't work so developers rely on stuff that comes out of Traktor Pro (like the icecast-stream or database).

On the official side I guess there won't be any efforts soon.

 

@Ali: Thank you for offering that work around but I don't think its a good idea to have Traktor create an extra audiostream just to receive some track infos ...

An API would be a good idea, especially I think, if a first step is made, ther are a lot of enhancements that can be done. As long as we use workarounds there is no need for NI to provide an API ...

 

they don't support the unofficial stuff or know about it (at least I think so).
An instantly written log-file should be plenty for the requests here, but I have no clue how to force Traktor into some kind of debug-mode.

You convinced me so +1 from me as well