Quantize on/off key command...

[colonyrecords]

Hi Guys,

 

To begin i am switching from sequencing on an MPC to sequencing in Logic. A neat thing I could do with the MPC was to turn quantize on or off during playback/recording without stopping the seq. Is there a key command that can be programmed to Turn Quantize On or Off at the press of a button on my controller in Logic. I've been through the manual and see the a key command that can be set to step through the next/previous quantize resolution but this isnt a ON or OFF thing. I also know that the MIDI input on the inspector can be hard set to quantize but that isnt accomplishing what i want.

 

This is useful for example if im recording some battery drums, and I want certain hits to be quantized and other to not be quantized for a less robotic performance.

 

Cubase has this, on the Cubase transport there is a "Q" button that turns quantize on or off which is exactly what I want

 

Any help is appreciated...

[David Nahmani]

if im recording some battery drums, and I want certain hits to be quantized and other to not be quantized for a less robotic performance.

 

So you want to toggle input quantize on/off as you're recording?

[colonyrecords]

Yes that sounds like what i want to do. if you have ever used a MPC or even Cubase they have the input quantize on/off button. Is that possible in Logic?

[David Nahmani]

I don't think so, because the input Quantize setting is controlling the entire region, not just the notes you're recording at the time. It's a region parameter. Basically you're telling Logic: once this region is done recording, quantize it to 1/16th grid.

[Alan Shields]

A workaround (if it suited your workflow) would be to select all those notes that you don't want quantised in the Piano Roll of Event Editor and turn Quantise off for them. This would take place after recording not during.

 

Alternatively, if it's a less robotic sound you're after, record your piece, quantise as necessary, then (with eyes closed) sweep the strength value up & down until you get the degree of looseness you require.

 

HTH,

 

Alan.

[Electronathan]

I'd also like to add that Logic's Seperate Notes by PItch command is also a great way to edit and manage MIDI events.

Instead of working with all your drum parts in one region, the kick, snare, hihats, etc. will each get their own track and you can, for instance, quantize the kick & snare and leave the hi hats unprocessed.

On top of that the piano roll displays whatever regions are selected so you can select and edit any combination of drum parts and work on them as a composite.

THEN, on top of that...! You can pack a folder of all the seperate regions and copy n' paste or loop or make aliases of your pattern(s) and only need to manage the folder region(s).

 

Logic just handles MIDI like nobodies buisness. 8)

[colonyrecords]

A workaround (if it suited your workflow) would be to select all those notes that you don't want quantised in the Piano Roll of Event Editor and turn Quantise off for them. This would take place after recording not during.

 

Alternatively, if it's a less robotic sound you're after, record your piece, quantise as necessary, then (with eyes closed) sweep the strength value up & down until you get the degree of looseness you require.

 

HTH,

 

Alan.

 

I will try this workflow and see if it fits me. Am i to turn off Quantize withing the Piano roll with the De-quantize feature???? So you mean leave the Midi thru to 16th quantize etc, record midi notes then while the seq is playing open the Piano roll editor, select notes and de-quantize?

 

Thanks for the replies guys, appreciate it...

[colonyrecords]

I'd also like to add that Logic's Seperate Notes by PItch command is also a great way to edit and manage MIDI events.

Instead of working with all your drum parts in one region, the kick, snare, hihats, etc. will each get their own track and you can, for instance, quantize the kick & snare and leave the hi hats unprocessed.

On top of that the piano roll displays whatever regions are selected so you can select and edit any combination of drum parts and work on them as a composite.

THEN, on top of that...! You can pack a folder of all the seperate regions and copy n' paste or loop or make aliases of your pattern(s) and only need to manage the folder region(s).

 

Logic just handles MIDI like nobodies buisness. 8)

 

I know i'm suppose to split the drum parts, my problem is i've been to lazy to do this in my projects. It really is the better way of sequencing drums so snares, kicks, hihats can get separate quantize applied.

 

You lost me with the pack folder method though I must admit. Would I do that just to make it easier to loop the split regions?

[Electronathan]

There's no shame in being lazy, I assure you!

It's my personal preference to use folders, but I like to keep my arrangement as clean and organized as possible. Bottom line: I make a lot of dumb mistakes if I don't organize my session from the get-go.

In addition to cleanliness, I'm LAZY..! I'd much rather work with one (folder) region for arrangement purposes than deal with a whole cacophony of colors and automation lanes, etc on 1 window only.

 

Mind you when I'm talking about lazy, I'm talking about "smart-lazy" not "I'm gonna sit on the couch and watch all 7 seasons of 24 - nonstop" lazy. There's a *subtle* difference.

 

I know this probably wasn't the kind of information you were looking for when you first asked about quantizing, but since you asked about folders, I'll show you a couple examples where they have come to my rescue.

 

...Back to 24.