Bazille : temporary "mute" a cable ?

[robisme]

Hi u-he team,

Bazille is amazing, but unplugging a cable often destroys a patch’s magic, making experimentation tricky.

It would be fantastic to have a temporary cable “mute” or bypass feature, letting us safely explore patches without breaking the sound.

This would make deep sound design and learning much more intuitive, while keeping the creative flow intact.

Or, at least, make the undo button able to repatch the cable we've just unplugged.

Thanks for considering!

[Mc UB]

Hi Robism,

A bypass would be nice, indeed. Been asked for before a few times.

But the undo repatching the last unplugged cable is already there. Works for me at least.

regards, Frank

[robisme]

Hi,
It must be a bug then, or a limitation on the demo version (and this is dealbreaker).
I use it with Reaper on Linux.
The undo doesn't repatch a cable.
Regards

[Mc UB]

Hi,

You are using the demo? Well, could very well be that's a limitation, I dunno. Using the full version in FL on Win.

A practical way to 'bypass' a cable is to set the knob at the input to 0. That way the cable is still there but it doesn't do anything.

Regards Frank

[robisme]

As a matter of fact, it's the first modification made on a newly selected preset that, instead of canceling itself, gets back to init mode wheb I press undo. It If I tweak several things, it works, until the last one (actualy the first one) is reached, instead of only undoing the tweak, the whole patch is canceled.
It must be a bug I guess. Can you reproduce please ?

[Mc UB]

Hi,

Sure, I'ld like to try. Need some more info though. What steps exactly should I take? It's not clear to me from your explanation.

Regards, Frank

[robisme]

Load a preset, tweak one thing, undo : instead of only undoing the tweak, it unloads the preset.


(Oh and btw, I've just bought it, couldn't wait)

[Mc UB]

Hi,

Just tried what you said, but it's just working as expected here. I load a preset, I twist a knob, or delete a cable, undo, and the twist is restored or the cable attached again. I can tweak multiple things in a row and it undo's those changes in a reverse, like expected.

One thing I did notice what's unexpected, if I undo enough, it even undo's changing the preset, so I come into the previous preset en can go on undoing changes I made to that patch, all the way back to where I first loaded a preset en go back to init state. There's probably a limit to the amount of undo stages though.

Come to think of it... that's what you describe: after your first edit, it unloads the patch and goes back to init. However, if you then redo, the patch comes back up again. In my case anyway...

If your issue persists now that you've bought it, the only thing I can think of is that it's related perhaps to a the Linux version? Perhaps reach out to U-he to raise the issue?

regards, Frank

[robisme]

You described exacty the issue : instead of undoing the first tweak you made, it goes back to init or previous track. Yes it can be redone.

[Mc UB]

Except that over here it DOES undo the first tweak. Then if I undo again it goes back to previous patch/init.

[tasmaniandevil]

You described exacty the issue : instead of undoing the first tweak you made, it goes back to init or previous track. Yes it can be redone.

Could very well be an issue that's only present in the Linux version.

[tasmaniandevil]

There's probably a limit to the amount of undo stages though.

Used to be ten steps, but we upped it to 30 not long ago.
The current release versions of most plug-ins are likely still at ten.

[robisme]

You described exacty the issue : instead of undoing the first tweak you made, it goes back to init or previous track. Yes it can be redone.

Could very well be an issue that's only present in the Linux version.

Ok. Is Bazille a synth you are still working on ? (I hope, because I've just bought it). Can I hope for a fix release some day ? (I know, it's Zebra year ...)

[tasmaniandevil]

If it's a bug, it will get fixed.

[tasmaniandevil]

I just tried it and can confirm that it's a bug happening only on Linux.
The very first action (the preset switch in your case) gets stored in the undo chain, but doesn't trigger the activation of the undo arrow. The second action activates the undo arrow. And when you now hit it, it will undo the first action (the preset switch) instead of the second action.