You can easlity use PatchMaster an map the probablity button, which make things quicker
@optoproductions Жыл бұрын
Thanks for the tip, I'll look into that! 👍
@adrimathlener8008 Жыл бұрын
Nice one.
@rsmus7 Жыл бұрын
I just need to click a step once and (wait a bit and) then I can hit the P button and edit the probability, this works with already activated steps and with "new" steps too, don't get fooled by the short moment where the active step gets dark ;-) From the manual: "When activating a given step by clicking it once, it will turn green showing that the step is on. Clicking the “p” button turns it yellow, and the main display shows the probability associated with this step. While the probability remains shown, the probability can be adjusted with the main knob, in 0.02 increments, between 0 and 1. When a yellow step is selected, clicking the “p” button again will turn it off."
@optoproductions Жыл бұрын
Oh weird maybe they updated it, if I click on an activated step with P mode it will deactivate the step.
@rsmus7 Жыл бұрын
@@optoproductions I'm using version 2.4.0 of the impromptu plugin with VCV v2.4.1, when I click on a step with P mode the step starts blinking, I'm using Win11, maybe you found a bug?
@optoproductions Жыл бұрын
@@rsmus7 I'll check it out tommorow 👍
@optoproductions Жыл бұрын
@@rsmus7 I just updated everything, and it doesn't work for me, maybe we're talking about different things? But let's say I am on step 1 and I want to change the probability on step 4, which is already active. It now turns off step 4. If step 1 is selected, and I press the p, it will only be activated for the currently selected step 1, whether I wait or not. But I'm on Windows 10, so perhaps that's different?
@rsmus7 Жыл бұрын
@@optoproductions thats weird, I can edit the probability on each step, no matter if it is activated or not , just by clicking on the step then clicking the "P" knob and then changing the "main knob", the state of the step ( active or non active ) stays as it was before adjusting the probability. maybe that's something to report at the VCV forum or the impromptu github