u-he

m-ac · Post by **m-ac** » Thu Sep 24, 2020 3:19 pm

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.

noiseresearch · Post by **noiseresearch** » Thu Sep 24, 2020 3:42 pm

/* whitenoise */

m-ac · Post by **m-ac** » Thu Sep 24, 2020 4:05 pm

Tbh, a lot of my frustration came from initially not being able to view the version numbers of the ones I already had installed. It was only after trying for 15 minutes that I realised you can see the version number after you boot the synth up but before you load a preset. So yeah, add that to the list of things that are a bit too quirky. Also, the fact I couldn't get the repro 5 nks previews to trigger, but again, there was a small line of text on the product page to show me how to do it manually. Never had to do that for an NKS ready synth btw, but whatever.

All that said, repro and diva are still my favourite synths.

noiseresearch · Post by **noiseresearch** » Thu Sep 24, 2020 4:14 pm

/* whitenoise */

the.new.me · Post by **the.new.me** » Fri Sep 25, 2020 4:30 am

Rant about being clumsy yourself and putting blame on to others

Howard · Post by **Howard** » Fri Sep 25, 2020 6:21 am

In Repro and Diva the revision number appears immediately below the data display.

Benutzername · Post by **Benutzername** » Wed Sep 30, 2020 11:46 am

All clumsiness aside, an option to check for new versions on startup would be great. Nothing big, just put an exclamation mark next to the version number and a message to the tool tip.

Funkybot's Evil Twin · Wed Sep 30, 2020 4:10 pm

Howard wrote: Fri Sep 25, 2020 6:21 am In Repro and Diva the revision number appears immediately below the data display.

I'll be honest here: I've been confused more than once between "Diva 1.4.4 Update Released" and "Rev 9709." The website [mostly] uses version numbers, the plugins use Rev numbers. My advice is pick one and stick to it! The only place both appear together is at the bottom of the U-he Diva page under the "Download for Windows" link. Everywhere else, it's one or the other.

For end users: would be much easier if the website only referenced Rev numbers. Or...if the plugin showed the version number.

Urs · Post by **Urs** » Wed Sep 30, 2020 5:18 pm

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).

Some companies add the revision number to the version, e.g. "Zebra2 2.9.1.9709", but that sounds a bit off to me since the revision number does not reset with a new decimal point in the version.

But let's also see how we got here. Originally we only had version numbers, but then it was impossible to give proper support when we released little bug fixes or beta versions. So at some point we simply printed the revision number on the UI, which made it easy for us to see which build someone needed support for. This is how the revision number entered the scene and became somewhat more reliable than version numbers when talking about what's installed anywhere.

Maybe it now sounds like we should switch to revision numbers altogether. But that doesn't sound right to me either. Because version numbers follow a system: The first number depicts major versions aka "upgrades", which usually mean major conceptual changes, often even new plug-ins to be installed in parallel to other version, often paid for upgrades. The second number depicts major feature additions over time, which are usually free expansions based on feature requests or developer ambition. The third number depicts minor improvements, bug fixes and things that don't make it into "major feature news". I don't want to take this kind of nomenclature away because it makes major improvements indistinguishable from minor stuff.

Suggestions for a good compromise are welcome.

Urs · Post by **Urs** » Wed Sep 30, 2020 5:21 pm

Benutzername wrote: Wed Sep 30, 2020 11:46 am All clumsiness aside, an option to check for new versions on startup would be great. Nothing big, just put an exclamation mark next to the version number and a message to the tool tip.

Yeah, this is indeed on our ever growing to do list. There's a bit of reluctance about "calling home" or requirement of an internet connection though. Also, we're thinking slightly bigger in terms of "optional service center" which also includes license management and quick & easy installations. Not sure where this goes.

mabian · Post by **mabian** » Wed Sep 30, 2020 5:27 pm

Urs wrote: Wed Sep 30, 2020 5:18 pm Suggestions for a good compromise are welcome.

Zebra2 2.9.1b9709 or
Zebra2 2.9.1-9709

Where the b9709 (or -9709) is for the build number.
Easy, faily compact, include all the information needed for support and version comparing, convenient in one word...

- Mario

fese · Post by **fese** » Wed Sep 30, 2020 5:38 pm

mabian wrote: Wed Sep 30, 2020 5:27 pm
Urs wrote: Wed Sep 30, 2020 5:18 pm Suggestions for a good compromise are welcome.
Zebra2 2.9.1b9709 or
Zebra2 2.9.1-9709

Where the b9709 (or -9709) is for the build number.
Easy, faily compact, include all the information needed for support and version comparing, convenient in one word...

Well, strictly speaking according to semver.org, the build number should be separated by a "+"-sign.

mabian · Post by **mabian** » Wed Sep 30, 2020 5:42 pm

fese wrote: Wed Sep 30, 2020 5:38 pm
mabian wrote: Wed Sep 30, 2020 5:27 pm
Urs wrote: Wed Sep 30, 2020 5:18 pm Suggestions for a good compromise are welcome.
Zebra2 2.9.1b9709 or
Zebra2 2.9.1-9709

Where the b9709 (or -9709) is for the build number.
Easy, faily compact, include all the information needed for support and version comparing, convenient in one word...

Well, strictly speaking according to semver.org, the build number should be separated by a "+"-sign.

I can stand that, thanks

- Mario

fese · Post by **fese** » Wed Sep 30, 2020 5:51 pm

@Urs, I'm still not sure what the problem with semantic versioning is. To me it makes sense. And if I look through the release notes for the different products on the u-he web site, you pretty much have used it anyway, and it works.

The important part is, whatever versioning scheme one uses, is consistency. Wherever a user could stumble upon a version number (plugin, manual, web site) it should be the same.
A horrible how-not-to-do-it example is something from my line of work, VMware VSphere. In the download portal and the support forms it is some kind of (non-standard, inconsistent) semantic versioning, whereas in in installed products you only see the build number. To match those you need to got to a vmware knowledge base article and search through several long tables of version to build number mapping. Dreadful...

Funkybot's Evil Twin · Wed Sep 30, 2020 7:24 pm

Based on Urs response to my earlier comment, why not...

1. Use version number for the Product
2. Use Rev numbers for updates

For example:

Zebra 2.8 Rev 9709

Which is basically what's already happening. So what would I change? I'd...

1. Put both on the GUI (version 2.8 Rev 9709 on the main screen, maybe add to the Prefs or create an About box - maybe add to the U-he logo dropdown)
2. Show both on the website together (Example: "Zebra 2.8 Rev 9709 Released")

u-he

KVR Audio

Your update system is clunky