u-he

geoslake · Post by **geoslake** » Mon Sep 28, 2009 12:22 pm

How is your dll upgrade policy ?
The demo I have is called zebra2.dll, which means that when zebra3 will be released (will be zebra3.dll obviously), it wont be backward compatible.
How did things happen when upgrading from z1 to z2 ?

Thanks

Urs · Post by **Urs** » Mon Sep 28, 2009 12:43 pm

easymode wrote:How is your dll upgrade policy ?
The demo I have is called zebra2.dll, which means that when zebra3 will be released (will be zebra3.dll obviously), it wont be backward compatible.
How did things happen when upgrading from z1 to z2 ?

Thanks

Zebra 2 was a complete rewrite from Zebra 1. That's why there isn't any backwards compatibility (and also why I asked for an upgrade fee). There's however no indication as to why Zebra 3 shouldn't load anything from Zebra 2. There's actually no indication at all the there will be a Zebra3.dll. So far I managed to put major upgrades into the second digit of 2.x. I don't see why there couldn't be a Zebra 2.47 rather than switching to 3.0 from 2.9 etc.

As I wrote somewhere else, I believe in ever evolving software. As such I have no intention to fade out Zebra2 and to start over yet again. There's no reason to do so. If there's ever gonna be a Zebra 3.x, then it'll be based on 2.x

(unless something unexpected happens that forces me to do a full rewrite, e.g. the extinction of C++ or the advent of a new programming/processing paradigm, both of which I wouldn't expect before 20-50 years from now)

Cheers,

Urs

kajiotaku · Post by **kajiotaku** » Mon Sep 28, 2009 12:53 pm

Here's a little GUI idea...how about a hue slider? All it would do is adjust the hue, like in Slayer2 or Photoshop

Maybe even contrast and brightness sliders? Just an idea. Not sure if you can do that in a VST...

Urs · Post by **Urs** » Mon Sep 28, 2009 12:57 pm

kajiotaku wrote:Here's a little GUI idea...how about a hue slider? All it would do is adjust the hue, like in Slayer2 or Photoshop Maybe even contrast and brightness sliders? Just an idea. Not sure if you can do that in a VST...

That's tricky. Each plugin instance would then need to allocate memory for its own set of bitmap graphics. That could make it a memory hog.

mabian · Post by **mabian** » Mon Sep 28, 2009 1:00 pm

Nah, why not making it valid for all plugin instances?

- Mario

kajiotaku · Post by **kajiotaku** » Mon Sep 28, 2009 1:00 pm

Urs wrote:
kajiotaku wrote:Here's a little GUI idea...how about a hue slider? All it would do is adjust the hue, like in Slayer2 or Photoshop Maybe even contrast and brightness sliders? Just an idea. Not sure if you can do that in a VST...
That's tricky. Each plugin instance would then need to allocate memory for its own set of bitmap graphics. That could make it a memory hog.

So it can't alter the hue and such live? D: Maybe even a color translator? Like FF0000 equals 00FF00 and it will do that live instead of trying to cache the bitmaps or w/e? It's not important or anything, but it'd be pretty.

Urs · Post by **Urs** » Mon Sep 28, 2009 1:18 pm

mabian wrote:Nah, why not making it valid for all plugin instances?

- Mario

Well, the idea was to offer 2-4 presets as preferences. That would be for all instances then and - while doing the trick - it would neither involve too many cpu cycles nor too much ram.

Live transformation of pixel colours is out of the question because an u-he gui can easily reach 2500 x 1500 pixels. It would bring your cpu down to its knees, unless I rewrite the whole stuff for OpenGL/DirectX - which I'm very reluctant to because I have some ideas for future ui stuff that may then be slower in that realm.

kajiotaku · Post by **kajiotaku** » Mon Sep 28, 2009 3:11 pm

Urs wrote:Live transformation of pixel colours is out of the question because an u-he gui can easily reach 2500 x 1500 pixels. It would bring your cpu down to its knees, unless I rewrite the whole stuff for OpenGL/DirectX - which I'm very reluctant to because I have some ideas for future ui stuff that may then be slower in that realm.

Then how about a script for GIMP or Photoshop that will change all the hues in the appropriate images for you? Or a program that will do that on it's own.

Urs · Post by **Urs** » Mon Sep 28, 2009 3:31 pm

kajiotaku wrote:
Urs wrote:Live transformation of pixel colours is out of the question because an u-he gui can easily reach 2500 x 1500 pixels. It would bring your cpu down to its knees, unless I rewrite the whole stuff for OpenGL/DirectX - which I'm very reluctant to because I have some ideas for future ui stuff that may then be slower in that realm.
Then how about a script for GIMP or Photoshop that will change all the hues in the appropriate images for you? Or a program that will do that on it's own.

You're welcome to create such a script. The png files are all there in your resource directories

kajiotaku · Post by **kajiotaku** » Mon Sep 28, 2009 3:32 pm

I'll try...

Cyoon · Post by **Cyoon** » Mon Sep 28, 2009 5:40 pm

kajiotaku wrote:
Urs wrote:
kajiotaku wrote:Here's a little GUI idea...how about a hue slider? All it would do is adjust the hue, like in Slayer2 or Photoshop Maybe even contrast and brightness sliders? Just an idea. Not sure if you can do that in a VST...
That's tricky. Each plugin instance would then need to allocate memory for its own set of bitmap graphics. That could make it a memory hog.
So it can't alter the hue and such live? D: Maybe even a color translator? Like FF0000 equals 00FF00 and it will do that live instead of trying to cache the bitmaps or w/e? It's not important or anything, but it'd be pretty.

and this as modulation source/target please

Echoes in the Attic · Post by **Echoes in the Attic** » Tue Sep 29, 2009 2:22 am

Ok, so going back to duophonic mode, I'm not sure I'm seeing any difference from mono. It doesn't seem like duophonic mode that I am familiar with (like on the oddysey/oddity).

When I hit two keys at the same time, I'm still just hearing one note. What am I doing wrong?

hakey · Post by **hakey** » Tue Sep 29, 2009 8:13 am

Echoes in the Attic wrote:Ok, so going back to duophonic mode, I'm not sure I'm seeing any difference from mono. It doesn't seem like duophonic mode that I am familiar with (like on the oddysey/oddity).

When I hit two keys at the same time, I'm still just hearing one note. What am I doing wrong?

That would happen if you only have one Osc in the Voice Grid - you need two OSC's for duophonic mode to work.

ZenPunkHippy · Post by **ZenPunkHippy** » Tue Sep 29, 2009 8:47 am

Once you figure it out, Duophonic mode is teh awesome!

A good example is to load the default Zebra preset*, set to Duo mode then hold a low note while tinkling the high notes. Sounds fabulous

If you set "Glide 2" to a suitable value you'll quickly make your way to pitch-bend heaven

A brilliant addition to an already brilliant synth!!!

Peace,
Andy.

*edit: not the "init" preset with one oscillator, the original default preset that is a bass patch with two oscillators and a delay.

Howard · Post by **Howard** » Tue Sep 29, 2009 10:13 am

ZenPunkHippy wrote:Once you figure it out, Duophonic mode is teh awesome!

Yep, especially "teh awesome" when you play mono.

u-he

KVR Audio

Zebra 2.5 Released!