Midihub 1.16.1 - Midi Mapping needs new value to register

Midihub Support
1

Hello @Giedrius and @resonotter many thanks to both of you, that solved that problem. I was indeed sending just CC127 every time to start and stop the clock.

However, I found another problem with the new midi mappings. For example, I have mapped a parameter to a Note On & Note Off Event. But I mapped it from two different channels, so I have two mappings. One Note On & Note Off Event with Note C-1 and Channel 1, and one Note On & Note Off Event with Note C-1 and Channel 2. Channel 1 sends only the Note off, Channel 2 sends always the Note On. In the former firmware, that worked, e.g. Channel 1 turns off, Channel 2 turns on. With the new firmware it does not work anymore because for that a Note Off Event works, it is required that a Note On Event on the SAME Channel is sent before. So the mappings does basically nothing cause I sent the Note On and Note Offs from two different channels. I suppose with CC Events it is the same, no possibility to map On Event form another Channel than Off Event.

Can you please have a look into this? Is this behaviour intended?

Thank you again :slight_smile:

Midihub 1.16.0 - Clock Pipe Midi Mappings
2

@andi2239, I didn’t come across any changes in behaviour with “default” mappings when testing for @Giedrius, but I never tried that.

Please upload the preset (maybe with a Comment saying “Here!” if it’s got many pipes)

3

Hi @resonotter , here is the preset
Midihub Proj2.mhp (998 Bytes)

Thank you for looking into it

4

Hey @andi2239, I took a look and made a 1.15.2 version.
I can confirm that No it doesn’t work in 1.16.1 and Yes does work in 1.15.2.

@Giedrius will know whether this is intended behaviour,
In the meantime, Transforming Ch.2 Note Off → Ch.1 Note Off is a workaround that I guess you’ve thought of.

5

Thank you for the report, I fixed it in 1.16.2 - now the mappings will get processed even if the value of the mapped control remains the same, like it used to be in 1.15.2 and earlier versions.

1 Like
6

Hi @Giedrius and @resonotter, now my preset works as expected with the new firmware. Thank you again!

Best,
Andi

2 Likes