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

[woggle]

... By the way, someone emailed me to ask if there was anything specific anyone wanted to see, macro or Lua script-wise, and he would build it. If anyone has any requests, I'd be happy to pass them on.

I would love someone to make something that can read in a midi file and then permute the midi information - pitch, duration, note onset. Not replace with random values but randomly permute the existing values. Then output to a new file.

That would be a huge help for me as I do this a lot in Matlab so it should help me to understand how things work more in Architect.

[Delta Sign]

I think we need a "Z-Order" value for components so we can layer UI-elements and define what's in front or in back. Right now it seems to be sorted by order of creation, so I can CTRL-X and CTRL-V to bring something higher up, but IMO this would be good to have built right in as proper settings.

You can actually right-click on a GUI element and use "Send to Back" and "Bring to Front" to change the order as well. However, I do agree a proper setting would be much nicer.

[Kalamata Kid]

I would love someone to make something that can read in a midi file and then permute the midi information - pitch, duration, note onset. Not replace with random values but randomly permute the existing values. Then output to a new file.

TO be able to lock some notes.
also
To make chords of notes that are close together and delete extraneous notes.
Ok, I admit this is an odd FR.

[Delta Sign]

... By the way, someone emailed me to ask if there was anything specific anyone wanted to see, macro or Lua script-wise, and he would build it. If anyone has any requests, I'd be happy to pass them on.

I would love someone to make something that can read in a midi file and then permute the midi information - pitch, duration, note onset. Not replace with random values but randomly permute the existing values. Then output to a new file.

The thing I posted yesterday actually does something along those lines. It generates a random 4 note sequence once, loops it and has a chance of changing one note of the sequence after each repetition, resulting in a slowly changing sequence. This could easily be applied to a MIDI file instead of the randomly generated sequence, I suppose.

The results are surprisingly musical for something that is basically entirely random

https://soundcloud.com/deltasign/evolving-architecture

Adding variation to note duration and onset sounds like an interesting idea.

[woggle]

I would love someone to make something that can read in a midi file and then permute the midi information - pitch, duration, note onset. Not replace with random values but randomly permute the existing values. Then output to a new file.

TO be able to lock some notes.
also
To make chords of notes that are close together and delete extraneous notes.
Ok, I admit this is an odd FR.

Once I get the basic setup I can try and extend it - particularly if it is in Lua, which I have no experience in but should understand from writing this in Matlab/Octave already. But I also want to be able to understand this in the native Architect node system. Having a starting example with an algorithm I already use and understand would be great

[woggle]

... By the way, someone emailed me to ask if there was anything specific anyone wanted to see, macro or Lua script-wise, and he would build it. If anyone has any requests, I'd be happy to pass them on.

I would love someone to make something that can read in a midi file and then permute the midi information - pitch, duration, note onset. Not replace with random values but randomly permute the existing values. Then output to a new file.

The thing I posted yesterday actually does something along those lines. It generates a random 4 note sequence once, loops it and has a chance of changing one note of the sequence after each repetition, resulting in a slowly changing sequence. This could easily be applied to a MIDI file instead of the randomly generated sequence, I suppose.

The results are surprisingly musical for something that is basically entirely random

https://soundcloud.com/deltasign/evolving-architecture

Adding variation to note duration and onset sounds like an interesting idea.

thanks - I will look closely at that today - here is an example of the sort of thing I would like to use Architect for ..."A piece using surrogate statistical techniques to generate new works from old. I used a recording of the loudest drops of rain falling into a swimming pool as the timing sequence and mapped the pitch sequence of gymnopedie#1 onto that. "
https://soundcloud.com/greghooper/unselected

and another using the pitch permutation technique https://soundcloud.com/greghooper/varia ... mnopedie-2

[cturner]

Ok, I got my first "chaotic/recursive" equation in Architect done.

Greetings-

Do you know about the André Sier/Richard Dudas abstractions for Max?

http://s373.net/code/A-Chaos-Lib/A-Chaos.html

Max is a pretty different language from Architect's, and Siers' work is in C language, but you might find something of value there. (Dudas did the "abstractions" in Max for MIDI control.)

I believe these still work in Max 7 (tried a bit just a second ago), so perhaps you can get these going in a Max 8 demo.

HTH, Charles

[ThomasHelzle]

I think we need a "Z-Order" value for components so we can layer UI-elements and define what's in front or in back. Right now it seems to be sorted by order of creation, so I can CTRL-X and CTRL-V to bring something higher up, but IMO this would be good to have built right in as proper settings.

You can actually right-click on a GUI element and use "Send to Back" and "Bring to Front" to change the order as well. However, I do agree a proper setting would be much nicer.

Thanks a ton, somehow I managed to miss that
But yeah, I'd prefer a z-depth setting too.

Cheers,

Tom

[ThomasHelzle]

My Midi Manglers graph became quite a mess in some parts and I haven't found a "paradigm" yet that allows me to build a clean structure - which I'm normally a big fan of.



Part of it is the "jumping data input" we discussed already where wires cross a lot, since the main data wire doesn't stay always on the left, but part also is, that there is no "wire dots". This is how they look in Houdini:



Those dots (on the right) can be placed with ALT-clicking on a wire, can be dragged wherever one wants and allow to create really clean and clear structures where normally the wires would overlap other nodes. They don't do anything to the signal and are purely organisational.

Cheers,

Tom

[ThomasHelzle]

Also Tom, if you get a second, could you check if this build fixes your issue with plug-ins missing when transferring a patch from one machine to another? You'll need to install the new build on both, resave the preset, and then transfer it. No rush, as I believe I've already reproduced and fixed this, but it'll be good to get a second opinion.

I saved the Bitwig project on my main machine, installed 0.9.3 on my laptop and was able to open it there with all the plugins found. Then I saved it there, transferred it back and sadly the plugins are still all red.
I also saved the Architect preset on my laptop (all green) and transferred that to my main machine, again I had red icons in the mixer.
But when I created a new file on the laptop and put the same VSTs in there, they transferred green and working to the main machine, so I guess newly created plugins work but not those in already existing files?

But this is great as it is already, that initial file was not important in any way and I can just replace/remove the VSTs.

Thanks a ton!

Tom

[mannymang]

... By the way, someone emailed me to ask if there was anything specific anyone wanted to see, macro or Lua script-wise, and he would build it. If anyone has any requests, I'd be happy to pass them on.

I would love someone to make something that can read in a midi file and then permute the midi information - pitch, duration, note onset. Not replace with random values but randomly permute the existing values. Then output to a new file.

The thing I posted yesterday actually does something along those lines. It generates a random 4 note sequence once, loops it and has a chance of changing one note of the sequence after each repetition, resulting in a slowly changing sequence. This could easily be applied to a MIDI file instead of the randomly generated sequence, I suppose.

The results are surprisingly musical for something that is basically entirely random

https://soundcloud.com/deltasign/evolving-architecture

Adding variation to note duration and onset sounds like an interesting idea.

thanks - I will look closely at that today - here is an example of the sort of thing I would like to use Architect for ..."A piece using surrogate statistical techniques to generate new works from old. I used a recording of the loudest drops of rain falling into a swimming pool as the timing sequence and mapped the pitch sequence of gymnopedie#1 onto that. "
https://soundcloud.com/greghooper/unselected

and another using the pitch permutation technique https://soundcloud.com/greghooper/varia ... mnopedie-2

Hi woggle, very cool! I'm going to try to do something along those lines and report back.

[woggle]

Hi mannymang - I should say for those pieces I used what I think of as a "selectionist" composition strategy - generate the piece algorithmically then discard notes / reorchestrate etc etc. Different to a set and forget "pure" generative strategy (although I don't add in new notes or pitchess, everything used was there in the originals)

[mannymang]

Hi mannymang - I should say for those pieces I used what I think of as a "selectionist" composition strategy - generate the piece algorithmically then discard notes / reorchestrate etc etc. Different to a set and forget "pure" generative strategy (although I don't add in new notes or pitchess, everything used was there in the originals)

I see, I'll investigate, although I'd like to see the pros chime in on this. Great idea BTW! Maybe thinning out midi notes from the original midi file per track?

[woggle]

Hi mannymang - I should say for those pieces I used what I think of as a "selectionist" composition strategy - generate the piece algorithmically then discard notes / reorchestrate etc etc. Different to a set and forget "pure" generative strategy (although I don't add in new notes or pitchess, everything used was there in the originals)

I see, I'll investigate, although I'd like to see the pros chime in on this. Great idea BTW! Maybe thinning out midi notes from the original midi file per track?

anything is worth a go - I also do things like take a recording of a piece by someone, reverse it, put distortion/reverb to smear out the pitch information, then extract pitch using Melodyne pitch to midi and orchestrate that result - using the errors to generate novelty
eg https://soundcloud.com/greghooper/varia ... paisajes-2

[mannymang]

Hi mannymang - I should say for those pieces I used what I think of as a "selectionist" composition strategy - generate the piece algorithmically then discard notes / reorchestrate etc etc. Different to a set and forget "pure" generative strategy (although I don't add in new notes or pitchess, everything used was there in the originals)

I see, I'll investigate, although I'd like to see the pros chime in on this. Great idea BTW! Maybe thinning out midi notes from the original midi file per track?

anything is worth a go - I also do things like take a recording of a piece by someone, reverse it, put distortion/reverb to smear out the pitch information, then extract pitch using Melodyne pitch to midi and orchestrate that result - using the errors to generate novelty
eg https://soundcloud.com/greghooper/varia ... paisajes-2

Nice work! Seems you could really generate a vast library with that technique, then mangle the midi even more.