Yes, we are working on an assignment but there are 2 things you should know as you begin to try and assign your own .TSi file.
1: use a midi translator or midi monitor to watch what each button and knob does on the SE. This will allow you to precisely choose which midi command to assign without using midi learn. 2: they duplicated our double filter making the double knob I created on the SE not needed. So to assign the double filter to the double knob and still make it work you need to assign each side of the knob in the following way:
Filter Direct (relative fader) inverted - left side
Filter Direct (relative fader) - right side
Filter Reset - center note on
pictures bellow
Personally I think these knobs should be used as 2 FX sends so you have 2 effects on one knob but some may want to use them for filters again.
Thanks for the tip. I was just wondering, could you let us know if you guys are working on an “official” tsi file? Because If thats the case, I wont throw my self into the project of creating my own…
Eans working on the mapping - people need to realise its ALOT of work and will take time to do properly, Eans not going to just do some half arsed effort.
Fantastic! Great news.
I think people totally understand that it takes a lot of time to do the work. Especially for a bussy guy like Ean.
We were just asking cause nothing was stated about a DJTT vsi for the SE. But now we know and cant wait
i really don’t know anything about midi assignments or anything of the sort and have no time at all to try and learn. all i know at this point is that i can’t get anything to happen at all with traktor pro and SE. I know Ean will hook it up just as soon as he can (much appreciation in advance), but i’m just confused as to what the implications are with this new traktor. is the overlay i just bought now essentially labeled different than the actual functions of the buttons and knobs in traktor pro? i feel like an idiot asking that but i just don’t get it and now feel like i have yet again a non working vci-100. otherwise all i have is traktor LE and i can barely even use that cuz the labels on the new overlay don’t match the functions.
please don’t get too grumpy with my question! i appreciate all the help the community has given me in my quest to get my vci-100 working and usable but i am admittedly a little bummed out right now after waiting a month for this software and i’m not as smart as all you uber dj’s!
Which firmware for SE do you recommend using if we are making our own personal TSI mappings for pro? 1.2 or 1.3?
I gave an inital shot using 1.2, but there are issues with the last effect button selecting monitor cue a/b depending on which bank is selected.
I also gave 1.3 a shot which was ok, but i noticed 2 problems so far. When mapping the existing 1.3 SNAP button it needs about 4 pushs to toggle properly. Also the second and fourth fx knobs don’t seem to control properly as they jump from 0 to 100 percent (currently i have mapped to a chained fx). I can’t understand why this is happening, as eans TSI doesn’t seem to do this. Any ideas of how i get around this?
Also if using 1.3 which other controls in addition to being mentioned on the vci100se require special attention to map due to the signals being sent out?
Final question, which Midi Monitor is most effective to use under Mac OSX to monitor whats coming out of the vci. I have currently been trying out MIDI MONITOR, and today i just learnt about MIDIPIPE. Any recommendations? or are these as good as any others.
Any midi monitor would do, Midi pipe is also actually a midi translation that you can use to program the midi messages. I think Bomes Midi Pro(not free) is the best midi translation program around if you are getting into that though.
1: use a midi translator or midi monitor to watch what each button and knob does on the SE. This will allow you to precisely choose which midi command to assign without using midi learn. [/quote] Thanks BentoSan for that reply. I’m using MidiMonitor at the moment and trying to get my head around the process of understanding what is happening. One thing that is strange is that the data results of MidiMonitor seem to be 1 value off the data (learnt) in Traktor. For Example: Hitting the side a SYNC button on the VCi-100 in traktor is Note D3(Ch1) but in midi monitor it is D2(Ch1) Likewise hitting play/pause in traktor is F3 but in midi monitor it is F2. Is there some sort of setting i am screwing up ? Or should i use a different monitor program (if so any suggestions for osx) at this stage i don’t want to delve into the translation aspects. Thanks in advance again. ________________ EDIT OK did some more playing around and found in BOMES midi translator how to capture and display whats coming out of the MIDI. Very strange how the Midi Monitor program displays one note off. Anyways, I found the solution so short story is use BOMES to display the MIDI and don’t bother with midi monitor. But a technical question. I’ve got bomes to display whats coming out. Lets take the second FX knob on the VCI for example. In Eans TSI this is basically mapped as CC71 CC75 and CC85 (effect amount 3) depending on which bank you are in. In Bomes, looking at the message trigger, I can understand and see the messages lining up for: CC75 (“CC#2: Controller75, 32” in bank c) CC85 (“CC#2: Controller 85, 26” in bank b) but in bank a where i would have expected to see CC71 instead the message reads “CC#2: Timbre, 99” so I could figure out how this = CC71. What’s going on here? How do i interpret Timbre to = CC71? Is there some sort of translating guide somewhere I can use? Actually answered my own question. You have to look at the HEX. in the example above the hex is B0 47 35. B0 is the continous controller and 47 HEX = 71 DEC and the 35 being the value. Cool!
that happend when you want the CD copy lol