Coloured static, visual white noise, random bitmap video, random video signal

30 frames per second
9000 PNG files
1920x1080 bitmap with RGB colors
Random RGBs generated with F# programming language using .NET System.Random()
PNGS assembled to video using FFMPEG
gist.github.com/kmrasmussen/2...

[@AgeingBoyPsychic]

This would be waaaay better if CZcams's compression hadn't left compression artefacts

[@torbammoyer3322]

I know its been 5 months since your post, but without compression artefacts like those, you'd have to download the video first (video should be around 53.4GB uncompressed means about 178.2MB/s download speed) There is almost no way to display such a video without compression artefacts through the internet.

[@bobbyc1120]

@@torbammoyer3322 It's amazing how big uncompressed video is.

[@bobbyc1120]

Put the video in 360p. You'll see occasional flashes of clarity followed by blurry gray noise. Those flashes are what's called a reference frame. That frame is saved at a high quality, and the subsequent frames are compared to that frame to save space.

[@JJBerthume]

That's fascinating

[@bobbyc1120]

This makes me wonder if newer codecs would be more effective at displaying this video. Considering that it's completely random, there should theoretically be no good way to compress it, but maybe some codecs can do so in a way that we perceive as less detrimental.

[@wasteddude9387]

Aren't compression issues minimized by smaller height x width, and a shorter length, looped? Isnt it a fact that smaller dimensions reduces file size? Considering the content, how could anyone detect a shorter, looped version? Then wouldn't the resulting file size be so much smaller, that compression wouldn't be as big a problem? I don't get it.

[@waste428]

This really fucks with my head