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

[gentleclockdivider]

Woow , that last piece is nothing short of being brilliant !

[gentleclockdivider]

Is there a way to make notes just a tiny bit longer than 1 step , for glissando effects , so that the end of the note overlaps the (beginning) of the successive note
The multiply parameter affects the whole step and not just the note data

[mannymang]

seems like Architect is exactly what I'd hoped it'd be for all these years...

Yeah, it's exactly what I hoped it to be and a lot more. I've been waiting for a tool like this for many years.

Nice Delta Sign! I love generative stuff. I haven't made a tune in a regular sequencer in many years.

Generative stuff is fun! It seems like Architect might become the ultimate generative tool box, at least when it comes to sequencing.

Great stuff!

I'm just experimenting with actually modulating plugin parameters from Architect for the first time, and it seems to work really well.

Here is another thing that has been sequenced completely in Architect. This time it's also modulating a bunch of synth and effect parameters directly. It's a little bit on the crazy side and it's hard to tell what's actually going on, but I thought I should post it nonetheless

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

Very cool Delta Sign. Any chance to share your presets or fragments for us programmatically challenged? Attached is the fragment I tweaked from your first post.

Thanks!

[Hanz Meyzer]

It's lacking of a tracker view

[Delta Sign]

Very cool Delta Sign. Any chance to share your presets or fragments for us programmatically challenged?
Thanks!

I can't save presets in the demo, but if I ever come up with interesting and reusable fragments, I'll share them, sure.

It's lacking of a tracker view

Colin actually mentioned some sort of tracker module some time ago, if I remember correctly.

[Hez]

Is there a way to make notes just a tiny bit longer than 1 step , for glissando effects , so that the end of the note overlaps the (beginning) of the successive note
The multiply parameter affects the whole step and not just the note data

I'm having a think about this now, so far my first idea is:

1. Unpack each MIDI message to a tuple, whilst in parallel sending the MIDI message itself to a MIDI branch switch
2. Get the first element of the tuple (message type)
3. Use scalar == to check if the message type = 'noteoff'
4. If it does = 'noteoff', set the MIDI branch to false, if not, send it to true (splitting the noteoff messages from the rest of the messages)
5. Send the messages routed through the false branch to a MIDI delay and set your delay as required
6. Recombine the false branch delayed and true branch non-delayed messages at a thru MIDI to get everything back together, with slightly delayed note offs

A quick test and this appears to work OK, not sure what unit the MIDI delay time input is in (milliseconds? ticks?) but yeah. You need to disable "Match Notes" on the branch and MIDI delay objects or else it'll try to regenerate sync'd note offs for you. I can upload a .frag if required.

EDIT: Ok so works fine in some situations but doesn't react well to lots of the same note being sequenced in a row. Depending on the delay time, note offs will start getting delayed until the 2nd or 3rd duplicate of a given note which starts to sound weird and choppy. It works well for specifically legato sequences though, or sequences where you intentionally avoid playing the same note several times in a row.

I'll see if I can crack that tomorrow - essentially we want to take the first note on and last note off from any group of repeated notes. It's easy to take the first note on and ignore the others (using MIDI Thinner), but taking the last note off doesn't appear to be quite as trivial. I think the answer may lie in using the Give Note Id object to get unique IDs for each identical note playing at any given time and ignoring note offs corresponding to any ID below the currently stored max ID, but I should probably sleep on it as I feel like I've overcomplicated this far too much already

[HunterKiller]

Here is another thing that has been sequenced completely in Architect. This time it's also modulating a bunch of synth and effect parameters directly. It's a little bit on the crazy side and it's hard to tell what's actually going on, but I thought I should post it nonetheless

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

Actually this example is precisely what shows off Architect perfectly, this is what people need to hear.

Don't be afraid to go a whole lot more crazy, but not inhuman-crazy, that gives a robotic vibe that says there is no human behind the maddness. Lol!

[lnikj]

Here is another thing that has been sequenced completely in Architect. This time it's also modulating a bunch of synth and effect parameters directly. It's a little bit on the crazy side and it's hard to tell what's actually going on, but I thought I should post it nonetheless

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

Actually this example is precisely what shows off Architect perfectly, this is what people need to hear.

Agreed. This is a fantastic piece Delta Sign

[lnikj]

Thanks for adding the checkbox persistence but scanning issues persist.

With the latest beta I managed to get the 2011 MBP scanned in just over an hour. I reckon there were 30+ crashes but only 13 plugins were blacklisted as opposed to 17 by 2/3 of the way through last time.

I'm curious about the sorting - is this based on something the VST reports back? I have such things as Late Replies, Kaleidoscope, Sandman & Sandman Pro, SpecOPS & Instant Delay classed as Reverbs, but 90% of my actual reverbs are not so classified.

[bronswerk]

Brilliant work Colin! For stepsequencing alone this could be very well the new standard.

(The only frustrating part is the waiting time for the registration/license mail to receive when you bought the program using bank wiring. When 2 banks are involved and each has their own processing time this could easily add up to maybe 5 working days? Aaarrrggh...)

[colin@loomer]

Is there a way to make notes just a tiny bit longer than 1 step , for glissando effects , so that the end of the note overlaps the (beginning) of the successive note

I (think) that in the mono seq, if you set a note's gate to maximum (tie) you will get this affect.

EDIT: Yes, it does.

[colin@loomer]

I'm curious about the sorting - is this based on something the VST reports back? I have such things as Late Replies, Kaleidoscope, Sandman & Sandman Pro, SpecOPS & Instant Delay classed as Reverbs, but 90% of my actual reverbs are not so classified.

Yes, it's based on what categories the plug-ins report and then how the JUCE lib categorises them. I'm just going to write my own, I think, because this code seems far too brittle.

[colin@loomer]

Is there a way to make notes just a tiny bit longer than 1 step , for glissando effects , so that the end of the note overlaps the (beginning) of the successive note

I (think) that in the mono seq, if you set a note's gate to maximum (tie) you will get this effect.

EDIT: Yes, it does.

[lnikj]

I'm curious about the sorting - is this based on something the VST reports back? I have such things as Late Replies, Kaleidoscope, Sandman & Sandman Pro, SpecOPS & Instant Delay classed as Reverbs, but 90% of my actual reverbs are not so classified.

Yes, it's based on what categories the plug-ins report and then how the JUCE lib categorises them. I'm just going to write my own, I think, because this code seems far too brittle.

I guess this is too reliant on what the plugin dev adds as metadata then. My 2C-Audio, Blue Cat, Unfiltered Audio and PSP plugins are put into (often the wrong !) folders and nothing else is - I assume because the rest do not have the metadata at all?

Unless you are planning to maintain your own database of plugin metadata (I hope not!) I would be perfectly happy with long lists (as I posted before) and the search facility you are planning to add. I would prefer them to be separated into AU/VST etc because at the moment I have double (and would have triple if I ever installed VST3s) entries for things and cannot see at a glance which version of the plugin I am about to choose.

[An alternative to a database would be to allow user tagging or to respect a user defined folder hierarchy.]

Anyway, not remotely urgent (for me) - please devote your efforts elsewhere.

[colin@loomer]

Thank you. I'm listening to what people are asking for, and it definitely seems plug-in searching and scanning is the current weakest link. But yes, searching and format (VST, AU) identifiers both seem like good way of taming the beast a little.