This would be a nice feature but you can use one midi item to send data to all 16 inputs of multitimbral vsti such as Sampletank by sending the notes for each instrument to its intended channel. Eg. Bass to Channel 1 guitar to channel 2.
If you want things to be a bit more organised you could allow free item positioning for the instrument track & add as many midi items as you need, renaming & colouring each one Like This:
Thank you for sharing your idea, but what if I want my project clearly arranged with the midi data on the track where corresponding the audio arrives? This can't be to much to ask for, can it?
I'm just saying that what Peevy showed is a workaround, but it's not a solution for a bug in Reaper's feedback routing which considers sending audio but receiving MIDI, all within one track, as a feedback loop - hence, audio and MIDI need to have their own separate feedback loops, as a fix.
Thank you for sharing your idea, but what if I want my project clearly arranged with the midi data on the track where corresponding the audio arrives? This can't be to much to ask for, can it?
That would definitely be a more ideal solution. But the way I do it is just to save space, IMO it beats having to have 16 separate midi & audio tracks for each instrument in a multitimbral Vsti like Sampletank.
Although if you want to use separate midi & audio tracks for each instrument another idea to save clutter would be to have Audio tracks hidden on the TCP but visible on the MCP & the opposite for midi tracks.
I do agree that it would be much better to be able to have the midi for each instrument on the corresponding audio track. You can actually do this in Ableton live using an external instrument track, all the routing is very easily done, just use as many external instruments tracks as you need. then you can group all tracks with the vsti & save it as a template.
It would be great to see something like this implemented in Reaper.
__________________ System: Mobo-Asus Prime Z370P II, CPU-i7 8700K, RAM-64gb DDR4 3000mhz, GPU Nvidia 3060 OS: Manjaro Linux / Windows 11 / macos Soundcard: Motu 828ES Monitors: Adam A5X
Pro Tools handles multi-out instruments nicely as well. You can route midi from one instrument track to another and then choose the corresponding outputs from the plugin hosted on that other channel as audio inputs. Pretty much exactly what we would love to be able to do in Reaper.
I'm just saying that what Peevy showed is a workaround, but it's not a solution for a bug in Reaper's feedback routing which considers sending audio but receiving MIDI, all within one track, as a feedback loop - hence, audio and MIDI need to have their own separate feedback loops, as a fix.
+1
I just voted for this Bug Report. I've been using Kontakt lately and this needs to be fixed. At least Schwa or Justin should comment on whether it's fixable or not.
Goldberg, you can already have it, but you have to enable feedback routing for the project.
Also, Justin has said somewhere that it's not really possible to have it any other way than from what it is now, because there has to be some causality (MIDI before audio, or somesuch).
I'm bumping this old thread, bigtime!
I thought this evolution was just one more step that a rather young DAW had to take in a close future. But v4 didn't adhere to this, and now I hear that v5 probably won't do it either. What in the ... !?!
Quote:
Originally Posted by EvilDragon
Justin has said somewhere that it's not really possible to have it any other way than from what it is now, because there has to be some causality.
I was about to say "can anyone point out a single bad thing about enabling this functionality?" when I saw what you wrote, Dragon. I would looove to read and hear about that. If the devs has any durable reason not to, then I (and hundreds, thousands of users) would surely love to hear and discuss that. (not directed to you, Dragon. Just me reacting).
If the userbase don't hear and fully understand that it's deliberate, and whatever solid reasons why there may be, then hundreds, thousands, will feel the development are just stuckup, silent and ignorant, and the remarkable market velocity that Reaper has achieved could dip.
I remember the quite well-received thread @ Gearslutz: "Goodbye Protools, Hello Reaper". Now that's a statement of recognition that all DAW-developers would drule to have, and Reaper got it. Wasting that velocity of approval would be stupid, and this is one functionality that would be sorely lacking and make Reaper feel retro 1997.
Since many DAWs has got this functionality working just fine for almost 20 years, why would cockos have a problem with it?
So .. especially that last link, Justin seems to say that the developers have coded themselves into a corner on this one. That how things are done in Reaper up until now, and the contingent needs of a close future, are two different modus operandis that won't mix well, that Reaper won't adapt to. Seems to say given how the situation is right now, it's too much effort to make it work, and it might mean having to re-evaluate or change things within Reaper that you don't wanna change/touch. It's what it sounds like, to me.
Either suggests the development team consists of very few people, and/or that internal culture of pride prevents further evolution, or changing along with evolutionary aspects.
I can only speak for myself, but I'm sooo certain lots of ppl agree to a great extent. This needs to get done.
I'll happily be the first to pledge that I will pay three times, four times the current price of Reaper if needs be.
A few months ago, I downloaded and installed the demo of the new Bitwig DAW. Just to check it out. Lo and behold, MIDI send and Audio receive on the same channel, and the ADC .. I mean ... I'm a capable pianist and thrive on playing stuff in by hand, live. Lots of guys are- and do the same. But in Bitwig there was no delay, none. The same exact moment I pressed a key down, I heard the note. Super responsive. No wait, rather it's "Just like it is in real life". After recording a few bars of piano to click, I played it back and the notes sounded exactly how I recorded them, the feel, their position in relation to the click, everything - like a tape recorder.
In Reaper, there's always this delay between key down and sound, that just disables you from being able to play with your feelings. Playing a tight piano-part to a hard swinging drums/bass accompaniment? With the notes sounding after you hit the keys? Forget it. And after struggling to get it right anyway, however you can, I have to stop recording, open the MIDI editor, grab the notes pull them forward a few milliseconds, just to even listen to a take. And if the sound level is too loud/soft, I need to go to a fader some other channel (oh, and need to find that channels first too) before I can adjust the sound level. It's nuts.
Bitwig woke up a feeling I had almost forgotten. It made me feel like I was back on a live piano again, back on Cubase again (which I left after 20 years). Feeling this again, after 8 months on Reaper .. it very closely made me tear up.
Reaper is better than the above in many respects, and that's why I'm here. But understand, this needs to get this going. Unless Reaper is to cater only to strict audio recording without real-time input fx, or only to loop-kiddies who paste/draw all notes in, the ADC/PDC in combination with sending MIDI/receiving audio on 1 channel needs to get done.
You'll have to excuse my sullen tone, but this makes me so pissed. I work with this, 6 hours daily at least, so what my tools offer me either makes or brakes my workdays. And I went over to Reaper trusting this functionality to be just a another step for a young DAW like Reaper to soon take. All other DAWs worthy a name has this, and Reaper has become a DAW with the most amazing CPU efficiency I've seen in any media application, good modularity and adaptability, all running on a stability that easily rivals Protools HDX (even with my 200 tracks 300 native plugins project sizes). But instead, Reaper 5 prioritizes things like a primitive script-based notation editor with bad graphics. Christ!
It's strange that in video tracks it doesn't have a problem to have a different signal path than audio. So video tracks seem the same but are different. As Justin said in 5 pre03 thread. http://forum.cockos.com/showpost.php...6&postcount=35
So we have some limitations in routing from audio/midi to video. I think it would be great if it could overcome these routing limitations. I understand that if it has not been done must be for good reasons. So I don't complain.
??? We've had that for a while now! The early posts in this thread are really old.
More importantly, we have multichannel audio on all tracks, and access to those channels right from the plugin pin connectors, and the ability to send from any channel to any channel. We can really take our sends from anywhere in the FX chain that we might choose. Likewise we can create "mid-chain" receives.
I personally have no opinion on the actual OP. I think that it is kind of just contrary to the paradigm that Reaper follows and is one of those things we sometimes have to just get over. Maybe your last DAW did it that way. What did they compromise to make that happen? Maybe it wasn't something you missed, but some of us might. Either way, Reaper just doesn't work that way and I don't really think it needs to. That's not the way we do things around here.
ashcat_lt, Reapers routing capabilities are so good it's a shame they cannot be used to do something trivial as multitimbral VSTi routing.
But it can does and will. It's simple and straightforward. It works and works well. Doesn't work quite the way some people think they want it to, but it does work.
This thread is a decade old, I still wish this feature was implemented into REAPER. Along with blank tracks being able to use no CPU usage at-all! this would make things a lot more efficient for Kontakt / Play / VEPro as a while for MIDI users!