This is why it is important to be able to quickly copy a layer in a part, position myself in another part of any song and be able to “quickly paste” a layer with the shared instrument.Īlso because the “shared” pull-down menu system, when you have many (very many) instruments open, becomes difficult to consult (at least for my old eyes). It is obvious that an instrument cannot be shared in another layer in the same part with the same midi channel and be “independent”, but I’m not asking for this. The need is to load the VST instrument into a layer and share it, provided that each layer has the possibility to intervene on the MIDI volume and that this does not influence the layers of other parts involved in sharing the instrument. Realize that this thing is repeated for another 10/15 sounds to share, and it becomes completely unmanageable. You quickly understand that it is not manageable to load 5 instances x 40 songs (200 instances) to have only a volume change for the same sound! In each of these songs, depending on the intro, verse, bridge, chorus, outro, the same sound will have 5 different volumes. I have a PAD sound that I use on 40 songs. I’ll give a practical example (which is what I’ll actually have to do for August):ĥ0-song setlist, completely based on VST instruments (no external MIDI module). In practice, in my opinion, the shared instrument with multiple layers makes sense only and only if we are talking about Virtual Instruments, because with external modules you simply need to copy a layer and paste it into another Part. They are on the same channel, but in different Parts, so I expect each layer to have the possibility to assign its own MIDI volume, which does not reflect on the shared instrument in OTHER parts layer The rule is: if (and only if) 2 or more Layers within the same Part (!) send on the same channel (!), their controls are linked
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |