Loomer

gentleclockdivider · Post by **gentleclockdivider** » Wed Jan 02, 2019 1:26 pm

Another quick question , I want to use a monosequencer (seq1)gate/trigger out to advance to the next gate of another sequencer (seq2) , old skool trick
I uses seq1 gate out and route it to seq 2 play step and set the seq2 to stationary ,
No luck yet .
On a side note , stationary isn't really stationary ..
Could you help me in the right direction by telling which ports need to be controlled ?

gentleclockdivider · Post by **gentleclockdivider** » Wed Jan 02, 2019 1:38 pm

Damn , I just got a hardcore crash whenn inserting a sequencer
And it's the kind of crash that keeps architect in windows memory , even after connecting my audio interface (integra 7)

Is there a log file somewhere , so I can upload it ?

colin@loomer · Post by **colin@loomer** » Wed Jan 02, 2019 1:44 pm

On a side note , stationary isn't really stationary

No, you are correct - it seems to be playing using Brownian motion. That, sir, is a bug. I'll get it fixed. I realised today what you meant yesterday about the divide/multiply mapping as well, and that too is a bug. Thanks for reporting.

Another quick question , I want to use a monosequencer (seq1)gate/trigger out to advance to the next gate of another sequencer (seq2) , old skool trick

The second sequencer, the slave, should be set to a Conduct of "Modulate", and have its mod inlets shown with the "Modulation" eye at the bottom of "Pattern". Set its "Control Action" to Gate.

Connect your master source to the "play pattern control" inlet.

colin@loomer · Post by **colin@loomer** » Wed Jan 02, 2019 1:46 pm

And another note: 0.9.2 beta is up here.

- (fix) Hosted plug-ins with no inputs and multiple outputs couldn't have their outputs routed to other tracks.
- (improvement) Plug-ins are no longer removed if their corresponding "find" option is left unchecked.
- (improvement) Plug-ins can now be sorted in the Mixer plug-in palette.
- (improvement) Plug-in preferences are now saved before a scan so settings are retained if a third-party plug-in causes a crash.
- (add) The default paths for each plug-in format can be optionally disabled when scanning for new plug-ins.
- (improvement) Reduced the height of the reference panel module properties.
- (improvement) Plug-in scanning can be cancelled during a scan.

koalaboy · Post by **koalaboy** » Wed Jan 02, 2019 2:21 pm

I also want to say 'Thank You' for such a nice UI that deals so effortlessly with HiDPI (on windows, at least).
The complete lack of 'problems' at 4K, and simple resizability only became apparent afterwards when I realised it worked 'as expected'.

whyterabbyt · Post by **whyterabbyt** » Wed Jan 02, 2019 2:30 pm

Cheers for those very swift improvements to the VST scanning. I'll have a play later on...

colin@loomer · Post by **colin@loomer** » Wed Jan 02, 2019 2:52 pm

No problems at guys. And thank you all again for taking the time to test, and for the much appreciated suggestions for improvements.

gentleclockdivider · Post by **gentleclockdivider** » Wed Jan 02, 2019 2:55 pm

colin@loomer wrote: Wed Jan 02, 2019 1:44 pm
On a side note , stationary isn't really stationary
No, you are correct - it seems to be playing using Brownian motion. That, sir, is a bug. I'll get it fixed. I realised today what you meant yesterday about the divide/multiply mapping as well, and that too is a bug. Thanks for reporting.

Another quick question , I want to use a monosequencer (seq1)gate/trigger out to advance to the next gate of another sequencer (seq2) , old skool trick
The second sequencer, the slave, should be set to a Conduct of "Modulate", and have its mod inlets shown with the "Modulation" eye at the bottom of "Pattern". Set its "Control Action" to Gate.

Connect your master source to the "play pattern control" inlet.

Double post , can be deleted

gentleclockdivider · Post by **gentleclockdivider** » Wed Jan 02, 2019 2:57 pm

colin@loomer wrote: Wed Jan 02, 2019 1:44 pm
On a side note , stationary isn't really stationary
No, you are correct - it seems to be playing using Brownian motion. That, sir, is a bug. I'll get it fixed. I realised today what you meant yesterday about the divide/multiply mapping as well, and that too is a bug. Thanks for reporting.

Another quick question , I want to use a monosequencer (seq1)gate/trigger out to advance to the next gate of another sequencer (seq2) , old skool trick
The second sequencer, the slave, should be set to a Conduct of "Modulate", and have its mod inlets shown with the "Modulation" eye at the bottom of "Pattern". Set its "Control Action" to Gate.

Connect your master source to the "play pattern control" inlet.

Not realy what I want

Edit : slave sequencer control action should be set to : ONE-step , but it still ignores tied gate triggers (from master seq )
When control action is set to gate , it re-triggers the first step when seq1 output gate+rest in between .
The problem is that whatever control action seq 2 is set to , the speed of the slave seq should be zero/static ...
This is what is mean
Master seq provides the gate and thus rytm , slave seq is just note data

for example
master seq ; gate-gate-rest-rest-rest-gate-rest-gate
sSlave seq pitche data : c.f.g.a

result would be :c.f.rest.rest .rest.g.rest.a
The speed at which it scans trough is only done by the master seq , and when it sends out a rest , the slave seq should be stationary , then when it receives a next trig/gate it should advance to the next step and NOT re-trigger the first step

Hez · Post by **Hez** » Wed Jan 02, 2019 3:33 pm

gentleclockdivider wrote: Wed Jan 02, 2019 2:57 pm
colin@loomer wrote: Wed Jan 02, 2019 1:44 pm
On a side note , stationary isn't really stationary
No, you are correct - it seems to be playing using Brownian motion. That, sir, is a bug. I'll get it fixed. I realised today what you meant yesterday about the divide/multiply mapping as well, and that too is a bug. Thanks for reporting.

Another quick question , I want to use a monosequencer (seq1)gate/trigger out to advance to the next gate of another sequencer (seq2) , old skool trick
The second sequencer, the slave, should be set to a Conduct of "Modulate", and have its mod inlets shown with the "Modulation" eye at the bottom of "Pattern". Set its "Control Action" to Gate.

Connect your master source to the "play pattern control" inlet.
Not realy what I want

Edit : slave sequencer control action should be set to : ONE-step , but it still ignores tied gate triggers (from master seq )
When control action is set to gate , it re-triggers the first step when seq1 output gate+rest in between .

I'm struggling with this too. There also appears to be a small bug with the transport enabled/conduct settings. If you set the grid step sequencer Transport->Enabled = True, then change Transport->Conduct to 'Modulate', it will continue playing automatically until setting Transport->Enabled = False. Flipping Transport->Enabled back to True will not restart the sequencer until Conduct is changed back to Auto.

Still very early days obviously so I'm probably doing something completely wrong!

colin@loomer · Post by **colin@loomer** » Wed Jan 02, 2019 4:00 pm

gentleclockdivider wrote: Wed Jan 02, 2019 2:57 pm Master seq provides the gate and thus rytm , slave seq is just note data

Ah, I think I see what you want to do. Should the slave (in modulate mode) have a Control Action of "one-step", then, and be routed like this:

colin@loomer · Post by **colin@loomer** » Wed Jan 02, 2019 4:01 pm

Hez wrote: Wed Jan 02, 2019 3:33 pm I'm struggling with this too. There also appears to be a small bug with the transport enabled/conduct settings. If you set the grid step sequencer Transport->Enabled = True, then change Transport->Conduct to 'Modulate', it will continue playing automatically until setting Transport->Enabled = False. Flipping Transport->Enabled back to True will not restart the sequencer until Conduct is changed back to Auto.

You're right, that doesn't feel correct. I'll get this tidied up.

ThomasHelzle · Post by **ThomasHelzle** » Wed Jan 02, 2019 4:15 pm

Back home, installed Beta 2 on my main machine, click on the standalone icon and get a direct crash without seeing any GUI.
Windows 8.1 x64, 64 GB RAM, GeForce GTX 1080 TI & GTX 980 TI, i7 6core @ 4.1 GHz, Focusrite Scarlett 18i20...

As a plugin it works in Bitwig 2.4.3.

Currently scanning plugins in the VST. Feels better than in the first version, but the options window is still "frozen" on top of everything else on my machine during the scan and sometimes also freezes other software that's open in parallel. Would be good to be able to put it in the background and/or move it around.

Progress still feels as if it could give a bit more feedback on what it's doing, like showing the scanned names.

It's good that system VST paths are now an option, but it still feels a bit like a blackbox since it does not show what paths are actually seen as system paths.
I personally like how Bitwig is doing it: It simply puts the default/system paths in the VST plugin scan directory list by default and the user can either leave them there or delete them if he/she want's different paths. Feels more streamlined and obvious to me, no "hidden" paths at all. This is especially true for VST2, which isn't really well standardised pathwise.
VST3 is a bit different since it has a fixed path, but I so far use VST2 mostly since there seems to be no point I can see for VST3 at all.

Any news on the VAT-ID?

Cheers,

Tom

colin@loomer · Post by **colin@loomer** » Wed Jan 02, 2019 4:21 pm

OK, sounds like it's heading in the right direction. I'll have a look at the Bitwig scanner than and see what I can ape for the next scanning iteration.

Not so happy about the crash though: does this happen every time you run the app?

The FastSpring guy said that apparently the VATID dialog appears towards the end of a checkout, so it should already be there.

gentleclockdivider · Post by **gentleclockdivider** » Wed Jan 02, 2019 4:51 pm

Can we expand the number of lanes in the grid sequencer , 8 is a bit meager
Also , where are the in/outputs of the macro located ?

Loomer

KVR Audio

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