Slicing 76800 datas without loosing fps. Is it possible?

benjamin vyger's icon

Good morning.

I'm trying to send 76800 data to a 240*320 pixel screen. I can send 1280 data at a time.

So I send 4 lines of 320 pixels at once. (4*320 = 1280) This means that I have to slice the entire data 60 times (76800/1280)

In my example, I split the data 6 times. So I send 24 lines of 320 pixels.

When I send a video I have 30 fps, if I send a static matrix, I have 100 fps.

If I send 240 lines with the same method, will I lose even more fps? Is there a better method?

Thanks for helping.

24 lines of 320 pixels sent

Max Patch
Copy patch and select New From Clipboard in Max.

Source Audio's icon

you can send as much and as fast as you want.

The question is - what can receiver side work with.

this looks as neverending story ...

Roman Thilenius's icon

as long as IPv4 is involved at one point you will always have fun with those tiny 65kb packages.
and one must be careful to really only use one package, in many networks the theoretical 16bit-minus-headersize will never be reached.

as opposed to what most people think, smaller packages are usually better than trying to get to the max anyway. so it could be that things work smoother when you send single lines instead of four, it is a matter of testing though.

if you are worried about reconstructing frame, why not use timetags?

Source Audio's icon

to start troubleshooting :

zlmaxsize maxes at

76800 - no way .

then - this construct with counter / switch

I can not imagine that it would output list fragments in correct order.