|
|
Subscribe / Log in / New account

The disabling of hardware codecs in community distributions

The disabling of hardware codecs in community distributions

Posted Oct 14, 2022 18:06 UTC (Fri) by bferrell (subscriber, #624)
In reply to: The disabling of hardware codecs in community distributions by IanKelling
Parent article: The disabling of hardware codecs in community distributions

I knew a developer in the days on the Apple II (not the IIe) who celebrated the legal case decision that allowed software patents.

Up until then, patents could only be granted to physical inventions. "Patented software allows me to get paid for my work for a LONG time after I write it and only I can get paid for something unique". The mouse hadn't extended copyright ad nauseam and had no place to root in the world of software.

While the intent was the individuals would be compensated better, the effect was that any kind of compensation can be turned into a property to be sold and traded.

Now everyone is trying for "do it once and get paid forever" (or a very long time).

An analogy would be a carpenter that builds a house and anytime in the future that it's sold, he get's a royalty of that down stream sale too (I just HAD to say THAT out loud didn't I? Watch and see if it doesn't get tried... Soon)

We're already seeing Tesla pulling silly nonsense on resales of cars with software options that they pull at will and/or charge subsequent buyer for again and again. Books, movies and music... All the same. And the "aware" citizens, they become "pirates" and scofflaws.

Solutions?


to post comments

The disabling of hardware codecs in community distributions

Posted Oct 14, 2022 23:08 UTC (Fri) by developer122 (guest, #152928) [Link] (2 responses)

Thankfully, with codecs it seems this is one of the *very few* areas where voting in the market is working. We're seeing a fairly rapid transition (everywhere that matters) to AV1 to replace these codecs, expressly because of all the fees.

As someone else pointed out (https://lwn.net/Articles/910919/) there's also work underway to kick out the licencing schemes on multichannel audio.

For the larger problem of software patents? Either come up with a way to poison the well or call your congressman, now that it's long-settled law. It's become a similar issue to ludicrously long copyright terms.

The disabling of hardware codecs in community distributions

Posted Oct 15, 2022 3:03 UTC (Sat) by linuxrocks123 (subscriber, #34648) [Link] (1 responses)

In the US, Alice v. CLS Bank has dealt a death blow to software patents. We just have to make sure they stay dead :)

The disabling of hardware codecs in community distributions

Posted Oct 20, 2022 12:05 UTC (Thu) by esemwy (guest, #83963) [Link]

Well, at least the dumb ones that go, “Do the same thing that people have done for a long time but use a computer instead.”

The disabling of hardware codecs in community distributions

Posted Oct 15, 2022 5:38 UTC (Sat) by scientes (guest, #83068) [Link] (2 responses)

I think Bender from Futurama, who runs on the MOS-6502 like the Apple ][, should celebrate. A world of software patents is a world of the robots, for the robots, and by the robots.

The disabling of hardware codecs in community distributions

Posted Oct 15, 2022 9:13 UTC (Sat) by nim-nim (subscriber, #34454) [Link] (1 responses)

Naw, it’s world of the lawyers, for the lawyers, and by the lawyers.

Let’s people decide by themselves which one is worse :).

The disabling of hardware codecs in community distributions

Posted Oct 20, 2022 11:39 UTC (Thu) by philipstorry (subscriber, #45926) [Link]

I admire your optimism.

But it's actually a world of robot lawyers, for robot lawyers, by robot lawyers.

In eons to come, alien probes will visit what was once our world. And their first interaction will be a query about which licenses they hold, along with a demand for an audit to ensure compliance.

The disabling of hardware codecs in community distributions

Posted Oct 15, 2022 5:57 UTC (Sat) by mattdm (subscriber, #18) [Link] (3 responses)

It's worse: the carpenter builds a house, and then gets royalties from anyone who builds any other house in the future if it uses any techniques like "framing" or "joists" or "doors".

But, analogies are dangerous, and this one gets weird because we get into things that ... maybe are okay with patents as they stand. If you design a new construction element that actually is innovative, 20 years might be just fine. Houses last a long time. But with software, especially in the case of codecs as things are progressing today, that basically locks up the entire useful lifetime of the idea.

I think the most reasonable improvements given that we're unlikely to actually get rid of software patents are:

1. Shorten the lifetime. 7 years, maybe.
2. Accidental re-invention should not be infringement, but rather immediate grounds for dismissal of the patent as a natural extension of existing knowledge

And bonus:

OMG do not allow design patents to apply to software.

Beyond or in addition to these:

* If your invention was created with government funding, it should be available for open source projects and academic use without license fees or other obligations. (Yes, I'm biased on this one.)
* Some way in which patented techniques could be used in further inventions without waiting out the original. The current approach, to put it mildly, does not encourage collaboration and building on each other's ideas -- it encourages extending patents with little tweaks that add to the original's effective life. I have no idea how to accomplish this realistically. Maybe simply shortened protection is the best that can be done.
* Perhaps some areas which have other natural drivers for invention just plain shouldn't be patentable. For example, compression will probably always be relevant even as the specific requirements change. Does anyone really think better audio and video codecs wouldn't have been invented if there weren't patents?

The disabling of hardware codecs in community distributions

Posted Oct 15, 2022 6:08 UTC (Sat) by mattdm (subscriber, #18) [Link]

And here I'm just making up something that I'm sure people better-qualified than me probably have covered, but:
any technology that becomes an international standard (ISO, IEEE, ITU, whatever) should

1. after some public period, be legally closed to any further "oh wait we have a patent that covers that!" claims.
2. therefore, have an official, reliable, world-wide "patent is done, this is for the world" date

This kind of goes hand-in-hand with some of the other things I listed -- the "no-accidental-reinvention" part could help make this reasonably possible, and from the other direction, the standard itself could cover open source project licensing and so on.

The disabling of hardware codecs in community distributions

Posted Oct 20, 2022 13:02 UTC (Thu) by philipstorry (subscriber, #45926) [Link]

I certainly think that the terms for software patents are too long.

My preference is for no software patents, but if we must have them then a much shorter period is required.

Our legislators seem to have forgotten that 20 years was picked as a compromise. In a world of physical manufacturing it was deemed roughly long enough for someone to acquire financing, arrange a location, set up tooling and begin production whilst still giving a period of monopoly on the sale of the invention. Effectively it gave you a head start over the competition.

By the late 90s software was at a point where it was already moving far faster than those 20 years were meant to deal with. Software doesn't require anywhere near as much investment in manufacturing and distribution logistics - a box with floppies or CDs, some booklets and a manual were not that difficult to produce. Many companies were already giving up on that, and by the mid-2000s a lot of software was simply downloaded.

These days we look back on the 1980s ring binders and generous manuals as a luxury of ancient times. If we're lucky then the software we buy has a PDF manual that consists mostly of screenshots. If we're exceptionally lucky then the screenshots in it are for the version we actually bought.

So we're basically looking at a system that was designed to deal with an initial startup period measured in years, but it's being used for an industry which can measure its startup period for products in days. Sometimes even hours.

It was almost defensible in the days of the GIF patent. But today 20 years is just unfit for purpose. 7 years is a more reasonable compromise, but still a compromise.

The disabling of hardware codecs in community distributions

Posted Oct 22, 2022 0:19 UTC (Sat) by himi (subscriber, #340) [Link]

Late to the party, of course, but the "accidental reinvention invalidates" idea is nice, but impossible to make workable in practise - the standard of evidence that would be required to prove that it really was accidental reinvention would be prohibitive. Particularly given the requirement that patents are published.

In theory that should be captured by the question of novelty, something that the patent examiners should be qualified to judge - the fact that they're /not/ is a separate issue from the legal rules around patents.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds