Loomer

nordickvr · Post by **nordickvr** » Tue Jun 30, 2020 10:02 pm

colin@loomer wrote: ↑Mon Jun 29, 2020 5:02 pm ...
Plus this does give me a chance to react to what people want more/less of, or for people to suggest gaps in module coverage.
...

This sounds quite promising!
Thank you Colin.

gentleclockdivider · Post by **gentleclockdivider** » Tue Jun 30, 2020 10:37 pm

Great

cturner · Post by **cturner** » Thu Jul 02, 2020 2:09 pm

Hi Colin-

I've moved my presets from a 2560x1440 pixel monitor to a laptop that's 1920x1080. Things are in a pretty big mess in Reaper. I thought that I might be able to find something in the XML that indicates overall window size, but had no luck.

Where are the overall Architect screen dimensions located--or barring that--any thoughts on bulk reduction of window size as presented to Reaper?

EDIT: I see "<VALUE name="AppUiHeight" val="1126"/>" in AppData/Roaming, perhaps others as I poke about.
ALSO: "<VALUE name="UiWidth" val="1443"/> <VALUE name="UiHeight" val="1126"/>"

Thanks!

colin@loomer · Post by **colin@loomer** » Thu Jul 02, 2020 2:24 pm

They are the keys you need to edit. AppUiHeight is for when you're running the app, and UiHeight is for the plugin.

There's also an emergency "reset to a safe UI size" key-press, which is CTRL + SHIFT + R (or CMD + SHIFT + R on macOS), and is there for exactly the situation you've discovered.

cturner · Post by **cturner** » Thu Jul 02, 2020 2:36 pm

Thanks Colin! I’ll try the keypress first.

cturner · Post by **cturner** » Thu Jul 02, 2020 6:27 pm

Hi Colin- The keypress you suggested works when it finally has focus, but it doesn't persist. This after a bunch of different tries at getting Architect to save the settings. "Architect.xml" has not changed its UI size even though the file modification time is newer than on Architect launch. Do I have to do this in the app as opposed to the DLL? "Architect.xml" was copied from another PC (same username), but maybe a permissions issue?

EDIT: I also have six instances of Architect VST loaded in six tracks of Bitwig, with three of the instances bypassed.

colin@loomer · Post by **colin@loomer** » Thu Jul 02, 2020 6:45 pm

It may be a clash between all the open instances. I can't remember off the top of my head if this value is saved when the UI is closed, or when the entire plug-in instance is closed. I have a feeling it should be the latter, and another feeling that it's probably the former.

Either way, I'll take a look at it, see if I can work out how best to deal with this situation.

It sounds like you are editing the correct .xml file, though, if the modification date is being updated.

cturner · Post by **cturner** » Thu Jul 02, 2020 7:03 pm

Looks like my permissions are OK, but I wonder if there are meaningful differences between 0.10.2 and 0.10.3 XML?

arax_1.png

arax_2.png

Although Architect application reset and saved the AppUI, it seems that "Width" (and "Scale") didn't exist in the previous version? Also, in the first DIFF, it seems that Architect app doesn't set "UiHeight" at all, although "UiWidth" is reduced by 10 pixels.

EDIT: Anyway, manually editing the XML did the trick.

;-)

colin@loomer · Post by **colin@loomer** » Thu Jul 02, 2020 7:10 pm

10.3 added AppUi* keys so that it could differentiate between the UI size in the application, and the UI size when running as plug-in. The issue here was that most people run the app full-screen, but then when they then run the plug-in, full screen is too bit as hosts tend to add borders, thicker title bars, or additional controls. UiWidth, et al, is for the the dimensions when running as a plug-in, and AppUiWidth (etc) is for the standalone app version.

cturner · Post by **cturner** » Thu Jul 02, 2020 7:13 pm

As above, a manual edit to the XML cleared things up. Thanks!

Kalamata Kid · Post by **Kalamata Kid** » Sun Jul 05, 2020 12:59 am

Hi Colin,

I see you are making progress.

1. I was wondering if there will be a midi morph module or a way to where two midi files are morphed. Presets can be used to select the various ways it can be done. Would be great to see and edit the results on a piano roll or on the midi list editor.

Or what about a midi morph looper. Oh, the insanity!

2. Hmmm, How about select every third note and move it to after the sixth note then stretch it or edit it in whatever way you please. Or to be able to select notes over a certain velocity or certain length etc. then edit them as desired.

colin@loomer · Post by **colin@loomer** » Sun Jul 05, 2020 8:41 am

Thanks!

1. The generic piano roll module is still on the cards for a 1.something release. Parts of it are existent in the [write to MIDI pool] and [MIDI player] modules. It will be a full fledged, "traditional" piano-roll sequencer (including the logical event view), in opposition to a step-based sequencer.

2. Transforms. Currently, there are a few basic transforms in the step sequencers. Again, post 1.0 they will be improved in several ways. I'm planning to have them: triggerable and configurable in the graph, so they can be synced with the timeline, etc; and customisable, so probably as either lua scripts or as sub-graphs.

Once both of these are in place, what you're requesting'll be a cinch.

cturner · Post by **cturner** » Sun Jul 05, 2020 10:17 am

I don’t think I know what a sub-graph is.

colin@loomer · Post by **colin@loomer** » Sun Jul 05, 2020 10:39 am

cturner wrote: ↑Sun Jul 05, 2020 10:17 am I don’t think I know what a sub-graph is.

That's not a surprise as they don't exist in the 0.10 branches! (Also: terminology liable to change.)

cturner · Post by **cturner** » Sun Jul 05, 2020 11:12 am

A Lua curiosity: https://www.kvraudio.com/forum/viewtop ... 8#p7822258

Loomer

KVR Audio

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