What's next for Zebra?

[bmrzycki]

Oh, crap - what I "wrote" wasn't quite what I "meant" to say! When I click on the different sizes, I'd primarily like ALL of the text to be larger on any of the existing sizes. And when the GUIs become larger, I'd prefer to see the interfaces condensed, so that we don't have quite so much (needless) space between the knobs!

Ah, understood. Yes, I can see how that'd be useful. Bigger text and knobs but not all that empty space to have to scroll around with.

[Krakatau]

[quote="" Anybody ""] anybody@u-he.com[/quote]



Even if it so natural that you might not be totally aware of it , i'm always amazed by your constant sense of self-derision

[AL321]

...osc fx 'hypercomb'. Turn it's value to max and play a high note sequence. You'll hear it changes a drastic amount every few seconds.

Can't hear that problem here (Cubase LE, OSX Snow Leopard).

Yes, a preset / mp3 would be nice... -> anybody@u-he.com

I guess we can suss it out quickly and fix it

mp3 playback / no download needed (might get a popup ad though):

http://www22.zippyshare.com/v/10736297/file.html


zip download, with mp3 and waveform picture:

http://www.sendspace.com/file/3y5xch (scroll down for link).



The first 8 notes are a saw-type osc with no hypercomb. Then there is 16 notes with hypercomb on.

Following that, there is the same sequence, but passed through a couple of external fx, to make the changes a bit more obvious.
Velocity was switched off, and osc retrigger was switched on. Same issue in both Sonar and FL studio (Vista 32 bit).

Have just sent an email to the address on your website, with a more complete zip (h2p + fxp), so let me know if you don't get it.

[Urs]

[quote="" Anybody ""] anybody@u-he.com

Even if it so natural that you might not be totally aware of it , i'm always amazed by your constant sense of self-derision[/quote]
Actually, hehehe, there was a time when I manually processed orders. During that time this email address was frequently monitored by at least two people (Hans Hafner and myself). Nowadays it's great for contacting me for plugin specific stuff as non-orders really stick out. And of course hans looks at it when I'm on vacation in a blind spot such as Tasmania or long distance flights

[mcnoone]

I'd like to see a physical modeling module.
If it was something that the comb filter alone, already can't do, then it might be useful.

[Sampleconstruct]

It would be cool to have a Remix Pad like e.g. in Alchemy where one could store like several snapshots for each patch. Especially when using all the 4 x/y-pads with lots of Modulation sources and targets one patch alone can create so many different sounds that storing these snaps with the patch would display it's full potential.The possibility to morph between the snaps would also be very cool.

[runray]

It would be cool to have a Remix Pad like e.g. in Alchemy where one could store like several snapshots for each patch. Especially when using all the 4 x/y-pads with lots of Modulation sources and targets one patch alone can create so many different sounds that storing these snaps with the patch would display it's full potential.The possibility to morph between the snaps would also be very cool.

+1

[Sampleconstruct]

It would be great to have Multi Outs in the next version of Zebra so that one could route the Master/Bus1/Bus2 to seperate Outs in a DAW for further procesing. Especially when using sequenced patches with several percussive sounds like this one:
http://soundcloud.com/sampleconstruct/f ... ebra2-demo

individual Outs would be perfect!

[Sampleconstruct]

More for the wishlist:
Can we have a copy+paste function for single modules and whole lanes even? Often it would save a lot of time when one could just copy+paste certain things from one lane to another, or copy an entire lane to another. Maybe a click+option+drag function would also work??
And when editing MSEGs I need a sort of percentage display as a reference point. Especially when assigning MSEGs to pitches it's a trial and error procedure as I can see nowhere, what value each breakpoint or step has.

[Perimeter Sound]

And when editing MSEGs I need a sort of percentage display as a reference point. Especially when assigning MSEGs to pitches it's a trial and error procedure as I can see nowhere, what value each breakpoint or step has.

I've been wanting that for a while now, almost can't believe Urs didn't plan ahead on that one eh. So +2 for that FR.

[aMUSEd]

It would be cool to have a Remix Pad like e.g. in Alchemy where one could store like several snapshots for each patch. Especially when using all the 4 x/y-pads with lots of Modulation sources and targets one patch alone can create so many different sounds that storing these snaps with the patch would display it's full potential.The possibility to morph between the snaps would also be very cool.

+1

This why I use Kore 2 - I made a Kore template for Zebra specifically to enable this and it works very well.

[Sampleconstruct]

Well I don't use Kore 2 and I didn't plan to do so. But maybe it's worth looking into in order to have an All-in-one-Software-Monster...

[Urs]

And when editing MSEGs I need a sort of percentage display as a reference point. Especially when assigning MSEGs to pitches it's a trial and error procedure as I can see nowhere, what value each breakpoint or step has.

I've been wanting that for a while now, almost can't believe Urs didn't plan ahead on that one eh. So +2 for that FR.

Hmmm, what's wrong with the value snap function of the MSEGs? Right-click MSEG editor and choose

I tried to add something visual to it (as in: white/black bars), but it looked crap so I didn't bother anymore. I might however be able to display the current value in the parameter display, like I did with the ModMapper and stuff.

Later,

Urs

[AL321]

And when editing MSEGs I need a sort of percentage display as a reference point. Especially when assigning MSEGs to pitches it's a trial and error procedure as I can see nowhere, what value each breakpoint or step has.

I've been wanting that for a while now, almost can't believe Urs didn't plan ahead on that one eh. So +2 for that FR.

Hmmm, what's wrong with the value snap function of the MSEGs? Right-click MSEG editor and choose

I tried to add something visual to it (as in: white/black bars), but it looked crap so I didn't bother anymore. I might however be able to display the current value in the parameter display, like I did with the ModMapper and stuff.

Later,

Urs

I'll add another +1 to this request. The problem as i see it, is situations when i have 2 seperate parameters modulating the pitch or a filter, and i need both modulations to take the target to an exact value, when combined.

So lets say the MSEG is modulting 12 semitones, but i only want it to affect 7 semitones in the second half of the pattern, because another MSEG or lfo is already adding 5 semitones in that section. I find i often have to move the MSEG node to the top, and start slowly moving it down, counting the number of steps. Obviously it's not a major workflow killer, but if it would be easy for you to display the step number / percentage, it would be a big help. Also with things like comb filter tuning and keeping Zebrify's envelope follower consistent.

Also a key trigger for the noise module would be nice. I know it's white noise, but i do notice the inconsistencies when i'm layering it with synths. I would also like using it to add some acoustic-style bass to Zebra made kicks, but as it is at the moment, the phasing issues would cause unstable bass levels.

Edit:
To add the the percentage part, sometimes when i'm working on complex modulations, the only way i can hear what level the MSEG is at, is to completely flatline the MSEG at a specific value, and fine tune the horizontal line to what i need. So it would be great if Zebra gave us a percentage that we could take note of, and happily carry on building our MSEG pattern.

[Perimeter Sound]

Hmmm, what's wrong with the value snap function of the MSEGs? Right-click MSEG editor and choose

I tried to add something visual to it (as in: white/black bars), but it looked crap so I didn't bother anymore. I might however be able to display the current value in the parameter display, like I did with the ModMapper and stuff.

Later,

Urs

Value Snap doesn't seem to do anything here. Unit Snap seems to have to do with the side to side/time length values, but Value Snap does not appear to do anything when I change it