Traktor (Scratch) Pro - MIDI construction & Issues

Is there already a working VCI-100 .tsi - file for Traktor Pro? No, I will not program my controller on my own, just give me a working config like it did in LE... :angry:

 

i think the midi map for the 1d which comes with pro is not that good. i tried it out...

still asking my self how it would be, 04:30 am, running four decks and already some vodka done... i wouldn´t find the function i wanna use

no chance to map all functions i need onto one 1d!

 

I'll have a go at making one this evening if my daughter goes to bed early enough! I messed about with it last night but had difficulties with the Scratch functionality, Got scratch on but couldn't get them funtioning like 3.4.

Laters

Syn

 

Making a good tsi file is a long job that require not only time for assignment...but also a study for "which function have to be placed..and where".
Moreover every controller has their tricks, differences regarding resolutions, problems with leds and so on...
In this world exist thousands of controllers and you can't pretend NI focus their mind in every kind of them. They gave us different .tsi map for most popular (and most professional) controllers because they couldn't stay years creating map file for every button of every controller..so..just relax yourself and ask (not here but in an appropriate topic) if someone has the same controller of you...and try to start to map your controller by your own....you know more than everybody which functions you need and want.
In these days i'll spend lot of time for make Xponent work at 100%...and i will share my map. For be honest i felt like "why not xponent and hercules mk2 yes?"
But then i've thought that i have all necessary functions for make it by my own...and i didn't came here with a knife LOL
Later


(This is for every MAP-Pretenders)

 

I just wondered about the NI testing.. the VCI-100 comes with Traktor LE, so in my opinion it is not too much asked to have a working version when you upgrade, right?

No problem with config my Akai pads later, but the pads came not as a bundles product with traktor.. that's the difference here.

 

I see that the MK2 is listed. Did you (or anyone) happen to see if the RMX is also supported natively? For that matter, is there anyone here with a RMX that is using Pro?

(Man I hope so because this sitting on this fence wondering if I should upgrade is getting painful.)

 

You know, I have been guilty of going off on one re NI, but my complaints have been about fixing issues within one generation of the software.

In your comments above, your mixing apples and oranges. Pro is a significant shift from Traktor 3. NI have delivered an effective level of support for programming MIDI. I'm using the Novation which comes with no NI support, and therefore it needs to be programmed from scratch, with a small 's'. If your new to MIDI, it's worth getting your head round it.

As far as bundling, your product shipped with Traktor LE, and it worked did it not? Yes, it did. You can't expect NI to have perfect line of sight across all hardware controllers that offer Traktor interaction.

The vci-100 is certified with Traktor 3, not Pro.

 

Easy all,

some kind of .pdf with the map for each controller would be ace - have NI released this type of thing?

keep up the good work all djd

 

Many controls on Reloop Digital Jockey does not work, including a pitch Fader, etc.

 

Id suggest using the "CD-DJ jog" for pitch bending, a good side effect to this midicommand is that when paused/cue'd u can use the outer rim for fast scrolling in tracks, like a seek position

 

Beatjump MIDI command?

I'm having to use Seek Position to jump through tracks, but it doesn't stay in time like Beatjump does.

Has anyone found the right MIDI-command for using Beatjump?

 

seek issue

Im having the same problem. when seek is engaged, I can seek through the track, but when I stop touching the seek function, I end up all the way back to the beginning of the track....WTF !

 

Oooohhhh!... Oooohhhh!... Oooohhhh!... Oooohhhh!... I Know...I Know.. pick me pick me pick me!..
You're using a Jog control and the Traktor logic is expecting a note on message when the wheel is released, I think its generically called touch-off. Traktor is not getting the correct message. All you have to do is switch to using a rotary control.

 

ahhhh

at last....a working seek function HORRAY...guess I wanted to use the shinny new JOG 3fh : 41h for everything.....now I understand, and actually this explains alot more.

 

Nice on PhilL, thanks very much, that's cracked it

 

I'm testing the default .tsi for my Behringer DDM-4000. Everything seems to work as intended except for the FX parameter knob controls. I've checked the mapping screen and all the settings appear fine.

I've also downloaded the DDM-4000 MIDI send overviews and have found that the MIDI send legend (cc 0 - 21, note 23 - 124) does not match the button alias used in Traktor Pro.. is it known if either Behringer or NI will be sending out an updated legend to help in manually mapping our controls?

Aside from my MIDI issue, Traktor Pro has been quite impressive. I haven't yet gotten a chance to test the Timecode Scratch portion of this new build, but i have found that the internal crossfader curve in Traktor Pro is nowhere near sharp enough to suit my needs (not a huge deal, it was half expected).

 

The included Xone 1D template is abysmal. Using a fader for an "on/off" value is pretty stupid.

I remapped mine immediately

 

Okay, read through this, but didn't seem to find a solution to my problem.

I'm having trouble with assigning the pitch bend (or rather "tempo bend" as it appears to be called now) to my Feena joystick. I can't seem to find the option of assigning it to anything but a button. When I try that, Traktor believes the joystick is one single button, no matter what direction I push it in. Anyone have a clue what I might be doing wrong? I'm sure this must be possible to achieve.

 

Willy, have you tried using Transport | CD-DJ Jog instead?
Its what I use on my BCR and SCS3.d's

Phil

 

Thanks Phil! Dat worked!

One problem down, a couple of more to go...