Midi Velocity

Is it possible to read midi Velocity from a device?

I need to look for the velocity on my bcd2000 as this is how the scratch ring work the jog wheels are infinite rotaries sending CC19 and CC20, velocity 64 (move anticlockwise) velocity 65 (clockwise)

Any ideas appreciated

I am off to bed now…

vvvvvvvvvvery good night

stu

I downloaded a copy of Midi Ox, It seems I can remap the midi so it spits out a CC when I rotate the ring to the left, but this does not show up in vvvv. It was very late/early in the morning when I did this. So maybe I was doing something wrong. Still not managing to get the rings working properly.

Anyone with midi experience on hand?

thanks in advance.

stu

OK!

Got it sorted with Midi Ox, seems I have to route to MidiYoke, ha ha I now have the rings sending different CC’s for left and right instead of different Velocities! makes my BCD2000 module a little more user friendly!

will upload newer version with MidiOx settings.

stu

hi, you can simply use the MidiNote node… where is the problem exaclty?

Hello Tonfilm

The problem is that although a scratch ring has a midi CC, it sends a velocity for left or right, 64 (left) 65 (right) on midi CC 19

There seems to be no velocity pin on any of the nodes, so how do I pick it up?

I would rather do this through vvvv if poss, as I have sorted the problem, but its a workround with MidiOx translating the value.

Cheers

stu

for what i read in the manual of that device
(yes, i dlded it only for “community charity purposes”, applause please, thx, enough.)
it sends (or “bangs” ) one CC event with value 64 if turned one step left (and 65 for right, bla…).

IMHO you should try to make use of the On Data-Pin.
see appatched tatch.

i wondered (or better: never heard sth like this) about “velocity” in CC-data. this may have irritated tonfilm when wrote about MIDINote.


btw. there are 2 MIDIcontroller-nodes in vvvv.
MidiController (Devices) and MidiController (Devices) Relative.
the last one (what i remember was told to me once) should be especially for use with those incremental controls. no experience though because i don’t have access to MIDIhardware with incremental controls.

hope this helps you ;)

stulloyd_bcd2000.v4p (10.5 kB)

the relative controller node should be it…
but could it be, that they are sending the velocity of the disc turn encoded in the controller value?

Yes Tonfilm

It looks like this is what they do as I have looked at the rings with the help of Midi Ox, I had already used the relative controller and had thought about using the on data pin too, but the on data pin will also send a 1 if you turn the ring right for the first time.

(Not looked at Kalles patch yet as I have just got in from work.)

Velocity is normally used for how hard a note has been hit on a keyboard. So it seems it is encoded with the CC.

Anyone got any ideas on how to extract velocity? or would it need a new hard coded node???

Thanks again, off to look at Kalles Patch now…

stu

I need to look for the velocity on my bcd2000 as this is how the scratch ring work the jog wheels are infinite rotaries sending CC19 and CC20, velocity 64 (move anticlockwise) velocity 65 (clockwise)

Velocity is normally used for how hard a note has been hit on a keyboard. So it seems it is encoded with the CC.

Anyone got any ideas on how to extract velocity? or would it need a new hard coded node???

no.

classic midi velocity (how hard a note has been hit on a keyboard) is encoded in the midi note event (see wikipedia) and can be retrieved with the MidiNote node. It is not a Controller.

there might be people calling one of the 127 midi controllers also “velocity”. but thats something different. The MidiController node is for receiving CCs and can retrieve the values of multiple CCs at the same time - thats the way to go.