HN user

_Gyan_

642 karma

https://www.gyan.dev

Posts5
Comments70
View on HN

libav is a part of FFmpeg, and the heart of it. But FFmpeg isn't just a skeleton. Most decoders + protocols + demuxers / muxsers + filters + scaler + resampler are native components.

The most well-known 3rd party libs provide a few (albeit commonly used) video encoders. Of course, having interfaces for these external libs is what allows media operations to be consolidated into a single process workflow. As standalone tools, x264/x265 would be more cumbersome to integrate into a pipeline.

API/ABI is meant to be preserved within a major version, but not across. The deprecation period is typically two years, but deletion is usually much later.

Do you have examples to the contrary from the past few years?

For a few years, the default aac coder has been fast. But the twoloop coder is better but slower, and was made default in May 2021. Add `-aac_coder twoloop` (in older builds) and recheck.

With ffmpeg, use the below command to calculate maximum timestamps

    ffmpeg -i INPUT -map 0:v -map 0:a -enc_time_base -1 -c copy -f null -
Note the time= value at the end of the process.
FFmpeg to WebRTC 5 years ago

For `-f h264`, `-bsf:v h264_mp4toannexb` is not needed. It will be automatically inserted as needed, with ffmpeg 4.0 or later.

For latency, specify a short GOP size, e.g. `-g 50`

Don't think that's the main reason. Hollywood has no compunction or lack of skill to embellish or dramatize a mundane life if they need to.

I suspect Bach's place at the top is received rather than recognized, which is not to say he doesn't deserve it. His skill lays in counterpoint and other facets of harmony. His music has structural elegance and ornamental beauty, not the full orchestral rabble rousing of Beethoven or delicate pianism of Chopin. Not exactly directly translatable to a poster or trailer.

FFmpeg Cheat Sheet 5 years ago

It hasn't, since ffmpeg's inception. It's very unlikely - it would require that ffmpeg verify codec compatibility with the output muxer. Not all muxers have registered a codec tags list , so that can't happen.

The primary endpoint is symptomatic infection, not any infection per se. And it's a bit of a kludge, as all the Phase III protocols I've read define symptomatic infection as X no. of symptoms for Y+ no. of days i.e. there are people with fewer symptoms who aren't counted (or even tested to check for infection).

The efficacy is the 1-relative risk of the primary endpoint.

From

Association between living with children and outcomes from covid-19: OpenSAFELY cohort study of 12 million adults in England

https://www.bmj.com/content/372/bmj.n628

"Conclusions In contrast to wave 1, evidence existed of increased risk of reported SARS-CoV-2 infection and covid-19 outcomes among adults living with children during wave 2. However, this did not translate into a materially increased risk of covid-19 mortality, and absolute increases in risk were small."

"Living with children aged 0-11 was associated with reduced risk of death from both covid-19 and non-covid-19 causes in both waves;"

The parameters being matched would be those that maintain decoder config. Usually, bitrate/quantizer values don't come into that.

I provide Windows builds of ffmpeg, linked via http://ffmpeg.org/download.html. The site is entirely static, no user data is collected or stored.

Starting in late October, lasting for around a month, users would get the dreaded red page upon visiting the site at https://www.gyan.dev/ffmpeg/builds/

Search Console would show a couple of files as 'install malicious or unwanted software'. Never mind that all files are plain archives (7z,ZIP) with no installers or even self-extraction, containing CLI apps. These file URLs when scanned via Virustotal (Google-owned) would be flagged by Google Safe-browsing and no other engine. Weird thing is, the same files mirrored at Github would be detected as clean. A review request at SC would get rid of the warning temporarily only to return after a day or two.

I found no support email so I opened a thread at Google Webmaster community (now called Search Central community). But there was no help and none of the regulars seem to be Google employees. Finally, I found an email through Mozilla's page on their use of Google's Safe Browsing blacklists at https://support.mozilla.org/en-US/kb/how-does-phishing-and-m... which leads to https://safebrowsing.google.com/safebrowsing/report_error/?t.... This page's title is 'Report Incorrect Forgery Alert' which would indicate a different purpose but I managed to get hold of human attention. After 10 days or so, the warnings disappeared. Till date, I don't know what triggered the warnings in the first place, and so how to prevent a recurrence.