 So everyone, well, I will go fast because I don't have much time. So I'm one of the VLC guys for quite a long time now, working on a lot of things and breaking a lot of things as well. So we will see today VLC 4, which is the next release that everyone is waiting for. And my first answer for you is when it is released and I don't know, I still don't know. So we had some objectives, a lot of big changes to fix long old bugs. So for the audio sampling we introduced a new clock model for the video resource management. We changed the model to a pull model instead of push. And for having a proper stream output, which is mostly transcoding and passing to some other modules, we had to rework the way we were dealing with the time. And also what everyone is asking is the new UI because the old one doesn't suit everyone. So we are on this scene quite a long time, six years now. Lots of commits, lots of merge requests, still a lot of merge requests waiting, a lot of changes. And we are still expiring milestone. We are turning into vaporware soon, like some well-known video game. We are progressing. What happened is that we are dealing with really old code because the core is hard for us. We are not the guy who wrote it. It was hard to understand and there is a lot of documentation, like everyone likes to write documentation, it was well-documented, I read the fucking code. So we knew what kind of trouble we were, we would be running to and we went into it. But everything is getting better. So we did the new clock, it works quite well. The video side is also done. The timestamps still have some issues. And the modern UI is on good progress and of course we still have to deal with more regression because the fix triggers a new regression. We will change the Chromecast because the current Chromecast is still buggy. So we had to provide a full HLS server for people knowing what it means. Instead of streaming the file directly to the Chromecast. So the Chromecast has better control of the buffering and doesn't run out of data. And also provide support for real subtitles which never really worked without HLS. We also removed things from the next release. We were providing a lot of VR, HMD, 3D, virtual, movie, theater and things. It was hype. The guy with the code is gone. So probably we won't maintain this or maybe not for this version. And on the audio output we are able to achieve finally as a video player, Gapless output for Gapless audio for when you are turning into an audio player. No more resampling glitches, something that people were always complaining that VRC is always sampling audio. And we also properly dealing with audio delay, which means when you plug your Bluetooth headset, video keeps in sync with audio. It's not the same for AirPlay which has quite a huge delay like two seconds. So those things are fixed and good and improved. And we also have some things we couldn't think we could fix. Like the frame by frame which was quite buggy for us. So you can do more than five frames ahead without running into issues. And also the guy which fixed this understood the thing so well that he also introduced a hack to provide a previous frame. And in video it's really hard to go back in time. And currently we have people working on super resolution, so upscaling. Most of this is done for Nvidia video cards and Intel. It works, doesn't provide much enhancement, but things are getting better. Also the stream output, so that was for the HLS output. We introduced hardware encoding on this side because we liked to drain battery for people doing Comcast. So now it's way better. Also we improved the subtittles on Android. It was quite laggy. We had to improve that and find a better way to upload textures. And so it's quite better now. For us, for the developer side and contributors, we are now able to build with Nissan. So Auto Tools is gone soon. Also we are probably starting to write Rust modules for improved security. So we made some changes to be more Rust friendly at the ABI level. And to provide a new player, we had to provide a new way to show video to people to present your collection. And so we had to write a media library. So this was a concept which was really buggy because it was built into the UI, in the older releases. Now we have a dedicated library. It discovers all your media on your device. It gets us metadata. It does terminating. It stores the playback restoration state, your preferences in language. It does everything what a modern video player should do. It provides full search and it's already used by the Android version and the macOS version. So it's quite well tested. For the developer, we are replacing a lot of things. So we are exposing a lot of API. I'm not sure how much time I have left. Okay, good. And we also discarding Bogus event model. But anyway, that's not interesting for this one. And we also have a lot of wrappers. So the old CPP, JNI, which is for Android, VLC kit, which is for macOS. We have a wrapper for VLC shop, which is also used by VLC for Unity, which is available in a different license, but that's another question. And we are also working on providing VLC on Unreal Engine for video games. So everything good on this side. But we also achieve something really interesting for people and professionals. The world, which is low latency, something that VLC never really achieved. So we had to deal with some of the buffering, framing, delay, decoder. So always one second on two seconds late. And we have a new option, which is low delay. So we treat a lot of things. We are able to target some decoder which can do low latency, because you need some kind of specific profile. And we are around 50 million seconds on the local network, which is really nice. Which means also that's less than three frames at 60 fps. And that's good. So that's a screenshot of glass to glass. And you can see that the counter of number of frames locally is around two and a half. So this is really hard to see that very latency now. But that's a specific mode. And the new UI, so that's what you're waiting for. Everything is rewritten using Qt Quick, which is mostly JavaScript, CSS. So a lot of changes, a lot of trouble. We are about not to provide light and dark teams, which was really nearly almost impossible in Qt4 without a lot of hacks. That's why we are not progressing on this. We are running through a lot of Qt issue. We still are running through, especially with Wayland on Linux. And also we need to provide a legacy interface, because not everyone will be happy to have a new interface. And some people still like the old interface. And we have to drop it. So we need to provide a way to provide that interface to people. So how does it look? Well, you have your library, and you have all the features when you can board into the categories and the discoveries, all the categories you had before, and everything is integrated. Yeah, and I need to do a demo. So this is dark. But that's not the right screen. So how do I switch? Okay, so probably I need to change the streaming up to something, to another, you know? Yeah, because it's not mirroring my screen, so no, no, it's already mirroring. Okay, good. This is duplicating. Yeah, okay. Well, good. So this is the dark team, which is switching automatically depending on the system. So you have this library, which is creating thumbnails and everything. So you have your progress bar, like on the video streaming websites. You have the quality and everything. You can resume your video, okay? So you have your subtletors selection. You have the drop down menu, which is disappearing, yeah, okay. So everything that you should expect from a recent player, and also you have a picture-in-picture. So you can still browse and find other content, and you have a modern music player, like some others, and, for example, where do I go to the tracks? So you still have your playlist, so that's not what I want to do, okay. And I'm also discovering some recent changes. So you should have the tracks, the list of tracks when discovering your albums. Yeah, okay. So that is... Yeah, sorry for this, yeah, okay, anyway, it doesn't matter. So I can go back to my slides, sorry for that. Okay, so we can try. It's available on 90 builds. Of course, it's still unstable, but it works quite well right now. So if you have feedback, we can take it and know what's going next. So we will probably provide a way to have more standardized hotkeys, that's something what people want. Also provide some upscaling shaders for, we're already working on Super Resolution, but very specific shaders for, for example, Anime, which are quite popular. We need to fix the HDR on Linux platforms. We are still waiting for a proper API. So we remove the subtleties in the black bar below this video for some platforms. That's another request. For some reason, we want also to provide some transparency support. Mostly this is for the video game engines that I mentioned before. And we are also sandboxing for security. So that's something we've worked for a long time now. It starts working. It's available on Linux windows. It's based on Linux on a Rust library, which is written in Rust. And also, we have a project which is quite successful, is that we are rebuilding the whole VFC into Wazem. The reason is that you no longer have web plugins in your browser. Depending on your browser, you have a lot of limitations, which means if you want to play back some video, you need usually to be in MP4, and you are limited to some codecs, and you cannot do what the old player was doing, and you cannot do this also using a plugin. So rebuilding everything in Wazem and using the web codecs acceleration provides you hardware acceleration in most of the cases, but it removes all the browser limitations you would have. So you have everything that VFC provides, all the formats, all the subtletors. You can watch DVD, ISO, in your browser. You have support for every comma you want, of course with convention or the depth. And if you want to do VP9 4K in software, you have that level of performance. So everything works. There is a link if you want to try it, but if you step to set up your browser, we move some limitations, but it works quite well in Chrome, and especially in Windows. Okay, I think I'm done, and I'm on time. Well, thank you for listening. If you have a question, technical, or we can talk after, because we are a bit late on this kiddo. Thank you. Thank you very much. And please test, provide feedback.