Vienna Symphonic Library Forum
Forum Statistics

180,757 users have contributed to 42,140 threads and 254,362 posts.

In the past 24 hours, we have 3 new thread(s), 15 new post(s) and 47 new user(s).

  • Workflow Enhancement: Patch Name Reflection

    I think the most tedious thing with VEP Workflow is simply getting the various patch names out of the instrument through the VEP template and out into the DAW so we know what we're working with.

    I'm not sure what facilities are available in the current DAWs but this is a prime opportunity to advocate for a reflection API that would allow tracks to be named from the patch selection automagically.

    I see you have the articulations reflected in your own Synchron player, but you don't name the mixer channel after it, you just show it in a special box under the instrument insert. A facility for naming the channels accordingly would be a nice step, but I'm typically not even working with those VEP mixer channels other than to route outputs as I usually want to mix in the DAW specific to the cue or song.

    Instance names are also hidden inside your VEP plugin and it would be nice if those could also be reflectable via the API, so that for instance we might create a summing stack per instance with each multitimbral MIDI part named automatically based on the VEP instrument patches and the DAW's audio channels named from the VEP mixer channels.

    You could also do this reflection on track and channel color choices. I would expect the reflection flow to mostly be from VEP to the DAW, but maybe some people will want to go DAW to VEP, as e.g. you allow renaming instances from the DAW plugin.

    Probably much of the hassle of making and using VEP templates is simply copying over names, so this is worth advocating for with the various plugin API bureaucracies and DAW vendors. While the win for VEP would be massive, it would also help working with other VIs directly in the DAWs. Maybe some DAWs already have something like this...?