Zebra 3 Public Beta Revision 20399

[Touch The Universe]

Sweet is this - having much fun already - just to check, that faint rumble noise pops in every minute or so is a demo limitation and not it going out of detune etc the same, right? I am hearing both in FL Studio Mac1 Taho 26

[Viktor [TUC]]

I don't want to get into the weeds here but no, there is a difference between a control surface in Logic, and a generic MIDI controller.

Apologies, I think I misunderstood what sort of device you were referring to. Yeah, what you describe is indeed a different thing.

[Howard]

manual says: "Add points .....................................double-click in the background or option+click (Mac) / ctrl+click (Win)"
I'm just doing something wrong ?

No, that's a known issue we need to fix. Thanks for the report!
Tip: Use the Add Points (pen) tool instead.

[Urs]

Sweet is this - having much fun already - just to check, that faint rumble noise pops in every minute or so is a demo limitation and not it going out of detune etc the same, right? I am hearing both in FL Studio Mac1 Taho 26

Have you registered it with a License Card? If you don't have a license yet, there's one in the first post to help beta test without demo limitations.

[ThoughtExperiment]

Just to be clear on CPU usage - Urs' original post waaay back on page1 mentioned 'no multicore support yet'. That seemed clear enough to me then, but somewhere along the way I read a post which mentioned something about utilising DAW multicore support? Up to now, I've been assuming that by the final release we'll have multicore support and the one or two patches which crackle (slightly) on my PC (Ryzen 5, 3.7GHz, 32GB RAM) will probably no longer crackle. Am I right to assume that or should I regard those patches as the outer limit of my CPU power?

[Touch The Universe]

Sweet is this - having much fun already - just to check, that faint rumble noise pops in every minute or so is a demo limitation and not it going out of detune etc the same, right? I am hearing both in FL Studio Mac1 Taho 26

Have you registered it with a License Card? If you don't have a license yet, there's one in the first post to help beta test without demo limitations.

Thanks, that seems right - I remember you being quite generous with your beta's in the past - I expected the same this time too - just missed the new system.

I heard both white noise - and detune/spiking though. Will see if it pops up again.

[Touch The Universe]

Changes sizes won't allow you to increase after decreasing in FL Studio, this has to be a bug.

[Matty686]

I noticed that the stereo phase of the reverb 1 is not random I would like an option for allowing true psudo randomness for phases in Fx maybe you could set a seed or Maby you could use system time and date I feel this would make the synth more organic and analog sounding

[WalterH]

Any chance we have dedicated bug report section for Z3 today ?

[Touch The Universe]

This thing has an excellent range, can get as quite nasty or beautifully pristine. Haven't even explored the oscillators yet, let alone 1 percent of this thing.

Is it wise to save a bunch of presets with it?

[exmatproton]

Just to be clear on CPU usage - Urs' original post waaay back on page1 mentioned 'no multicore support yet'. That seemed clear enough to me then, but somewhere along the way I read a post which mentioned something about utilising DAW multicore support? Up to now, I've been assuming that by the final release we'll have multicore support and the one or two patches which crackle (slightly) on my PC (Ryzen 5, 3.7GHz, 32GB RAM) will probably no longer crackle. Am I right to assume that or should I regard those patches as the outer limit of my CPU power?

Nah..i was talking about multiple instances (or, i meant using multiple instances). The context was adding 16 more voices to Z3.

[Urs]

Is it wise to save a bunch of presets with it?

Absolutely!

[Kyunghee]

Your controllers sends MIDI, so you can easily tell Zebra3 which MIDI CCs you want to connect to Control A-D and you're done, realtime control of these performance controls. And these are then recorded (or drawn like automation) in the MIDI clip.

I don't want to get into the weeds here but no, there is a difference between a control surface in Logic, and a generic MIDI controller - one device can't be both, and when you've got seamless intelligent plugin control, going back to manual/dumb generic MIDI, whether that's adding or switching to another MIDI controller device, or having to manually switch controller modes and templates, is not a solution. These is good reason I was asking for the specific request.

But Urs has already said likely these controls will become automatable, which is all I was asking/hoping for, so we're good!

Indeed, with my control surface (ableton move), assigning midi cc is pretty tedious, but it recognises any automatable parameter instantly. That means that I can easily control any parameter in Zebra ,except the ones which matter the most for performance

[Urs]

Just to be clear on CPU usage - Urs' original post waaay back on page1 mentioned 'no multicore support yet'. That seemed clear enough to me then, but somewhere along the way I read a post which mentioned something about utilising DAW multicore support? Up to now, I've been assuming that by the final release we'll have multicore support and the one or two patches which crackle (slightly) on my PC (Ryzen 5, 3.7GHz, 32GB RAM) will probably no longer crackle. Am I right to assume that or should I regard those patches as the outer limit of my CPU power?

We internally have a multicore option, but it has been glitchy. We'll make it available once and if we can unglitch it.

However, many of the modules (and presets!) will be further optimised.

Also, I have recorded a video today about optimisation and the built-in tools, but I don't think it'll be ready before Monday/Tuesday.

[WalterH]

damn it needs optimizations because I have only 2 OSC here only few parameters modulated 2-3 (volume and tune, and volume on another only).. and filter or delay modulated, it eats like 30-40% of CPU, I have 6 core 5820k working on 3.6ghz..