array sequencer test

[mztk]

here is a demonstration of array sequencer working
driving SE Polysynth. CV row only - it has moved on
a bit since. see notes in zip. btw: it runs on an insert
fx slot in vst host(didn't put everything in for this).

https://app.box.com/s/66e338cedu4lbvjezl1x

(let me know if the boxnet link worked; was asking for
logon a few days ago -?..-)

[tl]

boxnet link worked...
will test asap.

cheers,
tl.

[tl]

tested it a bit (in plogue bidule on win xp sp3 32bit)... as a user.
... cv sequencer changes polysynth pitch.
and reacts to host tempo changes...
but there's a difference (concerning timing)
between what i see and what i hear.
actual influence of the sequencer and visual representation
(displayed values and led indicators)
are out of sync.
and some sequencer controls (esp. "use every n-th step") don't work.
even after clicking reset or run several times.

cheers,
tl.

as i said i'm just a plain user giving feedback
and first of all having great respect for yr efforts and the work
you put in yr project.

[mztk]

yup, tl and thanks for testing it! as you see, it is
the first running protoype, with all the bugs - but the
core thing does run, and seems quite regular so far.
lol: it *more or less* works..

the main difference with this is the method of generating
the cvs and gates and storing them. 'old' method uses
2 patch modules for each step, eg: 32 modules (at least),
whereas this uses only 2, to store text data. other people
know how to do this of course, but i'm just figuring it out.

i now have it auto-updating which was my intention. lots of
other stuff done for stage 2 demo-(which is going to be a
version before 'auto-updating' because it's worth a look)

oh yeah 'run' on/off and 'reset are separate, so you may be
able to knock it back into sync by hitting reset.. and keep
hitting that update button...or just clear+update, and
randomize again.(it is much better now... )

(antto is shaking his head going oh no that's not how you do it...)

[antto]

i have absolutely no clue what you described, and i can't test anything since i don't have these modules

just make sure the actual control signals are not dependant on the GUI->DSP connection, since that is not sample accurate
what i mean is.. your sequencer should know all it's data on the DSP side at all times

[mztk]

i was kidding.

it's DH array stuff and KDL converters - i'm actually trying to
figure out how to use them but that's a plugin draft i uploaded;
it sort of runs as a fx on an insert on a channel(bcs i didn't put the
stuff in there to make it an instrument yet)

trying to work out exactly where you mean, GUI > DSP -float to volt?
or at patchmem? as you can see there is a gap here between the
text array held on? the text entry2? no: on the patch array float,
and what is written to the DH array sequencer. ( why i showed
it like this before fixing it)

sample accurate: yes, i was wondering: since the dsp side is capable
of 44.1khz (unless i'm getting mixed up) that should be ample to run
whatever a 16step sequencer could need. ?? is this the case ?? is it
pointless to try to run a sequencer 'gui side' - i can already see
problems: knobs not being in the right position, and sometimes a
preset loads without changing the pitches; quite weird. but i'm
going to see i if can get it to work anyway.

could you give me some insight into how i might rotate a sequence?
i've got something where i can move it to the right and loop/wrap round,
but not to the left - (or would it simply be with minus values?)

[mztk]

ok, what i'm getting at the moment is no update of control
position on preset/patch change - which i know is to do with
the way the array is written to the patchmem. doesn't seem to
retrieve the control positions atm, lol. i'll find the fix for
this.

this can produce all sorts of weird stuff like being able to
use the gates of one patch on the next until it gets an
'update/write' trigger.

also need to ensure display remains syncronised with what is
actually going on, re: start/reset. but otherwise seems to be
going ok, quite snappy action; remains to be seen where it is
in sync with hostbpm..

antto: absolutely agree that it would be best done in a dedicated
module - in the meantime it is teaching me the principles ;o)

[mztk]

here:

https://app.box.com/s/zi5d2g3wzpmit6f7rse9

is a prefab demonstrating how i'm using these DH Array
modules. i have no idea if it is correct, it just seems
to do something, some of it.

basically: the knobs are the values, and the array module
is being updated at regular intervals, this being triggered
by the bools ticker.

[mztk]

ok, so here is this thing again - got a bit more done to it
by this point, have done more since. messed this draft up,
missing out one sample set but it really doesn't change much.

https://app.box.com/s/8kqpw6w49la56yyzuux0