Will there be a f/w update 1.4 for the VCI-100? If so, what might it include, and when would it be available?
Printable View
Will there be a f/w update 1.4 for the VCI-100? If so, what might it include, and when would it be available?
working on it now finally- but no promises on a release date. It would do minor bug fixes and improvements but nothing too major.
any way this would also go from 1.1 or 1.2 straight to 1.4?
Ean, I don't know if you have a log yet for 1.4 requests, but aside from maximizing 10 bits out of the ADC (fingers crossed), can I make a request for the "filter/low(low)" knob to return to a single CC message instead of two?Quote:
Originally Posted by EanGolden
Good work, regardless
any chance of doing something about the lockup-problem with midi-out and windows? i guess lots of windows users are still hoping to get visual feedback on their vci's. the problem is described in serveral threads http://www.djtechtools.com/forum/sho...stability+pollQuote:
Originally Posted by EanGolden
if it's not possible to fix this problem, there is another quite simple thing you could do to give at least limited visual feedback for those who have to deactivate midi-out in order to get a stable system. you could change the behaviour of the following buttons: snap beat, quantize, smaple, loop8 (2x), deck C/D, headphone out (2x), eq fx (2x) and the 4 buttons in the filter-section, so that they light up/change colour after pushing them (if no other midi-command received). currently there are already 3 buttons (2xscratch and deck c) which behave like this (fw1.3). if i press one of those buttons they change colour (deck c) or light up (2x scratch) even if i dont have traktor running.
i hope you understood what i mean. if not, please aks/pm me and i'll explain my suggestion more detailed.
Hopefully this hasn't already been tried and I'm not just spouting old news, but since windows users have been having problems with the midi out on, couldn't you just use Bomes to translate the signals from the VCI and program it to have proper LED feedback without having to update the firmware?
I'm working on a project right now that turns the padKontrol into a 4 deck controller, but since the product supplied mapping software doesn't allow for much, I had to use a combination of Farmpad and Bomes. Since using the non-demo version, I have realized that Bomes can do damn near anything with midi with enough tinkering.
If you made a translator instead of a firmware update, you could update it a lot easier. Just a suggestion.
if things ever slow down for me i will start a project doing an Ean inspired mapping using bome's. the main goal will be to leverage the device target support to severly cut down the size of the mappings. this will hopefully make it alot easier to do some experimenting. also it will simplify using the modifiers, since i will be handling the deck selection inside bomes. and yes this also opens the door for a lot of cool midi feedback and additional modes (like my 8 hotcue special mode i did a while back).
if anyone wants to collaborate. the first step is to just map all the buttons so that they get mapped to 4 virtual midi devices that all send the same MIDI messages.
i haven't tried bomes myself but as much as i remember there have been some users trying to solve the problem with bomes without success. the actual problem isn't the led-feedback but the random freezes you get having midi-out turned on. some of the midi-outputs seem to overcharge the vci (buffer-overload? midi-signals interfering with each other?) which leads to a freeze in traktor. traktor continuous running after switching off the vci. but as long as nobody knows where exactly the problem is, even bomes can't help me.Quote:
Originally Posted by DJPhaidon
i guess it needs somebody with a more detailed technical knowledge of how midi is sent in traktor and how the vci handles the midi inputs to get closer to a possible solution for the problem. so i'm still hoping for a solution privided by djtt/vestax/ni. but to me it seems like they all look in another direction acting like everything is ok.
A simple solution would be to have Bomes act as a filter between the VCI and Traktor. All the midi from the VCI would be sent through Bomes to Traktor, but the midi out from Traktor would be filtered through Bomes in order to prevent the overload or whatever it is. So basically all the input that the VCI would receive would be from Bomes not traktor. I don't have a VCI or a windows PC for that matter, but I know that Bomes could fix the problem and correct the LED feedback.Quote:
Originally Posted by hurundi
thaks for the tip, i installed bomes yesterday and it seems to work! i don't know why, cause bomes just passes midi thru and i expected to still get random freezes. i have to test it a little longer to be shure that it really works, but i didn't get e freeze in my 15min test with extensive use of filters/fader fx/jogs.Quote:
Originally Posted by DJPhaidon
i'll post a more detailled answer in this thread http://www.djtechtools.com/forum/sho...stability+poll
I didn't really expect it to work without any presets or translators to shift the signals, but if it works fine without them then awesome. If it does start locking up again, then it might need a buffer between Tpro and the VCI, like having the Tpro midi out on channel 2, then put into variables inside Bomes, and sent on channel 1 to the VCI with the correct LED's and such.Quote:
Originally Posted by hurundi
I don't know if DJTT has an author version of Bomes, but a way to increase the functionality of the VCI without firmware upgrades could be to author a Bomes preset that fixes the issues with the 1.3 firmware through midi translators. According to their site, you could also have a custom interface like Stanton's DaRouter, which is built entirely with Bomes.