 I'm going to bring up my own notes. There you go. So, I've been working with the company whose logo you see here and that I've been working with for the past year on various wonderful museum experiences. I'm here for a year now and previously I was working on the development of a triple life enables streaming platform for your piano and at my previous job at a wonderful cultural institution here in the Netherlands. And then, next slide please. So, I'm going to tell you a little bit about who we are what what is q42 a little bit about what is Mikio and how Mikio links out links to try out. And I'm going to tell you briefly about how we serve museum collections, and how we use Mikio and, and some of the triple life come come come ability to enable museum storytelling and give you a very brief list of takeaways. Next slide please. So, we're qq 42 were about 80 people were a tech bureau based in the Hague and answer them. And we work for various industries various sectors. But we're also lucky enough to have a number of clients from the museums and cultural sectors. The company has existed for about 20 years and and at least 16 of those have been spent working with museums. And with those projects we've won a number of prizes grannies webbies, you name it, which is also wonderful that people see, see it and really sort of make those experiences. And a lot of those experiences that we built specifically for museums are powered by Mikio or have more and more becoming powered by Mikio. So, next slide please. And the micro usage usage how it started and how it developed was really through a number of projects with a variety of clients. Originally, and next slide please. This is going to be a lot of clicking drives I'm sorry. And so originally, Mikio came about by collaboration with a broadcaster and and a number of cultural projects that we did together with them and with various museums. And over the past few years we've really been expanding that user base, not just for people in education and publishers, but there's about six more gosh and people in from municipalities various NGOs political parties libraries film festivals, space agencies, and maybe even more. And so what this, what this tells us and we'll come to that conclusion at the end of the time but storytelling and platforms that enable people to do storytelling by way by ways of hyper resolution images is really something that is a brought me just there's a lot of a lot of sectors and a lot of people out there that really want to use the capabilities of the modern web to tell stories specifically around high resolution images. 2d 360 you name it. And Mikio got started in next slide please 2015, which is the first launch as a kind of a passion project. And as soon as Marcel announced the launch of Mikio. David Haschia who was then the technical director of your piano was immediately on the case saying hey is this triple I have compliant and I was going back to the history of some of the internal messaging. The first step was what the hell is to buy it. And over the years that that question has been asked a number of times by more and more and more people until next slide please. In 2019, Marcel announced full triple I have compatibility for for Mikio. So what it means in more specifically is that Mikio has now 100% enabled the image API number 3.0 and has enabled largely the presentation API to fortune point 2.1. And then there's a number of storytelling functionalities that are available in Mikio but that can't that can't necessarily be mapped to some of the triple I have standards. And so, before, before then before Mikio was to play if enabled we were doing some of the, the tiling and the resizing and the cropping. Things that that trip life enables by closed source and sometimes end of end of life services. And so having an standard that was open and I have an open protocol to do so was was very helpful for the things that we wanted to build on top of those functionalities within within Mikio. Next slide please. So, to give you a very brief intro so Mikio is a bit of is a standalone service and in the examples that I'm going to very briefly show you today. It's been fully sort of built into external websites but it can be used as a standalone storytelling platform. You can embed it in their own, you can embed it in your website as it's or you can sort of add some extra layers of styling to really make it your own. And what it is it's a hyper resolution storytelling enabler, as I would say, and it's a it's a it's basically a the dots and the images are markers and every marker is what in triple F lingo would be an annotation, but for editors to add various layers of information and story lines on top of it. You users can can use those markers on their own at their own speed drone will you just click it and read it or click it and add audio to it. Or you can have a whole a whole tour around it. And over the years, a number of functionalities have been added to that such as positional audio so every every marker can have specific sound effects when you hover over an image, or or even in 360 area. You can embed media into it. You can have scripted camera tours across an image or even across various images. And so, besides all that it's also a cloud based triple F image server and viewers so it's, it's, it's a service, and you, in order to use it you, you take the license, but you don't have to hassle about the whole management of it. And it has it comes. The service comes with its own storage but it can also be connected to your own storage or even potentially to your own triple F server if that's that would be a request. So that's in a nutshell what Mikio tries to do. And so I wanted to talk about the two ways that we that we use it one is to really serve. Next slide please. So we have a lot of specific museum collections, and at the moment there's, there's three that do. Two of which are for two of those we have built a bit of a custom connection, the Van Gogh Museum in here in Amsterdam and the Wrights Museum, literally physically separated about 200 meters at the museum plan in Amsterdam. So we use in the Mikio in the back end and then we serve the images through by what by way of a custom CMS, and the Philadelphia Museum of Art who uses the Mikio collections properties as is. So Mikio has a dashboard with with with which museums can can can manage the entirety of all the image collections that they want to make publicly available. That's a big exclamation mark. Those parts of the collection that they want to be seen that they want to be to be made publicly available from within the Mikio environment. Next slide please. And I'm going to rapidly skip this for time. So briefly so what we've done for some of the custom some for for some of those for the rest of the team in the van Gogh is added a proxy server and Mikio is all about speed so it uses WebGL WebAssembly and make sure that that the delivery of the high resolution images goes as fast as possible on all the devices, all the browsers and and poor connections. And part of that is also making sure that the delivery of all the the tiles and cutouts is as fast as possible and up until now we've we've done so by a custom proxy server that make sure that we don't have to sort of resize or recalculate specific types if that's already been been asked for by a user. And it looks like as of today Marcel announced that we can now do the server sounds server side so that we don't no longer need this this custom implementation. Next slide please. Before the van Gogh and and rex museum what we what we enable in in in our CMS so this is a bit separate from the building on the micro features and building on what triple F there allows is a variety of ways to really showcase the images in the way that is seen by allowing very specific crops and allowing setting a very specific focus point so that whenever, no matter what kind of device you see it on where there's a mobile or a 4k resolution monitor you always get this high resolution image. So I want to deliver to you the way that it next slide please. And so I wanted to demo two stories but because of display reasons I'll just I'll just name them and tell you about what I what I like about them. Next slide please. Things I talk is a platform that integrates micro functionality to tell the the stories of student research into objects and those objects can be museum objects that can also be random contemporary materials. And what things that talk do does is use mostly the, the functionality of micro to have a tour and the step step through the various angles and the various stories that can be told around one thing so you have, you always have one thing that that powers a variety of stories around some of those stories also start with like a 360 image of a room you can really sort of zoom into that. Coming back a little bit to a target Marcel gave to the museum's community for triple IF just a couple months ago. He was asked, you know, what would be handy to have in the triple IF API support for for for those 360 image experiences would be really something because we see that that's that's coming more and more to the floor. He also uses link data but that's a whole other story. Next slide please. And for the slavery exhibit which is a high profile and as an important and sensitive topic to speak of that open just this month at the Rijksmuseum. There's a new format in which we have so make your already had video tours, which is where you were taken to various camera position on on an image. And with a voice over that that really sort of takes you through the narrative. And we've now linked those various tours to various images so that in the slavery exhibit, you can you can sort of it's a it's a combination of all the the various images that make your has to tell a story through different angles and platforms and and zoom levels. Next slide please. And so very briefly. So, through play if I if I helps only show a large way to do it and by very large we mean in the case of the Rijksmuseum that's over four and 16,000 images at the moment. We, we are noticing more and more and more that museums really want to play us, we see it passing by in requests for proposals, and when we talk to people in museums, even sometimes if some of the colleagues don't always know that they already have to play enabled in their own collections. And it's not just the museums that have stories but there's really a broad demand for it. So, that's it for me, you can get in touch for questions next slide please. Oh yes. Free trials are available for Mikro and if you ask Marcel nicely and you need more time to extend that free trial. That's, that's probably, probably, probably possible, most of the time. My name is Erwin you can reach me here, and you can reach Marcel on the next slide or follow him on Twitter via Mikro. I hope there's one or two questions in the one or two minutes that we have left. Thank you so much for your technical support. Thank you. Good, good, good stay and loose. Let me share and let me just take a look and see. I couldn't see while that was happening. Yeah, we have a quick minute, especially because we're up against a break if anybody has a question I don't see one in the Q&A. That was great covering a lot of grounds. Very quickly. So, if you have a question, add it to the Q&A box or the chats. Otherwise, oh, here's one. How is your work with multiple museums aided collaboration between them. Maybe that's a wonderful question to end on and so what we what we try to what we try internally is that we have various various teams and so for ourselves we're trying to sort of unite them a little bit. A bit of sort of as a company what we like to say, the museum clients is that they get some of the benefits of us working with large companies, you know, who have the funds to do technical innovation at a level that some cultural institutions can. And so we also tried within our team to exchange that. It also means that we're talking to those different clients and they're talking to each other and so we try to sort of keep that a loop that when we implement something in our in CMS or in micro that another museum can also make make use of those of those developments. And so the way that micro came about in itself as an example of that because every project added to the core of what we could have. That's, that's wonderful. Yeah, that's a great answer. I think we've, we've, we've just hit the end of the session time, but really appreciate your staying loose. I hope that worked out okay. Thank you to Erwin for presenting on McRio. Thanks folks for joining us. I'm going to end the recording here but we can keep the questions in the chat going in the Huba platform if Erwin if you're still available to answer questions there post links. Thanks everybody and we'll see you after the break.