14 Bit HiRes Midi for CC Actions?

[rstockm]

My Hercules Inplulse 200 Deck supports 14 bit CC Messages (HiRes Midi) via MSB/LSB CC# pairs.
I'd like to use the device as a controller, for instance to move the edit cursor (absolut) via the deck-fader.

So
a) is there a way to assign a HiRes CC to an action (not: a CC lane etc.) to get the full resolution?
b) if no (which would be very un-REAPER ;-) - right now the fine-CC value is always send as the second value and the only one catched by the MIDI-learn. But I need the coarse value to get this running at all.
So for instance:

MIDI Chan 1 CC 0 (coarse)
MIDI Chan 1 CC 32 (fine)

is the MIDI output of the fader, and I'd like to map the action to the first one. I could edit the reaper-kb.ini (KEY section, been there, done that) but well - this is awkward. But I can't hand-edit the value in the action-dialog.

Any ideas? Do I miss something?

[mschnell]

AFAIK, ReaPack -> ReaLearn can do this.

If your application is more about designing a project independant Control Surface Interface, than doing "on the fly" projects, the CSI reaper extension supposedly can do this , as well.

-Michael

[helgoboss]

Yes, ReaLearn supports 14-bit CC MIDI messages.

I just had a look in the code and saw that the target "Project: Invoke REAPER action" converts the high-resolution value back into a 7-bit value (before passing it into the REAPER API function). I can't remember why I did this, probably just an oversight since this API function actually supports a 14-bit mode. I will turn that into a 14-bit value for the next prerelease and see if it still works. Maybe some REAPER actions won't respond to 14-bit values, we'll see.

All other targets (if applicable) use the full resolution already.

[rstockm]

@helgoboss Great news!
Another question: is there an ARM version in the making, or maybe even an universal one? Realearn would be the only non-arm plugin, preventing me from using the native ARM version of REAPER... (no bridged mode)

[helgoboss]

Originally Posted by rstockm

@helgoboss Great news!
Another question: is there an ARM version in the making, or maybe even an universal one? Realearn would be the only non-arm plugin, preventing me from using the native ARM version of REAPER... (no bridged mode)

For M1 you mean? I guess I should give it a go.

[mschnell]

Originally Posted by helgoboss

this API function actually supports a 14-bit mode.

This looks embarrassing to me. I would have thought that the Reaper API to set the tack volume slider would simply accept a floating point number (corresponding to the dB Value to be set) ?!?!?
-Michael

[helgoboss]

Originally Posted by mschnell

This looks embarrassing to me. I would have thought that the Reaper API to set the tack volume slider would simply accept a floating point number (corresponding to the dB Value to be set) ?!?!?
-Michael

For setting volumes and other stuff yes, it works with floating point numbers. But the extended action invocation API for invoking generic REAPER actions (KBD_OnMainActionEx) is pretty much tailored to the MIDI spec so no floating point parameters there.

[rstockm]

Originally Posted by helgoboss

For M1 you mean? I guess I should give it a go.

Excellent!

Please don't me shy if you get stuck or need testing partners. We (ultraschall.fm) already assisted reaper_js to get the M1-Job done.

[mschnell]

Originally Posted by helgoboss

For setting volumes and other stuff yes, it works with floating point numbers. But the extended action invocation API for invoking generic REAPER actions (KBD_OnMainActionEx) is pretty much tailored to the MIDI spec so no floating point parameters there.

Would it not be better to use the "general" API instead, so that resolution is not limited ?

-Michael

[helgoboss]

Originally Posted by mschnell

Would it not be better to use the "general" API instead, so that resolution is not limited ?

-Michael

I think there's a misunderstanding. ReaLearn uses whenever possible the most suitable API functions, the one with highest precision, most flexibility, best performance etc. It uses KBD_OnMainActionEx() ONLY if the user explicitly asks to invoke a REAPER action (via target "Project: Invoke REAPER action"). Hope this clears things up. There's no problem at all there and nothing missing API-wise.

[mschnell]

Ah I see.

So I was not wrong suggesting using ReaLeran's built-in feature (Target track volume) to move the slider in my previous post (as this as what I meant to do).

Thanks,
-Michael

[helgoboss]

Originally Posted by mschnell

Ah I see.

So I was not wrong suggesting using ReaLeran's built-in feature (Target track volume) to move the slider in my previous post (as this as what I meant to do).

True, that's the right way.

[mschnell]

OTOH, to "move the edit cursor" absolute even 14 bit does not seem enough. here supposedly some relative behavior with a rotary seems more appropriate.

Supposedly ReaLearn can help with that, as well.

-Michael

[rstockm]

Originally Posted by mschnell

OTOH, to "move the edit cursor" absolute even 14 bit does not seem enough

But there is a noticeable difference ?

[mschnell]

Between which and what ?

between 7 an 14 bit, the difference of course is huge.

-Michel