![]() ![]() You could use Keyboard Maestro to output these same notes in response to computer keyboard keys, or this whole scheme could be programmed slightly differently so it will respond to CC's generated by Keyboard Maestro. When that track is selected, and you play notes A-1 through B-1, those notes will mute three of your subgroups individually.For this I created a new track (which can live anywhere, BTW) and assigned it using the MIDI Thru tool in the Environment. These are cabled individually to each of your sub groups. And you can do additional programming in there to assign additional notes to other cables.Īt the end of each cable is a monitor (there just for show and troubleshooting) and a transformer which converts each note to a Fader 1, 9 event. I've also set up the next two consecutive notes to output from cables 4 and 5 if you wish to expand this. This lil' setup responds to notes A-1 through B-1, and those notes conveniently exit this object at the end of cables 1, 2, and 3. Each note can be routed out of an individual "cable" on this object. Find the easiest possible method for getting an environment object to look at notes and separate them.You can feed CC's and stuff through it, but not notes. ![]() Use the scrollbars to navigate it, or, download the picture itself, or open it in a new browser window, or.įirst, you can't play MIDI notes into a Track Stack and have them come out the other end. OK, so this was an interesting one LOL! Pictures first. Here is what my Environment looks like now: ![]() The note ON/OFF was something i was worried about and I had debated about using another transformer to create an alternating split, but I have to crawl before I walk and figuring out how to mute these tracks is proving to be a bigger challenge than I thought it would be. My thinking is that as soon as I select the Final Mix Bus, these keyswitches will now become active and Keyboard Maestro will be able to run through its automation process to bounce out all the groups I created. Using my two Wind Track Stacks as an example, I am cabling those to my transformer (so called "NoWinds") and then cabling from my Final Mix Bus into that same transformer (i would do this for every potential group I might have). The disconnect for me is why the monitor is reading the correct information, but the tracks remain un-muted, and I can't figure out if it is a cabling issue or a transformer issue. Mute the next group and bounce, so on and so forth. Mute this group and then bounce, unmute that group then move on. Since Logic doesn't have the option to use a key command to mute tracks, using a keyswitch will be the most efficient way to tell Keyboard Maestro what to do. The reason I am trying to use key switches is because I am going to automate my bounce process for all my mix outs. But strangely enough, my Track Stacks remain un-muted. So I fixed the fader to output on channel 1 instead of 4, so the monitor is reading nicely. ![]() The keyboard is connected to the input of the Transformer. The fader is programmed to output Fader 9 on channel 1, with a range of 0 - 1 (this is important). it's a keyswitch toggle that uses one transformer and one fader. If you want the key to work in the opposite way, you'll need to create a slightly more complicated transformer processing scheme where the NoteOn and NoteOff messages are handled separately.īut that aside, here's something you may be interested in. When you release it, the channel will unmute. This means your keyswitch will mute the channel any time you press the key. the mute button will activate with a fader9 value of 1 or higher. So on the bottom row of the transformer, set the Fader's first "Thru" parameter to 1 (this is the channel parameter). First, your Fader 9 events need to be on channel 1, but the monitor shows them as being on ch4. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |