
Originariamente scritto da
BetaBoy
Let me just finish my thoughts on the CorePlayer/CoreTunes model vs. our directshow filters registrations.
CP/CT
Please have no doubt that with CorePlayer/CoreTunes we will have server-side authentication and hardware lockin for the user. This is required for many reason including device type, Core Account linking, UPNP/DLNA/SyncML functionality. For more technical side read below...
CoreAVC/DS Filters
Let me explain the system for a possible future CoreAVC that would "tie" the installed copy of CoreAVC to specific hardware. There have been many misconceptions listed here about what this system will do, how it will work, etc.
First off, this system is being instituted for a number of reasons. CoreCodec, as a H.264 patent licensee, has royalties which must be paid, depending on the number of units distributed. These patent licenses have a variety of terms (depends on which patent), which place obligations on CoreCodec. These obligations include (in some cases) security requirements for access control, as well as reporting requirements. Part of the design of the system is to allow us to kill off older versions of the software and issue updates when they become available.
The upcoming system is also designed to be as minimally invasive as possible. Like the current version of CoreAVC, each user will be provided with a custom-built installer. This installer will contain a serial number, just like the current version does. For internet-connected users (most of you, since you have to be online to download and purchase CoreAVC), the installer will take care of everything automatically. For users installing on computers which are not connected to the internet, you will need to (one time) visit a single URL, and enter in a short hardware code.
CoreAVC will generate a hardware hash, which is designed to be very tolerant of hardware changes, but unlikely to work on other machines. An automated system will be set up to allow you to "clear" your account a limited number of times (for moving from one machine to another, or for severe hardware changes). If additional changes need to be authorized, you can simply drop us an email, and one of us will respond within 24 hours.
Although this system is partially designed to combat piracy, it's primary purpose is to (hopefully, still have to get the lawyers involved) allow us to provide free updates to CoreAVC, (rather than having to pay patent royalties on every version). The old copy doesn't get destroyed until the new one is installed (no retroactive deactivation of copies). We're not like starforce - no drivers are installed, and no other programs are affected outside CoreAVC. We don't force updates down your throat, deactivate old copies until new ones are installed, add any services, phone home every run, or run other programs when CoreAVC is not in use. For the vast majority of users, it won't ever be an issue, as they will never see any dialogs, get told they can't do something, or have to even type in a cd-key. As for us building an invasive hardware profile, there simply isn't enough data passed to be an issue. For example, your CD-ROM is assigned a number of 1-7, based on which model you have. Put simply, even if we look at the number for your CD-ROM, you still share the identifier with 1/7 of all the CD-ROM models out there (thousands).
Now enjoy CoreAVC 1.1 and lets get back to the codec ;-)