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

[lickle_emu]

Hello people,

For an absolute novice like myself, could somebody kindly break down in baby steps how can I use the mono sequencer to trigger a VST inside my DAW (Bitwig)?!

So far, I have added the mono step sequencer on the 1st track on the timeline, and I have added "MIDI output/host" on the graph.

What else am I missing here?!

Many thanks!

Silly me! I hadn't connected the mono step sequencer to the MIDI output in the graph!

[gentleclockdivider]

I'm still a bit in the dark concerning sending midi cc's
What I have done so far
-create an aux sequencer
-create a pack module
- route aux seq. to value in of pack ( middle inlet )
No I need 2 more values for the pack input midi cc number and the midi channel nr , the constant module won't do it , neither do the onboard controls
I just want to send an integer value , the numerical value doesn'
t help either >
I am at loss here

It would be usefull if we had a realtime monitor sto see the data going trough the wire


Also , how come that when we insert graphical component modules in the graph panel , these do not show up in the panel view ?

[colin@loomer]

I'm still a bit in the dark concerning sending midi cc's

I'm on the move at the moment, but tomorrow morning I'll do a screenshot or a macro of what you want.

It would be usefull if we had a realtime monitor sto see the data going trough the wire

Use a `print` module.

Also , how come that if we insert graphical modules in the graph panel these do not show up in the panel view ?

They do if you create them in the panel, but not in the graph.

[gentleclockdivider]

SO that a bug right , not showing up in the panel view while created in the structure view ?
What's the use then if these do not show up ?
It would be less confusing if graghical components can't be created at all from within the structure view

[colin@loomer]

Well I often use sliders etc for internal things that I don't want to appear on the panel, and find it's easier to create things on the panel that I want on the panel, and things I don't on the graph. And you can easily show or hide them using the Properties > Panel > Show options.

I can change this behaviour if that's the consensus.

[gentleclockdivider]

Sorry to be a bit of a pain but there is something else that is highly un-intuitive

When sequencers are created in structure view , you need to click in the properties if these will show up in the play /timeline view
Problem is that the scene select is not responding .

Everything works fine when sequencers are created with the '+' button in view mode

[mannymang]

Sorry to be a bit of a pain but there is something else that is highly un-intuitive
I created a monostepsequencer and routed it to midi out ( al done in structure view )...al fine and playing

Issue 1 . I can create new patterns and add mappings from the comp.keyboard (source type key) but no way to select them
The mappings only work when the sequencers are created with the "+' button in play mode


Issue 2
I want to use this particalur sequence in the play (ableton like ) view .
There is no way to use this existing sequencer , we need to click the '+'button in the play view to create a new one , making the old sequencer redundant
The way I see it , you can create sequencers either by using the + button in both play and timeline view and also in the structure view .

Hi Colin, enjoying Architect...

I also agree with Issue 2 above, unless I've missed it.

Thanks!

[gentleclockdivider]

You need to click in the properties panel of the seq.to make sure that these sequencers (created in structure view ) show up in the play mode .

See post above

But I still haven't figured out how to trigger newly created patterns in the play view ( from sequencers created in strucuture view )

[gentleclockdivider]

Ok I found it

So fo sequencers created in strucuture , for them to show up in 'PLAY mode ' set properties show in play and also set transport conduct to ;play , otherwise these won't be retriggarable

[colin@loomer]

Sequencers created in the graph are, by default, set to Auto conduct, which just means play the first (or current) pattern continually. This is for people who just want a looped pattern, for perpetuity.

What you want is Play conduct. The icons do change depending on if you're in Auto, Play, Timeline mode, but you're right: this can be confusing, so I will try to address this in the next cycle to make it obvious what is what.

[gentleclockdivider]

Yes , I justfigured it out
IBit of a hang over here

[gentleclockdivider]

Man , this is seriously driving me crazy ..
Here's an aux sequencer , enabling all 3 aux lanes
Set lane 1 to send values between 0-127 for the midi value
Lane 2 only sends value 74 (MIDI control nr), and lane 3 is only sending a value of 1 ( midi channe )
All into a pack controller module and into the midi out , still nothing

[Delta Sign]

The pack controller module only updates when it receives a message at the call input. You could either simply connect the 3 outputs from the aux sequencer to the call input, updating it every time it the aux sequencer sends a new message (this would probably make the most sense), or use something like the "on every tick" module.

[woggle]

aaaand I can now save and reload presets




( the only major problem is I have to discipline myself to do some work on a completely unrelated website)

[nordickvr]

...find it's easier to create things on the panel that I want on the panel, and things I don't on the graph. And you can easily show or hide them using the Properties > Panel > Show options.

This behaviour definitely sounds right to me.