Michael Canavan wrote: ↑Fri Apr 28, 2023 5:54 pm
Logics way might look "cleaner" but I prefer the way DP and Live do it,
Logic's way is not only about looking cleaner. Logic's way also ensures sample accurate MIDI rendering, which cannot be done with DP, nor cubase either for that matter. When the MIDI out from a VSTi is routed around to be used as a new MIDI input...it loses its MIDI timestamp and will be re-stamped on the next processing block. Depending on the size of your buffer this could be kind of large, but probably not bad enough to notice...but definitely not sample accurate
LogicPro on the other hand renders absolute sample accurate MIDI plugin results. The MIDI notes will be sample accurately timed in the same processing block where the VSTi is making sound, etc. Sample accurate.
Both Cubase and DP do provide a way to setup multiple tracks and pipe the output out of one track into another track and that's how you can handle it...and it basically works....but..not sample accurate.
A way to get sample accurate MIDI plugin use inside DP and Cubase is to use a third party plugin that hosts plugins, such as BlueCatAudio patchworks, Kushview Elements, DDMF and a few others. Then you can host both the MIDI plugin and the instrument plugin inside that bubble, and retain sample accuracy and not have to create extra tracks either.
Michael Canavan wrote: ↑Fri Apr 28, 2023 5:54 pm
because if you're using a drum machine VSTi it still is capable of making noise, so in instances such as wanting to use another source for a kick drum say, it doesn't silence the rest of the pattern in the drum VSTi.
In this case, the drum machine that outputs both MIDI and audio doesn't work as well in the LogicPro scenario because LogicPro's MIDI fx are just MIDI, no audio. In that case I recommend using the third party plugin hosters I mentioned above, if you care about sample accuracy of your MIDI processing.