Unquantized recording on A4

Moogalieri · 2013-10-29T09:52:47.000Z

curious if anyone thinks unquantized recording will exist for this? i dont think it currently works for the A4 although i have only owned the A4 for 3 weeks or so. Nice to break free from the grid sequencing on occassion

avantronica · 2013-10-29T11:54:25.000Z

it does ! - check out the global>seq config menu and uncheck quantize live record !

Dataline · 2013-10-29T12:52:59.000Z

After recording something ‘out of time’, you can then raise the quantization value within the TRACK SETTINGS

One of my favorites!

Moogalieri · 2013-10-30T01:13:23.000Z

Mind. Blown. pants. Crapped. Thank you.

avantronica · 2013-10-30T09:32:56.000Z

yep - and the micro-timed ‘accuracy’ can be witnessed in the note menu for each trig step - it’s quantized to 1/384ths of a bar or 1/24ths of a trig step, the uTM param can be shifted 23/24ths either way until the trig almost overlaps either neighbouring trig ! fun !

dubmo · 2013-10-30T09:45:25.000Z

@Dataline
this is gold

btw. is the only way to raise the quant. setting, to push the curser buttons left/right- or is there some trick like push the shift an turn encoder?
(i’m at work itm)

avantronica · 2013-10-30T10:23:40.000Z

@dubmo: in grid mode you can nudge trig(s) using the method you are alluding to
@Dataline was referring to the automatic timing ‘correction’ that’s available globally or per track through the Note setup menu (Fn+Note)
nudging can be used creatively to get progressively wrong - teh track/global quantization correction is always drawing the trigs towards being precise ‘on the trig 1/16th’

you can also nudge trig(s) using the method i described in the Note page under uTM param using all the usual encoder/acceleration techniques

i have an issue whereby the quantization using the Note setup page is tediously slow and doesn’t allow acceleration - to make matters worse, the quantization correction is expressed in a range 0-127 whereas the possible correction steps are limited to 23 (ie always towards centre) - so …
…
… you’re turning a knob through values which are doing nothing most of the time - ie 0>127 for 23 steps of correction … go figure, needs sorting Elektron ! A handy menu is ruined here, it takes about 5 knob turns to turn on auto quantization fully this way at mo

Unless i’m getting something wrong here ??

audiocookbook · 2014-12-14T18:32:45.000Z

@Void, @Dataline: I’d like a little clarification here if possible. When I disable quantization globally and then set global and track quantize to 0 (out of 127) on the Note page it still doesn’t seem like I’m getting unquantized recording. Grace notes, for example, are omitted and tuplets seem rigid. This is much more noticeable at slower tempos for obvious reasons. Is there another setting somewhere that I’m missing?

avantronica · 2014-12-14T18:54:08.000Z

seq config menu, quantize recording (destructive) ?

audiocookbook · 2014-12-14T23:07:03.000Z

Do you mean the Sequencer Config in the Global menu? If so, that’s what I meant by global quantization. I have it unchecked. It’s definitely less quantized than when I have it checked. Perhaps the sequencer resolution is not high enough to capture nuanced timing (grace notes, etc.). Another clue is that if I record in poly mode those grace notes end up on top of each other instead of getting omitted.

avantronica · 2014-12-15T09:21:09.000Z

There’s 16 notes per bar and a finite space window for each, either side of each theoretical quantized 1/16th position there are 23/24th steps of resolution. I don’t know how Elektron close each recording window but you obviously have to think of this constraint in assessing whether it’s about the sequencer or expectation Try doubling the tempo and chaining two patterns to see if it feels better to you, but there’s still an inherent limitation on how close a sequence of notes can be … just a thought !

audiocookbook · 2014-12-15T14:35:13.000Z

Thanks for the explanation and the suggestion. I’ll give it a try. I expect there to be limitations. Often the magic happens while working one’s way around them. In any case I am thoroughly impressed by the depth of this instrument. Cheers!

Manoeuvre · 2015-07-22T00:26:40.000Z

""avantronica"":

@dubmo: in grid mode you can nudge trig(s) using the method you are alluding to
@Dataline was referring to the automatic timing ‘correction’ that’s available globally or per track through the Note setup menu (Fn+Note)
nudging can be used creatively to get progressively wrong - teh track/global quantization correction is always drawing the trigs towards being precise ‘on the trig 1/16th’

you can also nudge trig(s) using the method i described in the Note page under uTM param using all the usual encoder/acceleration techniques

i have an issue whereby the quantization using the Note setup page is tediously slow and doesn’t allow acceleration - to make matters worse, the quantization correction is expressed in a range 0-127 whereas the possible correction steps are limited to 23 (ie always towards centre) - so …
…
… you’re turning a knob through values which are doing nothing most of the time - ie 0>127 for 23 steps of correction … go figure, needs sorting Elektron ! A handy menu is ruined here, it takes about 5 knob turns to turn on auto quantization fully this way at mo

Unless i’m getting something wrong here ??

I’m quite new to the A4… But, Avantronica exactly expresses my frustrations & needs regarding a simpler Quantize functionality! Have I missed an update or any news?mis there any progress on the Quantize issue? Perhaps one of the weak spots in speedy performance! I spent ages the other night searching for Quantize values that I’d get in seconds in other programs! What am I missing here?

josker · 2015-07-22T08:05:15.000Z

""Manoeuvre"":

I’m quite new to the A4… But, Avantronica exactly expresses my frustrations & needs regarding a simpler Quantize functionality! Have I missed an update or any news?mis there any progress on the Quantize issue? Perhaps one of the weak spots in speedy performance! I spent ages the other night searching for Quantize values that I’d get in seconds in other programs! What am I missing here?

Hmm… I always play stuff in, then dial in the amount of quantization that sounds good to me. Maybe nudge an individual trig this or that way by a few increments.

Could you tell us a bit more about what you’re looking to do with the quantize? Groove template type thing?

L4rs3rik · 2015-07-22T09:53:36.000Z

""Manoeuvre"":

[quote=“avantronica”]@dubmo: in grid mode you can nudge trig(s) using the method you are alluding to
@Dataline was referring to the automatic timing ‘correction’ that’s available globally or per track through the Note setup menu (Fn+Note)
nudging can be used creatively to get progressively wrong - teh track/global quantization correction is always drawing the trigs towards being precise ‘on the trig 1/16th’

you can also nudge trig(s) using the method i described in the Note page under uTM param using all the usual encoder/acceleration techniques

i have an issue whereby the quantization using the Note setup page is tediously slow and doesn’t allow acceleration - to make matters worse, the quantization correction is expressed in a range 0-127 whereas the possible correction steps are limited to 23 (ie always towards centre) - so …
…
… you’re turning a knob through values which are doing nothing most of the time - ie 0>127 for 23 steps of correction … go figure, needs sorting Elektron ! A handy menu is ruined here, it takes about 5 knob turns to turn on auto quantization fully this way at mo

Unless i’m getting something wrong here ??

I’m quite new to the A4… But, Avantronica exactly expresses my frustrations & needs regarding a simpler Quantize functionality! Have I missed an update or any news?mis there any progress on the Quantize issue? Perhaps one of the weak spots in speedy performance! I spent ages the other night searching for Quantize values that I’d get in seconds in other programs! What am I missing here? 8-)[/quote]
Using quantize expecting swing?

avantronica · 2015-07-22T11:51:17.000Z

i can’t speak for the other poster, but not me … it’s just a very slowly geared encoder
.
i think it would be better if you could play loose and tighten things up a bit quicker
.
obviously the only quantise value is 1/16ths, so everything is shifting towards that (leaving swing aside) - there are only 23 steps and a very clunky/misleading way to dial those in - unless i’m missing a subtlety to having it have a 7bit range on a slow encoder rate !!

Manoeuvre · 2015-07-23T01:26:35.000Z

As Avantronica says! This quantisation set up is unnecessarily complex. And not particularly effective. Nor artisticly rewarding! Playing around for far too long for a basic quantize value. And then having to put swing in elsewhere. I think the system used in most DAWs is simpler and more effective. What’s the point of 0 to 127 subdivisions, when our targets are more specific? Unless this is a mathematician’s definition of art? Let’s get to the point. (And, in many people’s opinion, this angle to programming, throughout the sub structures is the weak point in an otherwise very creative machine!) Science over creative simplicity. Pluses and minuses abound naturally 7-)

josker · 2015-07-23T13:13:15.000Z

Oh okay, so you’d like to take the guesswork out of the 0-127 quantization value? Yeah, true, could be nice. I tend to be pretty lax when it comes to dialing quantization… I just turn the knob and see if sloppy turns to groovy. If not, i re-record or turn the knob all the way for full-on precision

avantronica · 2015-07-23T16:56:40.000Z

^ i don’t think i’m wrong about the 23 steps aspect, but there may be a way to ‘weight’ the higher range to attribute corrections over the trigs with varying ‘errors’ with timing - i doubt it though
it’s not so much about ‘guesswork’ as it’s about getting there sooner, especially given that some of the twisting is (likely) doing nothing
i don’t use it much, perhaps because it’s a little irritating
but tbh
i’m not quite sure how DAW quantisation (not a fan) can be compared, isn’t that a case of snapping steps to typically 16/ths or 32/64/8 - whereas the only viable quantisation on AF is 16 (i.e. per trig), the next best strategy being what we have, i.e. correction towards the steps
i may be missing something - my only issue is that the dial takes some turning and is maybe misleading too