Your update system is clunky

[noiseresearch]

/* whitenoise */

[noiseresearch]

/* whitenoise */

[david.beholder]

It's not all that easy. Version numbers represent a certain feature set that's included at a certain time. Revision numbers represent the build history. A plug-in version can be built several times with slight changes (usually bug fixes).

Captain Obvious: Control Version System you use could have two tags version and revision. When code is submitted into branch revision is incremented, when software is being released release tags is set manually. Versions and tags are standard features of P4 and Git 99% of market.

I also think since U-he has similar looking interfaces in might make sense to put revision and version in the same spot in every plugin.

[Schrödinger's Cat]

Mini rant;

I can't find anywhere on your site that lists the latest version numbers.

I can't find anywhere on the site to download updates.

I didn't receive any emails to inform me there were updates available (the only reason I knew my current version was out of date is because a soundset I bought says it is)

The end.

On Windows, there are community maintained chocolatey packages available for u-he installers, meaning you get automatic updates and silent installation routines: https://chocolatey.org/packages?q=u-he

For the package managers on macOS and Linux, there are no u-he packages to my knowledge.

[blakflag]

I think the idea of a product manager is a good one. It doesn't have to be much more than a unified version comparer, installer downloader and install preference setter, and it doesn't have to be designed nice or beta tested to death. At this point U-He products are the longest part of my DAW reinstall process, since I have so damn many of them to install.

I wouldn't say their current process is clunky.. just there's so many betas floating around that it gets confusing what's what. If anything I think it's the forum layout and beta notice board that needs restructuring.