Zebra 2.3 Released!

[Urs]

- Is there a way to make the default preset the init preset with this version? It seems to load up a patch instead.

Sorry, unfortunately many, many, many people confuse a synthesizer that "sounds really boring when you first open it" with a "generally boring" one. I might find a way to add a "default patch" option, but it's too late for this release. Keep monitoring the forum for improvements

- Which supersaw is this version using?

There was a topic recently... I posted examples of 3 different versions of Eleven after being educated about flaws in my prior implementation. The one in the current version is supposed to be "the 3rd one" which was generally accepted to be the best sounding one.

- The looks options don't seem to save the skin size, only the type

That's intentional. I suspect too much trouble with hosts because gui resizing is not exactly a common topic within any of the plugin standards. Hence at "creation time" I want to pamper the hosts by giving them a standard size. Options may be evaluated in the future as engine improvements are an ongoing, neverending project.

Cheers,

Urs

[fgimian]

- Is there a way to make the default preset the init preset with this version? It seems to load up a patch instead.

Sorry, unfortunately many, many, many people confuse a synthesizer that "sounds really boring when you first open it" with a "generally boring" one. I might find a way to add a "default patch" option, but it's too late for this release. Keep monitoring the forum for improvements

- Which supersaw is this version using?

There was a topic recently... I posted examples of 3 different versions of Eleven after being educated about flaws in my prior implementation. The one in the current version is supposed to be "the 3rd one" which was generally accepted to be the best sounding one.

- The looks options don't seem to save the skin size, only the type

That's intentional. I suspect too much trouble with hosts because gui resizing is not exactly a common topic within any of the plugin standards. Hence at "creation time" I want to pamper the hosts by giving them a standard size. Options may be evaluated in the future as engine improvements are an ongoing, neverending project.

Cheers,

Urs

Thanks Urs, will test more soon to see if I come up with anything else.

Cheers
Fots

[Urs]

Cool!

I think however this version is it. I mean, it's merely a maintenance update on the way to Zebra 2.5 anyway. It fixes most (if not all) known issues with V2.2 and puts all the new features into an official version. Which is required i.e. for some upcoming soundbanks.

Later,

Urs

[fgimian]

Cool!

I think however this version is it. I mean, it's merely a maintenance update on the way to Zebra 2.5 anyway. It fixes most (if not all) known issues with V2.2 and puts all the new features into an official version. Which is required i.e. for some upcoming soundbanks.

Later,

Urs

Yeah, totally understand, and it does seem very stable. I think the Dark Horse skin bug is the only thing worth looking into, but it's very minor because the problem only manifests itself just after you have changed skin. If you set dark horse to your default, and reload Zebra, the problem doesn't appear.

Best Regards
Fots

[adamszabo]

When I have any other size then normal, and move it outside of the screen in FL I get while lines across the interface.

[Polybius]

Works like a charm in Renoise, thanks for the good care Urs!

[Urs]

When I have any other size then normal, and move it outside of the screen in FL I get while lines across the interface.

Yeah, I know. That's a little problem that's caused by non-integer pixel coordinates. havn't yet sussed out how to avoid these.

Urs

[Polybius]

Envelope attack modulation still doesn't seem to work tough, or am i doing something wrong?

[Urs]

Envelope attack modulation still doesn't seem to work tough, or am i doing something wrong?

It should definately work, but it only takes effect at the very beginning of a note. A slow attack can't be made faster while it's going. This makes it mostly useful for global and static modulators, such as global LFOs, ArpMods, Velocity and ModWheel but maybe not so much for other modulators.

I will probably at some point try to unleash it for continuous modulation, but I can't currently justify the extra cpu consumption for an otherwise rarely used case... especially as the MSEGs can be modulated easily as an alternative.

Urs

[Echoes in the Attic]

The 'make default' command doesn't seem to do anything. Is it supposed to make the current skin the default every time you load it?

With both the VST and AU version, when I change to the dark horse skin, make it default, and then close it, it reverts to the original skin when I load Zebra again.

This is RC2.

oh and also the extra modules at first in the default patch, left over from RC1.

Yeah, the SideBand modules mysteriously appear only when you switch to the Dark Horse. They disappear after any action in the Grid. I havn't yet found out how the skin has to be modified to start without this glitch, but I'll post the solution in my tech blog and update the files with the then-next version.

Other than that things work fine here, so it's probably a problem with file permissions. It might help to Repair Permissions (assuming you have admin rights on your machine) or even to simply copy Zebra2.component from MacHD/Library/Audio/Plug-Ins/Components/ to MacHD/Users/You/Library/Audio/Plug-Ins/Components/

I did actually just repair permissions. And I do have admin rights. Still, Dark Horse will not be the default. "Make Default" has no effect. Even when I save a patch as an Ableton Live device, it still opens up the next time as original skin.

So the only way to keep the dark horse skin is to make a user version of zebra and use it? Does everyone have that problem? Personally I prefer to keep all my plug-ins in the system folder.

[Urs]

So the only way to keep the dark horse skin is to make a user version of zebra and use it? Does everyone have that problem? Personally I prefer to keep all my plug-ins in the system folder.

Hmmm... it must be a permissions thing, really.

You can manually edit this:

- right click Zebra2.component (or Zbera2.vst) and select "show package contents"
- navigate to Contents/Resources/Scripts/
- open Zebra2default.txt
- replace the whole content with following line:

Code: Select all

THEME name='Unempty Dark Horse'

That should do the trick.

Urs

[Echoes in the Attic]

You can manually edit this:

- right click Zebra2.component (or Zbera2.vst) and select "show package contents"
- navigate to Contents/Resources/Scripts/
- open Zebra2default.txt
- replace the whole content with following line:


THEME name='Unempty Dark Horse'


That should do the trick.

Urs

Ok, so first it wouldn't let me save over the text file after adding that line, so I changed the admin permissions from read to read/write. Still wouldn't save so I changed the entire contents folder of the zebra AU to read/write, then I could save the text file. But after I added the line you suggested and opened it up in Live, there were no controls, just the dark horse shell on the performance screen. No menu or anything, just blank, so that's not working either.

thanks

By the way, where are zebras preferences kept? I looked for a plist file in both my user directory and system prefs but couldn't find it in either. I was thinking maybe trashing my preferences could help.

[Echoes in the Attic]

wait! I was adding that line to zebra.txt

sorry, let me try again...

[Echoes in the Attic]

ok, figured it out. It wouldn't let me add that line to zebradefault.txt because the file was set to read only for admin. After I changed it to read/write, I didn't even bother adding the line, as I guessed that perhaps the read only was preventing the "Make Default" command from working. And I was right! It works now and I didn't have to add the line manually.

thanks!

[ZenPunkHippy]

It is working correctly for me now in Logic. I can set the default skin from within Zebra and the next instance loads the correct skin. For that to work I had to change the permission of the file Zera2default.txt within the package.

Seems the default install has read/write set only for "system" on all files in that directory of the component, while the directory itself has read/write set for the user account.

Peace,
Andy.