Note off, apparently not recognized

Midihub Support
1

My patch here works fine to play a note on Midi channel one, press CC 69, the note sustains, and I can the play a different instrument on channel 2. All notes are off when pedal goes up.

This works fine with logic Pro, but for some reason with my Yamaha ES, the Ch 1 note off is not recognized, so it keeps ringing. Midi monitor shows me the note off is being broadcast.
I don’t see any special configurations in multi mode on the ES. I have a sound on channel one, a different sound on channel 2. Very simple. But for some reason, notes on channel one keep ringing. Notes on channel 2 accept the note off and are turned off appropriately.
Very curious behavior to me, I wonder if anybody has any ideas on this, it would be appreciated.
Much thanks!
Peter
prst#6 test.mhp (1018 Bytes)

image
image284×750 38.7 KB

2

try these to help hunt down the problem:

  1. merge your 4 ES outputs in your preset into one (cf. prst#6 resoESmerge.mhp )
    this will help by MIDI Monitoring everything that’s sent to ES in one place and identify if any “un-closed” Note On messages are getting through.

  2. temporarily change the Ch.Remap to send the Ch.1 notes to, say, Ch.3 instead.
    whilst this may give the wrong voice, it might help identify whether the hanging notes are a Midihub or Yamaha ES issue.
    (though your Logic Pro comment suggests the latter)

3

This is helping me track it down. One problem, if not the problem, is that when cc69 is depressed and note on/off are sent to channel 2, there is still a note off being sent to channel one. midi monitor shows this at the eighth pipeline from the top, the last pipe 'to ES". We need the note off to be sent to channel one upon 69 pedal up-not during 69 pedal down. How might this be accomplished?
btw-the channel 2 output two ES is the last pipe on the next (ninth) pipeline.
thanks for your help!
Peter

4

You can now add comments to pipelines, Peter :smile:!

We need the note off to be sent to channel one upon 69 pedal up-not during 69 pedal down. How might this be accomplished?

it’s a bit early here right now for anything precise; I’ll try to take a look later.
To help emulate this, please confirm that “CC69 depressed” = value 127.

5

Confirmed, C 69 is actually 127 in the up position and zero in the down position. This shouldn’t actually change anything I wouldn’t think.

Yes, I will use comments and pipelines in the future. Thank you.

6

Hey, @pje, I won’t get a chance to look at this for a couple of days.

In the meantime, a short stretch of the MIDI input from playing (either a .mid file from your DAW or even a .csv file saved from the MIDI monitor) would be useful to help replicate.

In either case, I’m interested in what comes into MH so I can just run it and track what happens as I insert CC69 toggles.

Cheers.

7

The midi input comes from midi guitar on inA, cc pedal board inB and breath control inD. It is processed and then goes out to the DAW Sound modules. So if I give you the readings from the DAW, you’re actually seeing what went out of midi hub not what went **
**. So please clarify what you would like. Thank you.

8

As I said

therefore, it would be useful to have a brief MIDI recording of what you play into MH when you (might) get these hanging notes.

ie. set up some temporary pipelines to bypass usual processing and give me the"raw" as t’were.

I’ll happily take a look without this extra useful info (when I’m less backed up) but what I test with may have no relevance to your scenario

9

The first midi file shows what is going into Midi hub. First I play the note, then I blow CC2 for volume then I depress CC 69 to sustain that note and switch to channel 2, then I play a note on channel 2 and blow CC2, and then lift off of CC 69 and all sounds should stop.
“raw” Midi as going IN MidiHub.mid (4.0 KB)

I have also included a midi file, from midi hub that shows the actual performance which I tried to duplicate as close as possible.
Midi at Logic Pro, FROM MidiHub.mid (956 Bytes)

1 Like
10

Any luck with what I sent you?

11

Hey I finally got an opportunity to look at the “raw” MIDI and I’m confused:

ES.Merge output

not consistent with same input:

My first run on seqA❖ gave hanging notes…

pje_raw_seq_A_0
pje_raw_seq_A_01106×600 105 KB

…because we have Note Off msgs on a different channel to their Notes On

whereas the 2nd run was rather messy with superfluous Note Off msgs…

pje_raw_seq_A_1
pje_raw_seq_A_11106×600 100 KB

…but at least every Note On is “closed” as it were

❖ I call your two seemingly identical phrases seqA & seqB

But…

“raw” has double notes!

Before I started to hunt down how this might be happening I noticed this:

pje_raw_seq_USB_C_0
pje_raw_seq_USB_C_01106×600 92.9 KB

there are two Ch1 Note On playing concurrently

eh?

sure enough, looking at the piano roll we can see this in the edited copy of the clip

pje_raw_seq_B_DAW_split
pje_raw_seq_B_DAW_split896×276 14 KB

(In the red copy, I’ve dragged the start of the 2nd note back)

How is this happening? Are there two keyboard inputs?

I think this needs to be sorted before we look at what MH is doing with the input




PS. my DAW plays out the coincident notes faithfully; Logic may do some housekeeping before sending

12

there must be two pathways that are doubling the notes in my mid hub construction. I am only playing a midi guitar note single note. I will look into this.

I’m not sure. I understand your PS.

13

the two pathways notion doesn’t fit with the fact that there’s a length and velocity difference between the two notes



I understood your "raw" Midi as going IN MidiHub.mid to mean just that, not via Midihub (except perhaps a simple new preset to do DIN → USB routing).

looking at your physical inputs:

pje_inputs
pje_inputs296×606 36.7 KB

I’m guessing you have BREATH = CC2 only and MG2 is the rest (including CC69 foot control)?
The rest is playback and can be ignored?
(btw, there are two identical LIVELOGIC lines)




the PS is merely a hypothesis of why you might not get stuck notes from Logic but do with the hardware.