Zebralette 3 Public Beta Announcement (Revision 15573)

[jtsterays]

When Zebra 3 is released, you guys will have 2 wavetable synths that use separated folders for the wavetables which will be quite annoying to keep them the same. Is there a plan for that?

[messmerd]

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.

The preset discovery provider might not be implemented correctly for the CLAP plugin.
It seems to be calling `add_feature`, `add_plugin_id`, and other such functions before it calls `begin_preset`. Either that or my host is misbehaving, though Zebralette 3 is the only CLAP plugin I'm experiencing this issue with, so I'm guessing it's the plugin misbehaving.

Here's the relevant part of the CLAP API for reference:
https://github.com/free-audio/clap/blob ... #L109-L123 (https://github.com/free-audio/clap/blob/main/include/clap/factory/preset-discovery.h#L109-L123)

[tumface]

When Zebra 3 is released, you guys will have 2 wavetable synths that use separated folders for the wavetables which will be quite annoying to keep them the same. Is there a plan for that?

I use symbolic links (ln -s on Mac and Linux, mklink /D on Windows) to give all of my wavetable synths access to a common set of directories with wavetables. Hive 2, Serum, Vital, and Phase Plant all have directory links to the same set of shared Wavetables. I use Hive's as the "master" directory that the others have links to. Works surprisingly well.

[xtreme sounds]

Hi is there a way to export a looped wav or single cycle waveform? I did the export thing and loaded it into the digitakt but a few problems occur. 1. the pitch is near the top end so I cant play high notes and the lower octaves are too low. 2) after pressing a note down the waveform makes a high pitched noise when it reaches the end of the sample. even in looped playback mode. no looping. any ideas what I can do?

[Hanz Meyzer]

I feel real craving for Zebra 3, I again used Zebralette 3...

[Shiek927]

With the end of the year coming up, I'm curious to hear what the future plans are for Zebralette 3 and Zebra3! hopefully we'll see an actual build of Zebra3 sometime in 2025!

[Urs]

I'm currently weighing the pros and cons of starting a Z3 development blog with screenshots and little videos about the new concepts in it. We're bit afraid of how much engagement this might require from my side, and thus possibly delay my input. OTOH we could manage expectations as of course Zebra 3 will start with what appears to be a smaller feature set than Zebra 2 (which has had many modules added over the years).

(like, we do not have a final feature set of FM oscillators yet, and thus we might not initially show or release Zebra 3 with FMOs)

[underscoreraven]

When Zebra 3 is released, you guys will have 2 wavetable synths that use separated folders for the wavetables which will be quite annoying to keep them the same. Is there a plan for that?

I use symbolic links (ln -s on Mac and Linux, mklink /D on Windows) to give all of my wavetable synths access to a common set of directories with wavetables. Hive 2, Serum, Vital, and Phase Plant all have directory links to the same set of shared Wavetables. I use Hive's as the "master" directory that the others have links to. Works surprisingly well.

Yep, I do the same, it's super convenient and saves disk space by not having to copy third party wavetable packs to multiple folders, "Link Shell Extension" makes this really easy to do on windows too. Though Hives wavetable list can kinda break if that shared wavetable folder ever becomes too big or has too many subfolders or something like that

[Fannon]

I'm currently weighing the pros and cons of starting a Z3 development blog with screenshots and little videos about the new concepts in it. We're bit afraid of how much engagement this might require from my side, and thus possibly delay my input. OTOH we could manage expectations as of course Zebra 3 will start with what appears to be a smaller feature set than Zebra 2 (which has had many modules added over the years).

(like, we do not have a final feature set of FM oscillators yet, and thus we might not initially show or release Zebra 3 with FMOs)

I would appreciate such a development blog, but you know best if its worth the time you have to put in.

Regarding expectations: Since Zebra 3 is not backward compatible to Zebra 2 (this might be one of the most important expectations to set right), I would also expect that Zebra 3 starts with less features.

I would actually prefer to have Zebra 3 out earlier, with just the core features out already, knowing more will come with feature updates. The modular architecture of Zebra should make it quite easy to add more osc, filters, effects later on I assume.

[Sound Author]

I'm currently weighing the pros and cons of starting a Z3 development blog with screenshots and little videos about the new concepts in it. We're bit afraid of how much engagement this might require from my side, and thus possibly delay my input. OTOH we could manage expectations as of course Zebra 3 will start with what appears to be a smaller feature set than Zebra 2 (which has had many modules added over the years).

(like, we do not have a final feature set of FM oscillators yet, and thus we might not initially show or release Zebra 3 with FMOs)

Though it does take a bit to set up and time to manage, I strongly recommend starting a Discord community server. Peter and his small team have done a great job with "Dawesome Village" on Discord, which I think is a perfect example of how the platform can be used to interact with your community, notify the beta team with limited access threads, all kinds of really useful things. And if you want to manage expectations based on community feedback, I think it's a really good place for that too.

[eclipse_soundlab]

I'm currently weighing the pros and cons of starting a Z3 development blog with screenshots and little videos about the new concepts in it. We're bit afraid of how much engagement this might require from my side, and thus possibly delay my input. OTOH we could manage expectations as of course Zebra 3 will start with what appears to be a smaller feature set than Zebra 2 (which has had many modules added over the years).

(like, we do not have a final feature set of FM oscillators yet, and thus we might not initially show or release Zebra 3 with FMOs)

I personally don't need FM, comb filters, resonators at start to top other synths.
4xOSC from zebrallete3, filters and 4xMSEG in zebra 3 is enough to be far superior then zebra 2, serum or pigments.

[robisme]

Still the comb filter please

[Shiek927]

I'm currently weighing the pros and cons of starting a Z3 development blog with screenshots and little videos about the new concepts in it. We're bit afraid of how much engagement this might require from my side, and thus possibly delay my input. OTOH we could manage expectations as of course Zebra 3 will start with what appears to be a smaller feature set than Zebra 2 (which has had many modules added over the years).

(like, we do not have a final feature set of FM oscillators yet, and thus we might not initially show or release Zebra 3 with FMOs)

I think this is fair! Zebra3 is going to be the new flagship that will be supported for many, many, years. I'm sure the u-he community, Hans Zimmer, and others will have request features for years to come. I think it's okay for Zebra3 to launch without as many modules as Z2 since it took years for it to get to that place anyway and it's only a question of 'when' and not 'if'.

I think simply getting Z3 out the door is most important and, after that, everything will be a lot easier.

[eclipse_soundlab]

Hans Zimmer,

32 resonators.

[Shiek927]

Hans Zimmer,

32 resonators.

At least!