Hey, good morning, everyone, I got 20 minutes to speak about 25 projects, so that's going
to be fast.
I have the unfortunate pleasure of doing a ton of updates of most of the open source teams
who are working too much, and so they don't present themselves.
So my name is JB, I do too many things.
I'm still the president of the Vidalan nonprofit, because no one else wants to deal with legal matters.
I work on a lot of the open source.
We'll see what that software, including VLC, 264, David and so on, maintainer of all the libraries
that no one wants to maintain, we'll talk about that.
And I'm president of several companies, video labs, FF Labs, one called Kiber, and I'll also
now member of the European Open Source Academy, which is great, I have no idea what that
means.
I think it's, I give awards to people, which is cool, right?
Anyway, let's go back a bit, FMP-7.1, which is probably the last one I talked about at
first them, which was probably two years ago, was like the largest FMP release ever,
there were so many new decoders and major ones, right?
A lot of things on Vulcan, a lot of things on VLC and VLC, I am F, and so on.
But also what was more important on the FFMP-7 versions were, everything that was done
by Anton, about the multi-shradding of the CLI, right?
Some of you already heard me talking about that, but this was probably like the largest
modification for normal humans who are using FMP, even if you're using the CLI of FMP,
are you normal?
I don't know.
But still, like so many people, like so much of the community is working, of course, on
the libraries, you may be correct, you may be format and so on, but so many of you try
to use the CLI, or use chatGPT to generate the common line, I know some of you do.
But like the problem was so many companies, including a Marx, bit-moving, all large companies
were, or VMA, right?
There are some of the people, so that's great, to bunch, are using directly like we developed
something about FFMP, because FFMP was, it was basically monosraded, right?
Which means that when you were doing HLS, adaptive streaming, you were waiting for the
lost lowest.
So there was like a huge work from Anton to use strides, right?
Strides are complicated, I bet most of you don't know what strides are, and if you do, I
don't think you do, right?
Yeah, of course, if you do, Anton, you do, but most of you don't.
I don't see that, right?
I think I do, I don't.
But anyway, that was a lot of work that was done on the FFMP.C, and so a lot of companies
now are dropping all their tools that were using on FFMP.
That was in seven.
FFMP H was out in, I think, April, it's a bit less compared to the other ones.
The major work was still on VVC, which is the next generation MPEG codex that no one will
have to use, but get codec engineering maintained and hired, so that's great for them.
But there is the VAPI decoder, which means that if you have a recent card that is going
soon to happen, you might have a accelerated VVC decoding.
There is a support of real video 6 decoder, great, I've never seen any real video 6,
but that's great, right?
Everybody is way more difficult is a FLVV2 or extended FLV.
It's a way that you use the very old FLV and RTMP, and you put every other codex in it,
and multi-audio.
It was a big fight of mine, because I said for years that RTMP and FLVs there for the
next 25 years, and so we need to support more codex and people say, no, we need new things,
and then people have, like, from WebRTC to SRT, to NDI, to whatever, and the thing
is like, RTMP is everywhere, right?
So there is no reason.
So now FLV can, an RTMP can give everyone, and 5.1 audio, only 30 years later, GPXL, it's a very
hot topic, but GPXL is the image format that is going to win for the future, compared
to EVIF and HCIF and so on, because they have the best marketing, are they good
features, but most of these have the best marketing, EVP decoding, FPV decoding, it's time
of Samsung decoder for to compare with ProRes, basically.
And Whisper filter, amazing, in FLV-8, but probably the biggest changes have been done
by Lynn, she was here, yeah, handling about VPA, VP9, everyone, and ProRes RAW decoder
in Vulcan, and having, like, actually GP with decoders inside, FFMP is kind of new.
David, yeah, so David is finished, congratulations to everyone, I mean, like there was almost
no development on David in the last year, because we don't everything we could on X86,
almost everything that Martin could on the on, and so we're at the end of the road.
The only new things that are happening on Whisper, thanks to Remi and Nacer and so on, but
basically I don't think we're doing anything anymore on David, it's insane, it's still
30,000 lines of C and 245,000 lines of handwritten assembly, which is probably the, yes,
the largest codebase of assembly in the world, I guess, to give you an idea, the whole FFMP
is going to be the codec, it's 110,000 lines of assembly for the whole codec, I don't
think we have more to do, right? There is still people doing some poor PC and long-son
work, but this is good, so we have, we can move to the next project, okay, VLC, tomorrow
is the 24-year of VLC, tomorrow there is no actual birthday of VLC, but on the first February
2001 there is a university who allowed to make that as GPL, so for us it's a birthday, right?
We still continue working on the VLC-3, the last version of VLC-3 has 547 million downloads
on our website, because people complain about the numbers we have, right? People are updating
and updating, well those are not updates, so that's quite large, and we did a lot of work
on VLC-3.023, one of the things is basically, sorry, the image doesn't show, we have
a dark mode on Windows, we work on, officially we support Windows on ARM, but mostly we still
work on Windows XP, right? So, the last version of VLC runs from Windows XP to Windows
11 on ARM, right? And when you compare to lazy companies like Google or Microsoft, like
we don't even do that while they have a bit more money than we do.
We're working on VLC-4, sure, it's not dead, this is a screenshot, not a design work of the
last three on MacOS, it has a new clock, a new playlist, a new player, a new media library,
and updated UI, a preposterous that is separated in a separate binary, so that when it crashes
and is scanning your stuff, it doesn't crash your VLC, do you also try to do a
new previous frame, yes, finally previous frames, a lot of new APIs, it supports pipe
wire and wayland, and maybe at some point we'll have a gapless and for subtitle, because
this is what people complain the most, and it takes me time to answer to them, so it's
easy to fix, then do that. When is it out? No idea. Yes, I know, 21st century, okay, that's
okay. Okay, some of the things are happening on VLC on mobile, most of you are not on iOS
I know, but some of you do, and yeah, for the same rate, VLC for iOS, now supports iOS 26,
we see support iOS 9, which of course, like not even Apple is able to do with iOS, that's
why it's so difficult. Kind of things on cloud integration, on codecs, but also lot of things
are happening on the same time for 4.0, HDR, picture and picture, multi-channel audio, dual
subtitle, and vision OS, oh watchOS, right? You remember there was a joke about VLC
running on the watchOS that I did a few years ago, well, someone revised that port, so you
can destroy the battery of your watchOS in 2 minutes. Actually, it's 10, but anyway. And same
things on Android, right? So the Android version has had a lot of work, we have the same
HD web access, remote access so that you can basically upload things without having to
manage the USB nightmare that is on Android. Support for 16K pages, which is a big topic,
lot of work on basically all the APIs, major library favorites, equalizer, lots of work
on the Android Auto, because as you might have seen, a lot of car manufacturers are moving
from their own crap to Android Auto or Android Automotive, you're going to see more and
more of that. And also, we still support Android 4.1, up to Android 16, that's probably
API 21. So yeah, still supporting most of the platform as we could.
Live DVD. Well, yeah, I took some time to maintain them again. It's boring. It's very old code.
It was not designed correctly. Yes, but we had to support for all DVD audio, this summer,
thanks to a G-Sock guy who's from Egypt. And so the thing is, you have to understand that DVDs
are not encrypted with the CSS algorithm. They are in a type of things that is called cpxm,
and which was an open source library that was dropped by someone somewhere, and that was never integrated
any distribution. Also, because, well, no one cares about DVD audio besides me, I guess.
I think there have been only 1,000 issues of audio DVDs, DVD audio in the wild, but still,
like, for long term, it's important to maintain them and have something. So we integrated this
library, rewrite, we would have of it, and put that inside the DVD CSS. And we worked on the
lib DVD read to have all the passing of all the structures, so you can have all of that.
A ton of new APIs, we moved everything to meson, and we spent some time to support UWB,
BSD, and some recent versions. So, I did really see the during the summer of lib DVD CSS read
nav, which we are not updated for four to five years. And we're now working on DVD RV,
which none of you have have heard, but those are the DVD camcorders.
Same for lib Lore. Again, like, and maintain library, I took back the maintenance ship.
Ton of things about new version of java, because I didn't know but java is alive again.
So now we support up to java 23. We've been working, I did a release in 1.4 this summer,
we just did like two days ago, a 1.4.1. We're working on everything related to 3D, SSIF, HDR,
and a ton of java, right, which I am amazingly good at. Now, especially to improve the
capability with new blue rays that are out that have no more features for the menus.
And we are going to work on everything related to HDR 10 and 3D.
We have a new project called check assembly. Check a sim. I don't know how you're supposed to
pronounce it. Check a sim, I guess. And it's not a new project, right? It was like all the tools
that we used to write all the assembly in x to x4 that was taken inside ffm pair and then
moved to David is basically a way to benchmark and run all your assembly code and check if it
matches your C version, right? It's a dark magic thing that no one understands except two people
in the world. It's amazing, but basically it's type of like it's similar to ffsing, right? And it's
going to check that basically the input in the output are the same whether you're doing the C and
all the other functions. And it's very useful because now we don't do just one assembly, but it's
a six arm with neon as a C, this five, there is multiple vector lens. And so this was moved to one
project that is still a video-long project and now it's been integrated back into David.
It's going to be in x to x4 and David 2. Oops. x to x4 is still alive.
Turn off things are happening mostly on neon and SV assembly. And this is going to be important
because the patterns of x to x4 are mostly expired next year, so people will use x to x4 completely
so they will use an open source encoder. David 2. Suppose call it as you want. David 2,
Dave 2D, David, you're French, right? This is also a horrible joke, but it's ready. It's not open.
If you need access, ask me. We're waiting for the official go of the final spec because
only the draft spec or EV2 are ready, but in the next two or three weeks you'll have it's
completely open and mostly working. EV2 is basically everyone and 22% better basically.
Oh come on, 22. I'm happy. Two other libraries that we've talked not often, one is
lip specialist. We did a large release, the first actual release of lip specialist. It's an audio
renderer for everything that is object high order, objects like what you call 3D audio, right?
Dolby 2 at most or whatever the name, right? All those soundbar. There is no open source renderer
and most of the time the renderer where mixed with the codex, like inside AC4 or 3G.
And we did that in a separate library which is doing basically all the rendering. It's also doing
everything like what we call bineralization, which is like when you have headsets and it feels like
it's fixed like spatial while it's not. And so everything is done in library, it's only library
because it's way more complex than you think. It seems easy, it's not, especially because you're
going to have like when you rotate the head you need to rotate your soundfield and have a constant
energy. This is not easy. And so this is the first release that we've done in October and we did a
huge demo because there is a new open source format for 3D audio called IMF. And there is another
library which is probably like the one I've never talked about which is the most, one of the most
active video and project. It's a lip placebo. Lip placebo is basically a GPU filter libraries which
is doing everything HDR tone mapping, reversal mapping and all those crazy things. It's starting to
actually MPV, right? So it's funny now it's a video run project. It has doing all the GPU pipeline
and I have turned off filters and well no one talks about it but like one of the most active
project we have. Just a few two things. I've done a release of mirrored bits, right? I took
over the main tone sheet of mirrored bits which is to do mirrored. It was no releasing six years.
It's done now using tons of distribution to distribute the mirrored so that you don't have to
select the mirrored but you just take one mirrored and it automatically magically gives you the best mirrored
the best file and one of the main features is the support HTTP. No S. And there is a small last
small project or a few other small projects. One is called the summer we did the reverse engineering
of the NDI protocol and we did the library. It was called Lib and DI. I'm not allowed to use that
name anymore because NDI is a patented and trademark project from Visiert and nothing has been endorsed
by them but basically we will reverse and broke the encryption so soon you're going to have
an open source way of using and generating NDI streams. And I guess that's most of the stuff I wanted
to talk about and last thing is a ton of people of you have asked me to get access to Kiber.
It's open right now. Even the website for those who don't know it's an open source framework
to be able to remote control any type of machines. It's basically streaming of all the sensor,
audio, video, subtitle, IoT sensor and everything over one single socket. Completely encrypted
in quick. The goal is the lowest latency possible so that you can control the machines. It has the same
in the same way as all the controls in inputs, game paths, keyboard, mouse and everything. Everything
is fully accelerated and is based on VLC on the client side and FSMPEG on the server size which means
that we have on all the platforms. The server is Windows, Linux, even Wayland, Mac OS and the client
Windows Linux Mac on the way to the TV, Android TV, the web version and everything. So you can have
finally something to replace Citrix or VNC in all the cases. It's fully open source. It's actually
dual-licensed commercial open source. The version that we out is not the final version, right? It's
ton of features that are behind some branches that we're going to merge in next few weeks. The
tip you want to try, you can join or ask questions. Thank you very much. My time is up.
Yeah, I can ask a question, answer a question, Voila and plug. Any question?
Yes?
It's faster. The question was about compared to sunshine and moonlight. It's way easier to use.
It's faster, but mostly it's based on quick, right? It's not using the GeForce
nightmare protocol opening 20 ports, right? It's only one port that is quick with
substream in quick with where we use the same time's quick streams for the inputs and that
ograms for the audio and the video. Yes, of course.
Yet another image format. The question was about GPEG Excel, right? It's a ton of joke, but like,
how many image format did we get in the last four years? Ultra HDR, AVIF, HIF, another version of HIF,
an animated version of it. Some depict 2000. And they're right. And they're just another one
instead of working together. There was flake and so on. So at some point, why another one?
But they have the name and they are, and they work as well as the other ones. So they will win.