Midi system messages

vvvv beta general
#1

i need to access midi system realtime messages coming in to vvvv.
(in case you wonder why. i have an external beat matcher that chucks out bpm, start/stop etc.)
i know what i need to receive, just not sure how to get it.

eg. i need to get at the midi data for ‘continue’

midi ‘continue’ = FB = 11111011 = 251

i am presuming, therefore, that it would come under the heading of ‘midi program’ and i would use the ‘MidiProgram (Devices)’ node.

this is where i get confused, as on the ‘MidiProgram (Devices)’ node i can only select midi channel and buffer length.

does buffer length refer to the length of the binary number received?

could someone point me in the right direction here?

#2

helo ksp,

i am not sure if it is possible what you’re trying to do. vvvv is yet missing a generic midi-input node. why’d you presume that your message should come via MidiProgram (Devices)

the buffer length on the midi input nodes is not related to your problem. it is actually a framebuffer of incoming messages. if midimessages are coming faster than vvvv can handle them you can queue them with that buffer length.

#3

thanks joreg.

“the buffer length on the midi input nodes… is actually a framebuffer of incoming messages.” - that is what i had originally thought, but then wasn’t so sure.

i presumed that these inputs would come under the MidiProgram (Device) because they are SysX messages rather than Control change messages, and in my mind have always thought of them as ‘program messages’.

i am basing my assumptions of being able to access these on the simple fact that the MidiClock and MidiTimecode device nodes seem to be interpreting these signals. but as those nodes aren’t available to look at it can’t tell for sure.

eg. the MidiClock could be receiving the midi ‘Timing clock’ message ( F8 = 11111000 = 248 ), which sends 24 times per quarter note (96 times per beat).

#4

right, i have done some extensive testing as far as my abilities will go.

i can send most of the data i require, i just cannot receive.

i attach 2 patches to show my workings.

@tonfilm - i believe that you wrote the ‘MidiClock’ and ‘MidiTimeCode’ nodes. can you shed any light on this.

thanks.

#5

right, i have done some extensive testing as far as my abilities will go.

i can send most of the data i require, i just cannot receive.

i attach 2 patches to show my workings.

@tonfilm - i believe that you wrote the ‘MidiClock’ and ‘MidiTimeCode’ nodes. can you shed any light on this.

thanks.

midi-ctrl-test1_midi-out.v4p (15.4 kB)

#6

…and the 2nd file.

#7

…and the 2nd file.

midi-ctrl-test1_midi-in.v4p (12.2 kB)

#8

it is silly, but maybe try this.

the nodes you mention range between 0…127 while midi usually ranges from 1…128. this concerns channels and notes afaik.

so ask your next best neighbour when trying to fetch your parcel. did the trick for me last time.

#9

thanks. but i have tried that. didnt work

i think one problem might be that the signals arent sent on any particular channel, but the vvvv input nodes all work on channels.

#10

oh yeah… and that you can send the required 2 parcels of data with each command from vvvv, but the inputs only give 1

#11

hello, next vvvversion will have MidiShort to get all midi messages in raw format, and MidiSysex for system exclusive data.

with them you should be able to get all signals from your beat matcher.

but i would try to use MidiClock, i am sure your beat matcher can send it.

#12

@Tonfilm, do you mean you have a solution for this and this post??? That would be sooo awesome!!

#13

@ Tonfilm. Thanks, guess i might have to wait for the update.

My beat matcher is a fixed unit ‘Red Sound - Micro sync’. It throws out MidiClock, but is not sent on a midi channel, so i can’t seem to pick it up in VVVV. Any tips?

thanks.

#14

I used such a Redsound, wel a voyager, and the Midiclock node does what it should? I got an LFO-like value.

#15

@ksp:
i’m quite sure, that you don’t have to wait long… less than 24 hours

see change log of the past years

#16

yay! i know what i’m doing for christmas!

#17

@ksp, like west said, it should be no problem to receive midi clock… check the midi port, enable the node and make sure no other software is using this midi port.

@west, yes MidiSysex is your node…

#18

@tonfilm. i have just tried the midiclock node again and found where i went wrong. can now get it to work. (i still need the sysex, but this will do me for now). thanks.