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

[colin@loomer]

Okay, answering one of my own questions partially... Kontakt detected as having 64 outputs, but unlike 2-output synths I cant tap any of them as the input to another Track.

Sounds like a bug, as you should be able to route stereo output pairs to other tracks. Let's have a quick look myself...

[SirkusPi]

Ok, if there’s one thing reading all of the above has shown me, it’s that the current Beta is way above my current level. Which is fine! Not everthing has to be dumbed down for me! (That would be a pretty dull world.) But I’m going to have to hold off until the documentation is in a more developed state and presets / user devices start appearing so I can figure out if I’ll personally get any practical use out of this amazing-looking but complex tool.

[colin@loomer]

Okay, answering one of my own questions partially... Kontakt detected as having 64 outputs, but unlike 2-output synths I cant tap any of them as the input to another Track.

So it appears to be working here (albeit not tested with Kontakt, which I don't have installed). If I add a multi-output plug-in to a track then create a second track, in the second track I can tap the multi-channel output using the Audio Input panel.

[whyterabbyt]

Argh, another one. Having sussed out the the plugin-cache file, I can see what's being blacklisted. But, despite not being blacklisted, and having 'proper' details in the cache file, the Bidule plugins are not showing in the plugin list anywhere.

WRT multiple output plugins, BFD3, which has 32 outs can be 'tapped' in another Mixer track, Reaktor which has 16 outputs also can, but Falcon, with 34 cant,
I realised Reaktor and BFD both have inputs though, so i tried Metaplugin; MetapluginSynth (VSTi version) has 0 inputs and 8 outputs and cant be tapped; Metaplugin (VST effect version) has 10 inputs and 8 outputs and can. Is it possible it only works for synths with inputs?

[whyterabbyt]

Also WRT your reply; I cant tap any more than (the first?) one output for any multi-output plugin, is that correct?

[colin@loomer]

WRT multiple output plugins, BFD3, which has 32 outs can be 'tapped' in another Mixer track, Reaktor which has 16 outputs also can, but Falcon, with 34 cant,
I realised Reaktor and BFD both have inputs though, so i tried Metaplugin; MetapluginSynth (VSTi version) has 0 inputs and 8 outputs and cant be tapped; Metaplugin (VST effect version) has 10 inputs and 8 outputs and can. Is it possible it only works for synths with inputs?

Thanks, that narrows it down. Sounds like somewhere along the line it is confusing inputs and output counts and filtering choices based on the wrong thing. Probably why is worked with me as my test plug-ins all had multiple inputs and outputs.

[colin@loomer]

Yes, that's exactly what was happening. Should be a simple fix, I'll get this rectified in 0.9.2 for tomorrow.

[colin@loomer]

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.

[Delta Sign]

[whyterabbyt]

Cheers. Sorry if Im flooding you with queries, but Ive always been thinking about this in terms of one of two main use cases ; hosting Bidule inside Architect with modular audio routing done internal to Bidule, or Architect hosted inside Bidule. Working out which one would work best is what Im trying to suss;

The questions so far have been focussed on the first option, but if multiple IO routing isnt available that might not be so useful right now, so I have a query which informs the other option: Bidule sees 256 automation parameters exposed by Architect (Param000-Param255); are they driving specific things or (since Bidule can link any arbitray plugins' arbitary parameters together) can I use them 'safely' for controlling other stuff.
And if I can, how do I 'output' them. I can put an Output>Automation module in the graph, but cant work out how to map it to one of those 256 generic parameters, I only seem to be able to control Mixer parameters?

If that's not what's supposed to happen is there any chance of some truly generic automation parameters?

Also.. is there an equivalent Intput>Automation Ive overlooked?

[Delta Sign]

I haven't actually looked into automation yet, but the parameters you are seeing are probably the performance parameters in Architect. Click on the knob looking thingy in very bottom left to see them. You can access them in the graph view with the Input > performance parameter module.

[whyterabbyt]

I haven't actually looked into automation yet, but the parameters you are seeing are probably the performance parameters in Architect. Click on the knob looking thingy in very bottom left to see them. You can access them in the graph view with the Input > performance parameter module.

Aha. Cheers!

[colin@loomer]

Cheers. Sorry if Im flooding you with queries, but Ive always been thinking about this in terms of one of two main use cases ; hosting Bidule inside Architect with modular audio routing done internal to Bidule, or Architect hosted inside Bidule. Working out which one would work best is what Im trying to suss;

Flood away. I want Architect to be used, so knowing situations of genuine users is good info.

if multiple IO routing isnt available

Fixed already, but too late for today's beta. Should be working in tomorrow's beta.

Bidule sees 256 automation parameters exposed by Architect (Param000-Param255); are they driving specific things or (since Bidule can link any arbitray plugins' arbitary parameters together) can I use them 'safely' for controlling other stuff.

They are generic parameters and can be used as both mapping sources and destinations.

Also.. is there an equivalent Intput>Automation Ive overlooked?

I use automation as a remote mapping source, but yes, a module for the same purpose is a good suggestion.

[kingtubby]

Ok, if there’s one thing reading all of the above has shown me, it’s that the current Beta is way above my current level. Which is fine! Not everthing has to be dumbed down for me! (That would be a pretty dull world.) But I’m going to have to hold off until the documentation is in a more developed state and presets / user devices start appearing so I can figure out if I’ll personally get any practical use out of this amazing-looking but complex tool.

I kinda feel the same, but I took the plunge any way, tempted by the intro price. Initially, the play, timeline and mixer seem quite accessible so I feel I can get going to some degree.

[experimental.crow]

Ok, if there’s one thing reading all of the above has shown me, it’s that the current Beta is way above my current level. Which is fine! Not everthing has to be dumbed down for me! (That would be a pretty dull world.) But I’m going to have to hold off until the documentation is in a more developed state and presets / user devices start appearing so I can figure out if I’ll personally get any practical use out of this amazing-looking but complex tool.

I kinda feel the same, but I took the plunge any way, tempted by the intro price. Initially, the play, timeline and mixer seem quite accessible so I feel I can get going to some degree.

colin ,
i know you envision a user base library a la ( or sim ) reaktor ...
until that starts to develop , you'd be well served by including a handful of presets
that would allow users the ability to dissect and study the structures and paths ...

'tis how i ( and many others ) came to grips w/reaktor ...
i'm not much of a builder , but i do dabble ...