![]() Now that macOS 10.11 (El Capitan) has been released, what can I do to upgrade to macOS 10.10.5 if/when I wish to? When I am in the Apple app store the only option I see macOS 10.11 as an upgrade option screenshot below. Never “purchased” or even attempted to download it via the Apple app store. I avoided upgrading to macOS 10.10 (Yosemite) when it was first released because of all of the stability issues surrounding it and have stuck to macOS 10.9.5. keyswitched articulations - whence you can also use AM Pro to show keyswitched articulations via a script in an automation lane.įrom my reading of the fora and key contributors my take away is that thet Multiport template is not necessarily the answer - and actually more instances has benefits.I am using a Mac Mini (Late 2012) that is running macOS 10.9.5 (Mavericks). Or then using one VEPro instance per instrument group in the case of e.g. My understanding is that a lot of users are using one instrument per VEPro instance with one articulation per midi channel in the case of Kontakt instruments and then articulations viewable in the automation lane via AM Pro scripts. I have set up a modest template recently. ![]() I recommend you take a look at Audio Grocery's AM Pro Toolkit and then search for more info about Logic VEPro set ups. It´s just silly to have for example 64 tracks sending midi to 64 different VE Pro instances. I have just been using Logic Pro X for a few days now. ![]() If I reassign the tracks output to the same VE instance and then try to change the midi channel, all the tracks associated with that VE instance gets changed. I would like to use one instance and just have different midi channels. My problem is that each track in Logic gets its own seperate VE instance. I am running VE Pro on a slave computer and Logic Pro X on a mac mini. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |