How does it survive YouTube transcoding.
maybe something akin to what QR codes use?
https://en.wikipedia.org/wiki/Reed%E2%80%93Solomon_error_cor...
YouTube as Storage
161–163 of 163 posts
Re: YouTube as Storage
#162Earlier quoted context omitted.
I've stumbled upon very valuable content with very low view numbers - the algorithms spiral around spectacularity and provocation, not quality or insight.
Then it's on you to share it !
But to whom, I have no followers and a blog update has been on my TODO list for two decades..
Re: YouTube as Storage
#163Earlier quoted context omitted.
This actually won't work against YouTube's compression. The DC coefficient is always quantized, rounded, scale, and any other things. That means that these bits are pretty much guaranteed to be destroyed immediately. If this is the case for every single block, then data is unrecoverable. Also, chrominance is not used on purpose, because chrominance is compressed much more aggressively compared to luminance.
I meant choosing multiple values, e.g. 4 to represent 2 bits. Say, 0.25, 0.5, 0.75, and 1. Then when decoding you would pick the closest valid value, so for example for 0.20 it would be 0.25. Not using AC coefficients would mean that theoretically you would get more bitrate for the DC ones.
I’ve been told this many times in the comments, but this again is not reliable. Simply put, compression doesn’t necessarily follow a pattern, so specifying “ranges” or rounding to a specific place will not work. Compression optimizes for the eye, and doesn’t do the same thing for every value. It will round some down, some other mores, others less. Giving a range is simply not enough.