Loomer

ThomasHelzle · Post by **ThomasHelzle** » Fri Jan 04, 2019 1:01 am

I have a request: Many of the modules need some kind of value on the inputs, but in a lot of cases, those values will be constants that never change, so all the data nodes clutter the interface without adding anything useful.
Wouldn't it be much more efficient if a node could just have default values set in it's properties for it's inputs?
Like a clamp between 0 and 127 to keep a value in the Midi range.
Could be a single node instead of three. IMO that would be very helpful to keep things tight.

And another one: I create an interface for my Midi Mangler and it uses up tons of nodes, mostly because the rotaries and faders have neither a naming field nor a value field built in. So again, something that could be done in one node needs 4 (The rotary, a name text field, a value text field and a convert to string to make the value show up in the text field).
Since I can't see many people needing rotaries that have no name and show no value, I would think this is so common that it would make sense to consider to have those all in one node.
(with switches to disable them if somebody doesn't need them or does want to create a custom layout)

Cheers,

Tom

Delta Sign · Post by **Delta Sign** » Fri Jan 04, 2019 1:06 am

Yes, I think that would be a good idea.

ThomasHelzle · Post by **ThomasHelzle** » Fri Jan 04, 2019 1:36 am

Ok, I'll call it a day now.
My progress so far:

Basically I rebuild this tool with some extensions:
https://www.screendream.de/code/toms-midi-mangler/

Good stuff.

Cheers,

Tom

Delta Sign · Post by **Delta Sign** » Fri Jan 04, 2019 1:50 am

Awesome

Delta Sign · Post by **Delta Sign** » Fri Jan 04, 2019 1:56 am

My last thing for the day:

This creates a random 4 note sequence, loops the sequence and then has a chance to change one note of the sequence after each repetition, basically creating a slowly evolving sequence.

It sounds like this:
https://soundcloud.com/deltasign/evolving-architecture

mannymang · Post by **mannymang** » Fri Jan 04, 2019 2:06 am

ThomasHelzle wrote: Fri Jan 04, 2019 1:36 am Ok, I'll call it a day now.
My progress so far:

Basically I rebuild this tool with some extensions:
https://www.screendream.de/code/toms-midi-mangler/

Good stuff.

Cheers,

Tom

Really cool!

mannymang · Post by **mannymang** » Fri Jan 04, 2019 2:13 am

Delta Sign wrote: Fri Jan 04, 2019 1:56 am My last thing for the day:

This creates a random 4 note sequence, loops the sequence and then has a chance to change one note of the sequence after each repetition, basically creating a slowly evolving sequence.

It sounds like this:
https://soundcloud.com/deltasign/evolving-architecture

Very nice, thanks for sharing! It will definitely be useful in my explorations.

woggle · Post by **woggle** » Fri Jan 04, 2019 3:52 am

my mistake

mannymang · Post by **mannymang** » Fri Jan 04, 2019 4:17 am

AZZIN wrote: Thu Jan 03, 2019 9:43 pm Ok, I got my first "chaotic/recursive" equation in Architect done. It was not "easy" or at least not intuitive. It is the Henon map https://en.wikipedia.org/wiki/H%C3%A9non_map, here is the Matlab/Octave code:
Code: Select all
alpha = 1.4
beta = 0.3

M = 1000;
x = zeros(1,M);
y = zeros(1,M);

x(1)=0.0;
y(1)=0.0;
tmp = 0.0;

for i = 2:M
  tmp = 1.0 - alpha*(x(i-1)*x(i-1)) + y(i-1);
  y(i) = beta * x(i-1);
  x(i) = tmp;
end
To implement this I ended up with something quite complex, with a macro called Henon_algo initialized by two signals (one reset and one init) and then continuosly triggered by a metronome. This will open up some possibilities for me to start midi generation based on chaos algorithms. The following attachment is the macro, together with the main patch. Does anyone (or Colin) have suggestions on the coding, or how to improve the same patch with less instructions? It was quite tough to understand the order of execution of signals and I had to use several "order" objects in sequence. Feedback welcome.
Thanks, Alberto

Very nice AZZIN! I was able to replicate your work from the images. I have no suggestions as I'm an amateur. Now I just need to figure out how to use it! Thank you for sharing!

mannymang · Post by **mannymang** » Fri Jan 04, 2019 8:16 am

I was able to do something with AZZIN's algo. It throws an error but it's not a showstopper:
https://soundcloud.com/user-332831953/e ... chitect-13
Thanks again!

colin@loomer · Post by **colin@loomer** » Fri Jan 04, 2019 9:06 am

ThomasHelzle wrote: Fri Jan 04, 2019 1:36 am
Basically I rebuild this tool with some extensions:
https://www.screendream.de/code/toms-midi-mangler/

OK, now I'm impressed. That looks great. Am I right in saying you are a graphic designer by trade? If so, what feedback could you give me on the panel and UI creation tools. Is there anything in particular missing?

colin@loomer · Post by **colin@loomer** » Fri Jan 04, 2019 9:07 am

ThomasHelzle wrote: Fri Jan 04, 2019 1:01 am Wouldn't it be much more efficient if a node could just have default values set in it's properties for it's inputs?

Yeah, I toyed with that idea but couldn't get it quite right in time, but I always intended to return to it.

mannymang · Post by **mannymang** » Fri Jan 04, 2019 9:09 am

AZZIN's algo rock style:
https://soundcloud.com/user-332831953/e ... chitect-14

mannymang · Post by **mannymang** » Fri Jan 04, 2019 10:01 am

Sorry, can't help myself.

Diggin AZZIN's algo rock. Tweaking live:
https://soundcloud.com/user-332831953/e ... chitect-15

woggle · Post by **woggle** » Fri Jan 04, 2019 10:02 am

some amazing work there mannymang - and AZZIN of course. I am still very much at the struggling stage but luckily am in no hurry.

Loomer

KVR Audio

Architect beta for macOS, Windows, and Linux. 0.10.5 now available