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

[colin@loomer]

No, the beta period, and pricing is set to continue through February. I promise I won't pull the rug out and suddenly hike the price without decent warning.

[gentleclockdivider]

I don't get those that haven't yet purchased architect .
It's not like it's a crashfest (cough blender 2.8 lol: )

[roelkers]

Hey I've been trying out Architect the past weeks, and I'm amazed by the possibilities and the slick GUI.
So first of all: Great Job!

One thing I've been wondering about when chaining sequencers are the "Row" modulation inlets. When I use one of these only the first step in the sequencer seems to be affected. Is there another parameter that sets which "Column" in the row is affected ?

[colin@loomer]

Hi Roelkers. You can send arrays or tuples with (position, value). There was a few posts a while back that illustrates the accepted formats if you check my history; I'm on the move at the moment, but if you can't find it, I'll post the details later today.

[roelkers]

Okay that explains it. I now managed to get it working. Thank you!

[ThomasHelzle]

Hey Colin,

I just did hit a snag:
I was working on a Lua script, using Architect (latest) in Bitwig Studio 2.4.3 as a plugin on Windows 8.1 x64.
Bitwig is setup in preferences to only show the plugin interfaces of the track currently selected.
While coding, I wanted to look up something in another Lua script I had created.
So I switched to another track where Architect was instantiated with that Lua script.
When I switched back to the instance I was working in, the Lua window was closed and on re-opening, all my code was gone.
I didn't hit "OK" in that window before, just "Compile"...
So now I have to redo everything from scratch.

I find this behaviour unexpected.
Would it be possible to change this, so that switching to another track/closing the GUI does not lose the content of the Lua editor?
In Houdini these kind of windows usually have an "Apply" button (save the script and run it but leave the editor open) and an "Accept" button (save the script and run it, closing the editor window) as well as "Cancel".
I see how "Compile" is useful as well for temporary tests, but it would be really good to have a way to "save" the script without closing the editor.
And maybe keep the temporary Lua content even when the plugin window is closed?
Otherwise this feels a bit shaky.

Thank you!

Tom

[masterhiggins]

No, the beta period, and pricing is set to continue through February. I promise I won't pull the rug out and suddenly hike the price without decent warning.

TLDR. Are you going to have some ready-to-go templates in the last beta so that those with little to no experience in scripting can just open them, make a couple of fast changes, and then use them?

[ThomasHelzle]

A request:
I often save out a single macro or Lua script as a fragment. In that case I usually copy the Reference Info text into the Export->Description field.
Would it be possible/make sense to have the Reference Info as the default in the Description field when exporting single modules?
Would make things easier and is probably often what one would want to have in there anyway?

Thanks and Cheers,

Tom

[gentleclockdivider]

No, the beta period, and pricing is set to continue through February. I promise I won't pull the rug out and suddenly hike the price without decent warning.

TLDR. Are you going to have some ready-to-go templates in the last beta so that those with little to no experience in scripting can just open them, make a couple of fast changes, and then use them?

There is no need too use scripting in order to use architect , plenty of modules ( 300+) to keep you going

[colin@loomer]

While coding, I wanted to look up something in another Lua script I had created.
So I switched to another track where Architect was instantiated with that Lua script.
When I switched back to the instance I was working in, the Lua window was closed and on re-opening, all my code was gone.

Yes, I'll get that fixed.

[colin@loomer]

Would it be possible/make sense to have the Reference Info as the default in the Description field when exporting single modules?
Would make things easier and is probably often what one would want to have in there anyway?

I agree, to the extent that that is what I (mistakenly) thought it did already!

[colin@loomer]

TLDR. Are you going to have some ready-to-go templates in the last beta so that those with little to no experience in scripting can just open them, make a couple of fast changes, and then use them?

Yes, the aim is to have a library of big building blocks and scripts.

[ThomasHelzle]

Thanks Collin!

[cturner]

Hi Colin- I take it that currently there's isn't support support for what I'd call "sparse arrays": arrays that might have a range of indices between 23 and 78 for example, and also with possible gaps in that range? ( I realize I could define an array with 100 elements, but I'd like to avoid that if possible.)

It also seems as though maps don't sort their keys? (Or that there's no way to sort a map ATM?) So if I have map {"38":9988, "42":6665} and insert "39":5432, I'll get {"38":9988, "42":6665, "39":5432} and not {"38":9988, "39":5432, "42":6665}?

Any suggestions on creating and maintaining an indexed data type where there are "holes" in the sequence and the first element isn't necessarily at index [0]?

EDIT: Although I'd love to hear your comments on the above, I forged ahead with a map using [is member] [get element]. After a bit of crashing around, things are working fine.

Thanks!

[colin@loomer]

You are correct in that maps aren't sorted by keys. There were both technical and conceptual reasons I didn't sort them: because maps support mixed keys, I'm not quite sure what the order would be between a string and a tuple, say.

I am aware of sparse arrays, though, so let me think about it for a bit and see what the best way of supporting these are. My immediate thoughts are, perhaps if I added guaranteed order for map elements when the keys have a natural order - as they do with numeric types - that would allow sparse array types.