Euclidean

i think so... i don't see why not anyway.

 

I tried my heart out and was unable to get these two to work together. Trying to get the tempo from salamanders patch to work with yours gave me the most trouble.

 

I've been really determined to get this to work and keep trying at it however the control schemes for playmode's patch and your interface are so different that its pretty difficult and not very self evident how to marry the sequencer with the interface. Is there a way somehow to directly turn the algorithm in the interface patch into a sequencer for a better control sceheme compatibility? :S

 

well sure, you're just calculating them one by one using an iterator. you could shove them into an event table or you could use a router to feed a sequencer.

 

This is pretty advanced stuff. I'm looking in the display handler macro and I don't have the slightest clue what is going on or where to go. I'd love to get to use this thing so any more detailed directions and maybe a screen shot would be great.

 

the macro simply called 'macro' inside the display handler takes the number of steps, the number of fills and an index ('++'). it outputs a 0 if the node denoted by ++ is off and a -1 if it is on. (the value for a filled box in the display handler).

you can use the output in conjunction with the value of '++' to write the values to whatever sort of table you like.

 

Could you explain where and how to plug the iterator? I'm just a dumb user, not much of a builder in any way. I see this half finished beautiful thing and I feel obsessed with getting it to work.

 

the iterator is already there, you just need to use the values it spits out in conjunction with the output from the macro.


in fact, don't even bother. every time you turn a relevant knob, the index and obj values from the display handler give you the index (1-16) and the value (0 or -1). -1 means on. use eventwatcher if you need help figuring it out.

 

playmodes patch doesn't use any tables or anything, it just goes to a pitch/gate out which is the same as I would like to do, infact I would like if I could just patch the two together but you used a completely different control scheme.

Your patch has two main parts that aren't connected, the time part from the ramp and the event part from the gui they just need to be connected but each time you give a direction I get more confused.

 

sorry i don't know what to tell you.
i don't have the time or interest to make this a real project right now.

 

a NoOb question...

but how do I get these Euclidian sequencers to communicate with a New Wireless instrument?

 

tut, tut, Richie, you are no longer a NoOb

have you checked your manual?

also try to reverse engineer the example on a previous post that uses SteamPipe.

Tip: click on the Eucllidean Instrument header, make sure Properties is chosen in the Browser, choose on CONNECT and look down until you see MIDI OUT and To Internal Instruments.

sowari

 

Thank you very much for the response. Everything's working out great.

My brain malfunctioned. I was thinking back to the old way of having a midi tab at the top of the Reaktor display.

 

Figured it all out and posted https://co.native-instruments.com/index.php?id=userlibrary&type=0&ulbr=1&plview=detail&patchid=11871

 

cool. moving forward, i think an ideal implementation might have 8 of these, and be able to choose a scale and starting octave that would set the pitch knobs for all of them. there's a scale make in automata but it would probably need some pretty heavy mods...

btw, i think the 'clock hand', so to speak, is slightly off centered in your upload - and now i think i'm having the notes go off 1 cell early, but maybe i modified the wrong thing.

 

Yeah I messed with the clock hand trying to make sense of when it coincides with a trigger. They definitely go off one cell early and if there is a fill on the first spot it won't trigger.

 

in my original upload, the hand's position is based on the midi clock.
easier i think just to have the midi clock do it's own thing and trigger from that, and let the hand run in sync.

 

I put the graphics back how you had them and removed the sync fix I did and added a demo instrument. I couldn't figure out how to trigger from the midi clock you made for the clock hand.
View attachment Euclidean.01.zip

 

Yes! that's what i was talking about. well done. i meant to just use the midi in and forget about the hand, sorry i couldn't explain better.

 

Hey guys! Playmodes here....
I've been messing further with the euclidean thing, and added some new features: accents and scales

In the accents section you can define the number of velocity accents in the sequence, and they will be assigned following the euclidean rule!

Then there is the Base+(should be called pitch indeed...) and Interval pots, which define the sequence of notes and its progression... basically this turns the instrument into an euclidean arpeggiator (should we call it like that?). I added a global scale selection, grabbed from somewhere in the UL...should check who did that, because it's nicely done and a very useful snippet of core code.

I'm sorry i haven't followed the graphic sequencer fork... it's really cool!!! i've been disconencted from the instrument during a long time, and i'm happy that it got its own life with some cool uploads to the UL.
Maybe someone could update this one with the graphical interface? would be nice to have the accents represented!

enjoy it!

http://www.playmodes.com