Yes it works.

I want to thank everyone who tired to help here.
It's really good to find that there is a community here ready to help members.

Thank you guys , I wish you all to be happy and do the music of your dreams.

 

More of these kind of threads and less of the boderline-on-the-spectrum childish arguments.

 

hey @Olymoon I know this thread marked solved and all, but just check "enable input for control messages" is enabled under Reaper preferences ->midi devices




Edit: I dont have amplitube, but when u try learn dont use the plugin's learn option, cauz it requires track to be armed and a midi input, so when u change input to audio it wont work, use Reaper learn this works when u have enabled it in preferences like mentioned above, click the parameter u want to map, click on para on top right and click learn.


If u want to Add the same control/knob across different tracks, use the option enable only when selected, or to watever u need

 

Last edited: Jun 23, 2023

Thank you.
I've done all this, but it was still impossible to control the amp while playing if in the same track, which is logical because Reaper do not listen to midi input in a track that is defined as audio.

The "child track trick" is working perfectly, using 2 tracks.

 

The work both.
You already solved, but if you like I can post the routing I did (reaper of course), you never know if you'll be in need of vocoders.

 

I'm very curious how you've done this.

 

Thats weird dude, and tickling my brain ever more so. I assume u r connecting ur contoller directly to Reaper, no virtual ports or Midi ox or anything, if thats the case and if u r willing, try this as is like the method i mentioned above but with a minor change.

1. Create a new track, and insert Amplitube.
2. Arm the track, and select the input (ur controller). Make sure u have enabled "input for control messages" in preferences
3. Now when u click the "para" button in Reapers FX window u wont c learn option
4. So now click on the parameter u want to map, using the plugins learn option and map it, this is to trick reaper so that it knows that its receiving cc signal.
5. Now unarm the track, clear the mapping from the plugins gui(if tr s an option)
6. Now when u click on the 'para' on top right of Fx window u should c the learn option.

Now u can change input to audio, Reaper should receive cc even when the track is unarmed, if u have enabled it in prefrences (like mentioned inprev post).

Try and let us know. and also let us know what controller u use.

 

Last edited: Jun 23, 2023

Thank you
I've checked again your first comment and checked that enable input for CC message was on.
Then I've followed all the explanation and used the param learn option.
But once I put the track to audio input, it does not receive MIDI, so the button is learned but as there is no CC entering, it does not move.
I can see that no midi is going in, because reaper have a midi meter on the tracks.

 

Yes, thank you, please post the routing.
Different solutions are always welcome so we learn more .

 

Reaper doesn't show midi cc in meters, once u change the input mode to audio. Just Checked. Check the option box below, try absolute mode

 

Working with parent and child tracks in Reaper is just so flexible and makes organizing complex mixes and setups really easy. You can nest as many tracks as you want. No need to make it overly complicated.

Sure there are limitations, but that's where ReaLearn kicks in. It's a really great tool to assign midi controllers all over your project.

 

Yeah, realearn is one option, but this is really a simple routing, Reaper is smart enough to route cc through a different path, even when when the track is unarmed and routed to receive audio, but something is in the way dont know wat it is.

 

See if you can "punch-in" automation by changing the audio channel to Touch or Latch Mode with playback already started and track not armed for recording. Move a control and see if it begins drawing automation. I'm curious to see if it is the same behavior as Logic or Protools.

 

Yeah it works, it adds automation lane, but after writing the automation lane if u use the read mode instead of latch write or touch it wont work until u bypass the automation lane or u just change back to latch or other two., but for this to workagain one the automation track is made it has to be armed.

 

Basically it's almost the same procedure for all daws, see the pics and the routings.

Tracks mic and vocoder (ems 5000 in this case) are essential, the other two (there can be many) are just optional external sidechain carrier generators.
Of course you can see that vocoder accepts MIDI and take audio only from mic (and optional audio carriers).

Beware that with different vocoders (i.e. Vocodex, Lector, Mvocoder), if they allow carrier sidechain the audio cannels routed could be different (but in this case are 1-2 for modulator (voice) and 3-4 for carrier sidechain.
Not only, at times they could be inserted in mic track and receive MIDI from another track (I can post those too).
Always follow sw intructions for best results.

 

Last edited: Jun 23, 2023

Yeah, it is best to stop playback after writing the data and then switch to Read mode. my Grandmother does not send cc# data really, only pitch/mod/note on/off. But Logic seems to begin accepting cc messages from one usb connected controller and then ignores the other. So to do a similar thing as this, I have to send data over 5pin Din midi from one to the other, and then it all goes over the one usb. its pretty stupid.

 

Reaper has two separate midi paths, one specifically for cc that works only when enabled under 'Preferences' that is being sent to DAW directly/globally so that all instruments receives the signal, i haven't figured out a way to view or monitor that channel or what it is, its an unsolved mystery. And the other for the usual midi 16 channel stuff that is sent to tracks.

 

Right, this is a two track solution (similar to child and parent track but with a different setup/routing) but I had the impression @justsomerandomdude was speaking about only one track and so far no one has managed to achieve this.

 

Maybe a Midi Monitor/Librarian/Editor like MidiOX or MidiQuest between the controller and the daw application? My guess is that the data streams in as Omni and the daw application channel selection just acts like a filter. I have never really liked those kinds of programs, so this is returning back to beyond my curiosity levels. lol

 

Nope, that shit is just global just goes inside reaper and its there like needle in a hay stack. I use Midi ox + Loop midi virtual ports which routes midi to Reaper and out of Reaper, u cannot Route out that specific cc midi path. What @Olymoon requires is to map that cc path to Amplitube, so that audio can be routed to the single channel can be used without much hassle. And thats wat Reaper is designed for.

Im wondering, if it has to do something with the midi signal from the controller. Normally by default all controllers send midi thro channel 1, even if its changed it will show up when learning for Ex. 'MIDI Chan 2 CC 1'

 

Last edited: Jun 23, 2023