Logic Magician And Midi Track Stacks

[Dave Leo Baker]

So you guys were spot on, using LM makes doing what I do with splits and multi-manual recording so much smoother / less interacting and stuff, more recording / arranging. There is one small thing, but I don’t even know if it’s possible to change.
If you have a track stack of midi instruments, the midi input control shift 1 says flex, not midi in. This is only relevant when you want to record from the stack itself rather than putting the midi data on each track. I took 2 pads instruments this morning, transposed, split the keyboard, added modifier plugins to the chain so I could enable / disable / pass parameters, all of which worked. Each one I set to Midi In from my lower manual controller. Then I stacked them and placed them in the tracks view below my bowls on the upper manual controller, which I’d set to that controller in midi in. On the lower controller stack, I pressed the keystroke for midi in and it said Flex instead. This is niche and not hard to work around, and very often I record the midi data separate on each track, but in this case these were treated like an organ / bass coupler with extra pedals so for the project it made sense to put all the data on that track.
Anyway this is probably a rare thing / anyone who does it would know enough to go to Inspector and do the change manually for just the stack.
Logic basically doesn’t take into account the midi in settings for the instruments in the stack if you are recording on the stack itself, you have to set your midi in on all the tracks if / when it matters. I often don’t record my midi data to the whole stack but just arm each of the member tracks for recording. But this stack only had one split, and the upper manual was one instrument / just some accent bowls, so I guess I found it.

All that being said, using Logic Magician as a longtime keyboard / midi guy is incredibly streamlined! Auditioning plugins, sends, and so many things made simple by one or 2 keystrokes / arrows.

Thanks again for all this work, it’s proving to be amazing. Very well worth the learning curve. To anyone else who’s new with this, I just bookmarked the Logic Magician page on the website, and keep it open when I’m working / look for what I need until this becomes muscle memory.

Cheers,

Dave

[TheOreoMonster LogicBand]

While Logic allows you to record on track stacks for MIDI tracks, the track stack itself isn’t processing the data. There for there is no MIDI input or etc parameters in the track inspector for a track stack. All that stuff is done on the individual tracks. The MIDI data you record on the Track Stack is being process by the individual tracks based on their individual settings. So you will need to set up the individual tracks accordingly.
Track Stacks is purely for routing and processing. You can also conveniently record MIDI Data on them to not have to record the same data to multiple tracks or record on one track and copy to the others.
Hope this helps clear things up. If you only really use track stacks as folders and want to understand them fully check out the Aux track module in the getting started course and the everything you need to know about track stacks tutorial on the YT Channel.
-T.O.M
Grab your free “Getting Started With Logic Course at https://logic.band/mailing-list//
Join The Band! Membership perks include in-Depth Tutorials,live Q&A & more https://logic.band/members
Interested in One On One Training? Visit
https://logic.band/training
Check Out LogicBand on Youtube!
https://www.youtube.com/c/logicband
Join LogicBand on discord https://logic.band/discord
Stay up to date with Logic.band on Social Media
https://twitter.com/logicdotband
https://www.facebook.com/logicdotband

> --
> You received this message because you are subscribed to the Google Groups "Logic Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to logic-accessibi...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/logic-accessibility/2981FB48-B899-465A-830C-06E9984BC2BF%40gmail.com.

[Laid Civic]

Hi Dave

This was good catch. Technically, lm should have reported midi in not flex, but something obviously confuzed it.
This is rare use case for sure, but it’s still technically error which I’ll take note off and fix in the upcoming lm update soon.
I personally never tried to use this in this context and obviously none of the testers, so I wasn’t aware of this til now.
Obviously, we can’t think of every possible scenario so it’s helpful when you guys find and report things like these. Thanks for that.

Cheers

[Dave Leo Baker]

Thanks. There are a few examples of stacks that are mixed and have full midi stacks under the arp category in the library.

There’s also one called Sea Beams Glittering and another called Ambient Stack.

Ambient Stack can be recorded upon separately but the others I mention are meant to record on as one instrument instead of each track separately. There used to be a kind of DX7 electric piano stack which had a “bell” and “bite” track which are not meant to be recorded on separately, but the full stack together. I don’t remember what that one’s called because I saved a copy of that locally years ago.

Anyway just a few examples, I know it’s hard to do all these testing scenarios. Harder still when someone says you have to do a bunch of steps first just to see it.

Peace,

Dave Leo Baker,
Your Spa Productions
Gentle rain for thirsty souls
https:artist.link/daveleobaker

To view this discussion visit https://groups.google.com/d/msgid/logic-accessibility/D01B9787-1D0F-4F06-8F6B-58A5743B85FA%40gmail.com.

[Laid Civic]

Oh, I dont have to go through all those. I just recreated what you described in your previous message and saw that lm doesn’t report what it’s supposed to do. 

If I recreate your scenario and get same behaviour, it means that it’s not speciffic to your own project, then really LM issue, which I like, because it’s easier to fix something that consistantly doesn’t work, then a thing which is issue on your end, but not on mine or vice versa.

Anyway, this is not big issue, I already identified exact point where LM gets confuzed so it will be fixed in next release.

To view this discussion visit https://groups.google.com/d/msgid/logic-accessibility/E4DBC611-6B15-4A71-BB91-F5DA5EFDA6F5%40gmail.com.