Zebra 3.0 released

[pdxindy]

I am thinking about pairing a scope-type overlay with the Target Finder (which I hope you have switched to "Tentacles" for fast overviews).

I prefer Lasers

[ThoughtExperiment]

I am thinking about pairing a scope-type overlay with the Target Finder (which I hope you have switched to "Tentacles" for fast overviews).

I prefer Lasers

They could both take yer eye out

[trance_lucent]

It would be cool if we had an option to "Export Wavetable - Post FX" with the oscillator effects applied to each frame.

Something like "Bake OscFX to Curve" would be amazing to have. Although it isn't as straightforward to implement as a simple |avetable export as you suggest.

[tasmaniandevil]

Currently on Fedora I can't drag&drop

We don’t have drag & drop support on Linux yet. We’ll either give it another shot, or add a file loading dialog with one of the next updates.

[Urs]

It would be cool if we had an option to "Export Wavetable - Post FX" with the oscillator effects applied to each frame.

Something like "Bake OscFX to Curve" would be amazing to have. Although it isn't as straightforward to implement as a simple |avetable export as you suggest.

Hehehe, apart from being technically involved, I'm afraid we do not see the point of giving away one of Zebra's strongest selling points. If you want the sound of Zebra 3, you need Zebra 3.

[mindlessgenius]

We don’t have drag & drop support on Linux yet. We’ll either give it another shot, or add a file loading dialog with one of the next updates.

Thanks for looking into it. Is there something I can do myself to copy and paste SVG outside of one Zebra 3 instance? They don't show up in the regular clipboard, so my suspicion is that it is something about my memory permissions, but I'm not sure where to start.
Edit: This accounts for both VST3 and CLAP.

[trance_lucent]

Hehehe, apart from being technically involved, I'm afraid we do not see the point of giving away one of Zebra's strongest selling points. If you want the sound of Zebra 3, you need Zebra 3.

No, unlike Sound Author, who proposed to implement this feature for export, I propose it purely for use inside Zebra.

This would be a cool tool for editing wavetables. Sometimes, while tweaking OscFX, you can find a cool sounding settings. And, if you don't plan to animate these settings, and want to use this sound as a base fir further editing, baking OscFX to Curve would allow to save OscFX slot.

However, I understand that, technically, this is hard to implement. This rather would use wav-to-curve import mechanics, so would not be precise. But, may be, still would be ok.

[Urs]

Ok, I get that... super hard to reliably do.

What we could do and what I've been thinking for a while is to add copy to the graph output to maybe copy the waveform and be able to paste it into the osc. This would only be an approximation though, just like importing single cycle waveform from .wav files.

[suice7]

I am on a hunt for a good midi control solution for Z3. Is there anyone using Roto Control with it? Do the controls of it detect and differentiate the devices inside of Zebra3 (i.e. have 8 controls for FMO2, then add Filter1 and Roto Control updates to the new "device")? Would this behaviour also apply to say Oxi E16? Thank you very much!

[samgreening]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

…

Therefore, the better modulation indicator is always a time based, scope type thing that shows some movement history. The better indicator shows the source and the target.

Something like that would be great! It would really help debugging and understanding modulation in complex patches.

MaxMSP has a similar feature called signal probes, where a mini scope pops up when you hover over any connections.

The docs for it are here: https://docs.cycling74.com/userguide/de ... g/#probing (https://docs.cycling74.com/userguide/debugging_and_probing/#probing)

https://docs.cycling74.com/images/4ac7d ... _1038.webp (https://docs.cycling74.com/images/4ac7d8f85b6b5132c8715caa49b5160e_1038.webp)

[Muryx]

Um die gleiche Lautstärke wie bei Zebralette 3 bei der gleichen Oszillator Eintellung in Zebra 3 zu haben, muss ich entweder den Main Output auf 140, oder den Grid Amp auf 70 stellen. Beide Presets sind vorher initialisiert worden. Aus Zebralette 3 kopiere ich die Oszillator Werte und paste Sie in den Oszillator von Zebra 3. Ich komme immer zum gleichen Ergebnis. Ist das richtig so?
---
To achieve the same volume in Zebra 3 as in Zebralette 3, using the same oscillator settings, I have to either set the Main Output to 140 or the Grid Amp to 70. Both presets have been initialized beforehand. I copy the oscillator values ​​from Zebralette 3 and paste them into the oscillator settings in Zebra 3. I always get the same result. Is this correct?

[chlorinemist]

I understand u-he's reasoning for not having extensive visual feedback but since this is a totally new kind of synthesis I think anything to make it simpler to understand will go a long way towards helping users use it. I noticed that there is already a lot more visual feedback in the final release than the beta's already and i think it is very helpful

[aMUSEd]

Is NKS Support planned for Zebra3?

Still looking at where NKS is headed...

(NI situation is a big blow/concern to us, we know too many people there and we have many close ties)

Best we can do for now is roll our own:

https://www.dropbox.com/scl/fo/36qswdv4 ... x1ige&dl=0

Not as good as native support as in Zebra 2, where each patch could be exported with its own personalised NKS template based on only the modules used - I can only manage a one size fits all approach which means being very selective about what to map and what to leave out. However if you have favourite patches I suggest using the built in tools in Komplete Kontrol to adapt the template to suit your needs

[Urs]

Um die gleiche Lautstärke wie bei Zebralette 3 bei der gleichen Oszillator Eintellung in Zebra 3 zu haben, muss ich entweder den Main Output auf 140, oder den Grid Amp auf 70 stellen. Beide Presets sind vorher initialisiert worden. Aus Zebralette 3 kopiere ich die Oszillator Werte und paste Sie in den Oszillator von Zebra 3. Ich komme immer zum gleichen Ergebnis. Ist das richtig so?
---
To achieve the same volume in Zebra 3 as in Zebralette 3, using the same oscillator settings, I have to either set the Main Output to 140 or the Grid Amp to 70. Both presets have been initialized beforehand. I copy the oscillator values ​​from Zebralette 3 and paste them into the oscillator settings in Zebra 3. I always get the same result. Is this correct?

Das ist korrekt. In Zebra mischt man ja meist 2 oder mehr Oszillatoren, so dass die bei Default besser etwas leiser sind.

That's correct. In Zebra one often mixes two or more oscillators, so they better are a little more quiet by default.

[Urs]

I understand u-he's reasoning for not having extensive visual feedback but since this is a totally new kind of synthesis I think anything to make it simpler to understand will go a long way towards helping users use it. I noticed that there is already a lot more visual feedback in the final release than the beta's already and i think it is very helpful

There is extensive visual feedback for the oscillator and MSEG.

It is also very quick and easy to drag any modulator into the oscilloscope...