Loomer

Tappistry · Post by **Tappistry** » Tue Jan 08, 2019 3:57 am

mgw38 wrote: Wed Jan 02, 2019 9:07 am This has very high potential. In terms of its core functionality, I am seriously impressed.

However, the plugin scanner is currently spectacularly broken. It took me about one hour and 10 crashes to get less than 5% of my plugins scanned. Eventually, the scanner got stuck in a crash-rescan loop and could no longer get beyond a certain point in the scanning process. I eventually had to give up and uninstalled the beta. Will try again once this works.

Most systems out there now do a decent job scanning plugins. There is no reason why Architect should not be able to do that as well.

Fyi, I am running on MacOS Mojave, maxed out late 2016 13 inch MacBook Pro (first one with Touch Bar).

I'm also having this problem on Win 10 (x64).

colin@loomer · Post by **colin@loomer** » Tue Jan 08, 2019 9:01 am

mannymang wrote: Tue Jan 08, 2019 2:19 am Is there a way to turn on and off the "distinguish notes" module during play?

You can use a branch to either route notes to or away from such a module.

colin@loomer · Post by **colin@loomer** » Tue Jan 08, 2019 9:02 am

Tappistry wrote: Tue Jan 08, 2019 3:57 am I'm also having this problem on Win 10 (x64).

New plug-in scanner, basically re-written from scratch, will be in the 0.10 beta.

cturner · Post by **cturner** » Tue Jan 08, 2019 12:49 pm

How are the "default" values supposed to work in the panel UI components? I presume that if a default is set, when the preset is called up, the UI component (text input, dial, etc.) will have that value on setup?

colin@loomer · Post by **colin@loomer** » Tue Jan 08, 2019 1:01 pm

If you ctrl/cmd and left-click, the component will reset to the specified default version. It also affects a few rendering things, such as with a rotary the fill will start from the default value. It doesn't reset to these values on opening the presets or anything like that.

gentleclockdivider · Post by **gentleclockdivider** » Tue Jan 08, 2019 2:15 pm

Bumping again concerning aux seq. being unmappable ( all parameters ) and grid sequencer ( some gui step parameters )

colin@loomer · Post by **colin@loomer** » Tue Jan 08, 2019 2:30 pm

Noted, thanks. If time allows, I'll get this fixed for tomorrow's beta.

Tappistry · Post by **Tappistry** » Tue Jan 08, 2019 2:55 pm

colin@loomer wrote: Tue Jan 08, 2019 9:02 am
Tappistry wrote: Tue Jan 08, 2019 3:57 am I'm also having this problem on Win 10 (x64).
New plug-in scanner, basically re-written from scratch, will be in the 0.10 beta.

Glad to hear!

gentleclockdivider · Post by **gentleclockdivider** » Tue Jan 08, 2019 3:16 pm

edit : Solved

gentleclockdivider · Post by **gentleclockdivider** » Tue Jan 08, 2019 3:44 pm

Can we have the option ( if not already possible ) to set the start point of a pattern
In the pattern properties this also affects loop .
The transport modulation begin /end is not what I am looking for

Just simple , loop set from 0 to 9 ...start pattern at step 2

colin@loomer · Post by **colin@loomer** » Tue Jan 08, 2019 3:52 pm

OK, good suggestion, noted. (And you can currently do it by setting the loop from 2 to 1. If the end loop point is before the begin point, it will wrap around the end of the sequence.)

cturner · Post by **cturner** » Tue Jan 08, 2019 7:45 pm

colin@loomer wrote: Tue Jan 08, 2019 1:01 pm If you ctrl/cmd and left-click, the component will reset to the specified default version. It also affects a few rendering things, such as with a rotary the fill will start from the default value. It doesn't reset to these values on opening the presets or anything like that.

Thanks for this. How do you get "default" for a "numeric value" UI component? Couldn't seem to make Ctrl-click work with them.

colin@loomer · Post by **colin@loomer** » Tue Jan 08, 2019 7:50 pm

Sounds like an omission on my behalf: I'll get that put in. Thanks. (And good job on the Turing source: very impressive.)

cturner · Post by **cturner** » Tue Jan 08, 2019 8:01 pm

Hi Colin- I've figured out the issue I'm having with Architect presets and Reaper, and have a step-by-step that hopefully will enable you to duplicate the same. Latest Reaper 64bit, Win10 Pro 64bit, latest Architect beta VST2.

1. Reaper follows your activities, and if there's been any change in the document, will ask if you want to save when you select Quit from the main menu. So "quit" then choosing "save" from the ensuing dialog is the most common way I leave Reaper.

2. Set up Architect on a Reaper track, load a preset, save and quit Reaper.

3. Re-launch Reaper. Architect and the previous preset should be there just as you left it.

4. Select another preset using Architect's preset facilities. Quit Reaper. Notice that you are not asked whether you want to save, lose your change, or cancel.

5. Re-launch Reaper. Notice that the preset from step 2 above is presented, not the most recently selected.

Obviously there are some work arounds for this, like saving before quitting. What I'm still unclear about is whether this will manifest itself within an edit session: whether Architect, upon losing and then regaining focus displays an older version of the preset.

grimleyj · Post by **grimleyj** » Tue Jan 08, 2019 8:03 pm

gentleclockdivider wrote: Mon Jan 07, 2019 9:37 pm Think I found a new bug
Trying to map a step value of an aux step sequencer to a performance parameter ( by right clicking ) , when clicking OK the dialogue does not dissappear , the mapping is not made.
It seems that none of the aux sequencer parameters can be mapped , not even the ones in the properties window.

Edit :the grid sequencer's velocities are also un-mapable .
Also some of the parameters in the properties window

This was the very first thing I tried to do with the beta and after an hour of fiddling around gave up.

Loomer

KVR Audio

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