There are two steps that everyone has to do in order to use this template, with the cool panel, to know about your system.
Virtual Device Nodes
- Configure which midi controllers are mapped to which of the 10 virtual device nodes.
- Configure the software instruments you intend to use.
Everyone will have a different collection of midi device ports, which can include both hardware and virtual IAC ports, so it will be different for everyone.
In order to make this panel somewhat generic, I have created the notion of 10 virtual "devices". In this project template they are found in the environment's clicks and ports page. Each one is represented by a monitor
object. Because they are monitors, you can always see activity here when you play on them to make sure you have things cabled right.
To the left of the 10 virtual device nodes you will find the Physical Inputs
object, which lists all of the currently known midi device ports on your system, including both hardware midi controllers as IAC ports. In this case, my system only has 5, and they are cabled to the first five virtual device nodes.
The above will be different for everyone, since everyone's system will be different. If you have more then 10 midi ports, then the first 10 will be cabled to the virtual device nodes, and the rest will not be cabled at all.
You will need to make sure that every midi port is accounted for (cabled). Any non-cabled midi port is automatically sent by logicPro through the SUM to the sequencer, normally, but in this template the SUM has been uncabled intentionally. So uncabled midi controllers will be ignored by LogicPro when using this template.
You can re-cable the Physical Inputs
ports as you wish to the 10 virtual device nodes. The order doesn't matter. For example if your primary midi controller is not the first port in Physical Inputs, its ok, you can cable the nth port to the Device 1 virtual device node...and then you will be able to consider it as Device 1 in the router panel.
You could theoretically cable two different midi controllers to one virtual device node, and they would become like one midi controller. Any ports you do not cable will be ignored by LogicPro unless you also cable the SUM port somewhere.Important NoteOnce you have done this, you should re-save the template as your own which more closely matches your system, however you should be advised that any time you disconnect midi controllers or change your IAC configuration, LogicPro will present the Physical Inputs object in a completely different way, the devices will not be in the same order, etc..which means this cabling could be wrong later if you unplug a USB midi controller, add an IAC port or anything else. That means even if you open a project later on a year later, the Physical Inputs object may not match what it was when you originally created the project, and you'd have to check and fix the cabling here for the project to behave correctly. I haven't been able to think of a clever way around this problem yet, if anyone has any suggestions I'm all ears.Virtual Instrument Nodes
Part 2 of setup is to configure 10 virtual instrument nodes
. Go to the environment mixer layer to see the following:
By default there are ten software instruments loaded on ten tracks in LogicPro and each of the 10 virtual instrument nodes is cabled to one one those software instrument channels. You can create any collection of instrument tracks, track stacks or anything you want in your project. You can reuse the existing tracks or delete them and create new ones, whatever you want. But for this template to work right, you will have to make sure that each of those 10 virtual instrument nodes (that you plan to use) are cabled to at least one instrument channel strip each. They can be cabled to more than one. They can be cabled to track stacks too. Whatever you want to do is fine.
5,1 MacPro 3.46ghz x 12 128gb ram, OSX 10.15 on OpenCore, Logic Pro 10.5, Mainstage3, Cubase10.5, StudioOne4, Reaper, DP10, VEP7, VSL, too many plugins to list