Kieran Kunhya

So in VLC, for example, we already have a plugin for haptic.

It's mostly for what we call 4D cinemas, right?

You know, those ones on hydraulic, I don't know how you say that.

Hydraulic arms.

And where everything is moving, like you have in theme parks, right?

And there is a data feed synchronized, which is basically transporting this information.

Is there yet a standard for that?

There are many standards, right?

Yeah.

You make me so happy.

And so, of course, like, we have a plugin, which is not in the normal version of VLC, that is basically transporting those type of movements, which is physical movements, which is haptic movements, right?

It is a human sense, so it will get in.

We are not the contributors.

We are the maintainers.

So we maintain for everyone, meaning that, for example, every year there is around 150 people who contribute to VLC and maybe 300 on FFmpeg.

Our goal as a small team is to get all the contribution in.

So if there is more usage, there will be more contributions and those people will do the right module, the new formats and so on.

We care about the architecture of VLC, the architecture of FFmpeg, right?

Now we're doing things in VLC, which is a spatial audio, right?

We did the demo not long ago.