It’s beneficial because I can see the automation along with the midi input data. So, for instance, I have a violin and then I can see the music I wrote and the automation to its volume, pan, sends, etc.
If my project was small, I would use one instrument track per instrument and I won’t have any problem. However, in large projects Cubase is not able to handle such a big amount of virtual instruments, that’s why I need Vienna Ensemble Pro to handle them (which allows me to save projects faster and protects me to most crashes). And my wish is to replicate that behaviour, which I think it’s optimal, with MIDI tracks. I think you can do something similar in Logic (at least with volume).
In the Vienna instance I have all the strings: Combis(ensemble, vl1+vl2, etc.) -routed to midi port 1-, Violins I -midi port 2-, Violins II -midi port 3-, Violas -midi port 4-, Violoncellos -midi port 5- and Basses -midi port 6-. I have different libraries (CSS and Spitfire).
However, I’m testing different ways of making the template. I realized this kind of automation is not well supported neither in Cubase or in Vienna Ensemble pro.In the latter, MIDI automation is “weak”. In the former, the problem I commented before (which is a problem for what I would like to do, I understand why it works as it works, but I wish it could work also as I need it to work). That’s why I’m looking for “workarounds”.
So that’s why.
Thank you for your interest