_Gyan_

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.

> You already provided better lines for some of the options than what their docs state

I wrote the docs section you refer to :)

They are meant to be narrow and to the point, not didactic, not least because the codepath leading up to an option and following that option depend on internal evaluations and other options.

> why would anyone want to do that?

Because the input has weird or unreliable DTS. One would have to check code history to see why an option was initially added. Many of ffmpeg options are there to deal with edge cases or weird inputs.

> -fflags +genpts+igndts -use_wallclock_as_timestamps 1

In theory, igndts is unsetting wallclock dts set by the last option. genpts should have no effect, again due to the third option.

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`

> literally the only difference is the contents of the "ftyp" box, every other byte is identical.

Not quite. There are some boxes acceptable in one but not the other. Strings inside MOOV are length-prefixed in MOV but null-terminated in ISOBMFF. There are a variety of differences like that.

The set of codecs allowed, also differs between the two.

Except for many primate cities: https://en.wikipedia.org/wiki/Primate_city#List

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.

See a video with similar setup of a rocket launch constructed out of a timelapse photo sequence: https://www.youtube.com/watch?v=aJy1u-N3NY0

A profitable strategy only if it attracts a lot more prey than predators.

The intro of the actual paper* is ambivalent, rather than what the post title asserts.

"We critically examine relevant findings and argue that there is no clear evidence for detrimental lasting effects of digital technology on cognitive abilities."

*https://www.nature.com/articles/s41562-021-01162-0

It's a shame that Graeme Garden and Barry Cryer appear to have retired.

FFmpeg already has registered channels there. Will update website within a day.

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.

It's not the first tracks. Read http://ffmpeg.org/ffmpeg.html#Stream-selection

The first one will re-encode.

There have been 2000 fixes related to fuzzer issues so far, averaging 400 fixes in recent years. Almost all of them are taken care of by Michael.

I don't see FFmpeg on there.

See https://link.springer.com/article/10.1007/s11214-020-00765-9

"The core EDL data processing and compression engine is powered by FFMPEG (ffmpeg.org)."

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.

Did you see https://doublecmd.sourceforge.io/gallery/?

Can anyone who's used both, compare it with Directory Opus?

UK schools were open most of the autumn/fall term. They have been closed since mid-December and reopened earlier this month.

https://en.wikipedia.org/wiki/Impact_of_the_COVID-19_pandemi...

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 Indian govt. seems to agree.

https://www.indiatoday.in/coronavirus-outbreak/story/night-c...

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

Yes, much of the demuxing and decoding relies on libav, but there are other demuxers and decoders in VLC as well. The library for handling DVD/BD playback is also distinct.

Managing playback (flow, state, buffering..etc) itself is not a facility of libav so that is managed by the app.