------------------------------------- How-To Videos Articles I've Written Mike Phillips Director of Training 1-800-869-3011 ext 206 "Find something you like and use it often"
I'll put it to issue tracker (than you will be able to vote:)), just need to gather similar discussions issues links for reference to support the request. e
Bump. Also, I was wondering whether or not this should be considered a bug instead of a feature request. I don't see why feedback routing has to be enabled in the first place when routing mid form a to b and audio from b to a. Also the priority seems somewhat low to me. Flexible routing is actually one of Reapers strongholds. I hope we get this fixed some time soon. Working with multi-out vstis and automating them is simply convoluted at the moment.
Here's my problem with what you guys are proposing (that audio A>B and MIDI B>A should not be considered feedback): Imagine track A has a VSTi on it, and track B has an audio-to-MIDI plug on it. Now, whenever our VSTi plays a note, it gets sent to B, where it's converted to MIDI, which gets sent to A, which triggers a note, which sends audio to B, where it's converted to MIDI, which gets sent to A... I can't think of a reliable way to allow what you lot are proposing while precluding stuff like this happening - after all, how is Reaper supposed to know when a plugin is capable of producing MIDI output from audio input? Feedback routings are just a bad idea in 99% of cases. Just make extra tracks, and use the track manager to hide those you do not wish to see in arrange view or the mixer.
Поиск
Users
Entrance
RE: Audio delay when send to MIDI track
