I noticed inside UXP code two directories in the media containing ffmpeg code: libav and ffvpx, and they go to the different librarys.
libav though has fewer files.
Why two separate ffmpeg
Moderators: trava90, athenian200
Re: Why two separate ffmpeg
Hmm, seems libav is used only for dom\media\webaudio, i moved all stuff into ffvpx, as deleted libav at all.
Re: Why two separate ffmpeg
And as a result you have non-vpx code living in a vpx submodule. Congratulations. I hope you never have to debug this.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Why two separate ffmpeg
quoted from https://github.com/MoonchildProductions ... ME_MOZILLA :Fedor2 wrote:Hmm, seems libav is used only for dom\media\webaudio, i moved all stuff into ffvpx, as deleted libav at all.
Code: Select all
This directory contains files used in gecko builds from libav
(http://libav.org). The current files are from v11.3 of the library.
All source files match their path from the library's source archive.
Currently, we only use the fft portion of the library, and only on x86
based platforms. If this changes, configuration files will most likely
need to be updated.
making it link to mozavcodec.dll is just no good to me, since FFT/rdft routines are stable and small, while mozavcodec.dll is big, that hurts startup time.
Re: Why two separate ffmpeg
This is reasonable. It is left find where else it is used.since FFT/rdft routines are stable and small, while mozavcodec.dll is big, that hurts startup time.