Midi Show Control Event not working

I need some help please. I am trying to simulate a Midi event on a Windows 10 PC using Nomad (EOS v3.2.10.36). I have installed LoopBe1 to provide a virtual Midi Tx/Rx connection which Nomad and the Waveform 13 (DAW) can see.

I’ve created a Show Control Event to run Cue 2 when a C (any) is received (above), but nothing happens.

I’m not seeing any entries in the Diagnostics screen.

Can anyone help please in seeing what I haven’t/should have configured for this to work?

TIA. Roger.

Parents Reply Children
  • The octaves of Midi notes aren't standardized. There are octaves 0 to 10 in Midi, but musically speaking there are also negative octaves. You will often see Midi octave 0 corresponding to musical octave -2, which i think is what you're seeing.

    The 3rd number pair of a Midi note is called velocity. This was meant for pianos to say how hard a key was hit. 01 was very soft, 7F was as hard as possible. Now that notes are often used for communication not involving pianos or actual musical notes, velocity is often being used to communicate a piece of additional information. In Eos for example you can map it to the level of a fader.

    I can't tell you why Midi Ox is choosing 68, but it is a valid number in this context.

  • Thanks for the help so far. Although I see the notes being sent on the Midi-Ox, I am not seeing anything in the Diagnostics screen in Nomad on the PC. Is there anything I've not set up correctly?

    TIA.

Related