Suggestions for further improving the firmware
Suggestions for further improving the firmware Posted on: 19.01.2009 by Madelyn Dunmon Hello!I hope this thread fits in nicely here - I haven't found any where you could post some suggestions for future FW updates, so I thought it would make sense to start one. First of all, I really appreciate the work that went into these mods, and I hope I can contribute a little bit to make these even better! So, here are my suggestions (maybe even for Version 1.4?): 1) Missing MIDI outs Some buttons can not be programmed to switch their LEDs on, even if in theory they should have this capability. So far, I have found the "preview", "set cue" and "cue play" buttons, as well as the jogwheel lights, but I am pretty sure there are more of them lingering around. 2) ability to switch LEDs OFF (and enable BOTH of the Dual LEDs) It would be very nice if we could switch the dual LEDs (with 2 colors) OFF completely. So far I believe this is not possible, since all LEDs only seem to know 2 states. Edit: add the abilty to also switch BOTH LEDs ON at the same time 3) Fix the "flickering LED Bug" I have tried to use a blinking LED to add another visual state to a LED and so far succeded, but there is an annoying bug where all LEDs flicker when you send out a MIDI message to a LED. This is a general problem, but especially annoying with blinking LEDs because then your whole VCI is constantly flickering like a X-mas decoration :eek: 4) dimmable LEDs Not sure is the hardware even allows this, but it would also be nice to able to dim certain LEDs. Would be better in a low light situation, where you don't switch off the LEDs completely, but dim them down so you can still see some light. These general improvments to LEDs would make it possible to use more sophisticated visual feedback on the VCI-100 LEDs And here is another one: 5) Kill switches on all EQ knobs Again, don't know if the hardware allows this, but special kill switch MIDI Notes on _all_ EQ knobs instead of just one would be nice. Would be happy to see some of these suggestions be incorporated in future releases. Discuss and add more to the list if you like and keep up the good work! regards, Frank | |
| Dj Gjaka 06.05.2009 |
Originally Posted by midifidler
|
| Adolf Hit 05.05.2009 |
Originally Posted by sm00sh
10 bit compared to 7 is still 8 times the resolution though |
| Tyrone Digby 05.05.2009 |
Originally Posted by sm00sh
|
| Basil Trykowski 10.03.2009 |
Originally Posted by Emiyanez
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! |
| team DonX 03.03.2009 |
Originally Posted by midifidler
To Vestax: Open source PLEASE!!! We can make a petition and try to persuade Vestax to release the source code... |
| Adolf Hit 02.03.2009 |
Originally Posted by autonic
With source code every body with basic programming skills could have a shot at personalising the VCIs functions to meet their own needs. |
| Karine Noe 02.03.2009 |
Originally Posted by BentoSan
How much is left before we have created a "default" VCI firmware?
Originally Posted by BentoSan
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? |
| Vernon Vanderberg 29.07.2009 | any news on future firmware updates? |
| Florence Alch 13.07.2009 | Iv got a good suggestion for further improving the firmware! ............. release it. |
| Xavier Emanuels 05.07.2009 | 10bit means 1023 steps vs the 128 steps the unit currently is sending over midi - that is a big improvement ! |
| Tawnya Llopiz 05.07.2009 | i would appreciate the support of a 4 band eq mapping. (a kill switch on the 1.3 "filter" (eq low) knob would do it) |
| Adolf Hit 06.05.2009 | erm - I doubt it will have true 14 bit resolution on the faders as the microcontroller the VCI is based around only has 10 bit capability. I would expect the firmware will take the reading, multiply it by 16 and send that as a 14 bit message. |
| Dj Gjaka 06.05.2009 |
Originally Posted by midifidler
|
| Adolf Hit 05.05.2009 |
Originally Posted by sm00sh
10 bit compared to 7 is still 8 times the resolution though |
| Tyrone Digby 05.05.2009 |
Originally Posted by sm00sh
|
| Vernon Vanderberg 10.04.2009 | 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 believeing that. |
| Karine Noe 23.03.2009 | Alright, thanks a lot. |
| Xavier Emanuels 20.03.2009 | Not yet the details will be released at a later date. |
| Karine Noe 15.03.2009 |
Originally Posted by BentoSan
|
| Basil Trykowski 10.03.2009 |
Originally Posted by Emiyanez
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! |
| Basil Trykowski 05.03.2009 | My main suggestion are: - 14 bits MIDI. - All knobs in mixer section sending double MIDI signals (left and rigth) and kill switches. - Pitch sliders also sending double MIDI signals (really usefull for improving precision with such a short faders...). - Improving MIDI out for all buttons. When version 1.4 is going to be available? Thanks again Ean, you really rock! |
| team DonX 03.03.2009 |
Originally Posted by midifidler
To Vestax: Open source PLEASE!!! We can make a petition and try to persuade Vestax to release the source code... |
| Adolf Hit 02.03.2009 |
Originally Posted by autonic
With source code every body with basic programming skills could have a shot at personalising the VCIs functions to meet their own needs. |
| Karine Noe 02.03.2009 |
Originally Posted by BentoSan
How much is left before we have created a "default" VCI firmware?
Originally Posted by BentoSan
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? |
| Yuonne Cauthron 01.03.2009 | VCI-100 = VCI-100 with Firmware 1.1 - 1.2 VCI-100SE = VCI-100 with Firmware 1.3 |
| Xavier Emanuels 01.03.2009 | 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 community would even donate some $ for the effort when it was finished, i know i would ! |
| Karine Noe 01.03.2009 |
Originally Posted by midifidler
Alright... are there a complete list of all the button and knobs midi-notes somewhere for firmware 1.3? |
| Adolf Hit 01.03.2009 | Vestax provides the firmware to Eans spec. We dont have access to the source code, know any master hackers? |
| Karine Noe 01.03.2009 | I assembled all of my issues with the default VCI-100 firmware in this thread: http://www.djranking s.com/community /showthread.php?t=3690 (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) |
| DJ Pablo 22.02.2009 | 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. |
| Madelyn Dunmon 07.02.2009 |
this will break all previous mappings- is it really that important?
|
| team DonX 04.02.2009 |
Originally Posted by eangolde
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... |
| 04.02.2009 |
Originally Posted by thebeatworx
Originally Posted by frankiee
Originally Posted by fcarsana
Originally Posted by deeflash
Ok- I am in the final stages of defining this firmware so get your feedback in now guys! |
| Daniel Lown 03.02.2009 | 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 |
| Ruiz dB 02.02.2009 |
Originally Posted by fcarsana
With the advent of Traktor Pro and modifiers, I believe alot of Fader Fx mode can be emulated. Regardless, my point is that modifiers are a user assignable SOFTWARE feature, not something that is hard coded in the firmware. |
| 02.02.2009 | thanks for the suggestions guys- I appreciate the feedback! |
| team DonX 03.02.2009 |
Originally Posted by thebeatworx
I believe it's not real... Could you please explain it with an example? |
| Ruiz dB 03.02.2009 | I would recommend removing multiple midi notes for the controls in the firmware. It limits the VCI when custom mapping to other applications including Traktor. If multiple notes are required, I'd recommend a software solution (like Bome's) that runs inbetween the VCI and the DJ app in which the user can assign his/her midi sends... |
| DJ Pablo 01.02.2009 | My wishes are Fixing the leds, 14bit midi, If possible double notes on crossfader (for fader efx) |
| Xavier Emanuels 23.01.2009 |
Originally Posted by midifidler
|
<< Back to DJ TechTools' VCI-100 FAQReply