Comment by daenz
4 years ago
How much data can you store if you embedded a picture-in-picture file over a 10 minute video? I could totally see content creators who do tutorials embedding project files in this way.
4 years ago
How much data can you store if you embedded a picture-in-picture file over a 10 minute video? I could totally see content creators who do tutorials embedding project files in this way.
Back of the envelope estimate:
4096 x 2160 x 24 x 60 is your theoretical max in bits/second, 127 billion.
Assume that to counter YouTube's compression we need 16x16 blocks of no more than 256 colors and 15 keyframes/second; that reduces it to
256 * 135 * 8 * 15 = 4.1 million bits/sec.
That's not too awful. Ten minutes of this would get you about 300MB of data, which itself might be compressed.
To do PiP (picture in picture), you would be restricted to a much smaller size, but otherwise good calculations.
4k video is almost always 3840x2160
4K consumer video is 3840x2160, 4K Cinema video is 4096x2160.
Just like 2K consumer video is 1920x1080 and 2K Cinema video is 2048x1080
2 replies →
“hope you enjoyed this video. btw, the source code used in this tutorial is encoded in the video.”
Would storing data as a 15 or 30 FPS QR code "video" be any more useful? At a minimum one would gain a configurable amount of error correction, and you could display it in the corner.
Yeah seems way easier than adding a link in the description
Links die. As long as the video exists, the files that the video uses will always exist.
As if videos don't die...
7 replies →