MIXVIBES Dj Community old forum

Just testing out some of the features of my U-Mix Control pro2 (on my friends win7 machine, in case you read my previous post). I noticed something with the Jog wheels (could be just the left one), and wanted to get some feedback from other users.

When using the touch surface of the jog wheel in either seek or scratch mode, the wheel seems to stop functioning at random intervals (ave every 10 secs or so) for about 3 seconds. For instance, if I seek backwards and forwards for a while, at some point to track will just stop seeking even though the jog is being turned.

At first I though this was related to touch surface sensitivity, but:
- I've tried turning up the sensitivity to full, which does not help
- If it was a touch issue, I would have expected, since the wheel is still turning, for it to stop seeking but start pitch bending - this does not happen (it stops seeking, and no pitch bend occurs).

Has anyone else seen something like this? I haven't upgraded to CrossDJ2.2 yet - I was hoping that might help, but from the release notes it seems like it's just a release for the video plugin.

Thank you

again a little bit more info as to the computer spec and set up ,,,
is it a gui freeze or is it noticed in the audio stream also ,,, ,,
check the teck manual for info concerning the operation of the jog wheels ,, i think using the side of the jog wheel implements the pitch bend and the top is for track control ,, also what mode are you in when this is happpening
link for manual
http://www.mixvibes.com/content/support ... umentation

It's a brand new high spec machine and the CPU is not being taxed. It's not a gui/performance issue (the audio stops too). It's just as if the jog wheel had been stopped (when if fact it's still being turned).

As I mentioned in the post, this is during both scratch and seek behaviour (so top surface of jogs). I only mentioned the pitch bend to try and help with diagnosis (as presumably the way Cross decides if jog movement should pitch bend or seek/scratch is by whether the top surface is touched or not).

I've just seen this item in the release notes for Cross2.2

FIX: Increase value of jog stop timer for U-Mix Remote mapping.

..which sounds promising - perhaps that will help.

I'll upgrade to 2.2 and report back.

bgsosh wrote:It's a brand new high spec machine and the CPU is not being taxed. It's not a gui/performance issue (the audio stops too). It's just as if the jog wheel had been stopped (when if fact it's still being turned).

I've just seen this item in the release notes for Cross2.2

FIX: Increase value of jog stop timer for U-Mix Remote mapping.

..which sounds promising - perhaps that will help.

I'll upgrade to 2.2 and report back.

open up preferences/MIDI and check to see if the MIDI signal is being stopped when this occures ,,by looking at the green on line icon,,,should be blinking while the MIDI notes are being sent ,, might help in pin pointing MIDI signals sent

daniel clark wrote:open up preferences/MIDI and check to see if the MIDI signal is being stopped when this occures ,,by looking at the green on line icon,,,should be blinking while the MIDI notes are being sent ,, might help in pin pointing MIDI signals sent

Good idea, thanks - I'll check that too.

some of the 's i ask are for a reason , support staff that has more of a knowedge base to work from,and experiences ,, by having the info here on the posting will give them a idea what you are working with ,, to help you solve it ,and get your software/hardware combonation working properly , and as always
welcome to mixvibes fourm

Ok, so I've upgraded to 2.2, and can no longer reproduce the issue

Really enjoying the controller and software!

Thanks for your help daniel.

always a pleasure