Difference between revisions of "MuLab notes"
From Helpful
m (→Tracks and modules) |
m (→MIDI routing) |
||
| Line 51: | Line 51: | ||
===MIDI routing=== | ===MIDI routing=== | ||
<!-- | <!-- | ||
| − | |||
| − | |||
| − | |||
| − | + | '''MIDI Input Channel Targets''' | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| + | By default | ||
| + | : it goes to whatever has MIDI focus (in a new project, all of them will) | ||
| + | : GUI focus alters MIDI focus (see below). | ||
| − | + | You can, instead, send each to a specific module rack, | |
| + | and disable the alteration of MIDI focus. | ||
| − | |||
| − | |||
| − | + | When | |
| + | : you have one controller that you use purely for tweaking and into distinct tracks at a time | ||
| + | : ...then auto focus is probably is quite convenient, for easier switching | ||
| + | |||
| + | When | ||
| + | : you have more than one controller, OR a controller sending more than one channel, OR are using MuLab more as a synth host than a multitrack recorder | ||
| + | : ...then you probably care to route specific channels to specific modules. | ||
| + | |||
| − | Perhaps the clearest overview of channel targets is at ''Project → MIDI Input Channel Targets'' | + | Perhaps the clearest overview of urrent channel targets is at ''Project → MIDI Input Channel Targets'' |
Not that the the module racks are just the most visible thing to send to. | Not that the the module racks are just the most visible thing to send to. | ||
Revision as of 22:02, 20 May 2020
