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

[urlwolf]

Would you recommend writing an entire piece in architect?
Is there any way to do 'non-generative' midi as well (ie a piano roll that humans edit with a mouse). If so, I've missed it. It may be against the philosophy.

Saving fxp and fxb with a shortcut would be good. As would be some simple way to manage vst presets.

[colin@loomer]

It has built-in step sequencers that you can use for more conventional compositional techniques. Somewhen after version 1.0 I'll be finishing the standard piano roll modules and vertical tracker sequencer modules, which again will enable a more traditional composition technique.

And noted about the vst presets. I'm reworking a lot of plug-in hosting code, and will aim to get these suggestions in.

[gentleclockdivider]

I managed to narrow down the problem , it seems to be related to the data switch having problems with the modulo output when it's set to 1000
When the switch is disconnected , it won't crash .

[colin@loomer]

Great, thanks for the additional info.

[gentleclockdivider]

Would you recommend writing an entire piece in architect?
Is there any way to do 'non-generative' midi as well (ie a piano roll that humans edit with a mouse). If so, I've missed it. It may be against the philosophy.

Saving fxp and fxb with a shortcut would be good. As would be some simple way to manage vst presets.

Of course there is .
But there a few things to keep in mind .
In the polysequencer you can't (yet) set individual parameters for an individual step belonging to the same row .
And the nice thing about architect is that you can actually make your own environment depending on your needs and the direction you want to head to .
ANd it's just fantastic for live use , assigning arrays to pc keys , you can switch/re-route midi channels on the fly , muting the output of sequencers ( while still playing ) etc..

[gentleclockdivider]

Nevermind , solved

[gentleclockdivider]

Follow these steps exactly to reproduce crash
-DO not run/play architect
-create data soursce value 1
-create math '+' object
-route data into both inputs and send it
-create metronome ( set to 1/16 to speed up things ) and route it to call input of math object
-create feedback loop (output math module back into first input ) , so we have a counter

-create modulo , route output of counter into the 'A' input and call input
-Copy/paste the first value and set it to 1000
-route it into the 'B' input of modulo and send it
-let's create a print module and tap off modulo
-now RUN architect
-create data switch 1-n

-route output of modulo into both inputs of the data switch
Crash should now occur

If not , change value of modulo to 1 and back to thousand while clicking on the screen to confirm , do this a couple of times
Crash will occur eventually , move print module abit around the screen

[abstractcats]

Welcome to Architect, and thank you for being part of the Architect beta test. A beta software
product is not quite a finished software product, and as such does not necessarily represent
the quality of the final release: features may be missing, and bugs may be present.

Architect is a modular MIDI toolkit and music production environment for macOS, Windows,
and Linux. Similar to the classic modular synths, you build patches from small modules that
work together to generate pieces impossible to conceive of using conventional compositional
techniques.



The most recent beta uploads will always be found here. As new beta builds become available, I will archive the older builds here so as anyone can downgrade if newer builds introduce show-stopping bugs.

The most recent copy of the quick-start guide (PDF) can be found here.

During the beta phase, Architect will be available at a discounted "early-bird" price, 25% off the standard price of £140 + VAT. You can purchase Architect directly from us here.

Happy Architecting (and Happy new year too.)

---

0.9.5 beta is available here

- (fix) Fix crash that could occur after deleting modules.
- (fix) Fix crash that could occur when starting Architect with certain audio drivers.
- (fix) Fix UI freeze on Windows that could occur when the mouse hovers over an automation curve node and shows a tooltip.
- (improvement) Module error symbols are now automatically removed when a meaningful change occurs to the graph.
- (improvement) MIDI events will still continue to propagate even after an upstream error.
- (improvement: plug-in) UI state is now persisted and restored when the UI is reopened.
- (fix) Aux step sequencer parameters can now be mapped to controllers.
- (fix) Grid step sequencer velocity and gate rows can now be mapped to controllers.
- (fix) Removed memory leak that can occur after streaming audio to the audio pool.

---

0.9.3 beta is available here
- (fix) Mappings made to a divide parameter were affecting multiply parameters.
- (fix) Sequencers set to "Stationary" were running in "Brownian" mode.
- (add) Added logging and callstack tracing
- (improvement) Sequencers now restart when the host transport jumps to the origin.
- (improvement) Plug-ins saved in mixer tracks now store more identifying information to better match against the same plug-in when the project is loaded on different machines or operating systems.

---

0.9.2 beta is up here.

- (fix) Hosted plug-ins with no inputs and multiple outputs couldn't have their outputs routed to other tracks.
- (improvement) Plug-ins are no longer removed if their corresponding "find" option is left unchecked.
- (improvement) Plug-ins can now be sorted in the Mixer plug-in palette.
- (improvement) Plug-in preferences are now saved before a scan so settings are retained if a third-party plug-in causes a crash.
- (add) The default paths for each plug-in format can be optionally disabled when scanning for new plug-ins.
- (improvement) Reduced the height of the reference panel module properties.
- (improvement) Plug-in scanning can be cancelled during a scan.

---

0.9.1 is now available here: https://drive.google.com/drive/folders/ ... sp=sharing

- (fix) Fix a crash that could occur at some time after deleting a sequencer module.
- (improvement) macOS application is now a 32-bit and 64-bit universal binary. The previous release was 32-bit only.
- (fix) Fix a minor typo in the metronome properties.

Just realized how out of the KVR loop I've been! That look really nice, Colin! I'll give it a spin this week! Love the name, and the price looks right on target. Cheers!

[colin@loomer]

Follow these steps exactly to reproduce crash

Thanks for the explicit steps. I've reproduced this crash, and am in the process of fixing it (EDIT: Fixed). It'll be gone (and other instances of basically the same bug) in the next 0.9 beta.

[colin@loomer]

Think I found another bug .
The range between 0,75% and 100% gives us 3 , which should trigger the last array

I've checked this, and it is working as expected.

To where a data-switch with 4 outputs sends is governed by the value of control inlet, as follows:
0: first outlet
1: second outlet
2: third outlet
3: fourth outlet
anything else: don't send

So by giving it a control index of 4, you're stopping the branch from sending at all.

Change that constant 4 for a 3, and you'll be good.

[colin@loomer]

@gentleclockdivider You mentioned an issue about the timeline feeling sluggish in the newer betas. Could you perhaps give me a bit more information? I'm having trouble reproducing this, (but bearing in mind I was recently performing surgery on code related to this, I'm well aware that there is a very good chance that I may have broken something.) Cheers!

[gentleclockdivider]

@gentleclockdivider You mentioned an issue about the timeline feeling sluggish in the newer betas. Could you perhaps give me a bit more information? I'm having trouble reproducing this, (but bearing in mind I was recently performing surgery on code related to this, I'm well aware that there is a very good chance that I may have broken something.) Cheers!

The timeline doesn't feel sluggish at all
I Mean in the play mode , expanding (widening )sequencer tracks feels sluggish, and only in play mode


Also colin , have you looked into the other issue >
When assigning a gui widget (which controls midi cc 74) to an automation lane , it creates a hell of a lot of data , up to the point that my hardware can't cope with it .
When assigning a performance parameter to an automation , the data is less dense and acceptable

[colin@loomer]

I Mean in the play mode , expanding (widening )sequencer tracks feels sluggish, and only in play mode

Great, I'll look into that this afternoon.

Also colin , have you looked into the other issue >
When assigning a gui widget (which controls midi cc 74) to an automation lane , it creates a hell of a lot of data , up to the point that my hardware can't cope with it .
When assigning a performance parameter to an automation , the data is less dense and acceptable

Not yet, but I will today if the other issues I'm looking into are resolved in time.

[gentleclockdivider]

The data module doesn't care if a text is written between "these" or 'these' kind of brackets .
Also , could you provide any info which kind of types/arguments/texts, the sequencer inputs accepts ( mod rows )
Maybe a list of commands etc

[colin@loomer]

The data module doesn't care if a text is written between "these" or 'these' kind of brackets .

By design. It's (sometimes) a standard in modern languages as it means you can create strings with one type of quote in by surrounding them with the other.

Also , could you provide any info which kind of types/arguments/texts, the sequencer inputs accepts ( mod rows )
Maybe a list of commands etc

(Copied from a few pages back.) Writing to a row can be done in any of the following formats:

* A single value, which will be written to the first step
* An array of values, which will be written to consecutive steps
* A tuple of (step, value)
* An array of such tuples, eg, [(1, 64), (2, 32)]
* A tuple of start position and array, eg (7, [32, 33, 36, 78]), which will write the array values starting at step 7

The values themselves are numeric in the majority of cases, but can also be boolean for trigger-type rows, and strings for arpeggiator source note rows