Zebra 3 Public Beta 2 Revision 20552
-
- KVRer
- 15 posts since 4 Sep, 2018
No comments to this question available please?
holoniverse wrote: Wed Jan 28, 2026 3:24 am What are system requirements for Zebra3? I downloaded and installed the beta but having drop outs and crackles on a lot of patches.
Using linux. My cpu is a bit more than 2 years old (on the road right now, don't remember exact version).
- u-he
- Topic Starter
- 30179 posts since 8 Aug, 2002 from Berlin
It depends on the preset.
So, it is easy to create a preset that no current computer can play. Therefore we have to find a different metric to determine minimum system requirements.
To do this reasonably, we will optimise the final set of presets so that they play well on a reasonably current computer, say, maybe a Macbook Pro from 2022 or a Windows computer with a 3 year old quad core processor. If a few presets are too expensive, that's probably okay, too, but in general we'll make sure that by far most presets will play on a fairly average machine.
A quad core processor will be part of the minimum requirement though, not just 4 logical cores on 2 physical cores.
So, it is easy to create a preset that no current computer can play. Therefore we have to find a different metric to determine minimum system requirements.
To do this reasonably, we will optimise the final set of presets so that they play well on a reasonably current computer, say, maybe a Macbook Pro from 2022 or a Windows computer with a 3 year old quad core processor. If a few presets are too expensive, that's probably okay, too, but in general we'll make sure that by far most presets will play on a fairly average machine.
A quad core processor will be part of the minimum requirement though, not just 4 logical cores on 2 physical cores.
-
- KVRer
- 5 posts since 3 Jul, 2022
Would you be able to implement some sort of feature that allows dragging control A to a number of parameters, say with a modifier key, i.e. instead of having to drag control A to target 1, dragging from control A to target 2, and so on?
Bitwig has the beautiful feature of having a modulator selected and moving any parameters to assign.
Bitwig also has the feature that while holding a modifier and assigning modulation, it allows you to move parameters and NOT modulate.
Still cant wait for the "light" mode color scheme
Bitwig has the beautiful feature of having a modulator selected and moving any parameters to assign.
Bitwig also has the feature that while holding a modifier and assigning modulation, it allows you to move parameters and NOT modulate.
Still cant wait for the "light" mode color scheme
-
- KVRist
- 202 posts since 1 Aug, 2019
Urs wrote: Wed Jan 28, 2026 8:02 am This was 2 years ago... looks different, but is still the same thing you can do today:
To make things sound "resonant", use a sine (upside down u shape, so technically an inverted cosine) and send it through sync then a window that starts and ends at the bottom.
This is great! What spectral distortion was used in the video? Compression? It’s not labeled
Also, I followed Along and made some amazing sounds. I realized You can essentially map one shape (using sync) onto another shape (using the guides), which is sort of like combining say a faster square onto a saw wave.
-
- KVRer
- 25 posts since 18 Dec, 2017
GUI bug in the 4in1 module, sometimes it won't unfold properly,also when it is the last module in the column, you can't scroll down, so half of the interface isnt reacheable.
I really love the extra features like vector movement and selector,
but i was trying to make an arpeggiator ala Korg-MonoPoly, where the oscillators round robin. But i've yet to find a way to make it happen. I thought it should work by using a 4 step mapper as a source for the selector, but if you select gate or trig and use increment mode, i would expect the selected step to advance (when key reset is off) But it does not advance, well occasionally it does but it seems almost random.
Is this normal? i'd really like to be able to do round-robin like selecting, and an option to reset the mapper from another source, instead of just key-on or manual mouseclick.
I really love the extra features like vector movement and selector,
but i was trying to make an arpeggiator ala Korg-MonoPoly, where the oscillators round robin. But i've yet to find a way to make it happen. I thought it should work by using a 4 step mapper as a source for the selector, but if you select gate or trig and use increment mode, i would expect the selected step to advance (when key reset is off) But it does not advance, well occasionally it does but it seems almost random.
Is this normal? i'd really like to be able to do round-robin like selecting, and an option to reset the mapper from another source, instead of just key-on or manual mouseclick.
You do not have the required permissions to view the files attached to this post.
-
ThoughtExperiment ThoughtExperiment https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=7790
- KVRian
- 1064 posts since 26 Jun, 2003 from UK
Small point, but Bitwig is a DAW, Zebra3 is a synth...0matt wrote: Fri Jan 30, 2026 6:09 pm Would you be able to implement some sort of feature that allows dragging control A to a number of parameters, say with a modifier key, i.e. instead of having to drag control A to target 1, dragging from control A to target 2, and so on?
Bitwig has the beautiful feature of having a modulator selected and moving any parameters to assign.
Bitwig also has the feature that while holding a modifier and assigning modulation, it allows you to move parameters and NOT modulate.
Still cant wait for the "light" mode color scheme![]()
-
- KVRer
- 15 posts since 4 Sep, 2018
This is a very sensible response, revealing years of experience. Thanks.
To me it mainly means that I should not freak out if some presets can be hard on the cpu.
My CPU is an Intel 12th gen i7-12700 which is generally acclaimed and supposed to be enough for several years more.
I am surprised I am having issues (also with Bazille), but I don't think changing CPU is an option, really required and also having huge results.
I wonder why it is squeezed out so quickly, if it's linux, Bitwig, the plugins or a combination of all.
BTW monitoring CPU load through bitwig's CPU level meter, I should assume that to be reliable (also when it's closing MAX it regularly pops and cracks, so I assume it's reliable)
To me it mainly means that I should not freak out if some presets can be hard on the cpu.
My CPU is an Intel 12th gen i7-12700 which is generally acclaimed and supposed to be enough for several years more.
I am surprised I am having issues (also with Bazille), but I don't think changing CPU is an option, really required and also having huge results.
I wonder why it is squeezed out so quickly, if it's linux, Bitwig, the plugins or a combination of all.
BTW monitoring CPU load through bitwig's CPU level meter, I should assume that to be reliable (also when it's closing MAX it regularly pops and cracks, so I assume it's reliable)
Urs wrote: Fri Jan 30, 2026 4:07 pm It depends on the preset.
So, it is easy to create a preset that no current computer can play. Therefore we have to find a different metric to determine minimum system requirements.
To do this reasonably, we will optimise the final set of presets so that they play well on a reasonably current computer, say, maybe a Macbook Pro from 2022 or a Windows computer with a 3 year old quad core processor. If a few presets are too expensive, that's probably okay, too, but in general we'll make sure that by far most presets will play on a fairly average machine.
A quad core processor will be part of the minimum requirement though, not just 4 logical cores on 2 physical cores.
-
- KVRer
- 23 posts since 6 Nov, 2025
With the (very good) CPU you already have, I'd be pointing fingers at the linux kernel - specifically realtime support like Ubuntu Studio gives you.holoniverse wrote: Fri Jan 30, 2026 11:45 pm This is a very sensible response, revealing years of experience. Thanks.
To me it mainly means that I should not freak out if some presets can be hard on the cpu.
My CPU is an Intel 12th gen i7-12700 which is generally acclaimed and supposed to be enough for several years more.
I am surprised I am having issues (also with Bazille), but I don't think changing CPU is an option, really required and also having huge results.
I wonder why it is squeezed out so quickly, if it's linux, Bitwig, the plugins or a combination of all.
BTW monitoring CPU load through bitwig's CPU level meter, I should assume that to be reliable (also when it's closing MAX it regularly pops and cracks, so I assume it's reliable)
Urs wrote: Fri Jan 30, 2026 4:07 pm It depends on the preset.
So, it is easy to create a preset that no current computer can play. Therefore we have to find a different metric to determine minimum system requirements.
To do this reasonably, we will optimise the final set of presets so that they play well on a reasonably current computer, say, maybe a Macbook Pro from 2022 or a Windows computer with a 3 year old quad core processor. If a few presets are too expensive, that's probably okay, too, but in general we'll make sure that by far most presets will play on a fairly average machine.
A quad core processor will be part of the minimum requirement though, not just 4 logical cores on 2 physical cores.
- u-he
- Topic Starter
- 30179 posts since 8 Aug, 2002 from Berlin
So in another thread recently someone had dropouts when using a bluetooth audio driver. Drivers and such can be a problem, too, particularly if they are optimised for low latency I guess.
Also, perception in forums and socials is often based on the most extreme issues. Like, the first beta had a bug where a few presets that would usually play fine would not put voices on stand by and thus use excessive CPU. I saw these mentioned sometimes, and in the current beta this is gone and those presets now play normally.
Also, perception in forums and socials is often based on the most extreme issues. Like, the first beta had a bug where a few presets that would usually play fine would not put voices on stand by and thus use excessive CPU. I saw these mentioned sometimes, and in the current beta this is gone and those presets now play normally.
-
- KVRer
- 11 posts since 7 Jan, 2026
I'm running into some confusion with the MSEG- this is probably a me issue but help resolving would be great. I am trying to setup a simple one shot envelope with the MSEG. Having read the manual I assumed that putting the MSEG in 'Single' mode would do so. However the MSEG continues to loop/retrigger even if I continue to depress the key (which seems the opposite of what is suggested in the manual). I am sure this is my misunderstanding but help would be appreciated! thanks.
p.s. I guess just setting the loop points outside any moving segment works but just out of interest.
p.s. I guess just setting the loop points outside any moving segment works but just out of interest.
- u-he
- Topic Starter
- 30179 posts since 8 Aug, 2002 from Berlin
So, under "one shot" I understand an envelope that gets triggered by each note and then plays through once each time regardless of sustain or gate off. Like it starts and then plays out in full no matter if the key is held or lifted at any time.
This is simply possible by putting an MSEG into "continuous" mode, and setting the the loop region to the last point.
"Single trigger" means something else: When no key is pressed, only the first note starts the envelope, and all subsequent overlapping notes take over the same movement fro the envelope. However, when keys are lifted, then envelopes leave the flock and ring out. Once all keys are lifted, the next key will trigger the envelope again and things start over.
This is simply possible by putting an MSEG into "continuous" mode, and setting the the loop region to the last point.
"Single trigger" means something else: When no key is pressed, only the first note starts the envelope, and all subsequent overlapping notes take over the same movement fro the envelope. However, when keys are lifted, then envelopes leave the flock and ring out. Once all keys are lifted, the next key will trigger the envelope again and things start over.
-
- KVRer
- 11 posts since 7 Jan, 2026
got it- thanks for responding so quickly! clear.Urs wrote: Sat Jan 31, 2026 1:03 pm So, under "one shot" I understand an envelope that gets triggered by each note and then plays through once each time regardless of sustain or gate off. Like it starts and then plays out in full no matter if the key is held or lifted at any time.
This is simply possible by putting an MSEG into "continuous" mode, and setting the the loop region to the last point.
"Single trigger" means something else: When no key is pressed, only the first note starts the envelope, and all subsequent overlapping notes take over the same movement fro the envelope. However, when keys are lifted, then envelopes leave the flock and ring out. Once all keys are lifted, the next key will trigger the envelope again and things start over.
- KVRAF
- 3385 posts since 25 Apr, 2011
don't be afraid to make this the new "can it run crysis" synth. DIVA was kinda like that too and it pushed innovation @ other companiesUrs wrote: Fri Jan 30, 2026 4:07 pm It depends on the preset.
So, it is easy to create a preset that no current computer can play. Therefore we have to find a different metric to determine minimum system requirements.
To do this reasonably, we will optimise the final set of presets so that they play well on a reasonably current computer, say, maybe a Macbook Pro from 2022 or a Windows computer with a 3 year old quad core processor. If a few presets are too expensive, that's probably okay, too, but in general we'll make sure that by far most presets will play on a fairly average machine.
A quad core processor will be part of the minimum requirement though, not just 4 logical cores on 2 physical cores.
- u-he
- Topic Starter
- 30179 posts since 8 Aug, 2002 from Berlin
