u-he update of almost everything August 2021

[BBFG#]

Is there a Dark Zebra update?

[gondii]

Awesome! Can't wait for Uhbik 2.0 to be out next.

A lot of dev work left there (gotta somehow make new algorithms surround capable and stuff), but the redesign of MFM2 is almost ready, so this will probably come up shortly (might even be called MFM3 because behind closed doors we also added some fun stuff over the years).

Oh right, forgot about MFM2/3. That's a good one to look forward to as well. Personally I'm in no rush, just nice to see that things are progressing with so much exciting stuff on the horizon!!

[beely]

Is there a Dark Zebra update?

From the thread linked to in Urs' op above:

For The Dark Zebra (ZebraHZ), as always, please request a download link from here:

https://u-he.com/my-licenses/

[Biome_Digital]

dp

[Biome_Digital]

I can't find any modern tags in Diva and Repro, they seem to be the same???

[Viktor [TUC]]

Hi Biome_Digital, they've been "modernized" in the sense that they've been adjusted to reflect the current set that we also use in Hive 2 and Zebra 2. They're not 100% different but a few were replaced or renamed and other have been added that we feel were sorely missing. They're now much more consistent with what we use in all our other synths.

Viktrr
u-he team

[Urs]

I can't find any modern tags in Diva and Repro, they seem to be the same???

This might refer to NKS maybe, where tags have changed. I do recall though that a lot of effort went into updating the tags to our latest standards set in Zebra and Hive.

[Ploki]

I wish ZebraCM was loadable as "Easy mode" to the big Zebra, kinda like presswerk easy modes

[beely]

Congrats on getting this update out - sounds like it was a helluva lot of work, which once again you're aren't charging anyone for...

Still, hopefully it's getting you out of a whole bunch of tech debt which will lighten up the load going forward and you can get back to doing the stuff you enjoy the most - working on cool new stuff that excited audio nerds will throw money at you for..!

[Funkybot's Evil Twin]

Even Protoverb got an update! Very cool!

Some nice presets in the browser now too.

[e-crooner]

Out of curiosity, is it a lot of work to update all those products for all those platforms and formats? Or is the process automated once you have updated one format?

[Urs]

hopefully it's getting you out of a whole bunch of tech debt

No worries, we got rid of a lot of leftover backlog.

[Urs]

Out of curiosity, is it a lot of work to update all those products for all those platforms and formats? Or is the process automated once you have updated one format?

We have a highly automated workflow. But even with automated testing, this needs an incredibly amount of human interaction and "massage" to make things rock solid. Hence, the platform support itself is really almost a minor issue. The bigger issue is to catch all uncertainty and circumstance.

For example, it was sheer coincidence that we found out that closing and reopening a project in a certain host in a certain way could lead to corrupted audio. It was easily fixed, but it was a non-trivial find, and it took several days to really get to the bottom of it.

Likewise, a certain project in a certain host could "explode" with a plug-in of ours, but after days of testing we could make it explode without any of our plug-ins. This isn't our fault, clearly, but it's an example of an uncertainly that may take days or weeks to look into.

That said, releasing updates for such a large number of different projects is a complex task. We need to find a way to make changes to plug-in formats, operating systems and our codebase independent of each other. Synching these has become impossible as the example of AAX shows. If we always need to get all of these factors in perfect shape at the same time, we'll spend time only on synching these issues rather than moving forward.

[Bombadil]

U-He ist der Hammer!

[e-crooner]

Out of curiosity, is it a lot of work to update all those products for all those platforms and formats? Or is the process automated once you have updated one format?

We have a highly automated workflow. But even with automated testing, this needs an incredibly amount of human interaction and "massage" to make things rock solid. Hence, the platform support itself is really almost a minor issue. The bigger issue is to catch all uncertainty and circumstance.

For example, it was sheer coincidence that we found out that closing and reopening a project in a certain host in a certain way could lead to corrupted audio. It was easily fixed, but it was a non-trivial find, and it took several days to really get to the bottom of it.

Likewise, a certain project in a certain host could "explode" with a plug-in of ours, but after days of testing we could make it explode without any of our plug-ins. This isn't our fault, clearly, but it's an example of an uncertainly that may take days or weeks to look into.

That said, releasing updates for such a large number of different projects is a complex task. We need to find a way to make changes to plug-in formats, operating systems and our codebase independent of each other. Synching these has become impossible as the example of AAX shows. If we always need to get all of these factors in perfect shape at the same time, we'll spend time only on synching these issues rather than moving forward.

Interesting And dangerous, the 'exploding' part I mean
So, you basically need to have all major hosts and operating systems, or resort to external testers.

U-he is bigger, but I suppose for a one-man company like TAL keeping his 12 plugins updated must be quite a challenge...