Brilliant!
lsmith dude, I’d like to give you some serious praise. Your indepth analysis and awesome customization and verbose help is beautiful. I checked out your blog, very cool. I feel like you’re really contributing a lot of value to these forums. Thanks so much for clarifying, I would’ve been beating my head into a wall trying to get cues 5-8…
In your midi mapping just add the search function to the up and down browse buttons… DONE
I wish I was in the same place with adjusting the midi mappings as you all seem to be, but I’m not. I’m still hesitant about upgrading to 1.2.1 because I’m happy with the 2.3 and 2.4 tsi. How well do Ean’s mappings work with 1.2.1? Aside from the filter knobs cycling through twice and a few other issues, should I just wait till a new mapping is released for 1.2. I suck at mapping. I think the traktor bible is in my future!
Looks like your prayers have been answered, Eans just released a proper 1.2 mapping!
Get on it! Take a back up of your setup now then its so easy to switch back and forth with no hassle.
Gav
yipee .. unfortunately i am off to the US soon, touring .. but not as a DJ, but as a speaker at a conference road show (7 cities in 14 days .. if anyone wants to meet up, here are the locations → http://cw.mtacon.com/).
when i get back i will look into adapting Ean’s TP1.2 mapping with my customizations.
downloaded the new 1.2 mapping but none of the buttons work at all for me??? any ideas??? noob mistake???
1.2 firmware
1.2.1 traktor pro
HELL YEAH! Good to be in the 1.2 game. I was looking forward to trying it out. Just played with it for an hour. So far…so good!
Thanks Ean! Just in time to mess with it for the weekend!
I had the same problem. I have firmware 1.3 though, so I’m not sure if the reason is the same. Anyway, the way I fixed it was going to Controller-Manager in Traktor preferences and selecting “Vestax PC-CONTROLLER” for both In-Port and Out-Port. I think it was set to “None” for some reason. Hope this helps…
Re: VCI-100SE TSI 2_4 FeedBack
thinking about this some more. i think given the device target support in TP 1.2 i think i will move to bome for my entire mapping. this why i can split the vci-100 into multiple virtual controllers which will let me cut down the mappings severly. bome is really not that expensive and works quite reliably. but i guess Ean will probably prefer keeping the barrier to entry low and not require bome. then again maybe with DJTT working out a deal to bundle a promo code with all vci-100 and/or overlays the price could be brought down low enough to make requiring bome feasible?
same problem here.. sample toggles the first fx button of unit 1..
have imported the tsi twice, with no results..
i’m having major problems with the latest tsi file for 1.2 pro. firmware upgrade to 1.3 check. overlays applied without incident, check. traktor 1.2.1 installed,check. import and apply tsi 2_4 (tpro 1.2). nothing. not a single button or fader works. zilch. however if i import the file for 1.12, this works fine, barring bugs mentioned, and an issue with the knob mapped to the filter. it dies not reflect the knob on screen, but a half turn of the knob on the controller equals a full turn on traktor pro. is this right???
anyhow that’s not my question really. re: tsi for 1.2 pro, any ideas what is ahppening or am i missing something blindinly obvious?
cheers in advance
twelve 45 UR THE SHIT!
scratch last post, hade a wade through the back postings and my man twelve 45 had sorted it already. now to have some fun!
Thanks for the input on the solving the filter problem. My issue is that my scratch LED seems to be reversed. That is when the light is off I am able to use scratch mode and when the light is on, nothing. Also, as soon as I play something in a deck, scratch mode automatically turns off. Is this a feature of the TSi or have I messed something up?
Ean’s mapping for 1.2 Pro feedback
firmware 1.3
tracktor 1.2 Pro
When I loaded Ean’s new .tsi for the 1.2Pro upgrade it works fine, aside from a few minor bugs which I’m assuming Ean will learn and address when he gets a little more time to finish the mapping. I’m guessing that since so many of us were having issues with the 1.2 upgrade, that Ean just wanted to get us something that would work until he could do a full revamp of the mapping.
There are a few bugs I’ve noticed, but the mapping works more or less the way it did before the upgrade.
These are the bugs I can think of at the moment that I’ve realized.
Pitch fader: If I only have one deck playing and nothing synced to it, I get a +/-100% pitch range; when I have a deck synced to it, I get roughly +/- 8%. Also it seems that sometimes I can change the speed on the master deck and the other decks that are ‘synced’ to it, don’t change speed with the master, they stay at the synced speed. Occasionally, however, they will stay in sync. Minor issue that I’m able to work around pretty easily.
Sample button: As far as I can tell does nothing. I’m guessing that Ean hasn’t got to this one yet with the 1.2 upgrade.
Juggle button (not knob): Occasionally the juggle button seems to toggle on Deck B. Explanation: When I load a new track I almost always hit sync immediately, then hold down juggle button to jump to cue point 1(sync button), then hit play as soon as the broadcasting deck gets to it’s first beat of a measure. Sometimes when I do this the juggle light is still on (unnoticed) and when I hit play button it adds Cue point 4 on top of Cue point 1, or it jumps to Cue point 4, without playing. Cured by hitting the juggle button again to toggle it off. So far I’ve only noticed this happening on Deck B and not every time, so it may be something to do with my timing in releasing the buttons, not sure yet.
All basic functions seem to work just fine. Faders and knobs correspond to their onscreen positions and all faders, buttons, and knobs work great aside from the sample button. I’m hoping that Ean has done his testing and is, as we wait (patiently), working out the bugs so he can give us a fully functional new .tsi sometime this month (fingers crossed).
Thanks again to Ean for sharing his expertise in midi mapping with all of us. I have faith that he will work it out in the near future.
question:
when i press play the light on my black vci, just turns to blue the second i press it. as soon as i release the button the light turns to white again.
in this way it is not possible to see the status on the unit.
any ideas?
cheers
chill
i have tested the following:
with an other regular unit, firmware version 1.2 and tp 1.2.1.
it is the same issue. it is not possible to use the forth knob of the bottom line knobs on the left or right deck as play/pause button, because you can’t adjust the on/off state of the led for this button.
smae behaviour with t3.4.
any ideas?
what am i doing wrong?
don’t you guys hate that with ean’s tsi you don’t see the playing status of a deck directly on the unit?
cheers
chill
No. I don’t see the benefit of having such feedback from the VCI. if there is music coming from the speaker or my headphones, I know the deck is playing. if there is a moving waveform onscreen, I know the deck is playing. If i pushed play, i know the deck is playing. why would i need more information than all that?
then again you refer to buttons as knobs.
So all of a sudden now when I fiddle with the gain knob on the VCI (using the latest mapping on Traktor 1.2), the entire track scrolls back and forth and the sound cuts out completely. The software seems to think it is still playing music but there is no sound coming out anymore and the gain knob has this bizarre effect on the waveform - it scrolls from beginning to end of the song as you turn the knob. I don’t see any duplicate mapping in the controller-manager. Any idea what went wrong?
This is probably an easy one but couldn’t find it: the default loop button makes a loop over 8 beats, I’d like to change the preset to 4 beats. I’ve been looking around to see where the 8 is hardcoded but no luck 
Any hints are greatly appreciated!
Just go into the midi window and look for that loop command, and then under there you can change it to 4.