Find the templates on GitLab here: https://gitlab.com/dewdman42/Logic-VEP- ... -templates
- OSX High Sierra or above
- LogicPro 10.4.5 or above
Adding more VEP instances and tracks
We have since figured out an easy way to create the VEP AU3 tracks on the fly. You can build up each VEP instance with 127 tracks in less than 1 minute. The above provided template was created by following the procedure outlined below. The instructions are not hard and its not too laborious, but there are some gotchas that can come up in a couple places if you're not careful that might cause some confusion. So try the easy instructions and read on in case something goes wrong.
- Start with a brand new project in LogicPro.
- You will be prompted to create a new instrument channel. If not, then select Track->New Tracks from the menu to create the first new instrument track.
- Select VEP AU3 plugin. Make sure to check the Multi-timbral checkbox and set the number of parts to 16. You will end up with 16 tracks created.
- Select the last one, which is currently assigned to midi channel 16. Look at the track properties on the left and change the midi port to 2 and the midi channel to 1.
- Now select the track above that one, which should currently have midi channel value=15. Press CTRL-RETURN on the keyboard to re-create a track for midi channel 16. (hint - using up arrow to select the track above is quick)
- Now select the last track again, which is currently set to port2, channel1. (hint- using down arrow is quick). Hit CTRL-RETURN 15 times. The last track created should be port2, channel16. (NOTE - this is where you can get into trouble. Its really important you do not accidentally create too many channels in this step. See troubleshooting section later).
- Repeat the procedure in steps # 4-6 above until you have 127 tracks. The midi channels used do not need to be consecutive on ports 1-8. They can be spread out across any of 48 midi ports supported by VePro. However you can not exceed 127 tracks per VePro instance. If you did them all consecutively, then the last one should be port8, channel15. port8, channel16 would be the 128th and will cause problems if you try to create it. (Note, this is where you can really get into trouble if you accidentally create the 16th track here, see troubleshooting below) You can always change these later to any midi channel/port you wish, as I said, but don't exceed 127 total unique channels used per VePro instance.
That's it. That sets up a max of 127 tracks on 127 midi channels feeding into a single VEP instance. If you wish to add another VEP instance for 127 more tracks, then choose Track->New Tracks menu command and repeat the above procedure to create 127 more tracks. Any of the above can be done on an ad-hoc basis. You can build up thousands of tracks in just a few minutes..
- The VePro7 AU3 plugin is considered "Beta" by VSL. However, It has been working very well for me. There are only two noted problems you may encounter (that we know so far), which may or may not apply to you. One is that midi transport and sync does not seem to be transmitted from LogicPro to VePro when using the AU3 plugin. So if you are using a transport-oriented instrument plugin then you should consider using the normal AU version of the VePro plugin for now until either Apple or VSL fixes that, its not clear yet whom is to blame. The other problem is that in LogicPro if you try to save AU3 tracks as Library Patches, the port assignment is not saved. So when you reload those patches back into a LogicPro track, they will all be set to Port 1.
The following problems will not happen with the provided template above, except perhaps if and when you try to add more tracks to it or build one up from scratch.
While pressing CTRL-RETURN to create each track of a port, if you accidentally hit CTRL-RETURN again while the 16th channel is selcted, LogicPro will not create a 17th channel track, but it will actually create a new track on a totally new VEP instance, but also having channel 16. This is not that you want. In this case simply selecting the track header and pressing DEL should get rid of the problem to continue on.
If you accidentally CTRL-RETURN past the 127th midi channel (usually port8, channel15), then the problem is a little worse then the previous one. In this case it will not create a new VEP instance channel, it will attempt to create a 128th track on port 8, channel 16, and that will break the entire instrument setup because you're only allowed 127 midi channels per Instrument. To rectify this situation, first open the environment. Select the errantly created track header. The environment should also highlight the object that is associated with that track header. select that object in the environment and delete it. The Tracker header will probably change to a label of "NO OUTPUT". Select that track and delete it.
You will know if you have accidentally done the second mistake if you open up the environment and go to the Mixer layer. You will see many mixer channel strip objects. Some of them will be blank...and when you see a group of blank ones for a particular instrument, that is where you probably messed up.
if you see this:
Then you messed up while trying to create all the tracks for instrument 10. Go find the wrongly created item per the instructions above and delete it. When its fixed it should look like this:
If you're careful not to hit CTRL-RETURN too many times then you shouldn't have either problem mentioned.