Replies: 3 comments 1 reply
-
I have tested in Reaper and I can send multiple MIDI commands to my hardware device very quickly and it will handle them all correctly when it comes from a normal MIDI track within Reaper. This means the problem is definitely somewhere in my relearn configuration. I'm still trying to figure out exactly where it is going wrong. I am watching through all of the tutorial videos now. Hopefully I will see something that seems like it may be related to the problem. |
Beta Was this translation helpful? Give feedback.
-
Two things:
|
Beta Was this translation helpful? Give feedback.
-
I ended up getting it to work. Oddly the solution was to remove "04" from the target pattern for the first mapping and set the min/max of the target in the glue both to 4. I don't know why this behaves differently, but doing this made things respond quick and snappy. It's probably related to what you said. What do the brackets mean in the target "pattern" field? The brackets were automatically added |
Beta Was this translation helpful? Give feedback.
-
I am trying to configure MIDI mapping from one program to another where I need to take MIDI input from the first program, remap it to a new value, and then send it to a hardware device. The issue is, ReaLearn seems to be getting kind of hung up when I try to send two commands within a relatively short period of time (within about a second or so)... I know my MIDI device can handle MIDI inputs much faster than every second, so I'm fairly certain the hangup is happening within ReaLearn and not with my MIDI device itself.
Here is an example of commands I am trying to send. First I will send a note (Note 40 on channel 2 for example)
This note gets remapped to a CC command to trigger a tone change on my MIDI device.
Then about a second later I will send another note (Note 40 on channel 3 for example)
This note gets remapped to a different CC command to trigger the activation of a stomp pedal on my MIDI device. (Note: For triggering a stomp pedal the actual value passed doesn't matter, it just needs to trigger that CC command with any value)
Both of these commands seem to work if I trigger them individually, but if I try to trigger one, then the other within a reasonably short period of time they seem to trip over each other and will trigger very inconsistently.
Any idea what is going on here?
Beta Was this translation helpful? Give feedback.
All reactions