16A Swing Quantize no longer works (Logic Pro 9)

[young_marley]

Hi guys,

 

This problem just started happening a few weeks ago. Whenever I click on a MIDI region and quantize to the 16A Swing value, it snaps all of my notes to the 1/16-Note grid (i.e. no swing, just straight 16ths). The other swing values like 16B, 16C and so on work just fine. Any ideas?

 

Thanks!

[Eric Cardenas]

Click this link to your signature and add your system information:

• Logic version and sub-version (e.g. Logic Pro X 10.2)

• OS X version and sub-version (e.g. OS X El Capitan 10.11.2)

• Computer (e.g. MacBook Pro, Mac Pro, iMac)

• Processor (e.g. 2.2 GHz Intel i7)

• Memory (e.g. 8GB)

• Audio interface manufacturer and model (e.g. RME Babyface Pro)

 

(most of that information can be found by choosing Logic Pro X > About Logic Pro X, and  > About This Mac)

 

Whenever I click on a MIDI region and quantize to the 16A Swing value, it snaps all of my notes to the 1/16-Note grid (i.e. no swing, just straight 16ths). The other swing values like 16B, 16C and so on work just fine. Any ideas?

 

Is this happening on a specific project or is it happening even on a new empty one?

[David Nahmani]

Whenever I click on a MIDI region and quantize to the 16A Swing value, it snaps all of my notes to the 1/16-Note grid (i.e. no swing, just straight 16ths). The other swing values like 16B, 16C and so on work just fine.

That's the expected behavior:

16A = no swing.

16B, 16C etc... = increasing amounts of swing.

[Holger Lagerfeldt]

Ive always wondered why there's both a 1/16 and 16A, when they're the same. It must be a workflow thing.

[stardustmedia]

Ive always wondered why there's both a 1/16 and 16A, when they're the same. It must be a workflow thing.

 

I wondered that too.