- This topic has 190 replies, 3 voices, and was last updated 1 month ago by
.
-
Posts
-
really an alpha
https://www.dropbox.com/s/hhoo49bgypth25i/Multi_Euclid%20v0.2.amxd?dl=0happy holiday
this one uses 4 euclidean seqs
independentish
i have them feeding one scale scanner atm
i could set them independent ranges – which would mean independent scale scanners
or i might just have switchable single note outputs for drum stuff
was going to be a lockstitch rewritedave
v0.31
https://www.dropbox.com/s/ju2yr0g95472f6w/Multi_Euclid%20v0.31.amxd?dl=0housekeeping
fixed:
timing was 1 step behind – not the usual reason :/
root selection not working = use UI keyboard to set root
button to use MIDI note to select root
added:
display each sequencer on keyboard
next up:
add duration seq?
+
lockstitch type tools for sequencer interaction and drum/trigger sequencingmay use a switchable UI for use as a trigger sequencer
or
second device?dave
I like it
>root selection not working = use UI keyboard to set root
>button to use MIDI note to select root
What’s the use of the dot at the extreme top left BTW ?> add duration seq?
yes>+lockstitch type tools for sequencer interaction and drum/trigger sequencing
>may use a switchable UI for use as a trigger sequencer
>or
>second device?
might add value, but already quite crowdybegan as a Lockstitch update
yes is quite crowdy – i have a few UI ideas for thatthe dot is top right – unless you see another one…
and has not been connected to the right object
and so doesn’t function at all :/
it switches to MIDI note in for root selection…alpha v0.4
https://www.dropbox.com/s/tctz2rzmwn2nb06/Multi_Euclid%20v0.4.amxd?dl=0
lots of tidying up
added duration seq – duration = up to 1*step length including clock divider/multipliers
still not initialising correctly
euclidean display working properly now
thinking about individual ranges next
now that internal timings are okdave
i don’t like concentric circles
can’t follow what is happening at all
so
image has 2 sizes of display – i prefer the smaller one
multislider below for steps, hits etc.
4 of these…
+ Clock display from Adlais/Iosif
this cleans up the UI loads
i’m thinking about different ways to access the Scale Scan block
for use with instruments or drum racks etc
which will be next…so this looks like a very extended Lockstitch update
dave
beta 0.5
https://www.dropbox.com/s/07749rehl3ffkmm/Multi_Euclid%20v0.5.amxd?dl=0some code tidying to do then
accessing the scale scanner then
UI
davebeta 0.51
https://www.dropbox.com/s/rfbmprekuoaqqlk/Multi_Euclid%20v0.51.amxd?dl=0
i’ve added 4 combiners which combine the sequences output by the euclidean modules in interesting ways
they don’t look great but are functional and follow on from Lockstitch
they may also be too many optionsi am on holiday at the moment
so getting on with it…dave
i am thinking about a lot of the possibilities for this…
while is quite nice and interesting
is also not necessarily inspiring…so:
euclidean modules generate a sequence of 0s and 1s
a limitation of this is that they are evenly spaced – more or less
i have been looking at ways to combine them which are more interesting:
following each other, lacing them etc.
but that may mean the clocks are no longer relevant
as the clock will count through the sequence generated after combination
so the graphics – as they are – become less important = a side showi’m going to play with these ideas
as i don’t like the results with the previous ‘combiners’
see where it takes me
so back to alpha
any thoughts/ideas?
now is a good time to throw them in the ringdave
this is a group of 16 step trigger sequences
they are generated from 2*8 step euclidean trigger sequences
one with 4 hits the other with 3 – no rotation
the calculations are simple
row 5 is a reverse of 4 – so really there are only 7 variants
as reverse can be offered for allmost of these patterns are not typical ‘euclidean’
as they are not so evenly distributedMight be fun for each timer to have a co-efficent of the main tempo, such that you can create phase differences between them.
As for independent scale scanners, couldn’t that be done with parallel instances of them in the same Group device?
I do like the idea of it however, both the independent ranges and the independent scale selection idea, but again, that could be done with multiple instances. I’m far more impressed with using the built-in tools, when it comes to performance stability and leanness. And I’ve notice on the microtonic forums for example, that people wish there was a single-pad version of it (such that you could plant it in a drum rack, or minimize the number of pads and bulk necessary)
But I like the potential of poly-modalism of bela bartok and the phase music of steve reich in the same device…
That root selector is not working
And the entire set crashed-a single midi track-when plugged into a push and I attempted to create a new scene by capturing the performance of the output on the multi-euclid.
Also, on the scale readout, I don’t see the different color pads as being particularly easy to follow. Maybe if it was vertical orientation, such that it matched up with a midi-note/piano roll design. And the colors would make sense if they corresponded to the color choices on a push, for example, because the clip readout is able to retain the separate color of each pad. Otherwise, I’m not retaining any information in my Neanderthal brain from all the colors bouncing around…(particularly because I don’t see color labels for the separate seqs, and the playhead doesn’t match the color on the scale view.)
Finally, the iOS Fugue Machine tends to be easier to follow, and can implement that phase idea I mentioned prior.What if it was laid out a bit like a trolly car or steam locomotive on tracks. Put the wheels on the bottom so we get a sense of movement. Put the directional instructions to the front (right) of the trolly, not in the middle. Put the meters up top. Have the scale notes spit out the back on the left of the device, stacked vertically, equivalent to you recording a midi-clip and monitoring the output spitting out…So visually you get a transference of wheels moving, and ground rolling by. Maybe put the clock (or multi-clock) in the middle as a polarity (like in the fugue machine) such that you get a sense of the motor/pistons that translate into the wheels. (If you’re overly ambitious, let the pistons change in length so it looks like a wobbly jelly car as it rolls) somewhat like these animations:
https://jackschaedler.github.io/circles-sines-signals/dft_introduction.html
- You must be logged in to reply to this topic.