Zebra 2.5 LFO in user/step behaves inconsistently

[k-bird]

Was rolling some C64 sounds this morning and i think i've found a bug in the behaviour of the LFOs in user/steps while running Reaper.

Freshly reloading the VSTi and patch, the steps controlling the pitch of the oscillator snap pleasingly from value to value, making a pleasing oldschool arpeggio effect without retriggering the envelope.

But something is making it mad.

In Reaper, if i render to WAV, change the loop boundaries of the project or reload the project file from a working version, the steps stop snapping and start gliding quickly between one another. This makes the notes all wobbly and naff.

Example (2 MP3s + patch): http://dl.dropbox.com/u/1650913/zebra2_ ... aviour.zip

If i delete the instance of Zebra 2.5 and reload the patch mid-playthrough from "initialize", it comes good again (but breaks when i stop playback and start it again). Seems like some sort of restart initialisation call coming from the host and confusing something inside Zebra but i'm not sure because i don't know how VST works.

Any ideas? Setting i'm missing somewhere that controls hard/soft step snapping?

[Howard]

Example (2 MP3s + patch): http://dl.dropbox.com/u/1650913/zebra2_ ... aviour.zip

Listening to the "broken" version, it sounds as if the LFO User mode switched over to lines instead of steps. You could send the patch, and I'll check it out in Reaper / Mac.

[Urs]

This might be a MIDI Learn issue. Can you send the file

Vstplugins\Support\com.u-he.Zebra2.midimap.txt

to urs@u-he.com?

Or just have a look at it in Wordpad.

Maybe for some reason some LFO mode is assigned to ModWheel or something.

Urs

[k-bird]

Example (2 MP3s + patch): http://dl.dropbox.com/u/1650913/zebra2_ ... aviour.zip

Listening to the "broken" version, it sounds as if the LFO User mode switched over to lines instead of steps. You could send the patch, and I'll check it out in Reaper / Mac.

The h2p-format patch should be in the zipfile.

I thought maybe it was going to lines mode, but in lines mode it didn't hold at any of the values the way that broken step does. Broken step does more of a quick but unwelcome portamento between values.

Urs, the file you mentioned only has the line

Code: Select all

// Global MidiCC Map

and a few blank lines underneath.