Difference between revisions of "MuLab notes"
From Helpful
m (→MIDI routing) |
m |
||
| Line 51: | Line 51: | ||
===MIDI routing=== | ===MIDI routing=== | ||
<!-- | <!-- | ||
| − | |||
'''MIDI Input Channel Targets''' | '''MIDI Input Channel Targets''' | ||
| + | By default | ||
| + | * channels not routed to a specific place goes to whatever has MIDI focus (so all of them, in a new project) | ||
| + | * GUI focus alters MIDI focus (see below) | ||
| − | |||
| − | |||
| − | |||
| − | + | There are two changes: | |
| − | + | * you can send a channel to a specific module rack | |
| + | * you can disable the change of MIDI focus. | ||
| + | ...and you can ''still'' get away from under such fixing, by changing the sending channel of the MIDI controller. | ||
| − | |||
| − | |||
| − | |||
| − | + | '''Why the following focus / not?''' | |
| − | + | ||
| − | + | ||
| + | The idea is roughly that when you have one controller that you use purely for tweaking all the racks, and then record distinct tracks at a time, then auto focus is probably more convenient | ||
| + | And 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 channels to specific modules. | ||
| − | Perhaps the clearest overview of | + | Perhaps the clearest overview of current 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 10:42, 11 July 2020
