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

[cturner]

EDIT: Also seems like there's a space required after the comma separating the key/value pairs in a map?

I don't believe that's the case, but if you've found an example where you need a space, could you send it to me and I'll see if I can work out where the lexer is going wrong. Thanks

EDIT2: Is there a discrepancy between what the manual and application say is a map definition? Must the "value" be either a scalar or an array, not tuple?

No, the value can be anything, as far as I recall. I think the map key can be anything but another map or array (although I think I could probably relax this limitation, if requested.)

I'm having a bit of a time trying to understand how to define keys that are vectors.

Ah, so that is the request! I'll see if there is any technical reason why array map keys were forbidden, and if not, I'll allow them.

Back to this finally; thanks for your responses. I was crashing around yesterday, and in the future I promise to observe a "cooling off" period before I go posting things for you to answer.

1st point: Can't reproduce the lexer issue today, and it was pretty obvious yesterday. I should've been able to make it happen again from the snippets left in my text editor. I'm declaring the issue non-existent.

2nd point: My confusion was with [build map], the function of which I misunderstood.



Today with a clearer head, I presume that the statement outlined in blue is functionally the same as the one outlined in yellow? So I was trying to feed [build map] with a (correct) definition of a map, and of course [build map] wanted to build a map from scalars and vectors.

3rd point: I haven't tried to build a map with an array as key, but one embarrassing confusion I had yesterday involved not remembering keys must be unique, correct? Writing a new element to the map with the same key value will write over the previous value, yes?

Thanks again, Charles

[colin@loomer]

Today with a clearer head, I presume that the statement outlined in blue is functionally the same as the one outlined in yellow? So I was trying to feed [build map] with a (correct) definition of a map, and of course [build map] wanted to build a map from scalars and vectors.

Yes, that's right. [build map] builds the structure piecemeal from (key, value) tuples.

keys must be unique correct? Writing a new element to the map with the same key value will write over the previous value, yes?

Again, absolutely right.

[colin@loomer]

0.9.9 beta is now out, with a few more bug fixes. Download it here for macOS, Windows, and Linux.

- (fix) Fix crash that could occur when certain hosted plug-in windows were still open when Architect is closed.
- (fix) Cables can now be deleted even when they have been set to transparent.
- (fix) [is nth tick] module now works correctly for divisions that don't fit exactly in a bar.
- (add) Confirmation and the opportunity to save is given when closing the standalone application if the current preset has unsaved changes.
- (add) Confirmation and the opportunity to save is given when requesting a new preset if the current preset has unsaved changes.
- (add) Shortcut key (ctrl+N or cmd+N) to create a new preset.
- (change) Cases of priority labels in [note priority] module are now in headline case, to match other module properties.
- (change) Setting module attributes using strings is now done case-insensitively when the property is a fixed enumeration (i.e., not for setting files from the MIDI Pool on a [MIDI player] module, or for specifying custom scale names.)
- (add) [numeric table] and [boolean table] have a wrapping setting that allows reads beyond the table indices to be folded back to the correct range using various schemes.
- (change) [numeric table], [boolean table], and [grid] no longer have "setup event" set to true as default. Setup events for these modules can still be turned on from the properties.

[ThomasHelzle]

[cturner]

Ah, my first crash! Latest Win10Pro 64bit, latest Reaper 64bit, latest Architect VST2, 96khz/2048 session:



In this configuration, I get an error at setup concerning an argument missing from the comparison. Switching the handedness of the two terms fixes that. But executing the comparison takes down Reaper. I'm ultimately not sure what the truth value of a vector comparison involving an empty array, but it's probably not crash.

HTH, Charles

[colin@loomer]

Thanks. Reproduced it here, should be a simple fix, so I'll get this done for the next beta.

[cturner]

Ace, Colin!

[mannymang]

Having trouble with Architect hanging starting up a preset with VST's. CPU at 25%+. Have to stop/start Architect. Preset loads with heavy CPU the second try, then CPU goes down to normal after VST's load.
Win 7

[colin@loomer]

Any chance you could narrow it down to certain VSTs?

Thinking about it, that 25% CPU sounds suspicious because it makes it sound like 1 out of 4 cores has locked up. Maybe send me the preset and I may be able to work out what's going on, even without necessarily having said VSTs myself.

[mannymang]

In this preset it's Kontakt 5, Absynth 5 (always a problem), Massive, and Jamstix 4. I'll try to narrow it down asap. But if I were the gambling type, I'd say Absynth 5 since I've only introduced it in my testing in the last day or 2

[AZZIN]

Hi Colin, after ~1 month I think I barely scratched 10-15% of Architect functionality, but there is something that I still don't understand architecture-wise ; the memory modules. In order to store a number (variable or whatever) we need at least three blocks (see attachment).
The same chain could be done ideally with just one block of type "memory" (red) whose left inlet would be "store", the right inlet would be "read" and the outlet is the value banged only by "read". What am I missing?
I say this because the interface is easily cluttered in case there are several varables to store.
What do you think?
Alberto

[colin@loomer]

You can do as you requested with a [latch] module.

The reason memory modules work like this, is because having static memory removes the need for feedback and sneaky routing when you have multiple modules reading and writing to the same static memory area. If you only need a value to be written in one place and read in one place, you can just use a [latch].

[AZZIN]

Ah, ok, good to know... thanks for the prompt answer!
Alberto

[colin@loomer]

No problem. I'll make this distinction clear in the documentation.

[Winstontaneous]

Hi Colin, does the version number getting cloes 1.0 meant the beta period is over soon?
Hoping to pick up during intro offer depending on finances, thanks.