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

[cturner]

Well, you've got a long way to go to beat TextMate!

[cturner]

Hi Colin- I believe you can crash Reaper by saying something like [0]->[is nth tick]. I assume it's divide by zero, but shouldn't this be caught by the object?

[cturner]

And another question please, Colin: does the Architect plugin respond to MIDI Program Change messages, or is there another mechanism to change preset via automation or some such? Thanks and good weekend!

[colin@loomer]

Hi Colin- I believe you can crash Reaper by saying something like [0]->[is nth tick]. I assume it's divide by zero, but shouldn't this be caught by the object?

Yes, you're right. I'll fix that! Thanks for reporting.

[colin@loomer]

And another question please, Colin: does the Architect plugin respond to MIDI Program Change messages, or is there another mechanism to change preset via automation or some such? Thanks and good weekend!

I have the code to change presets with MIDI program changes, as my other plug-ins do just that - I simply disabled the functionality in Architect as I wasn't sure how to differentiate between:
(a) wanting to change preset and
(b) wanted to use an Architect patch to process MIDI program change messages.

I guess I could just add an option to switch between these two modes. I'll add it to my list.

Have a good weekend, yourself.

[cturner]

Thanks. I'm trying to figure out how I can easily maintain preset changes in Bitwig that correspond to changes in the playing clip. I'm kind of amazed that one device preset is assumed for an entire track, or that automation is a sufficient substitute, but maybe I don't know enough about Bitwig as yet. As far as Program Change is concerned, I think I could implement what I need locally, but Program Change may not be the best solution.

[ThomasHelzle]

You could have a look at the switcher devices in Bitwig - may be easier to maintain depending on what you want to do. Together with modulation or automation etc. this would be my personal choice over PC type switching each plugin, especially since the switchers let sound out playing notes...

[cturner]

Hi Thomas! Thanks so much for kindly sharing your knowledge of Bitwig. I tested using Architect parameters and Bitwig automation, and found I was quite clumsy in drawing a straight line in the detail panel. I’m sure that’s just unfamiliarity. The bigger issue is inside a preset, where ideally, I should be able to construct and destroy pieces of the patch. Patcher scripting in Max comes to mind, although I never liked it.

I’ll look at the switcher objects. I wonder also if you knew whether one could write a Bitwig controller in Java or JS that would observe clip changes, and then use the clip name as the name of the preset to change in a VST device? I thought of lashing Moss’s OSC controller to Max to attempt a test of it’s feasibility.

Bon ouikend!

[cturner]

I spent a bit of time with this question yesterday and I think using MOSS’s OSC controller from Bitwig, and Max/MSP hosting (hilariously) another instance of Architect, I’ll be able to sequence my tunes at the bar-level as desired. It may be that using SYSEX to send Architect arrays into Bitwig is a better solution than Bitwig device preset switching, but we’ll see.

[David]

Pre-sale inquiry:
I've been really impressed with the Piano Roll block in ToyBox's recent Synth Pack, in which you can modulate the playhead position across the MIDI-note grid, as in the ref video. Is that something that Architect would be able to do also? While also modulating the note values themselves? Thanks!

Ref:
https://www.youtube.com/watch?v=Zkjm79dzd20

[colin@loomer]

... can modulate the playhead position across the MIDI-note grid, as in ... While also modulating the note values themselves?

Yes, I can't see why not. The built-in sequencers can operate in a mode where the playhead is controlled by an external source, and modulating notes themselves is easily done in a variety of ways.

(Seeing as you're using the eval, you can't open third-party patches, but can open third-party macros. Would you like me to have a go at putting together a simple macro similar to what you've demonstrated in the video for you to play about with?)

[David]

... can modulate the playhead position across the MIDI-note grid, as in ... While also modulating the note values themselves?

Yes, I can't see why not. The built-in sequencers can operate in a mode where the playhead is controlled by an external source, and modulating notes themselves is easily done in a variety of ways.

(Seeing as you're using the eval, you can't open third-party patches, but can open third-party macros. Would you like me to have a go at putting together a simple macro similar to what you've demonstrated in the video for you to play about with?)

Jeez, yes, I'd LOVE to see that—Thanks!:)

[colin@loomer]

Jeez, yes, I'd LOVE to see that—Thanks!:)

Sorry for the delay, I got snowed under with a few other pressing issues. But here is a quick attempt at something similar:



It uses a poly step sequencer as the raw note source. Every 1/8th note, the top metronome randomly sets the playhead position of this 8-step sequence. Then, each note goes through the tranposer, with the tranposition range being dictated by the TRANSPOSE slider.

Finally, a second metronome, this time synced to every 2 bars, randomly changes the force scale to make some bars in C-Major, and others in C-Minor.

You'll need to place the macro in your External macros folder. The easiest way to access this is to right-click on External node in the Graph library tree. Unzip the frag file into the Fragments folder. Refresh the tree, and it'll appear in your library.

The only thing you'll need to do to use it is set the destination for the MIDI output module. If you're running Architect in another host, you can use "Host" to output MIDI that the host can then route to other plug-ins. Or you can add a track under Mixer and route it to an internally hosted plug-in.

This was a literal 2-minute attempt at what you posted, so I'm sure I've missed some bits; and if that's the case, don't hesitate to let me know and I can spruce it up a little. I've left it playing in the background whilst typing this reply, routed into a nice Rhodes sample lib, and it's rather pleasant!

[ThomasHelzle]

Hi Thomas! Thanks so much for kindly sharing your knowledge of Bitwig. I tested using Architect parameters and Bitwig automation, and found I was quite clumsy in drawing a straight line in the detail panel. I’m sure that’s just unfamiliarity. The bigger issue is inside a preset, where ideally, I should be able to construct and destroy pieces of the patch. Patcher scripting in Max comes to mind, although I never liked it.

I’ll look at the switcher objects. I wonder also if you knew whether one could write a Bitwig controller in Java or JS that would observe clip changes, and then use the clip name as the name of the preset to change in a VST device? I thought of lashing Moss’s OSC controller to Max to attempt a test of it’s feasibility.

Bon ouikend!

If you need exact values, click on the automation points and enter the value in the inspector maybe?
If you click with CTRL on a line, you can move it around as a whole, ALT allows you to bend it, not sure what your trouble is though.

The switcher devices allow you to stack as many instances of plugins as you want and switch between them without hard cuts, instances sound out even if switched off. Together with modulators that may work for what you do, although I don't have a clear picture of what you want to achieve.

And yes, the API can be used (Java or JS or compatible languages) for stuff outside of controllers.
You can have observers for all kinds of events and the clip name should be trivial to grab, but sending that to the VST device may be tricky - no idea how to do that.
I personally would probably rather come up with a different logic that is less complex, but again, I don't know exactly what you try to do so can't help much there.

Cheers,

Tom

[David]

Jeez, yes, I'd LOVE to see that—Thanks!:)

Sorry for the delay, I got snowed under with a few other pressing issues. But here is a quick attempt at something similar:

…
This was a literal 2-minute attempt at what you posted, so I'm sure I've missed some bits; and if that's the case, don't hesitate to let me know and I can spruce it up a little. I've left it playing in the background whilst typing this reply, routed into a nice Rhodes sample lib, and it's rather pleasant!

Thanks so much Colin! Now all I have to do is download the current beta, and re-read all the help files you provide:) I'll admit I basically glazed over with all those first time around, way back when, as it all seemed way over my "gimme some presets!" head. But now I'm definitely motivated to grit teeth and dig in. Thanks for that, too—I hope:)