Multiply Quantisation issue

[stevoj]

This is probable going over old ground (I'm sure I've seen the question raised before), but there appears to be a slight bug (or maybe it's a feature:)). When using multiply, with quantisation mode set to subcycle, there is often a gap in the overdubbed material, either at the start or the end of the loop. If I set Quant=Loop, then multiply seems to work OK.

I was wondering if it's possible to have a separate setting to set Multiply Quantisation separately (or is it already there and I'm not seeing it?).

How do other folk get around this issue?

[Per Boysen]

I ususally use Multiply and Overdub together, which I have found to help ("Quant = SubCycle" here too). There was some Multiply fix in the latest upgrad that I haven't yet checked out in detail.

[Jeff]

I'm not aware of a problem here, but I usually use Cycle
quantization with multiply.

Look at the preset parameter named "Round Mode" and see if it is checked.
If not, check it and see if that helps.

[stevoj]

Hi,

Checking the round mode box seems to make no difference.

I confirm that multiply works OK with Quant set to Cycle (or loop).

But if Quant=SubCycle, if I end a multiply with overdub, the end of the loop is OK, but there remains a gap at the begining of the loop.

Stephen

[Jeff]

I played around with this a bit and didn't see anything unusual.

Can you elaborate more on what the "gap" is? Were you overdubbing
something that didn't get overdubbed?

If you do this again can you pay attention to the color of the loop meter
while you multiply, the meter will be red (the default color unless
you change it in the palette) during any recording mode (record, multiply, overdub, etc). If it isn't red, then it won't be overdubbing.

I'm wondering if the subcycle quantize means that the multiply isn't
actually starting until the second subcycle of the loop if you're a little
late with the multiply, this would cause a "gap" at the beginning.

If you pressing the Multiply well ahead of the loop start/end point?

[stevoj]

You're absolutely right in your thinking Jeff, I am pressing Multiply too soon, and also stopping it too soon - the red recording light turns to green before I really want it too. Maybe I'm just too used to the EDP way of working.

Essentially, the problem seems to be that the recording within Multiply needs to be rounded properly (in my understanding, the multiply recording length needs to be an exact integer - I know that the multiply length is an integer, I mean that the recording within that length needs to be exactly the same as the multiply length).

Yes, setting Switch Quantisation to cycle or loop pretty well seems to solve this, but I like to have this set to sub-cycle.

Anyway, it's no big deal, as, like Per, I find that the workaround is to start off in overdub, then any 'gaps' are filled out without problem.

Stephen

[Jeff]

Hmm, I thought it was working close to the EDP, at least as far
as the start and stop points. There is another subtle difference
but it shouldn't affect the start/end.

If you have Round Mode checked, the Multiply function will overdub
exactly a multiple of one cycle relative to where you started. So if
you started at subcycle 3 of 4 the Multiply will add cycles but always stop
overdubbing at subcycle 3. For example:

- Multiply starts on subcycle 3
- Multiply reaches the end of the loop (subcycle 4) and adds a new cycle
- Multiply stop on subcycle 6 of the now 8 subcycle loop
- Multiply rounds to subcycle 7 (4 subcycles per cycle relative to
the start at subcycle 3
- Multiply is not active during subcycle 8

If you think the EDP doesn't work like this I'd like to know. Also be sure
in the Preset you have Multiply Mode set to "New".

If you always want Multiply to start on a cycle boundary and have other
things quantized to subcycles, then you can use a script.


!name Multiply Cycle
Wait cycle
Multiply


or


!name Multiply Cycle
Variable saveQuantize quantize
set quantize cycle
Mutiply
set quantize saveQuantize


The difference is that the first script waits until the next cycle and the
second script schedules a quantized Multiply at the next cycle. There
are subtle differences between the two, I usually use the second approach
because the script ends and gets out of the way immediately.

[stevoj]

Yeah, one of those scripts will certainly work, thanks.