U-he Copy Protection/Licensing System Discussion

[Teksonik]

After reading this is in a thread about another subject:

As I said initially: We are changing our licensing system. So there's opportunity to discuss things, and constructive ideas are very welcome.

I thought it would be better to bring the discussion here. Copy Protection is a very contentious subject so let's keep it civilized. Let's discuss not argue.

My personal feelings are....I don't have a problem with Challenge/Response but I know some people hate it.

As long as the system does not require the installation of third party malware like iLok or CodeMeter (I doubt it will) then I have no problem. Requiring a Dongle would cause me to launch all my nuclear warheads at U-he headquarters but again I doubt a dongle is an option on the table.

Whatever best protects U-he's interests while being as unintrusive to the end user as possible gets my vote.

U-he has always had one of the most user friendly CP methods in the business and I have faith that won't change at least great deal.

[Funkybot's Evil Twin]

I'm fine with the current approach, but I don't know why U-he wants to change in the first place, so I'm open to whatever. I'm sure they'll come up with something good.

[pdxindy]

I like it how it currently is... but I have no idea what the change may be so have no comment on that.

[AnX]

I'll put this here too then....

Some synths have a 'back' or 'splash screen' or something similar... could the personal info not be put on that? So it's only visible when you click to view that part?

...and leave the legal eagles to discuss what right or wrong

[Urs]

It is going to be a keyfile. The keyfile stores the license holder's (chosen) name and email address, plus all serial numbers, the date of issue and a few watermarks to verify the legitimacy of the keyfile itself.

The format of the keyfile will be PNG, and when opened in a picture viewer, it'll look like a credit card, displaying the above name/email/date and a list of all the licensed products.

It's elegant. It's simple. It will look pretty.

(we're inspired by Plogue on this, who have been using "license cards" for years)

[EvilDragon]

Aha, so pretty much how Plogue does it. Really nice IMO.

[elxsound]

NFT license card FTW!

[Funkybot's Evil Twin]

I'm good with that!

[Urs]

Aha, so pretty much how Plogue does it. Really nice IMO.

Yes. We're restricting the info to name/email tho and instead of the collectible vibe (which I really like) we do an all-in-one for practical reasons.

[Kr3eM]

It is going to be a keyfile. The keyfile stores the license holder's (chosen) name and email address, plus all serial numbers, the date of issue and a few watermarks to verify the legitimacy of the keyfile itself.

The format of the keyfile will be PNG, and when opened in a picture viewer, it'll look like a credit card, displaying the above name/email/date and a list of all the licensed products.

It's elegant. It's simple. It will look pretty.

(we're inspired by Plogue on this, who have been using "license cards" for years)

I assume this does not impact the functionality like let's say portablility?

[EvilDragon]

Ofc not.

[dune_rave]

hm, this is interesting.

[Biscotto]

[FrettedSynth]

It is going to be a keyfile.

Thank you! was kind of afraid when I first saw this post.
Gave up on anything that requires online authorization years ago.
Which was one reason I tried Uhe plugins, Yeah now I'm hooked.

[Kr3eM]

Ofc not.

Well I had to ask, I have seen some bending on definitions regarding this subject the last decade....
developers state Serial as authorization while it's actually a C/R or a online activation or a combination of whatnot....

Not that I thought Urs would do something like that but I have been wrong before...

As long as the functionality stays the same for me as a user I have no problem with any changes... it can be a wav file that contains a unique fart sound for I all I care...