I’m all for the 14-bit midi
I would also rather have a plain vanilla firmware where no button or knob sent more than one message and all the buttons just sent midi messages and didn’t link to any othe rbuttons or functions or pages etc…
This would allow much more ability to program everything in midi translator and traktor… something closer to 1.2 but without the weird things like the effects buttons being linked the effects section and such…
also control over all LEDs
Everyone should be using 1.3 because its much better than 1.2 in bug fixes alone but you should be programing in 1.2 to not deal with multible messages. i have yet to be able to re-create the fader FX functions in Traktor Pro- if anyone else can find a way I would be most grateful!
this will break all previous mappings- is it really that important?
can you tell me exactly how you would use the double crossfader?
I really have to agree with a previous poster here and state that there are some hardware shift states that are required (the jog wheel scratch/seek and the FX bank for instance) This allows us to build different characteristics for the hardware into each layer.
Ok- I am in the final stages of defining this firmware so get your feedback in now guys!
Yes, sure! 
In that way we can use the crossfader as FX X-Fader: on the center position both dry/wet knobs are at 0%, if you move the X-Fader on the left, FX1 Dry/Wet increase and on top left, Freeze… the same on the right, but for FX2…
So, it will be cool if on the top left and on the top right there are two freeze notes…
Hope you understand…
Nope, don’t think so. From my perspective, improving LEDs and maybe killswitches would be more important … and … being able to actually order an upgrade kit with the new and improved firmware, of course
I hope I’m not to late for my request Ean, or if it’s actually possible.
Maybe it’s possible to change the firmware, so that I can use the scratch/juggle
buttons for another functions.
I use only the (light on) scratch function.
maybe is it possible to assign the scratch or juggle function in TPro software (always on?).
or maybe just one knob for 2 jogwheels.
I hope this make sense.
I assembled all of my issues with the default VCI-100 firmware in this thread:
(that by the way got locked, and I got referred to this thread, which really doesn’t adress many of my issues since this is a VCI-100 SE thread if I’m not mistaken?)
Anyhow… how do you create your own firmware Ean/Admins? Do you have an Vestax hookup helping you out, our have you figured it all out by yourselves?
I’d love to dig in and do some firmware modding, if just anyone pointed me in the right direction (and of course share it with everyone on this board)
Vestax provides the firmware to Eans spec.
We dont have access to the source code, know any master hackers?
Of course I do.
Alright… are there a complete list of all the button and knobs midi-notes somewhere for firmware 1.3?
This isnt a VCI-100 SE thread, this is for all VCI-100’s, both the original and the SE included. This VERY much applies to your issues, infact so much that every single one of your requests is already being delt with as we speak within this thread - and anything that hasnt already been mentioned in this thread i have talked to Ean about personally and is being delt with.
If you got hacker friends download the firmware and get them starting to reverse engineer the firmware! Im sure a few members of this forum would even donate some $ for the effort when it was finished, i know i would !
VCI-100 = VCI-100 with Firmware 1.1 - 1.2
VCI-100SE = VCI-100 with Firmware 1.3
Alright, then I obviously missed that.
How much is left before we have created a “default” VCI firmware?
Now I’m a bit lost… Just to get things straight:
Ean sends specifications to Vestax, and is then sent a working firmware back with the settings of his choice. Why is there any need to reverse engineer the firmware back at all with this Vestax hookup?
This oversimplifies the process some what, it takes a long time to organise these changes , and software engineers are far from cheap so vestax is spending money to impliment these changes for Ean, hence they arent going to be interested in continuing to release updates everytime someone thinks of a cool feature.
With source code every body with basic programming skills could have a shot at personalising the VCIs functions to meet their own needs.
Oh Yes!!! 
To Vestax: Open source PLEASE!!!
We can make a petition and try to persuade Vestax to release the source code…
My main suggestion are:
When version 1.4 is going to be available?
Thanks again Ean, you really rock!
Hi,
I know that in version 1.3 pitch sliders send two different MIDI signals, depending on the mode, for pitch or effect control (IMO, not really important with Traktor Pro modifiers…). Here, what I am suggesting is completely different… One MIDI signals when moving up from the click point and a different one when moving down to improve the resolution and the precision of pitch selection (similar to the way the filter knob is working on firmware 1.3…).
Thanks!
Are there a list of all of the modifications somewhere? MIDI-wise that is, I’m not interested in a specifikation of the particular midi-mappings inside traktor.
Not yet the details will be released at a later date.
Alright, thanks a lot.
Can anyone with knowledgeable insight tell me if the VCI-100 hardware is capable of 14bit MIDI?
Im excited to see the direction the VCI-100 will take with these new changes. but for some reason I cant see the 14bit MIDI out put happening.
More than welcome to enlighten me if Im out of line for thinking that.
Interested to know this as well.