
Coding theory: data compression

Data compression or encoding refers to procedures to reduce data storage requirements. Basically, a distinction should be made between 2 types of data compression, lossless data compression and lossy / lossless data compression.
In lossy data compression, an attempt is made to filter out irrelevant sound, image, or audio information that falls below the threshold of human perception. This includes, for example, certain color values and image spaces and tones and frequencies that are no longer perceptible in the audio data.

In the audio sector, you can dispense with frequencies above 20 kHz with no qualms of conscience, which corresponds to a sample rate of 44,100 kHz, without noticing a noticeable audible loss (as an adult!). We speak here of irrelevance reduction or redundancy reduction. Even soft tones after loud sudden noises cannot be perceived by the human ear for a short period of time.
These themes can be summarized under the general term “psychoacoustic effects of perception”. Lossy / non-lossy data compression runs on the entire media area. Otherwise, the huge amounts of data would no longer be manageable.
If you go too far with data compression, a video will show typical compression artifacts or block artifacts. Video looks pixelated, often accompanied by blurry, blurry images, and streaks of color. Either the sound is muffled, squeaky, or has hearing compression artifacts as well. This video cannot be decompressed back into the original video in this way because essential video and audio information is simply missing.
The opposite of this procedure is lossless data compression. Data that has been losslessly compressed can be decompressed 1: 1 at any time without data loss. A known example of lossless compression is ZIP or RAR files. When you create a file from a text file, the file size is not reduced by omitting irrelevant data. With lossless compression, recurring information is routed and / or stored through counters. This can be explained with a simple example:
uncompressed text: Friday, Friday, always Friday
Method A
lossless compressed text: Friday, -1 over and over -4
Information “Friday” that is repeated 3 times is addressed in a space-saving way by specifying the position of the first definition.
Method b
Lossless compressed text: 3f, 3f over and over 3f
The information “Friday”, which is repeated 3 times, is addressed in a space saving way with the 2 characters “3f”.
The compromise: audio quality vs. Video quality
An audio and video analysis related to the content of the source video is essential before the encoding process. Get an accurate picture of the source video you have. A compromise must be found between good video quality / moderate audio quality and moderate video quality / good audio quality. H.264 is a very high compression video codec, but it should distribute whatever bit rates can be sensibly saved in advance.
What target bandwidth groups would I like to serve?
High / moderate video quality of source video?
Much / little movement in the source video?
High / moderate audio quality of source video?
For example, plan a higher bit rate for audio quality than video quality for a television interview. In contrast, for a complex documentary that requires a lot of movement, plan for a higher bit rate for video quality than for audio quality.
With this approach, you can distribute bitrates sensibly up front and save storage space if necessary. If you often have to do with web video encoding, we recommend that you use a checklist that you can work with on the corresponding video and audio prioritizations.






