paid for firmware 1.3 upgrade through Vestax, but didn’t get it
…As the title says, I paid for the firmware 1.3 upgrade through Vestax, but didn’t get it.
I had to take it back to my local shop to get the left jog wheel sensitivity dial on the back replaced after falling off. They had to send it to Vestax Canada to be fixed, so I thought this would be a good time to get the firmware 1.3 upgrade.
When I got it back, I noticed that DJ Techtools .TSI file didn’t work properly, so I ran the test (hold both vinyl button) as listed on this forum, and not surprisingly, I realized I still had firmware 1.2…But I paid $80 for it, even though it already had firmware 1.2
Is there any other way for me to prove to my local shop that I had to pay for something I didn’t get? The reason I say this is because they don’t really have a lot of experience with controllers, so me having to prove my point would probably involve having to use their computer to connect my VCI-100, and show them this site to show them the firmware test.
I’ve had a history of buying defective equipment from these guys, so I would prefer to have a more definitive way of proving that I just paid for something I didn’t get.
with the 1.3 firmware the jog wheels will still turn off if you press both vinyl mode buttons.
I personally test by holding the top little black button closest to the on/off switch when i turn on the unit on - if the LED lights up next to the button as the unit boot then you know that you have the 1.3 firmware.
Holding the button down as you power the unit on boots into 1.2 mode, if you want to get back to 1.3 mode just turn your unit off, then back on again without holding anything.
Do you hold the button down before you turn it on?
If so, I did that, and yeah the red light next to it lights up.
The weird thing is that tried loading the custom SE mapping from the mapping section, and it didn’t work properly…But the second I loaded a member’s mapping that was made for firmware 1.2, it work properly?
I was under the impression that mappings for 1.2 didn’t work properly if you had 1.3?
The DJTT mapping works somewhat with the 1.2 version of the firmware but not fully - the main thing that has issues are the 4th effects buttons being the same as the 2 buttons in between the eq’s
It seems like you have to fight for getting your money back. I would say you have to take your VCI to the shop and show them how things work
But you they gotta pay you back because vestax does not support 1.3 firmware so you might say they have promised you something they cant do
EDIT: i noticed on the firmware 1.2 that the crossfaders does not work in fader fx mode.
This test is different from the one that BentoSan posted…But also, this test doesn’t give me a clear indication of lights turning on or off, to indicate whether I actually do have firmware 1.3 or not.
Can someone give me a concrete answer so that I can know whether I should call my local shop or not?
If the above tips aren’t working for you. Do this: Get some kind of MIDI monitoring program and turn a low/low (filter) knob. FW 1.3 will show one CC# on the left part of the rotation, and a different CC on the right. FW 1.2 only uses the one CC. Also, moving a channel fader will show two CC#'s, vs. one in FW 1.2 There are a ton of things like this in FW 1.3. Basically, if you see multiple CC’s and note numbers coming from one control, you have an upgraded vci.
The above tests ARE working for me…And according to the test posted by BentoSan I DO in fact have firmware 1.3. The other test posted after that doesn’t seem to be a very definitive way to tell which version I have as there’s no indication clear indication of whether it’s 1.2 or 1.3 (eg: light turns on/off as in the first test).
There just seems to be some conflicting information being posted…So it’s a little bit confusing right now.
Getting a midi monitoring program will not be easy for me…And I’m not even sure what the CC’s are that you’re talking about, so it seems as though I’d have to learn a lot more in order to even use that method.
Sorry dude, my bad. I guess I didn’t read the posts closely enough.
FYI, there are lots of free midi monitoring programs out there for both PC and mac. The CC’s I’m taking about are part of what info is sent via midi. Generally, something like a knob will send a CC (Continuous controller) message with a number indicating what CC it is. So, since regular midi uses values of 0 to 128, as you turn a knob a message might look something like CC32 = 00, 01, 02… etc.
These monitoring programs can be indispensable when mapping your controllers with something like FW 1.3, since that firmware has knobs and buttons sending multiple messages, instead of the usual one message.
