kotrl

If I want to do small fader rides through MIDI (either automating a gain plug-in or volume fader), is there a way I can decrease the sensitivity of this mapping? For example, if the top of the fader was +6db and the bottom was -6db, this would give more resolution and make small moves easier.

Sorry to resurrect an old thread To marquee a region and dragg to a new track is easy enough. How should one create the cross-fades though? E.G. Do you select all regions and drag to extend the start an end, and then add a fade?

What's the relationship between these three things? - Quantize settings in the region inspector - Quantize settings in the piano roll - Quantizing an individual note by pressing 'Q' Some related (but less important) questions might be: Which has priority? Can a region be quantized to one setting, then notes individually quantized to another? Does Logic always remember the note's unquantized position?

Haven’t had the problem in a while. On Sonoma with PlugSearch 4 now

I possibly had this on Ventura too (now on Sonoma), at least it was recent enough that it must've been. But I haven't had the issue in quite a while. Latest version of Plugsearch and Logic now

Ah… I’ve been making hazardous Keyboard Maestro macros today and it must’ve selected that

Earlier I dragged a box over some notes in the piano roll and something I wasn't expecting happened. The box I drew stayed there, and two handlebars appeared on either side (like the ones you see when you select text on iOS). Dragging the handlebars resulted in all the notes getting longer or shorter, like if you were to select the notes from the edge. I definitely didn't imagine this, but after starting Logic to take a screenshot, I can't make it happen again.

I use both PlugSearch and Keyboard Maestro and had exactly the issue you describe: immediate crash when clicking the traffic light. Haven't encountered it recently though, maybe it was related to a particular macro…

There's a trick when drawing automation (I think with the marquee tool) that lets you automatically create ramps, but I can never remember what it is. I think it's a modifier, and then you drag inwards.

Thanks very much! I'll try that on my next project.

I am, of course, sending to two different buses?

Supposing I want a short delay in the verse and a long one in the chorus, what's the least fiddly, simplest way? I thought the secret to an automation-free life was to put the different sections of my vocals (verse, chorus) on different tracks, apply my different send settings there, and then send the tracks to the vocal bus. But the downside here seems to be that effects like reverb and delay are sent before the processing on the bus channel. So that takes me back to doing it on the bus channel, fading one send down, and fading another up, on each section with automation, which I can make a bit more efficient with the marquee tool and aliases of region automation. Might it possible to switch between Send A and Send B with a single lane of automation? Or is there a better way of splitting them out to different tracks?

Oh you're right! It seems after flattening the take folder all the regions work like that. I just didn't know the click zone existed, so thank you!

Thank you David! I wish it was possible with crossfading regions. After flattening my comp folders I usually go through and refine the crossfade point, which I've sped up a bit with a macro but seems a bit slow. Maybe I need to do things the other way around.

😯 How do you change the start and end point of two regions at the same time like that? I'm using a fade tool but the cursor never changes to that icon