 Hello everyone, welcome to Renault Talks IP. I'm Renault Lavoie with Read All Communication. Audio in 2010 is as important as video, so I dedicated this Renault Talks IP on the audio, but a question I receive, how many audio flows make sense in what the audio source and destination should do with them? So that's an interesting question, you can say it's trivial, but no, it's not trivial, and let me explain you why. So first of all, in an HD or 3G signal, you have up to 16 mono channel. So then you can say, okay, I will create 16 flows. But the problem happened when you do dash 7. So those flows are double. So you're looking at 32 audio channel. And if you scale your system, just thinking about a big system we face sometime, it's about 500, 1000 senders, 1000 times 32. So you're looking at 32,000 flows for audio in your network. It's starting to really scale up the number. And of course, you have all other processing, you have all other video, video multicast and also ancillary. So the number goes really high. So what's the good number? In MeteorNet IP, we started with 8 flows, 8 multicast or unicast. But then with undersea coming, it's become 16. And as you know, we can put like, we can put 48 mu one in a switch. So you can see the number adding there 48 times 32. And in 2015, when we did that, it was really hard for a control system to cope with that. So we said, okay, let's go back to a basic, let's do 4 flows. But in the four flows, let's give the ability to the customer to put 16 mono channel. Just one thing though, I will explain you how this is possible. And with packet time will not work in 16. But let's keep that for for a few minutes. So we did those four flows. And the customer told us in your encapsulator, you shouldn't be able to shuffle them, which we did. And they said on the receiver side, you should be able to select which one you want. Meaning that I send you four multicast with audios, each one of them can have two, one, let's say 16. And then your receiver will cherry pick from those four flows. They can come from different sources. They can come from different centers. And there's no problem there. You're in 2110, everything is is time based with the with the PTP. So interestingly enough, when you do that, you can shuffle at the receiver. And then you remove the embedded and the embedded from the old time. So wow, now I can have a shuffling device inside the network, which we do, or we take our destination and the receiver will be able to shuffle them. When interesting things we add, because we had an application with a customer, and they say, can you double my mono channel? Can you send two of them? Same thing. And we ask ourselves, why? Because some receiver in 2110 do not support only one mono. They need to have this stereo channel. So then we create, we double the mono and these equipment start working. And you think it's trivial, but if or the encapsulator did not do it for this customer, it's really complicated to do. So it's simple things like that we learned from 2015 doing audio. And like I said, at destination, we're able to shuffle or to cherry pick the audio you want on four different multicast. So now let's talk about packet time. As you know, audio has packet time. So in, in 2110, they are defined as the following zero means one millisecond, one is 125 microsecond, 250, 333 and 500 microseconds. So now interestingly, the 2110 dash 10 also specify that the packet should be a UDP, sorry, datagram size limited to remember my my MTU 1500 bytes to be more precise, a thousand four hundred sixty bytes of data. So now let's take a one millisecond. And you can see the equation on my left side. This is really interesting. So my packet size of my of my packet is thousand four hundred sixty bytes. You have the number the size, the bit per sample, you have the sampling rate, let's say 48 kilohertz, and you have the packet time. As you can see with this equation, if I'm running at one millisecond of packet time, I can only put 10 channel in my flow. So then my 16 will not work for a one millisecond. And this is some limitation you have to be aware of. The other interesting thing is it could be worse if I do 2110 dash 31, because I can have 32 bits per sample. So you can redo this equation, if you like, and find what's the number of channel you can do. I hope this was useful. Really, the shuffling, the calculation to know how many how many channel you can put in a multicast or in a flow. And like I said, audio is as important as video. So we'll try to do more audio presentation in runotox IP. Thank you very much for watching. And for more information, please don't hesitate and go to see readall.net. We have more runotox IP and more to come. Thank you very much. Have a wonderful day.