One REALLY great thing about using multi midi objects is that you can populate tracks without cabling them to actual intruments. In theory you could populate every conceivable lib you own without much overhead inside Logic. Also, you can use many single midi objects instead of the multi midi objects.alright, per @dgburns suggestion, here is a version of the template with midi multi-instruments as the track assignments. Please let us know which you prefer. There are pros and cons
PS - after trying it for a bit I can honestly say I don't like working with the midi multi-instruments at all, much prefer using the original multi-timbral template (the one without the word MIDI in the name).
- Midi tracks can't be bounced without a lot of hassle. Multi-timbral version can be bounced even in non-realtime, very easily.
- Midi tracks have better mute/solo buttons and track fader that effect midi rather then audio, while the multi-timbral track controls are global for the whole instrument, which is useless.
- Its definitely easier to expand that MIDI version if you want to make a template bigger then 1270 tracks.
- There is MIDI mixer which you might find useful for controlling various CC controls if you use the MIDI version of the template
- The MIDI approach is not how Apple is currently handling multi-timbral instruments, that is the so called "old-school" approach. The original template i made is based on Apple's current approach to handling Multi-timbral instruments and the way VSL also setup their initial AU3 templates.
- Probably more pros and cons that some of you will think of. The entire interaction is different each way which can be confusing for some. Pick the way that makes sense for you and use it, I don't see a clear winner either way.
Thanks @A.G. Yeah I figured this out. ON the system requirements it just says 10.1 or higher. But I did the system upgrade to 10.3.6 and now all working. Thanks so much.You need High Sierra 10.13.6 or later OS to install AU3.