Sorry for the poor quality looks like i recorded with a potato, dont use a screen cast or capture device as im not a youtuber. Video was too large to upload do had to do pic instead, because the video was shaky pic looks burred, but...
There, Single track, Eq/hp filter is just for visual representation that audio is being processed, green automation lane is Whammo, blue is ReaEq. Both being controlled by single control.

 

Last edited: Jun 24, 2023

A simple screenshot woul've helped [print].

This works live in realtime without recording it beforehand?

 

The idea was to upload a video, only after uploading the file here, i got to know it was too large lol.

? i dont understand.

 

Did you record audio and controllers at the same time? IOW, is this the result of one realtime performance?

 

You could post the video on youtube (even in private mode) and post the link to it here in forum?!?!?

 

Sorry guys, that I'm not participating, but I've been too busy these days.

I'll check all the answers once I can.

Anyways, big thanks to you all.

 

Yes, it was live, But as u can see tr like i've selected 'record output', tr is no need for automation lane, as the audio is already been processed. But i opted it, so as visual rep. as u can c the waveform from Hp filter.

U can keep the audio raw by selecting 'record input'. Reaper only records the automation when Latch or write or touch mode is enabled, but process the audio though, as u can listen trough ur monitors. Its best to keep the audio Raw and capture the automation.

But recording a Midi Item is different as most of the events like expression, breath etc. are captured inside the midi item itself, even while using retroactive capture, exceptions being cc s that are not encoded (empty) and that are being used with learn feature.
(@No Avenger might have a good knowledge about this, but this is also for others.)

For ex. lets say u have a midi controller with 8 faders, those eight faders are programmed to send a cc event such as Brightness, attack time, or any such non sense, the problem happens when u actually set the control to one parameter and the controller event is set to another and sent entirely different mesg. So most controllers has these options called "programs" to change this event function. Every Program send different midi event like attack, portamento, release. So to avoid this hassle its best to use a midi monitor, and check that it only sends a 'control change' message when u are mapping that knob or fader to ur FX (last Pic.)

Here 'MIDI Chan 1 CC 74' is programmed to send brightness in P1 (program 1), but i mapped it to control Reso. look what it captures.



Midi ox to monitor the input.

 

Yes, only thing, you have the "hassle" to reroute the whole stuff to MIDI-OX through LoopBE or MIDI jacks.

 

Not necessary, if u want to only monitor i.e to check what is what, u can just run it in parallel, IOW run alongside ur DAW like standalone, separately.
Edit: or u cloud use reacontrolmidi.

 

Last edited: Jun 27, 2023

Haven't watched it yet, but I just saw this on YT. And immediately thought "mmm... just 10 days before would've been perfect for @Olymoon and other nice people in this thread"

 

This was on my main page of yt. Funny

Midi Controlled - Plugin Control in REAPER

 

Interesting thread, I want to do the same thing with my Midi Fighter Twister.

 

Try and share ur results here.
FYI its mostly about using cc to control parameters on a vst on a single (audio) track, which receives/monitors audio and also cc from Reaper's Control Path, which doesn't requires the track to be armed, and no need for additional tracks to route midi into the audio track.

 

I have to test it, because when I start MIDI-OX and add my midi keyboard (let's say keystation32) in monitor it takes exclusive control, so it doesn't allow parallel split of midi messages. The only way to send them is adding in MIDI-OX a route TO daw through another virtual midi channel.
I have to test reacontrolmidi too.

 

That happens when the midi driver for the controller is been already in use, mostly windows driver instead of the manufacturer's. Midi ox must show "There is not enough memory" error. Dont mess it up unnecessarily unless u want to, u r better off with Reacontrol midi.
These might be interesting read
http://www.midiox.com/cgi-bin/yabb/YaBB.pl?board=query;action=display;num=1399759433
http://www.midiox.com/cgi-bin/yabb/YaBB.pl?board=query;action=print;num=1605930730

 

No error message at all, it's just: MIDI-OX first, nothing else will get the controller, daw start first, nothing else will get controller, simple as that.

By the links they speak about sysex buffer error and/or driver problem, so it's not my issue, if we can call that an issue.
They also mention a routing through Midi Yoke, that is, a virtual midi cable (I expressed myself wrongly before, writing channel) so we come back to the starting point.

I'll need time to check reacontrolmidi but I think I won't go beyond the limit of the midi driver in anyway.

 

S, what happens when u start Daw first and open Midi ox after that ?

 

No errors.

It doesn't matter if is MIDI-OX, just one and one only sw takes straight input from controller, and that's the first that starts.
To me was not an issue because I always used midi virtual cables to route among midi sw, though I would like to share midi input in parallel.

EDIT:
see this link about "multi-client midi driver", basically, if vendor does not provide it, it's MS single client:
Multi-client MIDI (again!)

RE-EDIT:
in this link there is some info about multiclient drivers, though the guy is wrong about the "superiority" of Voicemeeter on Asio Link Pro (I was a Voicemeeter user before ALP).
List of Multi-Client Audio & MIDI Drivers (Windows)

 

Last edited: Jul 7, 2023

You can create a group of tracks, like this:

Then you insert your FX and arm both tracks.

Edit.: I see now it's already answered but I'll keep the screenshot here if anyone need it.

 

I use LoopMidi