> Non-commercial use only. You agree that you will not use our Services for any commercial or business purposes and we and our Providers have no liability to you for any loss of profit, loss of business, business interruption, or loss of business opportunity.
Also, let's not forget that the majority of devices still don't have AV1 hardware decoding support. For example, Apple only recently (2023) added support with iPhone 15 Pro and M3 Macs.
> For example, Apple only recently (2023) added support [for AV1].
Apple has been actively obstructing open video formats for a long long time—Apple is the reason there isn’t a baseline format for <video> in the HTML5 spec, for instance. (Or at least there wasn’t when the spec was still a well-defined document with a version number; I see no merit in keeping track of the “living” one.) Incidentally, Apple is a member of MPEG-LA and claims to hold numerous patents covering both AVC and HEVC.
At this point, whatever harms befall Apple’s users due to lack of Apple’s lack of format support are entirely Apple’s fault.
The claims made by Dolby that some H.265 patent claims that are formulated very vaguely also apply to AV1 are probably bogus.
Like many other such frivolous patent lawsuits, Dolby hopes to either scare the other company into making a deal in order to avoid bigger legal expenses, or to establish a legal precedent if their cunning lawyers can convince a technically incompetent jury that the H.265 patents are applicable to AV1.
This is the kind of trial that should have never been decided by a normal jury, but only by a panel of neutral experts in this field.
Is a panel of 'neutral' experts even possible to field in this area? I feel like anyone with sufficiently in depth knowledge of both the AV1 and HEVC specs has almost certainly derived a big paycheck for years from stakeholders on one side or the other of these lawsuits.
I'm no expert, but Google having designed AV1, I can certainly imagine a world where the codec infringes upon HEVC just enough that the lawsuit fees would come out in the wash.
You are right about the danger of non-neutral experts, but there still is an essential difference between a group of experts and a jury.
The experts may be biased, but when they open the mouth and try to argue their position their bias becomes obvious for the other experts and it can be contradicted with logical arguments.
Unless all the experts work for an interested party, it would be very difficult to impose an incorrect verdict, because it is impossible to argue in its favor without the mistakes in the argument being immediately exposed by an interlocutor.
On the other hand, with a standard jury most people will be unable to see what is wrong in the arguments presented to them and they will not be able to distinguish truth from lies in such technical subjects.
The US elections and the elections in many other countries are an eloquent proof of the capacity of average people for distinguishing truth from lies concerning much simpler facts than the details of video compression patents. Expecting a jury to choose the right verdict in such a trial seems too optimistic.
What I don't understand is why the AV1 pool isn't activating their MAD clause.
Part of the idea with AV1 was that with the constituents also holding such a massive warchest of patents (plus big tech being richer than god), they would countersue and demolish anyone that tries to bully AV1 users. Which would act like deterrence.
Where is all that might? Was it all just saber rattling, and are they basically going to let the AVC / HEVC patent holders make a fool out of them?
As a side note this isn't always superior - recently discovered my desktop uses way more power with hardware decode than software. Counterintuitive but issue isn't per pixel efficiency but that it keeps the GPU in a higher power state
There is a recent one, which shows that the weight was generally stable after 1 year of discontinuation of GLP-1.
> In this cohort study of adults with overweight or obesity who initiated treatment with injectable semaglutide or tirzepatide and discontinued the index medication between 3 and 12 months after initiation, 19.6% restarted the index medication and 35.2% received an alternative treatment in the year after initial treatment discontinuation. The average weight change 1 year after index medication discontinuation was relatively small; however, there was considerable individual-level variability.
Thanks for sharing. Note that the data quality from this study is quite low because 54.8% of the cohort eventually restarted their medication or transitioned to an alternative therapy (mostly a different weight loss medication).
I don't know why a study that focuses on discontinuation didn't split the groups that restarted or transitioned against the group that actually just stopped.
> Water, Yellow Pea Protein*, Avocado Oil, Natural Flavors, Brown Rice Protein, Red Lentil Protein, 2% or less of Methylcellulose, Potato Starch, Pea Starch, Potassium Lactate (to preserve freshness), Faba Bean Protein, Apple Extract, Pomegranate Concentrate, Potassium Salt, Spice, Vinegar, Vegetable Juice Color (with Beet).
If 95% of what app does is calling a DB, then the bottleneck is in the DB, not with the PHP.
You can use persistent DB connections, and app server such as FrankenPHP to persist state between requests, but that still wouldn't help if DB is the bottleneck.
Depending on what you are doing, the above is not necessarily bad.. often much better than an SQL that locks an entire table (potentially blocking the whole DB, if this is one of the key tables).
Pricing link is the second one in the top menu, and it shows all prices in a straightforward way.
reply