 This is basically the story of the DLC Viderland and Viderland projects. There will be more, I mean, today talk about where we are, where we're going, and tomorrow there's a part session, so please, please come if you're interested. And the season is going to be my job, so whatever I might say is just my opinion. So first of all to me, I joined the project as a student 12 years ago. At the time the project was actually still based at the university where I went to be studying, so it was kind of easy. And then when I graduated three years later, then I just carried on, but as a hobby, I'm not free time. I enjoyed Nokia, it didn't pan out very well as most people would know. Nowadays I'm working for NVIDIA, so I'm still doing mobile development there, but nothing to do with videos. So this is where Viderland was started, so a campus at the French University. And the story is such that, well, in 1989 they wanted to bring a network, a computer network to the student dormitories because they didn't have anything there. I mean, the French community at NVIDIA is anyway. And they made a very bad choice, they decided to go for stock and rent. I don't think anybody remembers what that event is. So all those people might even, the name, do you even remember how the stock has looked like? But you still have them there. So in 1996 they found a way to write to ESAnet and to do that had to pitch the idea that they would be streaming video over the network. And that's how they got the record to give away the infrastructure. Obviously the rest of the students didn't have any money to actually pay for that. And that didn't really work because fast decision making is fast enough. Oh, I think it was 10 megabits at the time, for streaming video. So in 2002 they were running again, and this time doing a multicast. And again they got it for pretty steep discount, but for 100,000 in the world. So the VLC itself started in 1996. Basically the idea was to stream video, and initially it was to stream video on the network. But we only have the project history going back to 1998. I think because the original project was so badly written that it just started from scratch. It imported the new thing into CVS. Well, 17 years ago, so it still was a lot of time. And it went open source with the university's commission in 2000, before that it was a field source. Well, it presented so far very long. So that's when it started becoming more popular. In 2001 we had Windows support, I think. Basically people started contributing so much to the university from that date onward. In 2008 they were not really a student at the campus. We were interested in the project anymore, so we just created our own foundation. And we've been independent since then. So the foundation is made by the main developers and contributors. Our venues are mainly solely from donations, which means we don't actually have that much money. We don't have advertising revenue, we don't have much subsidies. So it's really just covering our own conference and then traveling infrastructure. They got right once, of course, like domain names, that kind of thing. Hardware for development and testing. Here we have our yearly meeting and these are a few of the work photos. So in 2004 we finally had stuff mostly working and since then we've been open source for three years. And that was reference slides at the time. So this is actually a slide that was made eight years ago. Trying to explain what the project was doing at the time. And it's still more or less what it is doing. So it does, for a year, they are initially only able to receive streaming from the network. But they are able to support for obviously local file playback, which is what most people are using nowadays. I think, I mean, VLC has become de facto the player that you saw anything and he didn't just place it. And I think most people are using, actually, very local files. But originally it was really meant to play a network stream. Live streams. But this is very old. So since then we have actually created a project and we've also discarded old ones. So as you can see this, sorry, this time we have a separate VLS and UD servers. They don't exist. VLC is doing everything nowadays. Both client and servers. We have a bunch of other tools that are mostly less known. Because they are not, mainly because they are not user and user applications. So of course, you probably don't get to use them so often. We have a lot of libraries. Again, this is not so popular so well known because these are not end-user-facing. They are extremely useful. And especially X264 is extremely popular with the same content industry. I mean, a lot of DVDs and Blu-rays are actually... That DVDs and Blu-rays would be included with X264. So TV channels might be included with X264. But of course, this is mostly professional. So you don't get to hear about it from the press so much. And those playbook libraries are actually included in VLC and in a bunch of other media players. But they are under the hood so you don't really see them. So the player is what we are most famous for. And that's focused... The VLC story itself is just a player. As I was saying earlier, we got the source code. And started in 1998. We had the first system working. A new version that could play a live video in 1999. And since we got the first source in 2000, people joined. And that's how we got the support, which is when the project started becoming more famous. Especially outside the university. And even outside France. Support for streaming outputs of actually sending stuff out of VLC, rather than just receiving and playing locally, came in 2003. And we reached our... We are kind of full-featured goal of version 1.0 in 2009, after we become already a separate foundation. And other two key milestones we've ever seen then. So we switched from our original GPL license to the lesser GPL license in 2011. That's because we realized that the market was such that we probably would get more interest from companies if we switched to slightly more liberal licenses. So the idea here is that we can now embed our medieval engine in your own application, even if it's not a GPL application. So it could be another open source license, so it could be proprietary. In 2012, we got version 2.0, and also the first release of the Android mobile UI, which is actually a separate code base with the same engine. So VLC is known for playing a lot of different files. We're running a highly versatile and portable, and we support weird OSes that nobody's using anymore. OS 2, I think it probably has one developer and two users. Originally, we only looked for the most of our users on Windows and iOS, desktop-side and iPhone and Android on the mobile side. And our motor is a two-musically-paying thing, except encrypted stuff. And I installed the codex, because I think there's about 200 codex and 100 file formats. I don't even know other than myself. And when we say VLC, I think VLC itself is only 300 lines of code, I think. So all of the logic is actually in our medieval engine library. VLC is a high-level play, pause, next-volume controller, it's only 6,000 lines. And then most of the logic is it's more dirty little details in the core library, which is about 6,000 lines of code. But all of the specific format, codex, source, like local files, disk, HTTP, all the protocols, all the video output, all the OS-specific outputs, all the audio and video features are in modules, which are then plugged in. It's kind of similar to GSTRIVER, if you're familiar with that one. We have a lot of different inputs and outputs. Obviously, we can play files, CDs, DVDs, more rates. We can play digital TV, if you have a TV stick. We can play the camera and the microphone, so that's not so useful for a media player. And at first, nowadays, a lot of streams are streamed via HTTP or they're right there with HTTP, like HLS. Or Adobe, or there's a lot of Dash. Quite a few different protocols that are HTTP-based. Five formats, I can look at and go through all of them if there's any specific question about how you can raise it. And that the flow is pretty typical of a media player, so we have the input, we've got access for some media secrets. Then we pass the file with an immersion, then we have the decoder's features and output. And I think that's pretty much what I have.