Software help archive
LED VU Meters + Aftertouch Pads and Functions
Support
LED VU Meters + Aftertouch Pads and Functions
A read-only archive of old serato.com help threads.
LED VU Meters + Aftertouch Pads and Functions
Product
ITCH
Version
2.2.2
Hardware
Vestax VCI-380
Computer
PC
OS
Platform
-
RobArran
7:43 AM - 29 September, 2012
Every so often my led vu meters and all pads and functions stop working. This has happened at various stages throughout use but generally happens when the unit is switched on at the back with the power switch whilst ITCH is already running. This has happened since purchase and I have waited to see if this behaviour is going to be rectified in 2.2.2 (which Im trying at the moment) but it doesnt seem fixed.
Martin C
2:16 AM - 8 October, 2012
Hey RobArran,
Just to clarify whats happening here, if you had the unit connected via USB first, with ITCH open, then switched the 380 on, you would get this issue.
If you did it in another sequence, you wouldn't get the same issue?
After how long during play does this usually happen?
How long do they stop working for?
Do you have any other USB devices connected, such as an external drive/mouse/keyboard?
Just to clarify whats happening here, if you had the unit connected via USB first, with ITCH open, then switched the 380 on, you would get this issue.
If you did it in another sequence, you wouldn't get the same issue?
After how long during play does this usually happen?
How long do they stop working for?
Do you have any other USB devices connected, such as an external drive/mouse/keyboard?
RobArran
1:46 PM - 10 October, 2012
Hi thanks for replying,
I'm running a few trials here whilst replying.....
Yes to your first two points. Switching the VCI-380 on first and then running ITCH doesn't cause the issue. Which is all well and good until I need to beatgrid or manage my files in offline mode and then revert to checking them against another track live, this is when I lose the VU outputs and (randomly) the hotpads.
I do use a wireless usb mouse, however, I get the same problem with or without this connected to another usb port.
The problem occurs immediately, and does not seem to be affected by how long the unit has been on (maybe the pads are affected by the length of time the unit has been on which may be why they seem to be random in their failings).
The vu meters will not come back on until I power off the unit and shutdown ITCH and then power back on the unit and fire up ITCH.
I'm running a few trials here whilst replying.....
Yes to your first two points. Switching the VCI-380 on first and then running ITCH doesn't cause the issue. Which is all well and good until I need to beatgrid or manage my files in offline mode and then revert to checking them against another track live, this is when I lose the VU outputs and (randomly) the hotpads.
I do use a wireless usb mouse, however, I get the same problem with or without this connected to another usb port.
The problem occurs immediately, and does not seem to be affected by how long the unit has been on (maybe the pads are affected by the length of time the unit has been on which may be why they seem to be random in their failings).
The vu meters will not come back on until I power off the unit and shutdown ITCH and then power back on the unit and fire up ITCH.
RobArran
1:55 PM - 10 October, 2012
As I was running through the various trials as mentioned above I also noticed that when switching the vci on whilst ITCH was running, ITCH did not revert back to 'online' mode, it stayed showing only one deck. This is the first and only time I have seen this! I have tried to replicate it again but it may have been a 1 off glitch as I am unable to replicate...... Thought it was worth mentioning though.
Martin C
2:58 AM - 12 October, 2012
I have tried this, but am able to reproduce.
Keep in mind, you should be able to create beatgrids and everything else in online player, so you shouldn't need to keep switching back and forth if this is the case.
There is a free program called MIDI-OX: www.midiox.com which can test if your unit is still sending MIDI correctly.
It would be a good idea, that when your pad lighting stops, that you open this program and test if the MIDI messages are being sent.
Check out this article to learn how to use MIDI-OX: serato.com
Keep in mind, you should be able to create beatgrids and everything else in online player, so you shouldn't need to keep switching back and forth if this is the case.
There is a free program called MIDI-OX: www.midiox.com which can test if your unit is still sending MIDI correctly.
It would be a good idea, that when your pad lighting stops, that you open this program and test if the MIDI messages are being sent.
Check out this article to learn how to use MIDI-OX: serato.com
RobArran
9:39 AM - 12 October, 2012
Hi :) I will give the unit a thorough check with this program. I am aware that I can beatgrid in online mode, however, what I dont want to find further down the line when my warranty is expired that this problem escalates.
Ill update when I have run some checks.
Thanks
Ill update when I have run some checks.
Thanks
RobArran
10:07 AM - 12 October, 2012
Quick question. Should Midi-OX log commands while ITCH is running ?
Martin C
6:37 AM - 13 October, 2012
It can be open in the background while ITCH is being used, if thats what you mean. The log should only be written to when you a touching the controller as far as I am aware.
Do you have any other USB devices connected to your computer? External drive or mouse?
Do you have any other USB devices connected to your computer? External drive or mouse?
RobArran
11:18 AM - 13 October, 2012
Hi, yes I had midi-ox open in the background when running ITCH. When running midi ox alone it reported midi commands fine, I tested most of the buttons, faders and the jogwheels. Upon starting ITCH and replicating my problem I then tabbed into ox to see what was happening but it no longer showed any output. It just seemed that ITCH was 'hogging' the midi commands, maybe something to do with the settings in midi ox ?
RobArran
3:43 PM - 13 October, 2012
Hello again. whilst performing a live set on mixify my pad buttons stopped working. As I have mentioned above, this happens frequently but randomly. I have attached a short video so you can see what occurs (apologies for the quality).
As yet I haven't contacted Vestax about this problem as I'm not sure if it lies with the controller or the software. Right now I think there may be a problem with the unit. Your comments would be appreciated.
As yet I haven't contacted Vestax about this problem as I'm not sure if it lies with the controller or the software. Right now I think there may be a problem with the unit. Your comments would be appreciated.
Martin C
2:51 AM - 15 October, 2012
Hey Rob,
Thanks for the video :)
I wouldn't expect the MIDI messages to stop being sent when ITCH is in use, that doesn't happen when I test with a similar setup.
Can you make sure your wireless mouse is disconnect in this scenario? I have definitely seen this type of thing happen when using mouses in the past.
Have you tried testing your unit with another computer to see if the same thing happens?
Thanks for the video :)
I wouldn't expect the MIDI messages to stop being sent when ITCH is in use, that doesn't happen when I test with a similar setup.
Can you make sure your wireless mouse is disconnect in this scenario? I have definitely seen this type of thing happen when using mouses in the past.
Have you tried testing your unit with another computer to see if the same thing happens?
RobArran
6:38 AM - 15 October, 2012
Hi Martin,
Ive had the unit 4 months now, I can assure you I've tried all manner of configurations including another laptop and my main desktop pc, I've tried numerous clean installs, with and without mouse attached. The laptop in use was bought new specifically for this unit and has been tweaked using both Seratos and Dub Spots guides to optimisation. At first I did think it to be a software issue and is the reason I have waited patiently to see if software updates would fix this, sadly 2.2.2 did not remedy this and was the reason for my initial post.
Thanks for your responses to date, today however, I will be contacting my supplier for a refund.
Ive had the unit 4 months now, I can assure you I've tried all manner of configurations including another laptop and my main desktop pc, I've tried numerous clean installs, with and without mouse attached. The laptop in use was bought new specifically for this unit and has been tweaked using both Seratos and Dub Spots guides to optimisation. At first I did think it to be a software issue and is the reason I have waited patiently to see if software updates would fix this, sadly 2.2.2 did not remedy this and was the reason for my initial post.
Thanks for your responses to date, today however, I will be contacting my supplier for a refund.
Martin C
9:55 AM - 15 October, 2012
Hey RobArran,
From what you have told me, it is starting to sound like a hardware issue, so my advice would be to contact Vestax, I am sure they could help you out, and repair or replace the unit if it turns out be an issue.
However I do understand if this has become too frustrating and you just want a refund. When they function well, its a great unit in my opinion!
From what you have told me, it is starting to sound like a hardware issue, so my advice would be to contact Vestax, I am sure they could help you out, and repair or replace the unit if it turns out be an issue.
However I do understand if this has become too frustrating and you just want a refund. When they function well, its a great unit in my opinion!