Developing for a Creamware dsp card requires you to have a computer (obviously), then buy a Creamware dsp card and manage to work out some terms with Creamware to get the full Development kit.
Developing for VST/VSTi requires (a computer again and) and the SDK which is a free download from
http://www.steinberg.net/Steinberg/Deve ... angue_ID=7 .
It is true that the coding environment needed for VST/VSTi on Win/Mac isn't typically free (tho there are some options) but is probably less expensive than ScopeDP. It is definately more flexible in *general* terms to a programmer than a dsp audio card and creamware's ScopeDP in terms of an investment. Tack onto that the fact that the Creamware dsp card userbase is a much smaller market than the 'VST/VSTi' (or AU) market so its essentially a niche market within the overall audio market.
I can certainly understand why Creamware would offer copy protection as an incentive to its developers (and to itself) to believe that their market can remain a niche market and still be profitable. The idea that a creation of labor could wind up readily available to someone who just pays Creamware for their card and then heads over to Soulseek, Kazaa or heaven forbid a BitTorrent link to fill out their plugins list isn't very comforting I'm sure.
It is understandable that from a casual user's perspective draconian copy protection measures often get in the way. Seemingly the user who legally purchased the program is in some way being punished and forced to deal with the copy protection, while 'warez' users use the software without strict copy protection and hence don't suffer from its mechanisms.
But whats the solution? USB dongle? A complicated online registration system tied to your system id? (Ok we have that). Most Dongled devices not only don't offer free updates they also don't typically open the dongle to 3rd parties for copy protection. They only protect the parent application (and often other products from the same company.) Imagine if Steinberg/Emagic/Cakewalk had to be the arbiter of every VST/VSTi or AU activation and transfer. Want to bet they would leap for joy at the thought of the KVR userbase demanding that a free massive online database be created to facilitate the moving of 'used' plugins *entirely at the expense of Steinberg/Emagic/Cakewalk?
I'm sure we all know how well a simple serial number would work.
Don't despair however. I haven't heard Creamware mention that you can only 'reregister' a certain number of times (although there may be a hardware limitation here due to burning the code). Most other systems that I know of that use hardware id's base the id off your system and limit the number of 'transfers' that you can do to system changes. Of course most of these are also immediately cracked.
round & round & round.
<font size=-1>[ This Message was edited by: valis on 2004-05-14 09:56 ]</font>