Quick update:
"In playback, I would expect this to shift R1's start and
end times" should read *P1*'s start and end times, sorry.
LFOs set to trig might actually work, but then I'd have to
have the tracks' trigs on the same steps, which isn't really a good
option.
On Wed, Jan 09, 2008 at 02:11:38PM -0800, Niall Munnelly wrote:
> I've encountered a weird behavior with LFOs in a new kit,
> and I'd appreciate it if someone would corroborate or refute
> my findings.
>
> Set up R1 to capture a snippet of audio {using MLEV or ILEV,
> whatever's handy} and P1 to play back with a START value of
> 32 and an END value of 94.
>
> Edit the P1 track's LFO with the following parameters:
>
> TRACK whatever the P1 track is
> PARAM = END
> SHP1 = SQUARE
> SHP2 = unused
> UPDTE = FREE
> SPEED = 64
> DEPTH = 16
> SHMIX = 0
>
> Copy this LFO and paste it to the R1 machine, changing only
> the TRACK value to P1's track and PARAM to START.
>
> In playback, I would expect this to shift R1's start and end times
> forward, then backward, equally and periodically. To my
> ears, this isn't the case. There's an audible stutter,
> effectively a third pattern, that would indicate that the
> LFOs are not synchronized. I also hear it when UPDTE is set
> to TRIG on both LFOs.
>
> Would one or two of you please verify that this is
> happening, or that I'm just talking bollocks? Am I trying
> to effect these simultaneous modulations of START and END
> the wrong way?
>
> Thanks.
>
> --
> Yours,
> Niall.
> .. . . . . . . . . .
> Aleph Null. A Simple Insinuation Around Silence.
> http://aleph-null.net
> .. .. gpg public key - http://aleph-null.net/niall.gpg .. ..
--
Yours,
Niall.
.. . . . . . . . . .
Aleph Null. A Simple Insinuation Around Silence.
http://aleph-null.net
.. .. gpg public key - http://aleph-null.net/niall.gpg .. ..Message
Re: MDUW LFO Confusion
2008-01-11 by Niall Munnelly
Attachments
- No local attachments were found for this message.