Zebra 2.3 Released!

[mkastrup]

For some reason, this new beta is compatible with my old projects that use Zebra 2. Has anyone else encountered this? I've tried setting it up with the installer, as well as the pre-installed version, but in both cases, when I load an FL Project that used an early version of Zebra, FL reports errors and will not load the plugin. However, if I create a new plugin instance, it works just fine.

EDIT: Nevermind! Fixed it.

Are we missing a NOT here before compatible ?

[zircon]

Ha, yes. Here's what happened.

When I use beta versions of Zebra, I leave the DLL names as-is, but then I keep a copy of the normal release in my u-he folder as "OZebra2.dll" (old Zebra.) I use this old version in most projects. However, after installing the latest beta, my projects using the "OZebra2.dll" release would not load it. As a workaround, I simply renamed the NEW beta version to "OZebra2.dll" and it worked fine with old projects. So, the new beta support files don't work with the old version of Zebra, but that's not really a surprise to me.

[mkastrup]

Ha, yes. Here's what happened.

When I use beta versions of Zebra, I leave the DLL names as-is, but then I keep a copy of the normal release in my u-he folder as "OZebra2.dll" (old Zebra.) I use this old version in most projects. However, after installing the latest beta, my projects using the "OZebra2.dll" release would not load it. As a workaround, I simply renamed the NEW beta version to "OZebra2.dll" and it worked fine with old projects. So, the new beta support files don't work with the old version of Zebra, but that's not really a surprise to me.

Ahh well, thats elementary dear watson You cant expect the host to know its to load up another named dll for your old projects heh heh. In the long run i think its more sane to just keep projects using the dll named Zebra2.dll

What if you wre to pick up a project in year 2012, ohhh hmm now what could i have named that dll heh heh

Anyway, i going thru the same thing in my end but came to the conclusion, keep the project under the proper dll name which is Zebra2.dll

Cheers

/Michael

[zircon]

I noticed that in the new beta, sometimes when browsing through patches and playing notes, the synth suddenly becomes muted. I have to switch through a bunch more patches to get it to unmute itself. Very odd.. doesn't happen with all patches, just a handful (I think MSEGs tend to do it.)

[mkastrup]

I noticed that in the new beta, sometimes when browsing through patches and playing notes, the synth suddenly becomes muted. I have to switch through a bunch more patches to get it to unmute itself. Very odd.. doesn't happen with all patches, just a handful (I think MSEGs tend to do it.)

I've seen this before in other versions and i think its related to the VoiceMix page but i have no how and why.

/Michael

[Per Lichtman]

Okay, I've only had a few minutes to test the new betas in demo mode but here's what I found so far.

Tested with Xlutop Chainer V 1.03 using Windows XP Pro SP 2 on a Pentium IV 3.2 GHz with HT disabled.


Z2Win_270508 - Loads without incident so far.
Z2Win_070808 - Crashes when I try to access the GUI. Using the generic parameter display seemed to work.

[mkastrup]

Okay, I've only had a few minutes to test the new betas in demo mode but here's what I found so far.

Tested with Xlutop Chainer V 1.03 using Windows XP Pro SP 2 on a Pentium IV 3.2 GHz with HT disabled.


Z2Win_270508 - Loads without incident so far.
Z2Win_070808 - Crashes when I try to access the GUI. Using the generic parameter display seemed to work.

Hi Per

I assume you have read about errors occurring if your host can see 2 versions of Zebra2.dll. You could try rename the 2'nd version or first version dll to Zebra3.dll and see if this helps.

/Michael

[mabian]

Okay, I've only had a few minutes to test the new betas in demo mode but here's what I found so far.

Tested with Xlutop Chainer V 1.03 using Windows XP Pro SP 2 on a Pentium IV 3.2 GHz with HT disabled.


Z2Win_270508 - Loads without incident so far.
Z2Win_070808 - Crashes when I try to access the GUI. Using the generic parameter display seemed to work.

Hi Per

I assume you have read about errors occurring if your host can see 2 versions of Zebra2.dll. You could try rename the 2'nd version or first version dll to Zebra3.dll and see if this helps.

/Michael

I'd rename old zebra2.dll as zebra2.dll.org, so that scanners do not even try to configure it as a synth (in general, scanners only consider files with .dll extension).

- Mario

[Per Lichtman]

Actually, I had already gotten rid of the older .DLL entirely and had to re-install it afterward, so that's not what's causing the error.

[mkastrup]

Actually, I had already gotten rid of the older .DLL entirely and had to re-install it afterward, so that's not what's causing the error.

When you re-installed did you re-install over the old directory or created an new directory with a name not used before ?

Some old ini files might have survived the re-install.

Anyway, on each new Zebra beta i create an entire new directory name for the new build just to make sure nothing will collide. Just trying to help locate the problem.

/Michael

[Per Lichtman]

Perfect, installing them into their own directory fixed it.

[mkastrup]

Perfect, installing them into their own directory fixed it.

Seee, we fixed it Great Per

[Per Lichtman]

Yeah, normally I copy to another directory but after I had some bad experiences with the Cakewalk synths in that area a year or two ago I stopped making the assumption that it would work better so it seems better to check these days.

Thanks again!

[psycox]

the 2.2.1.b8 works well in fl studio 8.02. the only bugs i found are some graphic defects after resizing the gui.

and i have a simple question. causes the voicedrift button exactly clones of the osc-output every triggerd note ?

[Urs]

and i have a simple question. causes the voicedrift button exactly clones of the osc-output every triggerd note ?

Only when the Osc is also set to reset phase...