There is such a thing as free. People who write Free software are doing R&D without any plans for monetization.
Codecs are software. Software has about zero manufacturing or distribution cost. Development does take effort. Very much effort for modern CODECs, but it's one thing to cover development costs and another to collect rent from - err monetize - a "standard".
AV1 is supported by Google, sure, but also companies like Netflix and Apple. If Google's business model for YouTube was to charge a subscription fee to everyone like Netflix, wouldn't they still have the same incentive to develop AV1?
This is really commoditize your complement. Which works regardless of the revenue source in the primary market.
I’m saying that if your business model is free software, it needs to be monetized some other way. Advertising is one way, which has become common. How that happens needs to be part of the public interest analysis.
Mutual self-interest is a good, solid business model. JPEG was developed long ago by a bunch of companies who needed a good, standard image format. Now AV1 is being developed by a bunch of companies who want to use less bandwidth for the video and will save truckloads of money not paying patent license fees. Not to mention standarization, economies of scale, and interoperability benefits. A company simply not having to pay the fees for something proprietary can be all the funding needed to support a free software version.
Free software development generally only needs about 1/10th as much monetization to begin with. You may get to start with the works of other people; others using your work builds the user base quickly without paying to advertise and sell your product; you'll get a lot of free testing/debugging/code feedback; etc.
Rather than monetize the software, fund its creators. They, along with everyone else, get great use value out of the software and they are empowered to live, live, do, play, and generally be.
They may also make money using the software to do whatever it is other people will pay for. That is the case for one project I contribute to on Pateron. Use value is real high and a community of users is funding the developer.
I am supporting a couple of other projects that way right now. I've got good developers on Patreon, and I'm happy to know that they're developing the software that I value. That's the end of it.
I'm also happy to know that software is out there for general use too. I don't really care if everyone's paying. Would I do care about is the developers are getting paid.
I think more developers should communicate where they are at in terms of support, and I think a whole lot more of us need to put small amounts of money toward making sure those developers are okay.
Xiph.Org's 2011's letter to the FTC directly discussions "industry standard" unethical conduct like effectively concealing what would later be claimed to be a patent encumbrance from a standard setting organization, exactly as Nokia did in this case.
https://www.xiph.org/press/2011/ftc/ftc-comments-20110614.pd...
Developing the technology that has become the standard takes a lot of resources; you have spent them.
Standard bodies usually compare several technologies and pick one; you have risked that your development effort would not make it into the standard, and would be a dead end.
It looks a bit like bidding for a military contract. Did General Dynamics receive unearned windfall when USAF accepted their bid for a fighter jet, and kept paying for each F-16 they ordered? Surely the price of each included a part of the R&D costs.
Planting a flag next to General Dynamics driveway so that you can collect a percentage off every aircraft that goes buy is rent seeking.
If patent holders were required to specifically identify and price the technology they encumber standards with such that the standards setters can pick and choose which were worth it-- that would be a different matter, but it isn't how it works. Note that I pointed out that the specific patented technologies often have negligible or even negative benefits.
Additionally, the companies pay the salaries of engineers and researchers who did the work. If your point is that engineers and researchers don’t get paid enough for the value they create, you’re talking about a completely distinct issue that has more to do with the structure of corporations generally.
Maybe people at the top get too much of the compensation, but what about the network technicians and IT departments that provided a functional work environment? What about building maintenance? What is harder, the research involved, or learning & navigating knowledge of the legal and financial mechanisms necessary for large complex organizations with a thousand interlinking pieces to other organizations? Who should get more compensation when the absence of any one component, not just the researchers, might have caused failure?
I want to be clear though: I'm not defending astronomical compensation of the very few at the top. I'm saying that if there's inequity here, it doesn't begin or end with the engineers and researchers. Its victims are the sum total of all the people, all of the functions, without which the system fails.
Look what happened with web standards. Developing and testing new web standards requires building reference implementations in browsers. Browsers are expensive to develop, so the standards are controlled by a handful of companies like Google and Apple. But the standards are free to implement. Is that better for the public? Maybe, but the public interest analysis is more complex than “free to implement.”
There is no such thing as “free.” R&D will be monetized somehow—the question is how. Different monetization approaches have different and non-obvious impacts on the public interest. Consider for example the shift away from paying for software to giving it away “free.” You used to pay Symbian $5-10 bucks per phone for an OS. Android you can get for free. But Symbian didn’t build an advertising platform into the core of each phone. Monetization matters.