Cornel Lazar

Usually the fans run high until all the spotlight indexing is done.

You're right, that does not happen when the group is not on. However, I need the group on in order to edit multi-tracked drums All the regions in the grouped tracks have carefully edited transient markers. HOWEVER, while troubleshooting this issue, the only thing that I could think of messing with is the group itself. Even though this SHOULD not matter, I removed unused drum tracks from the drum group (i.e. drum tracks that have no regions on them... these unused tracks exist from the template I'm using). Lo and behold, Logic is no longer creating manual flex markers all by itself... As I've said before weird. I don't see why Logic would care about any tracks that have no regions in them, but obviously something unexpected in the flex algorithms is happening in this scenario. I guess, for now, my problem is solved. Thanks for your input, I appreciate it.

Thanks for the reply. This isn't an issue with the tool though. As you can see in the gif, I'm grabbing towards the top, which normally would MOVE everything in-between the previous and next flex marker, and create one manual marker. I don't have an issue with that. The problem I'm having, which is what I've tried to show in the gif, is that when I create a manual marker, regardless of the tool, Logic creates MANY additional markers throughout the region, both before and after other manual markers that may exist. It creates these markers apparently in a haphazard fashion, not even on transient markers that exist in other tracks. Hence my frustration If you look closely at the gif, you'll see that the transient markers have already been moved via quantization to 16th notes. However, my issue happens whether I quantize or not.

bumpitty bump... Anyone?

Hi all, I'd appreciate some insight, if possible. I'm editing live drums using the flex time slice algorithm, and I'm encountering very frustrating behavior when creating manual flex markers. I've done all the usual (tweaked transient markers on the q-ref tracks with group off, set up a drum group with editing and quantize-locked settings on, then turned on flex and quantized to 16th notes). Kick, snare, and toms are the q-ref tracks, but the transients have been carefully edited on each track for accuracy. Once I try to manually edit flex markers by clicking and dragging just one transient, Logic decides to seemingly randomly create a LOT of other flex markers all over all the grouped regions (not just what you see in the capture, but throughout the regions). This makes it almost impossible to edit without going through the whole track over and over again to delete markers that keep getting created. See here: It's very possible that this is user error, or incorrect settings somewhere, but I can't figure out what it is. In all the youtube videos I've seen on flex timing drums, I don't see anything similar happening. Any insight would be greatly appreciated. Thanks! Cornel

Is it just me or do the strings have a heck of a lot of bow noise in the upper registers?

My pleasure. I'm just disappointed that it's not working with patches. Yeah, maybe the next release will let us nest stacks like we want. It's annoying to nest summing stacks within folder stacks 'cause meters are lost when collapsing the folder stack.

Yep, I can confirm that. So if you need to use patches, this approach won't work. However, if you don't rely on patches, then it works well enough. I've been messing with it for quite a bit today, and the patches issue is all I've found so far.

One other side effect I'm noticing is that for enclosed summing stacks, patches don't seem to recall correctly. I've messed around with Logic drummer producer kits within a summing stack, and clicking on different producer kits patches in the library does not actually update the stack. One workaround so far is to temporarily drag the stack outside of the parent stack, choose your patch, and then put it back in the parent stack. A bit annoying, but not horrible.

Sure thing. There may be some slowdown in saving patches, I haven't been able to confirm yet if it's due to this hack, or because the template I'm working on has lots of stuff in it, but just a heads up. If you see the spinning beach ball thing, just wait it out.

hey, sure thing. Just to make sure we're on the same page... The way a summing stack works is you have a "parent" AUX channel strip that has a BUS assigned to it's input, and it's output is assigned to whatever (default would be Stereo Out). In the Logic user interface, this AUX has a special property that enables it to be a container, so to speak, for other channel strips, at the same time as being a summing sub mix bus. These enclosed channel strips have their output assigned to the same BUS that the parent channel strip has as it's input assignment. From a signal routing perspective, this is the same as any other signal routing, it's just that the Logic interface gives this special summing AUX track the ability to act as a container for other tracks (via that little triangle arrow that allows you to expand and collapse the stack). So once you've created the summing stack within the folder stack, you then go to the environment and re-assign the SUBx channel (that's the folder stack channel strip) to the next available AUX number, let's say. Once you do that, that channel strip becomes an AUX, to put it simply, BUT it still retains the properties of a stack, meaning it has the little triangle arrow and you can collapse it or expand it. This top layer stack channel strip is now an AUX instead of a SUB, and it needs a an input assignment to an available BUS, and an output assignment (Stereo Out is the default). So now there's a BUS tied to it's input. Then, go to your enclosed summing stack, and assign the output of that stack channel strip to the same bus as your input bus for the top layer channel strip. This is actually the same way a normal summing stack works (i.e. all the channel strips inside the summing stack have their output assigned to the BUS that's assigned to the input of the summing stack parent channel strip, it's just that Logic does this assignment automatically for you). You can now create additional summing stack inside this top level summing stack, and route each additional summing stack parent channel strip to the same bus as the top layer summing stack input. Just added a gif: Hope this helps!

My pleasure. I was happy to see that it's possible. But yeah, I don't know why it's not possible via the interface since it's obviously doable. There may be some issues with saving patches for such stacks, not sure yet 'cause I'm still testing. For that matter, I don't know why it's not possible to have more than two layers, since it's obviously possible to create routing like that. Still, as much as the environment is annoying and lagging behind the rest of the interface, I'm glad for it at times.

Revisiting this topic... As far as nesting summing stacks, my nephew Justin said something to me earlier today that triggered a thought... So I went and tried it, and it works (if this was known already, my apologies). If you put a summing stack inside a folder stack, and then go to the environment and re-assign the VCA (channel that belongs to the folder stack) to an AUX, you now have a summing stack inside a summing stack. Works correctly, you'd just need to manually route the input of the input of the enclosing stack to whatever bus, and the output of the enclosed stack(s) to that bus. You can then create as many additional summing stacks inside the top layer, but it seems you can only have 2 layers deep. Cornel

I think I found the answer to my issue... the dang "Signal Flow Channel Strips" setting in the mixer view menu... Sorry to bug y'all with it

Hello all, I'm messing around with more complex routing as I'm putting together a template. I want to organize the drum tracks in a specific way, since I typically use more than one source for say kick (kick in, kick out, trigger, drum machine layers, etc). I'm also wanting to experiment with incorporating Logic drummer tracks as I'm doing production work, before recording live drums. So in the above kick drum group, I'd be doing individual processing on the direct sources for basic EQ and such, and then I'd be multing the sources via a bus to separate parallel buses for getting further processing done on the kick, such as character, additional parallel compression, maybe parallel effects chains for getting punch, click, etc. So the routing would look like this: 1. kick mic'd sources, kick parallel buses, trigger, sample layers, and a Logic drummer layer 2. summed via a summing stack so that I'd end up with one channel for kick when collapsed 3. outside of this summing stack I'd have the Logic drummer instrument track set up as a multi output instrument, for the whole Logic drummer kit. 4. then, once I add all the other drum kit components in a similar fashion, I'd put all of it inside a VCA folder stack that would control the overall volume of the whole expanded kit. The reason I want to incorporate the Logic drummer instrument is so that when I do production work, prior to recording live drums, I'd be able to use a similar sounding Logic drummer kit, dry, and use all the same parallel processing that I'd end up using in mixing. After recording the live drums, I'd then get rid of the Logic drummer track. So after painting that picture, here's the issue I'm seeing. When I create any multi-output instruments and use the -+ buttons to add additional output AUXs, in the mixer window they look like track stacks in that they'll have the arrow that makes them LOOK like track stacks, but collapsing won't work. Also, once I add tracks for these new AUXs, they show up in the main window, but without the track stack arrow. Flattening the stack is grayed out. So to me, this looks like a mixer window bug. Further more, if I try to put any of these multi-output AUXs, the kick let's say, INSIDE the kick track stack described above, it ends up looking right in the main window, and sounding right from a routing perspective, BUT in the mixer window, the multi-output AUX does not want to sit inside the kick track stack, but behaves erratically when I collapse or expand the kick track stack (i.e. the multi-output AUX moves around on it's own, sometimes it ends up next to the Logic drummer channel, sometimes next to the kick track stack, depending on whether the kick track stack is collapsed or not. As such, this makes the mixer really not work as expected, which is why I'm thinking it's a bug. Would any of you be able and willing to test this out and see if you get the same kind of behavior? You should be able to duplicate this by creating any multi-output instrument, create an addition output channel, and then put that channel in any other summing stack. Thanks!