Download the Updated VCI-100SE Mapping (3_5_2) Due to popular demand, the DJTechtools VCI-100SE ver. 3_5_1 tsi mapping ( http://www.djranking
s.com/community
/showthread.php?t=12739) has been updated to a newer version, 3_5_2! This update has fixed most all of the remaining bugs, incorporated some community
user's requests, and has added some new functionality to the mapping as well.
There is also now a lengthy and thorough 9 page TSI Walkthrough document that is included in the attached zip file that explains the basic functionality of the mapping and its features (including some new ones). A huge thanks goes out to pilmat for his huge help with the walkthough!
The following bugs have been fixed since 3_5_1:
- Outer Jog Wheel now controls Tempo Bend in Fader FX Mode
- Outer Jog Wheel now controls Tempo Bend while holding SLICE/ECHO buttons
- When holding SLICE/ECHO, only the jog wheel of the Deck you press the SLICE/ECHO button on will control the SLICE/ECHO parameters.
- Modifier3 would get stuck if you were holding Shift and one of the Bottom4 buttons and released Shift first.
- When copying layered decks (A->C or B->D) the volume of the copied deck (C/D) defaults to zero now to avoid the volume jump.
- In Fader FX mode w/Scratch off the Right deck, spinning the jog wheel quickly would turn on FX2 Effect1 but not release it, now it does.
The following features have been added since 3_5_1:
- Shift+Filter = Key Control
- Shift+Slice = Slice Toggled On
- Shift+Echo = Echo Freeze (aka Echo+Feedback) Toggled On
- Shift+FX Preset 1 = Cruise Mode
- Shift+FX Preset 2 = Tree Browser Up
- Shift+FX Preset 3 = Tree Browser Down
- SHift+FX Preset 4 = Tree Browser Expand/Collapse
One of the requested features I couldn't implement was offsetting the LEDs of the four bottom buttons (for non-Arcades) in Juggle Mode to differentiate 1-4 & 5-8. I liked the idea but couldn't get it to work for those LEDs for some reason. Sorry, it'll be looked into further in the future.
If anyone finds any bugs or odd functionalities with this updated mapping, please let me know (via this thread)!
Requirements
You must have Traktor 1.24 or later to use this file otherwise it will not import properly.
To Load this file
Select the BIG import button in the lower left hand corner of the preferences tab.
If this is your first time loading the TSI file, please load it 2 TIMES for the fx to load properly.
The 1st and 2nd time you run Traktor after importing this TSI file, the controller may lock up in fader fx mode. Just quit and re-open the program twice and the issue should go away.
What Settings to Load
|
Leeanna Ayla
18.07.2010 |
Originally Posted by Gianmarco
Note: this new mapping might change the mono/no mono setting you may have in your outputs. It did to me.
So be sure to check your outputs after you import it
-Gianmarco
Changed a bunch of my settings. Such as analyze on startup, and a few other things. Not a big deal though. |
Meg Reinoehl
18.07.2010 |
Originally Posted by djproben
Ahhh that does make sense to me now... so, yes, I was being dense. Sorry I didn't mean to cause offense. Yes I was expecting it to be set up like a turntable; I'll play around in the mapping myself and see if I can set it up a way that is more intuitive for me.
No offense taken. |
Takisha Hodulik
17.07.2010 | Note: this new mapping might change the mono/no mono setting you may have in your outputs. It did to me.
So be sure to check your outputs after you import it
-Gianmarco |
Danae Dumler
17.07.2010 | Ahhh that does make sense to me now... so, yes, I was being dense. Sorry I didn't mean to cause offense. Yes I was expecting it to be set up like a turntable; I'll play around in the mapping myself and see if I can set it up a way that is more intuitive for me. |
Meg Reinoehl
16.07.2010 |
Originally Posted by djproben
I'm sorry this makes no sense to me -- am I being dense here? The problem is not where it's initially set but the behavior when you move it. Even a slight touch on the pitch slider makes the actual pitch jump dramatically. Obviously this is completely unacceptable when the track is playing. I sometimes use an x-session pro with pitch sliders mapped and the mapping I use there does not have the same behavior - a small movement of the pitch slider leads to a small movement of the tempo, just as a real pitch slider would do. If this behavior is intentional for some reason that is fine, but does anyone know of an easy way to map the pitch sliders in the normal way so that they work as actual pitch sliders rather than creating such a huge noticeable jump in tempo when they are touched?
I believe the behavior is due to where the mapping has 0% set to. Because it's set to 0-16% rather than -8/+8, when you move the pitch slider from the middle position, you're actually moving it to the +8 position since +8% would be right in the middle.
Now, whether or not you like this is another topic, I was just trying to explain what exactly was going on.
Personally, it's extremely rare that I play anything at a negative pitch value, so it doesn't bother me to work around this. But it would be more intuitive to have it set to -8/+8 so that the pitch fader could be set to the middle position and work like a turntable would. |
Takisha Hodulik
16.07.2010 |
Originally Posted by djproben
I'm sorry this makes no sense to me -- am I being dense here? The problem is not where it's initially set but the behavior when you move it. Even a slight touch on the pitch slider makes the actual pitch jump dramatically. Obviously this is completely unacceptable when the track is playing. I sometimes use an x-session pro with pitch sliders mapped and the mapping I use there does not have the same behavior - a small movement of the pitch slider leads to a small movement of the tempo, just as a real pitch slider would do. If this behavior is intentional for some reason that is fine, but does anyone know of an easy way to map the pitch sliders in the normal way so that they work as actual pitch sliders rather than creating such a huge noticeable jump in tempo when they are touched?
The issue, as far as I know, is being worked on. Some of us are supplying the DJTT team with information on when it is happening and under what circumstances so that they may better find a solution.
I already stated on a previous post on how to initially fix the problem before you start mixing.
And if you did not bother reading that or do not want to do it there is a way to make it easier (assuming you have it set to no more than like 10%, maybe 35%...MAYBE)
Here is what I do. When a track is playing move the pitch bend ad IMMEDIATELY click shift and recalibrate to middle position (with key lock on of course). You can easily do this in literally less than half a second, should go unnnoticed.
-Gianmarco |
Danae Dumler
16.07.2010 |
Originally Posted by No Left Turn
Ahh, apparently the .tsi has 0% set to the top of the pitch slider (where -8 normally is). So when you start Traktor with the pitch slider at the center position (or 0%), that's normally +8% and moving the pitch slider will adjust the pitch accordingly. If you start Traktor with the pitch slider at the top position, you'll see that the pitch slider in Traktor doesn't jump or anything and will have a range of 0-16%.
I figured this was the way the .tsi worked so I've never thought of it as a bug. Ean even mentions this in the mapping tutorial videos.
I'm sorry this makes no sense to me -- am I being dense here? The problem is not where it's initially set but the behavior when you move it. Even a slight touch on the pitch slider makes the actual pitch jump dramatically. Obviously this is completely unacceptable when the track is playing. I sometimes use an x-session pro with pitch sliders mapped and the mapping I use there does not have the same behavior - a small movement of the pitch slider leads to a small movement of the tempo, just as a real pitch slider would do. If this behavior is intentional for some reason that is fine, but does anyone know of an easy way to map the pitch sliders in the normal way so that they work as actual pitch sliders rather than creating such a huge noticeable jump in tempo when they are touched? |
Leeanna Ayla
16.07.2010 | @flashflooder I sent you a few typo corrections to the walk through via email. |
Scarlett Saupp
15.07.2010 | Excellent to see another update with all the work you guys have been putting into the MF. Ean's mentioned how hectic things have been, so a big thank you from me for this.
Looking forward to loading this up and playing with it this weekend |
Meg Reinoehl
15.07.2010 |
Originally Posted by photojojo
Start Traktor, load a track, start the track, then move the pitch slider. How far is the initial movement? A few of us are seeing 8% as the initial pitch range adjustment. If you hold shift and move your pitch slider to center on the controller it zeros it out and doesn't appear to happen again until you start traktor up again. Even when everything was already at zero from the start.
Ahh, apparently the .tsi has 0% set to the top of the pitch slider (where -8 normally is). So when you start Traktor with the pitch slider at the center position (or 0%), that's normally +8% and moving the pitch slider will adjust the pitch accordingly. If you start Traktor with the pitch slider at the top position, you'll see that the pitch slider in Traktor doesn't jump or anything and will have a range of 0-16%.
I figured this was the way the .tsi worked so I've never thought of it as a bug. Ean even mentions this in the mapping tutorial videos. |
Merlyn Komula
15.07.2010 | @ ff
Thanx dude got the email!!! Time to take a test run!!!
SS |
Leeanna Ayla
15.07.2010 | I've done a quick run through and it seems everything I pointed out is fixed. Great job!!! I'll post if I find anything else. |
Merlyn Komula
15.07.2010 | @ FF
Hey can u post the zip like u did on 3.5.1! Two ways of dl, or can anyone just repost it here please or send me an email!
[email protected]
thanx dudes
SS |
Meg Reinoehl
15.07.2010 | Loving the quick support! Can't wait to try this when I get home. |
Jodi Lacerra
15.07.2010 | A new updated zip file has been attached to the initial post in this thread. If you downloaded it before this post, please re-download it since the mapping and walkthrough have both been updated.
Thanks to everyone who provided quick initial feedback on this mapping! All of the issues that were brought up seem to be solved now; however, if anyone finds anything else please let me know. |
Takisha Hodulik
15.07.2010 |
Originally Posted by photojojo
From Phill's walk through which you've obvioulsy not had to time to read either
SHIFT + JUGGLE 1-4 will toggle Snap on/off
SHIFT + JUGGLE 5-8 will toggle Quantize on/off
my appologies, i have not had the time to read that, let alone try the new mapping
Anyways, in terms of the pitch jump issue, i ran some short tests
Steps:
-Turned on traktor, then VCI, moved the pitch bend, recalibrate after it jumped, problem solved. turned VCI on and off (while traktor was still on), problem did not happen again.
-Turned on VCI before traktor, turned traktor on, moved pitch fader and re calibrated once it jumped, problem solved. turned VCI on and off (while traktor was still on), problem did not happen again.
From this, it seems that the problem is with traktor. So after fixing the problem after I start it, it does not happen again until after I start traktor again. It does not matter (it seems) how many times I turn the VCI on and off while traktor itself is on.
Another note: the pitch always jumps all the way down no matter if u move it slightly up or down on the controller.
I did this test on all 5 pitch settings (8%, 10%, 35%, 50%, and 100%). On all instances they all moved all the way to the lower extrema if i moved the pitch bender down or up.
This test DOES NOT show if there are any problems after a while of use
NOTE: this is with the 3_5_1 mapping AND I FORGOT TO TEST DECKS C AND D! silly me
hope this helped
-gm |
Leeanna Ayla
15.07.2010 |
Originally Posted by Gianmarco
This.
I have not had time to run tests, but I will when I have the time
I do hace one recommendation:
Shift+List Up = Snap(SNP) on/off
Shift+List Down = Quantize (QNT) on/off
Im my opinion....THIS WOULD BE SO USEFUL!!!!!!!
-Gianmarco
From Phill's walk through which you've obvioulsy not had to time to read either
SHIFT + JUGGLE 1-4 will toggle Snap on/off
SHIFT + JUGGLE 5-8 will toggle Quantize on/off |
Takisha Hodulik
15.07.2010 |
Originally Posted by pilmat
As a general rule, you should always check ALL your knobs/faders every time you start Traktor.
Phil.
ditto
I do this all the time, i mean believe about it, rock bands sound check all the time before shows, same thing should be done here
-gm |
Takisha Hodulik
15.07.2010 |
Originally Posted by photojojo
Start Traktor, load a track, start the track, then move the pitch slider. How far is the initial movement? A few of us are seeing 8% as the initial pitch range adjustment. If you hold shift and move your pitch slider to center on the controller it zeros it out and doesn't appear to happen again until you start traktor up again. Even when everything was already at zero from the start.
This.
I have not had time to run tests, but I will when I have the time
I do hace one recommendation:
Shift+List Up = Snap(SNP) on/off
Shift+List Down = Quantize (QNT) on/off
Im my opinion....THIS WOULD BE SO USEFUL!!!!!!!
-Gianmarco |
Leeanna Ayla
15.07.2010 |
Originally Posted by No Left Turn
What exactly is this issue? I've heard it mentioned in this community
a few times now. I sort of have an idea of what you're describing in this thread, but not exactly...
Start Traktor, load a track, start the track, then move the pitch slider. How far is the initial movement? A few of us are seeing 8% as the initial pitch range adjustment. If you hold shift and move your pitch slider to center on the controller it zeros it out and doesn't appear to happen again until you start traktor up again. Even when everything was already at zero from the start. |
Meg Reinoehl
15.07.2010 |
Originally Posted by Gianmarco
the pitch bend issue (the jmpin thing) wasnt fixed
good job anyways!
-gm
What exactly is this issue? I've heard it mentioned in this community
a few times now. I sort of have an idea of what you're describing in this thread, but not exactly... |
Lilliana Perris
15.07.2010 | Question:
If you only have FM1.2 and the 2.5 TSI overlay.....can I still use this 3.5.2 TSI?
Is it VERY different?
I guess I will answer my own question when I go through the content of the ZIP file.
Really wanting Fader FX....
|
Leeanna Ayla
15.07.2010 |
Originally Posted by pilmat
As a general rule, you should always check ALL your knobs/faders every time you start Traktor.
You sir are correct and I will adopt that as my start ritual.
Originally Posted by pilmat
Cris (flashflooder), we should add this to the walkthrough!
Phil.
You should stress that it needs to be the shift and reset to 0 feature and not just move the physical pitch fader to the center or you'll have a flood of people complaining that they're songs start out pitched up or down. |
Corine Kasman
15.07.2010 |
Originally Posted by photojojo
I believe you're on to something. I tried on each deck from a fresh start of Traktor and when I move the pitch fader the first time on every deck it jumps 8%. If I hold shift and move the fader even just a little then re-center it the next time I move the fader it works normal. So a temporary work around is just to hold shift and re-center all your pitch faders when you start Traktor.
As a general rule, you should always check ALL your knobs/faders every time you start Traktor. When you launch, Traktor has no idea where any of your controls are and either leaves them at the last know position or defaults them (eg. line faders).
My launch and unplug-replug ritual is to go through all the faders (pitch too and reset to zero with the shift). Press Slice and Echo on both decks and at least validate that the knobs in the mixer section equate with the GUI knobs.
Cris (flashflooder), we should add this to the walkthrough!
Phil. |
Leeanna Ayla
16.07.2010 |
Originally Posted by Gianmarco
from what i have experienced with it, its only an initial issue, so before i start i mess with it once, it jumps, then recenter/calibrate it with shift. does not seem to happen until the next time i turn it on
-gm
I believe you're on to something. I tried on each deck from a fresh start of Traktor and when I move the pitch fader the first time on every deck it jumps 8%. If I hold shift and move the fader even just a little then re-center it the next time I move the fader it works normal. So a temporary work around is just to hold shift and re-center all your pitch faders when you start Traktor. |
Corine Kasman
16.07.2010 | Chris (flashflooder), can I suggest you post the walkthrough as a PDF? I believe its easier for everybody (correct me if I'm wrong).
I haven't tried the TSI yet, but I should get to it toevening
.
Phil. |
Jodi Lacerra
16.07.2010 | Thanks guys for the specific details on remaining bugs/issues with this mapping. I will be working on it today and plan to post an updated zip file by the end of the day.
Please let me know anything you find in the meantime and for everyone else, please hold off on downloading these files until I post a cleaner version of the tsi. |
Leeanna Ayla
15.07.2010 | A few more things.
- On initial load FX slot 1 is chained, not sure if this is intentional or not. After selecting an FX preset and clicking the cue button it seems to stay on advanced even after restart.
- While holding shift and pressing copy to left, the track was copied to deck A while the track was playing and stopped playing after it was loaded at the designated load point in the track. This only happened once and I wasn't able to duplicated it. I had just been browsing through the tree on the left when it happened.
- When holding FX preset 2 and pressing either cue button it will scroll up the tree on the left.
- When holding FX preset 3 and pressing either cue button it will scroll down the tree on the left. Seemed to load the proper FX and set the desired value when double clicked.
EDIT:I've just skimmed through Phil's walk through so if any of this is by design please disregard it. I'm going to sit down with it this afternoon and give it a good read to try and learn something. |
Leeanna Ayla
15.07.2010 | Info for decks C and D when in juggle mode, looks to be pretty much the same so maybe it's an easy fix.
- Pressing cue point 1 on deck C and pressing juggle 1-4 toggle play on/off on deck B
- Pressing cue point 2 on deck C and pressing juggle 1-4 toggles play on/off on Deck C
- Pressing cue point 3 on deck C and pressing juggle 1-4 does nothing
- Pressing cue point 4 on deck C and pressing juggle 1-4 does nothing
- Pressing cue points 1-4 on deck D and pressing juggle 1-4 does nothing, play is not activated on any of them.
- Pressing cue point 5 on deck C and pressing juggle 1-4 toggles play on/off on deck D.
- Pressing cue point 6 on deck C and pressing juggle 1-4 toggles play on/off on deck C.
- Pressing cue points 7-8 on Deck C and pressing juggle 1-4 does nothing.
|
Meg Reinoehl
15.07.2010 |
Originally Posted by photojojo
In juggle mode all of the cue points work for, but if a deck is not playing and you press a cue point and hold it then press the juggle 1-4 button it does not activate play.
More details:
- Pressing cue point 1 on deck A and pressing juggle 1-4 toggles play on/off on Deck B
- Pressing cue point 2 on deck A and pressing juggle 1-4 toggles play on/off on Deck A
- Pressing cue point 3 on deck A and pressing juggle 1-4 does nothing
- Pressing cue point 4 on deck A and pressing juggle 1-4 does nothing
- Pressing cue points 1-4 on deck B and pressing juggle 1-4 does nothing, play is not activated on any of them.
- Pressing cue point 5 on deck A and pressing juggle 1-4 toggles play on/off on deck B.
- Pressing cue points 6-8 on Deck A and pressing juggle 1-4 does nothing.
I'll dig into Decks C and D later today.
This is EXACTLY what I described in my previous post. Thanks for making it crystal clear. This is all new to 3.5.2 and did not occur in 3.5.1 |
Meg Reinoehl
15.07.2010 |
Originally Posted by Glen
juggle mode on 1-4 doesnt work for deck b
This works fine for me in 3.5.2 |
Leeanna Ayla
15.07.2010 |
Originally Posted by Glen
juggle mode on 1-4 doesnt work for deck b
In juggle mode all of the cue points work for, but if a deck is not playing and you press a cue point and hold it then press the juggle 1-4 button it does not activate play.
More details:
- Pressing cue point 1 on deck A and pressing juggle 1-4 toggles play on/off on Deck B
- Pressing cue point 2 on deck A and pressing juggle 1-4 toggles play on/off on Deck A
- Pressing cue point 3 on deck A and pressing juggle 1-4 does nothing
- Pressing cue point 4 on deck A and pressing juggle 1-4 does nothing
- Pressing cue points 1-4 on deck B and pressing juggle 1-4 does nothing, play is not activated on any of them.
- Pressing cue point 5 on deck A and pressing juggle 1-4 toggles play on/off on deck B.
- Pressing cue points 7-8 on Deck A and pressing juggle 1-4 does nothing.
EDIT: Changed the last point form "Pressing cue points 6-8 on Deck A and pressing juggle 1-4 does nothing" to Pressing cue points 7-8 on Deck A and pressing juggle 1-4 does nothing.
I'll dig into Decks C and D later today. |
Hang Postman
15.07.2010 | juggle mode on 1-4 doesnt work for deck b |
Leota Saniuk
15.07.2010 | same here using safari .. got it to download in opera. |
Merlyn Komula
15.07.2010 | Having trouble with the zip file!!!
Please supply another dl location please!!!
SS |
Meg Reinoehl
15.07.2010 | The updated mapping is great, but I've found a couple of new issues that are near showstoppers for me. Holding down a hotcue, pressing either Juggle, and then releasing the hotcue no longer allows the deck to continue playing. There are 2 anomalies... 1) holding hotcue 2 of Deck A and pressing Juggle 1-4 will continue playback. This is the only hotcue that this still works with. 2) holding hotcue 1 and pressing Juggle 5-8 will start playback of Deck B and NOT continue playback of Deck A.
Reverting back to 3.5.1 resolves these issues and retains the expected behavior.
Chris, let me know if you need me to explain this further or send you another video of this behavior. |
Leeanna Ayla
14.07.2010 | It's happened to me a couple of times even after I re-calibrate with shift. Before I loaded the new TSI I checked my in/out ports and they were set to all ports. I know they were set to VCI previously though. Wonder if that may have something to do with it? |
Takisha Hodulik
14.07.2010 |
Originally Posted by flashflooder
thanks guys for the input on the pitch/tempo fader jumping issue. i could never get it to jump when i tried to make it (i've had it happen before when i don't want it to) and the functions in the mapping seem to make sense so i didn't have any ideas on how to fix it except for maybe removing the tempo reset (shift+tempo middle point) and seeing if that would do it. If anyone had any insight on exactly when the tempo fader jumps (or a past tsi version someone uses that doesn't experience this issue) would be very helpful!
ill run some experiment in my secret laboratory tomorrow afternoon, hopefully my pesky sister wont come wreaking it again
-gm |
Jodi Lacerra
14.07.2010 | thanks guys for the input on the pitch/tempo fader jumping issue. i could never get it to jump when i tried to make it (i've had it happen before when i don't want it to) and the functions in the mapping seem to make sense so i didn't have any ideas on how to fix it except for maybe removing the tempo reset (shift+tempo middle point) and seeing if that would do it. If anyone has any insight on exactly when the tempo fader jumps (or a past tsi version someone uses that doesn't experience this issue), it would be very helpful! |
Takisha Hodulik
14.07.2010 |
Originally Posted by photojojo
Great work guys!! All of the new stuff seems to work great, but I've just run through it all once. I still get the pitch issue as well. When it happens it's like the fader believes it's at 8% when it's really at 0. It's pretty random, but it seems to happen fairly often. I've started writing down what was going on when it happens.
I'll play around with the new features and see if I can find any bugs this week.
from what i have experienced with it, its only an initial issue, so before i start i mess with it once, it jumps, then recenter/calibrate it with shift. does not seem to happen until the next time i turn it on
-gm |
