Midihub 1.16.0 - Clock Pipe Midi Mappings

Hi there,

i have a problem after updating to Version 1.16.0. I use the Midihub Clock Pipe as Master Clock for my gear and have mapped the start and stop commands to my midi controller. After the update, it is possible to start the clock and stop the clock as before, but when i want to start the clock AGAIN, it does not work anymore. Just the first start and stop works, but then the clock does not start anymore using my external midi control. The midi messages are received my the midihub, but the mapping does not respond anymore. Is this a bug or am i missing sth? Before the update everything worked fine.

Thanks a lot,
Andi

Hey, could you upload your Preset .mhp here, or just send it to me via PM?

Hi, thanks for the reply. I attached the Midihub Preset. Thank you
Midihub Proj.mhp (4.6 KB)

Hey, I tried with 1.16.0 and it seems to work ok, as long as your mapped CCs hit value 127. I couldn’t reproduce the problem. The 1.15.2 firmware behaves the same way.

Is there something else that could be impacting this?

Hey @Giedrius, there is a behaviour difference between 1.15.2 & 1.16.0, I think.


Using toggling CC#11,12 buttons (0 ↔ 127):

  • in 1.15.2, Clock Start & Stop still work if you remove the 0 value from the map stream

  • with 1.16, it doesn’t

@andi2239, are you sending just 127 in, or is your issue different?

The Clock pipe’s Start and Stop buttons expect either CC with value = 127 to trigger, or Note On with velocity >= 1.

Toggling mode is not well suited for Start and Stop buttons, as it would trigger the action every 2nd toggle action (when it goes to ON state)

I’m not getting this, G:

If I only send 127 to Start/Stop in 1.16, it doesn’t function.
It wants a <127 value inbetween the 127s.

1.15.2 behaviour also fits with the “Toggling mode is not well suited” recommendation, but it doesn’t need the intervening value <127

Ok, I see what you mean, you’re right.

I’ve fixed the Clock pipe in 1.16.1. The Midihub Editor should suggest to do the update automatically.

2 Likes

5 posts were split to a new topic: Midihub 1.16.1 - Midi Mapping needs new value to register