Zebra3 Info

[Spirit2017]

my CPU (i3-3.06 GHz),
thanks for the tip EvilDragon i will try this out


WoW this is what i have missing always in zebra.
NoW with 96 KHZ the sunrise!

So is it possible to have 96 Khz in Zebra 2.8(HZ) and the DAW is by 44,1 Khz?

[david.beholder]

WoW this is what i have missing always in zebra. NoW with 96 KHZ the sunrise!
So is it possible to have 96 Khz in Zebra 2.8(HZ) and the DAW is by 44,1 Khz?

Looks like Diva quality settings are controlling oversampling, but there are no quality settings like this in Zebra. Good request for Z3 tho.

[~Pd~]

It's about flexible choice of what note to listen to per oscillator, what event to be triggered by for each envelope and so on. It's very difficult to map this into the paradigms of voice based synthesizers, i.e. it might be difficult to transport a sequencer or arpeggiator on global level by a trigger event emitted from an LFO or function generator on voice level - especially when you play a chord

I have to yet figure out how to ship around these issues.

Wouldn't the arp be disabled in "modular" self-playing mono voice mode? I mean, right now, Zebra has the voice modes poly, retrigger, legato, arpeggiator and duophonic. So modular could be a separate monophonic voice mode, where the self-triggering options are enabled and no incoming MIDI notes are required. Then there's no need to worry about how self triggering fits into the jungle of regular poly mode.

Maybe in modular mode a key range could be assigned to shift the tuning of the whole patch up and down, and other keys could be used as retriggers to resynch the LFOs or sequencers and whatnot. But it's not a mode you'd play like a church organ or a Minimoog, IMO.

[Urs]

In Hive we experimented with a sequencer that could just be a modulator. I think this is where it is going. Arp and sequencer(s) in Zebra could run without necessity to trigger voices, but create control signals. That's also a long standing feature request.

The difficult part will be creating a design that does not make "ordinary" use overly complicated, or "exotic" use look like a bug.

I'll try to elaborate more tomorrow.

[EvilDragon]

my CPU (i3-3.06 GHz),
thanks for the tip EvilDragon i will try this out

Yeah i3 is not really that powerful unfortunately

Zebra 2.8 most definitely won't have an oversampling option, I'm pretty sure... I would update to a much beefier CPU so you can run your projects at 96k.

[pdxindy]

my CPU (i3-3.06 GHz),
thanks for the tip EvilDragon i will try this out


WoW this is what i have missing always in zebra.
NoW with 96 KHZ the sunrise!

So is it possible to have 96 Khz in Zebra 2.8(HZ) and the DAW is by 44,1 Khz?

I always run Zebra at 96Khz... it benefits a lot from it.

And you cannot run Zebra at 96... you have to make your whole project 96

[Spirit2017]

The i3 is very good.
It works fine with DIVA (divine 8voices) and Repro1 HQ.
Maybe Urs don't know this but the i3 has the power.
Zebra HZ with 96 Khz no problem.
What i mean is that zebra needs this HQ button

[EvilDragon]

For Zebra 2, I'm pretty sure it will not happen, since that would mean messing with the code of each and every module... So just run your projects at 96k if you want that. For Zebra 3, anything might happen, though.

[david.beholder]

In Hive we experimented with a sequencer that could just be a modulator. I think this is where it is going. Arp and sequencer(s) in Zebra could run without necessity to trigger voices, but create control signals. That's also a long standing feature request.

Please consider ability to manipulate seq in real time in song mode way i.e. 2-3 different patterns and ability to switch between them.

[Sound Author]

Not sure if this has been discussed before, but I really dig the use of constants in Hive. I'd like to see constants included to the list of modulation sources in Zebra. However, in Hive, I use constant values to adjust parameters that aren't presently displayed within the UI. Not sure there are any "hidden" parameters in Zebra. But I guess there could also be other creative uses for constants. Of course, we have mod mappers...a table of constant values...so there's that. Anyway, just a thought.

[pdxindy]

Not sure if this has been discussed before, but I really dig the use of constants in Hive. I'd like to see constants included to the list of modulation sources in Zebra. However, in Hive, I use constant values to adjust parameters that aren't presently displayed within the UI. Not sure there are any "hidden" parameters in Zebra. But I guess there could also be other creative uses for constants. Of course, we have mod mappers...a table of constant values...so there's that. Anyway, just a thought.

I want random option that is random

right now, random if connected to multiple parameters, all of them get randomized by the same values.

[EvilDragon]

That kind of random can be useful as well... But yeah, I get ya.

[david.beholder]

I want random option that is random

right now, random if connected to multiple parameters, all of them get randomized by the same values.

I guess several random values are easy to get with random, couple fast user lfos and mod matrix. But it's more like kludges.

[vvilms]

All of this talk about LFO's triggering gates in Zebra, and now Prop-H have gone and added VST support.
No more need, on my end, Urs. =)

I jest, as the bit you mentioned about triggering gates on an arp patch -- I'd actually done a bit of exploring with sending CV info from Reason to Zebra in Live over an IAC Bus, and Live crashed every time I tried enabling the arp, so lmao.

[nilhartman]

I for one would love to be able to write Zebra/Diva/Bazille internal modulation signals (like LFOs and such) to MIDI or DAW automation lanes. I know that straight mapping from a plugin to another one or to a DAW parameter is almost impossible (at least without tedious workarounds and often some latency), so that would do it... if technically doable of course.