Zebrify cutoffs snap to 0 after first playback

Official support for: u-he.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Hi guys,

Running into a very strange bug using Zebrify - on re-opening a session with the plug-in instantiated, all my saved parameters are correct and the session plays back and sounds as it should. However once I press stop, at least one of the active VCFs (normally VCF1) will snap to zero and not come back unless I automate it to do so AND start playback before varying automation break points (just automating it as a flat line will not work). Anyone else ever run into this problem? Anyone at u-he have any ideas? Causing a big problem on a sound design project I'm on, hoping to find a fix soon. I can take a screen video if that would help.

I'm using the current version of Zebrify (2.5.1) in Pro Tools 10.0.1, MacOS 10.7.2.
Hackintosh, Intel i7 2600k 3.39 GHz 4-core, 16 GB 1333 MHz DDR3 Corsair Vengeance RAM.

Thanks,
Sam

Post

I have a guess. Check to see if the parameter in question is modulated by a controller like the mod wheel. Chances are it is. Then check the preferences in your DAW. It should have a parameter that says something like "Zero all controllers on stop." You need to uncheck that parameter and your problem will go away.

This happened to me using Sonar X1 and Alchemy Player. If you can set the parameter in your default setup, you won't have to do it every time.
This space has been unintentionally left blank.

Post

right-click the offending knob and "MIDI Unlearn" :)

-> we've been working a lot on the MIDI learn side lately, we'll soon update everything with a potent way to prevent those accidental MIDI learns.

Post

Thanks guys!

MIDI Unlearn seems to have worked, don't think Pro Tools has a snap to 0 MIDI option but let me know if anyone knows otherwise.

And thanks to Urs and co. for patching this.

Post


Post Reply

Return to “u-he”