never ever used it!Quote:
Originally Posted by flashflooder
Printable View
never ever used it!Quote:
Originally Posted by flashflooder
+1Quote:
Originally Posted by sno
You ever fix the bug where if i adjust the pitch fader with my hand on the platter, it sends the pitch WAY out of wack; instead of getting an incremental adjustment, it usually goes to -99.9%. It drives me nuts! Any fixes?
you need to upgrade to traktor 2.1.1Quote:
Originally Posted by bmwnutfrombirth
ur best vci mapping yet :) I request an overlay!! :))
I second that emotion! Come on guys, let the VCI go out in style one last proper overlay for TP2!!!! PLEASE!! :)
I also hated that the outer jog wheel no longer controls tempo bend, I used that all the time, can't believe that was made on purpose, I think you're confusing "vibration" with "rotation"... I never had tempo bend altered by a heavy bass in a gig... or maybe your jog wheels doesn't work right, but the mapping needs this, I'll try to fix it , many thanks for the great mapping, anyway... it's not perfect but that should make us learn to map controllers ourselvesQuote:
Originally Posted by flashflooder
Edit: I'm talking about scratch mode ON, so maybe it's just me...
On this newest mapping, we only use fx unit 1 in faderfx mode for all decks. in previous mappings, deck a used fx unit 1 and deck b used fx unit 2. im ok with this change but i still like the option to apply fx to individual channels rather than over the entire mix. i realize this is still possible with this mapping but my issue is this: when touching either jog wheel while in fader fx, fx unit 1 is engaged but remains engaged when you lift your finger off the jog wheel. let me explain by example: two track are playing, one in deck a, the other in deck b. fader fx mode is on and if i touch the jog wheel for deck a, fx unit 1 is engaged and heard over deck a. when i lift my finger off the jogwheel, fx unit 1 is still engaged for deck a. now when i touch jogwheel b, the fx is played over the whole mix rather than just deck b because fx unit 1 is still engaged on deck a. it should behave like the volume fader in fader fx mode where the fx is off until you move the slider down and when you move it all the way back up, the fx unit 1 disengages. so my question is this: how do i map it so that when touching the jogwheel, fx unit 1 is engaged (like it does already) but when lifting my finger off the jogwheel, fx unit 1 is disengaged?
thank you for your time in helping me solve this problem
it seems like you need to change Interaction mode from "toggle" to "hold"
I just made an update to the mapping (now v4.1 which I re-uploaded to the initial post) which fixes the following:
- LED issues for the bottom 4 buttons on each deck. I decided to use klaemo's dynamic LEDs in Juggle Mode which will be on if a Hotcue is present because it is nice extra feedback and for those (like me) with an arcade, I never have any visual feedback so I think it's fair to use.
- Fixes the Fader FX scratch off bug, removes the Shift+Jog set Hotcue functionality
- Adds Shift+Jog move to be a quick track seek (which works with scratch on or off)
quick track seek ftw!
awesome work Flashflooder and klaemo too!
+1Quote:
Originally Posted by arumdevil
i cannot download the newer tsi, i download it and its a .xml file
if i remove this extension it is correctly see as .tsi, but traktor doesn't import it
edit : working using firefox instead of safari
excellent stuff! thanks a lot!Quote:
Originally Posted by flashflooder
one question: is it just me or does anyone else have the issue that the cue/headphone led doesnt light up anymore for the selected deck?
Hmm I'm having trouble with version 4.1 in that scrolling through a song with the jog wheels doesn't work but the super speed shift scroll does work.
Edit: Nevermind I just added the older version on top of 4.1 using the smaller import button and it seems to work
Edit: Wait no still having problems, 4.1 scrolling through tracks using the jogs doesn't work.
Yeah exactly the same problem for me; both in scratch and not in scratch mode the jog wheels no longer search through the song. Tried re-mapping 'seek position' to the two midi output signals from the jog wheels but no joy.Quote:
Originally Posted by brosephh
Any ideas Flashflooder? Super keen to combine this version with my X1 mapped for decks C+D for that "pretending you have an S4" feeling.
Are you guys both sure that you have v1.4 firmware on your VCI-100? I have not tested this mapping on v1.3 so I wouldn't be surprised if there was some buggy behavior on v1.3 (and I know that the jog wheel midi signals changed from fw 1.3 to 1.4).Quote:
Originally Posted by buckwilder
If you are sure that you are using 1.4 FW and the latest version of Traktor and are still having the issue, either email or PM me so we can delve a little deeper into what the issue might be.
I cannot replicate this issue you are having. Did you figure out a fix? Otherwise, are you sure you are using VCI-100 FW 1.4 and the latest version of Traktor Pro v2.1.1? That is what I used for my testing.Quote:
Originally Posted by awesomesoundtrooper
There's also a chance that those LEDs died out. It is not too uncommon and I've had a few die in my VCI-100 over its lifetime.
you can check for defective leds using the hardware test mode: http://www.djtechtools.com/forum/sho...79&postcount=8Quote:
Originally Posted by flashflooder
That might just be the case. Just tried disco mode and they didn't light up.Quote:
Originally Posted by flashflooder
I had the same issue with the left echo button which wouldn't turn blue anymore. But as today it seems to be working again. :)
I'm going back to 3.6.4. Playing around with a couple of other people made it all too clear that the v4 mapping isn't for me right now.
On my rig the LEDs on the Loop, Scratch, FaderFX and Juggle buttons kept on burning even though I was switching them on and off multiple times. No fun showing off your digital gear to people used to Vinyl and CDJs when there's still a lot of bugs around (at least with my self-modded -100).
I confirm the scratch issue, when scratch is on, you just can't scratch. It stops the track, but impossible to move back and forth. Jog seek works though, good work on that as well as the hotcue tap thingy...:)
I imported Klaemo's fix on the top of it and it works pretty well though (dunno if it its actually combined or if if it's just the original one...) :) but I prefered the old fx assignation anyways.
Oh yeah, I wanted to point that out btw, you can't fader fx both track at the same time with the new version, kinda is a problem on big buildups imo.. :eek:
Why do you say that?Quote:
Originally Posted by Koesj
Multiple people have mentioned this issue to me but for most people, updating to the latest version of Traktor Pro solved this issue. Some others were not importing the tsi properly and some were not setting their ports correctly. Others also seem to think they have FW 1.4 when they actually have FW 1.3.Quote:
Originally Posted by Pedrotax
To date I have not been able to find any patterns to this issue or replicate it myself. If you have any clues as to why this is occurring for you, please let me know.
Yes, Fader FX was changed to use one FX bank instead of two. I totally understand your reasoning for needing two, the change was made mainly to accommodate other FX controllers such as our Midi Fighter. This change made the mappings work together more smoothly. If it is a major issue for you I would use klaemo's change for now. If I have some time in the future, I will try to update klameo's mapping on that with the new changes I made in the updated version. Thanks for your feedback.Quote:
Oh yeah, I wanted to point that out btw, you can't fader fx both track at the same time with the new version, kinda is a problem on big buildups imo.. :eek:
Im having the exact same issue. Loaded up the tsi before a gig and was like "wtf", the platters would not scratch.Quote:
Originally Posted by Pedrotax
My vci shows up as the 1.4 HD firmware inside traktor.
For the scratch issue it's alright, not that important now that I'm using the fix, and indeed might be caused by my version of Traktor, since i'm pretty sure about the firmware and mapping importation... Don't need to make it a priority imho :)Quote:
Originally Posted by flashflooder
I'm convinced both versions of the mapping should be carried on though, they both work well for different purposes. ;)
As for the midifighter explanation, I figured that out as I checked out some of the MF threads concerning those issues. So well done for that :D
Thx for the clear explanation.
hey im using Klaemo's version because i like being able to apply effects to each deck independently but i think ive found a bug id like to confirm:
in fader fx mode touching the right jog wheel should immediately engage fx unit 2 for deck b. (touching the platter of the left deck while in fader fx mode, turns on fx unit 1 for deck a)
but touching the platter of the right deck while fader fx mode does not turn on effect unit 2......effect unit 2 is turned on when REMOVING my finger from the platter.
do you get this behavior?
thanks by the way for sharing this version with me!
Traktor cannot directly tell you whether your VCI-100 is FW 1.4. I assume you are looking in the Controller Manager and are seeing that I put "[FW 1.4]" in the mapping name. This means that the mapping is designed for FW 1.4, not that your VCI-100 is FW 1.4.Quote:
Originally Posted by SHUJINCELL
However, there are ways that you can determine whether you have FW 1.4 in Traktor after having this mapping loaded. One way is to move a Pitch fader and see what the minimum bpm increment is. If it is .04 then you should have FW 1.4, if the minimum movement is .16 then you have FW 1.3.
People seem to be continually getting confused with whether their VCI-100 is FW 1.4 or an older FW version. Personally, I recommend that everyone upgrades to FW 1.4 as the higher resolution pitch faders and jog wheels have a lot of benefit. Additionally, FW 1.4 fixed a lot of LEDs to allow control via Midi.
However, I will try to add back in the old jog wheel midi commands so people with FW 1.3 can use this new mapping without scratch issues. Not sure exactly when I'll have time to do this but hopefully within a week or so.
Hi all,
Been using DJTT VCI maps for some years and never had a problem breaking the chain for fx when importing. Always big import out after new tsi added and double load with big import in. I can't get this fx chain to break whatsoever. Very strange as I had no issue with 4.0. Anyone had a problem? Is there something i'm missing? Have the presets been altered in this mapping? May have to go back to 4.0 and live with the bugs as i can't resolve this. Any suggestions?
I'm using 1.4 fw with Traktor 2.0.3 on Mac. 2.1.1 too broken imo.
Could you please explain what you mean by "breaking the chain for fx when importing"?Quote:
Originally Posted by D-Kem
Also, I would recommend upgrading to Traktor 2.1.1 as a few users mentioned issues with this mapping on older v2 Traktor Pro software but that was fixed for everyone I've heard back from by upgrading Traktor. I am also curious what bugs you were experiencing with 2.1.1 that made it unusable to the point of downgrading to 2.0.3 if you want to share.
Hey fella, any news on the overlay? :)
Thanks for your reply Chris.
Breaking the chain is probably not the the best phrase. Basically the presets won't load as expected. Getting an awful combination on the the 4 preset buttons currently. Double big imported countless times now but no success.
The biggest issue for me was time code failing on the right deck, albeit intermittently. Has happened a couple of times at home and once at a gig whereby it refused to calibrate at all. It stayed in waiting despite switching of cables, carts, vinyl etc. No probs in 2.0.3 and according to the forums i'm not the only user with this issue. There are a host of other bugs which wouldn't have been a deal breaker but the time code is.
2.0.3 currently set up on a different user. Desperate for 2.1.2 as the new time code has arrived but will only work from 2.1.1.
Done! :)Quote:
Originally Posted by flashflooder
If I didn't miss anything, this should be version 4.1 but with the old 3.6.4 FaderFX behavior.
btw, should I start a seperate thread for my mapping? I think, it would make it easier to maintain the two versions.
edit:
I just fixed this, try the new version attached to this post.Quote:
Originally Posted by brianpkelly@hotmail.com
that was a really obscure bug, though.
My jogwheel can only seek through the track if i hold shift. Is it meant to be like that.
Yes.Quote:
Originally Posted by Pandaz
edit: see two posts above, i just fixed this :)Quote:
Originally Posted by brianpkelly@hotmail.com
Updated to the latest version of traktor and it does seem to be quite buggy compared to the previous version. That aside, everything seems to be working correctly except my pitch faders. The faders work but once you move em they jump to a high range and wont center unless you hold shift and move the fader. I've noticed this fader behavior with previous mappings and Im beginning to think that maybe the vci didn't accept the firmware correctly. My pitch faders only worked properly on the first mapping once the firm was reversed engineered and the HD firm was released. Every mapping after that, my pitch faders operated incorrectly.
is anyone else having their VCI-100 freeze while using Fader FX?
I just upgraded to Traktor Pro 2 last night and tried it out with this mapping. I had the same issue before the upgrade and was hoping this would fix it.
Vista
FW 1.4
Traktor Pro 2
Anyone found a fix?
I'm using this mapping (4.1) with a VCI 100 (FW 1.4) in Traktor Pro 2 (2.1.1) and it's been working perfectly for several weeks.