Genius work.!
i fucking love you. good work man.
Holy shit!
Sweeet!!!
New 1.3.3 (final?) version is here!
Ok, here is a new version of the firmware, this time I integrated almost all the requests I received.
I still don’t know if improving the jog wheel resolution really helps as I’m not into scratching, and I didn’t get any feedback. It may be more sensitive to vibrations as it’s more precise. That’s why I included two different firmware files, one with improved jog wheel resolution and the other without.
Enjoy!
DaveX
Features (new features since 1.3.2 are in bold)
- 4x Pitch faders resolution
- 4x Jog wheels resolution
- “Play” buttons (VCI-100 SE mapping) could be lit using MIDI out messages
- Left sync button behaves like right one (no more hardware toggle)
- Filter knobs send both regular 0-127 CC signal along with one for each side
- A MIDI CC command is sent along with the Note ON command when the pitch fader is centered (so it’s possible to reach the exactly the center position even using the DJTT mappings)
- Outer part of jog wheels sends Midi ON/OFF message on separate channel when in scratch mode (channel 2)
This is awesome! I can’t wait to try this out. I will be testing it soon and after doing so I will make a modified version of the most current VCI-100 mapping (3.5.2) to reflect the changes in this firmware so those who upgrade can experience the improved VCI-100 functionality.
And for those wondering, DJTT has been in communication with DaveX regarding firmware modifications. We’re just so happily surprised that all our requests were implemented so quickly! Three cheers for DaveX.
I’ll go ahead and ask the question. Is there any way this firmware can damage the VCI or render it inoperable? No offense DaveX, it’s just that your first post to the forum is such a huge deal and almost seems to good to be true. And we all know that things that seem to good to be true usually aren’t. 
Now I’m silently cursing that I ordered my VCI-100 too soon. Had I been a month later, perhaps it could have come standard with DaveX’s firmware installed. 
I feel your worries, photojojo. I hang around on quite a lot of forums and sometimes you do wonder at a poster’s credibility when he / she has a virtually nil postcount or has a very recent joining date.
Nothing personal, DaveX and it seems that you’ve been most helpful and knowledgeable. Guess your work will give the VCI-100 a greater boost to what Ean and buddies have already done. Vestax should pay you guys!
The DJTT staff are all over testing this, so wait for our reports unless you are confortable with reflashing microcontrollers, in which case join us in testing!
That’s what we keep saying. Without these mappings, do you think the VCI-100 would have a cult following and a hugely increased lifespan? From Vestax’s side, however, their older products eclipsing their newer ones (like VCI-300) is not good business for them. Turnover is what they want - they want you to try the new hot hardware each season. So, IMO, it seems we are at an impasse - some parts good, some parts bad, zero sum.
The move to proprietory interface, HID-based controllers, however, is a different matter. Nasty for the homebrew world, bad for future proofing. There may well be more decompiling and hacking firmware in our futures.
Can we not switch back and forth between firmware versions with this one? If i install it and dont like it will i have to take it apart again and reinstall the old version to get the functionality i have now back?
Oh, don’t get me wrong. I wasn’t saying or hinting anything negative (directly or otherwise). I myself wouldn’t hesitate from version 1.3.1 onwards had I the firmware upgrade kit on hand. Besides that, my VCI-100’s all disassembled and the top cover’s back in the sprayshop after a slight incident tore off the initial paint.
I’m definitely not a programmer so in layman’s speak, would increasing the resolution of the pitch faders allow them a wider range of tempo changes or make them more sensitive in real world usage? I noticed that the current bpm changes are around + / - 0.10+ with each nudge.
If this means the VCI 100 can have near enough the jog wheel scratch sensitivity as the VCI 300 then I’m going to be all over this firmware. Unfortunately I’ll have to wait until the weekend in order to upgrade. Can Ean and the crew perform the upgrade and report back as to me this sounds like front page news! I remember when every VCI 100 owner was pining for 1.4 firmware from Vestax/Ean and now it seems we may finally have our wish from DaveX (who needs more than a Nobel Peace Prize if he has vastly improved the VCI 100). I also think a Youtube comparison video on 1.3 vs 1.3.onwards firmware needs to be done, so we can digitally hear and see the differences in pitch and jog wheel sensitivity. All in all, great work and I salute you, DaveX.
aarggghhhh!!! i was gonna do this tomorrow and have been reading up how to flash.as i bought my vci as a 1.3 im guessing that i would have to buy a firmware kit.can someone let me know if this is the case as i will have to order one.thanx
Yes you will need the firmware kit.
Sounds like you already know where the threads are.
thanx.hope this comes good photojojo.coz im gonna have pristine faders and jogs now
this would be the icing on the cake.
So incredibly glad I accidentally ordered a firmware upgrade kit with my vci-100. now to dig it out of my garage o_o;
Great work DaveX, really looking forward to hearing back from the DJTT crew on these changes
Sorry to sound like a noob as this is way over my head, but will the higher precision mean more midi messages and possibly more pops and crackles from midi overload?
I’ll wait for the tests but this is exciting stuff…
Another thing which needs confirming is will Traktor be able to utilise the higher performance jog and pitch faders? As with the VCI 300, doesn’t the Itch software allow the jogs and faders to utilise the 14bit precision? Someone correct me if I’m wrong.
Edit: I thought there may be a problem with left sync led in 1.3.3 but after testing everything’s right!
Short answer: No. The maximum frequency of midi messages on 1.3 firmware is achieved when you scratch/seek on both jog wheels at the same time. This frequency doesn’t increase in 1.3.x, but the relative value sent in the midi messages is more precise. So if you’re able to scratch on 1.3 without and pops and crackles, you shouldn’t have any problems with 1.3.x.
Yes, Traktor is able to use both signals at high precision, I tested it and it works just fine.
Help!
Hi DaveX,
I’m going to try this firmware upgrade tonight but reading the text file about changing the Traktor mappings, I was wondering if you could explain further (maybe step by step if poss). e.g.:
How to:
- Remap your controllers:
- Deck A/C Tempo = CH02.PitchBend
- Deck B/D Tempo = CH03.PitchBend
- Deck A/C Tempo Reset = CH02.Note.C0
- Deck B/D Tempo Reset = CH02.Note.C#0
- Divide the jog wheel sensibility by 4 when using the high precision file
I am not an expert in the midi mappings so if you could help with this it would be appreciated as I am DJing tomorow night.
Thanks
with updates and improvements like these the VCI 100 could become the sl1200 of controllers