XOR Userforum
Still Struggling with Quantizing HALP - Printable Version

+- XOR Userforum (https://xor-electronics.com/forum)
+-- Forum: Products (https://xor-electronics.com/forum/forumdisplay.php?fid=3)
+--- Forum: NerdSEQ (https://xor-electronics.com/forum/forumdisplay.php?fid=6)
+---- Forum: General Questions (https://xor-electronics.com/forum/forumdisplay.php?fid=17)
+---- Thread: Still Struggling with Quantizing HALP (/showthread.php?tid=1030)

Pages: 1 2 3 4


Still Struggling with Quantizing HALP - Karlo - 03-07-2021

I have a pattern with a bunch of different notes spaced every quarter note. Trigger is 40 for each note

table on row00

Table 
Speed 06
Type Loop
Range 00 > +0C

Allow notes D, F, G#

... it only plays those notes, but I can hear the table cycling through the quantized value on the decay in-between my quarter notes.

I can hear the table quantizing/changing pitch to the tails of my notes, how do I make it stop so It holds the quantized value until a new trigger?


RE: Still Struggling with Quantizing HALP - Karlo - 03-10-2021

Bumping because I editing this for help because I'm still struggling with quantizing.


RE: Still Struggling with Quantizing HALP - Karlo - 03-11-2021

Anyone?


RE: Still Struggling with Quantizing HALP - theotteryears - 03-11-2021

I think you could either shorten your decay, or if this is not feasible - then run the pitch CV out into a sample and hold, and mult the trigger out into the SandH trigger in and your envelope. I believe that should sample the CV only when you have a trigger, and not let the changing CV in...


RE: Still Struggling with Quantizing HALP - mgd - 03-11-2021

Maybe you can describe more precisely what you actually did, what you expect precisely and what happens.

From the above I basically understand "you have notes that are correctly quantized as designed but there are strange artefacts".

Is that what happens?

Kind regards,
Michael

PS: I've tried to replicate your findings and the only setting, that created something remotely resembling your description was when I had set "quantize" to "coin". That basically went away when I inceased the time to 24 (4*6 or 18 in hex).

Is that what you do?


RE: Still Struggling with Quantizing HALP - Karlo - 03-11-2021

(03-11-2021, 03:33 PM)mgd Wrote: Maybe you can describe more precisely what you actually did, what you expect precisely and what happens.

From the above I basically understand "you have notes that are correctly quantized as designed but there are strange artefacts".

Is that what happens?

Kind regards,
Michael

PS: I've tried to replicate your findings and the only setting, that created something remotely resembling your description was when I had set "quantize" to "coin". That basically went away when I inceased the time to 24 (4*6 or 18 in hex).

Is that what you do?
 
Yes

So you set the ticks to 24 which slows the table way down?  ...that makes sense as the table wont update or quantize 6 ticks per quarter note. That's seems so simple and obvious, clearly I'm novice when it comes to trackers. 

Theoretically (i'm not in front of the nerdseq at the moment to check) but 24 ticks is great if your just quantizing quarter notes, but what if you have a pattern than has some quarter notes and then some whole notes too, then you'll still hear the table quantizing the ticks at quarter note intervals from the table while the whole note plays through.

I suppose you could just use a different table for each note duration, 16ths, 1/8ths, half, whole, etc etc and then you wouldn't hear the quantization steps / tick because the table ticks would match the note lengths.

I hoping there is more direct path to pitch quantization than having to use different tables for each note duration.

My apologies if I'm not clear on the correct terminology.


RE: Still Struggling with Quantizing HALP - Bleep bleep - 03-16-2021

Hello, you could set your table with an automator as source. 
Then use this automator in envelope mode and trigger it with the gates of the track you are using.

This gonna make the table to go one step every time you trigger a note.

Another way to do the same thing is to use a cv input instead as a source and just feed it with the trigger output of the track you use.

So you have choice to spend either a cv in or one envelope and one automator Smile


RE: Still Struggling with Quantizing HALP - mgd - 03-16-2021

(03-16-2021, 12:41 PM)Bleep bleep Wrote: Another way to do the same thing is to use a cv input instead as a source and just feed it with the trigger output of the track you use.

That's a neat trick Smile

Essentially that means at least for local tracks triggers of the track you use should be available as input source internally w/o having to plug a physical cable.

For CV16 (not yet available) there should be the option to use one of the 6 lanes (for lack of a better word) as input source.

Kind regards,
Michael


RE: Still Struggling with Quantizing HALP - Karlo - 03-16-2021

(03-16-2021, 12:41 PM)Bleep bleep Wrote: Hello, you could set your table with an automator as source. 
Then use this automator in envelope mode and trigger it with the gates of the track you are using.

This gonna make the table to go one step every time you trigger a note.

Another way to do the same thing is to use a cv input instead as a source and just feed it with the trigger output of the track you use.

So you have choice to spend either a cv in or one envelope and one automator Smile

I'm not at the NerdSeq now, but do I select the automator as source instead of tics in the table? Where do I assign the automator to table?

Edit: in the manual, it does appear that source is set from inside the table. I'm going to try this tonight! Thanks for the tip!


RE: Still Struggling with Quantizing HALP - mvdirty - 03-16-2021

As a potential alternative, I believe (but have not double-checked the exact mechanics) you could clock the table from FX. Might be worth a look if you want to get fancier and/or can’t afford to tie up an automator, etc.