Poll: What kind of copy protection do you prefer?

Anything about MUSIC but doesn't fit into the forums above.

What is your copy protection scheme of choice

Serial number
55
55%
Keyfile
17
17%
C/R
0
No votes
PACE/iLok
6
6%
eLicenser/Steinberg
4
4%
Waves/Arturia/NI/Props (dev's own system)
1
1%
None of 'em
17
17%
 
Total votes: 100

RELATED
PRODUCTS

Post

When I buy a plugin I like copy protection that:

1. Ensures the developer gets paid for their work
2. Is easy to move from machine to machine
3. Keeps anyone with an Internet connection from getting the plugin for free

iLok is the only copy protection that accomplishes these things.
Bitwig Certified Trainer

Post

In my case iLok (dongle) is 100% effective at ensuring the developer doesn't get paid for their work.

My preferred approach?

Look at Klanghelm

Post

In my case iLok (dongle) is 100% effective at ensuring the developer doesn't get paid for their work
:D :tu:

Serial number or serial file do it for me. As a customer I don't care how much safe or safe is the protection for developer. I just want to download stuff and use it here and now, and whenever I need to.
Blog ------------- YouTube channel
Tricky-Loops wrote: (...)someone like Armin van Buuren who claims to make a track in half an hour and all his songs sound somewhat boring(...)

Post

aciddose wrote:Having both serial and key file as separate options is a bit dumb.

They're the same thing!
Thanks for sharing your insight, I didn't realize that.

Looking at the poll results, it thus become clear that serial/keyfile is a what users so far voting clearly prefer.

Post

lachrimae wrote:Look at Klanghelm
A gentleman's agreement type of copy protection, yeah it is bascially the perfect way to go about it :tu:

I believe in a world of trust and copy protection has got nothing to do with that

http://klanghelm.com/faq.php

Post

I think this isn't much what "I" prefer, but what I am able the work with. From the given options, I think Challenge/Response is by far the worst of all, and I had very bad experiences with it (in some implementations, the fact that you change some unsuspect componentes like the graphics card was enough to force another authorization).

That said, some developers are generous with those (like Native Instruments, IK Multimedia, Arturia) since they eithergive you a fair amount of authorizations, or simply don't seem to impose a limit, as long as you are not making something definitely strange (like authorizing a new system everyday).

Dongle protections are good since they work independente of the system. The com is that, when you have two systems, you have to always keep plugging and unplugging the key, risking damaging the connectors and the keys themselves. I like that method, but would prefer that more companies do what UVI, VSL and AIR do, which is offering the possibility to authorize at least two keys (or more). Just having one key is too reductionist, since usually professionals have at least one desktop and one laptop (sometimes more).

Licenses usually are individual (or should be) therefore, since the individual is using just one system at a time, having more than one key authorized is just a matter of comfort and usability (IMO)
Fernando (FMR)

Post

fmr wrote:I think Challenge/Response is by far the worst of all, and I had very bad experiences with it

That said, some developers are generous with those (like Native Instruments, Arturia) )
I don't think of NI or Arturia as "classic" C/R. As they use their own serial center, I think of them more in terms of soft eLicenser, which again is born from a dongle...

Post

Fish.

Post

currently the worst implementation of C/R is, imo, Cytomic's.

Andy has concocted this new scheme whereby not only do you have the auth limitations you'd normally associate with C/R (though his auth limits are very clearly defined, whereas some other C/R using devs kind of leave it open), but the amount of auths left on your account will carry over to a new owner should you be horrible & evil enough to want to sell your license ... which by the way is no walk in the park, since you'll need to pay Andy 30% of the plugin's value...and can only sell at least 6 months after your last auth.


somehow, he's taken the worst aspects of C/R and license policy ...and wrapped them into one abomination.
And thinks this is a good idea.

luckily I like his plugins, have no plan on selling and - touch wood - have not had any hardware issues that might cause my auth count to dwindle due to setup changges.

but, for a one-man operation, these kind of draconian policies do not fill me with confidence should anything unforeseen happen to him or his company.

Post

DJ Warmonger wrote:
In my case iLok (dongle) is 100% effective at ensuring the developer doesn't get paid for their work
:D :tu:

Serial number or serial file do it for me. As a customer I don't care how much safe or safe is the protection for developer. I just want to download stuff and use it here and now, and whenever I need to.
When developers do their own copy protection and they get ripped off by the pirates, they don't get paid. When good developers don't get paid they do something else to put food on the table.

I would much rather pay for good plugins and keep the quality of the plugins high. Developers can't afford to work for free.

u-he has done a great job of creating copy protection that works without a dongle. Not every developer is as savvy re: copy protection.
Bitwig Certified Trainer

Post

billcarroll wrote:
DJ Warmonger wrote:
In my case iLok (dongle) is 100% effective at ensuring the developer doesn't get paid for their work
:D :tu:

Serial number or serial file do it for me. As a customer I don't care how much safe or safe is the protection for developer. I just want to download stuff and use it here and now, and whenever I need to.
When developers do their own copy protection and they get ripped off by the pirates, they don't get paid. When good developers don't get paid they do something else to put food on the table.

I would much rather pay for good plugins and keep the quality of the plugins high. Developers can't afford to work for free.
This. It's short sighted opting for the least hassling, or no copy protection when it prevents the dev's from making enough money to be able to make top products.

Post

I always thought pirates managed to crack C/R software by figuring out the "formula" the Challenge uses to create the Response code ?

I use a device to create codes every time I log into my online bank account. What makes that code more difficult to "crack" is that the code created is dependent upon the time (of clock) every time I create one to log into the bank account.

Post

When developers do their own copy protection and they get ripped off by the pirates, they don't get paid. When good developers don't get paid they do something else to put food on the table
Most of people who want to crack software will likely suceed anyway. If they don't, they are probably not going to buy this software anyway, so developer won't benefit from it.

Advanced (and complicated) copy protection is trouble mostly for customers. IMO the copy protection should be just a way to tell "hey, this product is not free" and not cause drama and sleepless nights.

Also, copy protection is just another product part that my fail for no benefit. The more complex, the more likely.
Blog ------------- YouTube channel
Tricky-Loops wrote: (...)someone like Armin van Buuren who claims to make a track in half an hour and all his songs sound somewhat boring(...)

Post

billcarroll wrote:When developers do their own copy protection and they get ripped off by the pirates, they don't get paid.
I don't understand why you have to state half-truths in order to get your point across.
It reminds me of statistical spin where only the data that makes a point is shared...

I'll complete your sentence for you:
When developers do their own copy protection and they get ripped off by the pirates, they don't get paid by those pirates, but there are a number of people that reward those devs by purchasing their product specifically because of their licensing policy.

You purchase products that are heavily fortified, thus rewarding devs that choose that licensing scheme.
I purchase products that have minimal protection in order to reward and support those kinds of devs.

Here are a few facts:
Both types of devs get paid.
More of your type of devs will get paid if you can convince people of your philosophy.
More of my type of devs will get paid if I can convince people of my philosophy.
There are no statistics that show which licensing scheme has more effect on income.

Post

DJ Warmonger wrote:a way to tell "hey, this product is not free"
I figure that is what upgrade prices are for :D

Post Reply

Return to “Everything Else (Music related)”