Lesson plan
Lagarith
Lagarith is an open source lossless video codec written by Ben Greenwood. It is a fork of the code of HuffYUV and offers better compression at the cost of greatly reduced speed on uniprocessor systems. Lagarith was designed and written with a few aims in mind: ;Speed: While not as fast as HuffYUV, it still outperforms most other lossless video codecs when it comes to encoding times, although decoding speed may be slower. Recent versions also support parallelizing on multi-processor systems. ;Color-space support: Color-space conversions can cause rounding errors, introducing data loss, contrary to the ideal of lossless video compression. Lagarith attempts to avoid this problem by supporting YV12, YUY2, RGB, and RGBA colorspaces. ;Keyframes: Disallowing inter-prediction means that each frame can be separately decoded. This makes cutting, joining and seeking much easier. These three things, as well as being more efficient at compression than HuffYUV, make it editing stage.
Article summary
Lagarith is an open source lossless video codec written by Ben Greenwood. It is a fork of the code of HuffYUV and offers better compression at the cost of greatly reduced speed on uniprocessor systems. Lagarith was designed and written with a few aims in mind: ;Speed: While not as fast as HuffYUV, it still outperforms most other lossless video codecs when it comes to encoding times, although decoding speed may be slower. Recent versions also support parallelizing on multi-processor systems. ;Color-space support: Color-space conversions can cause rounding errors, introducing data loss, contrary to the ideal of lossless video compression. Lagarith attempts to avoid this problem by supporting YV12, YUY2, RGB, and RGBA colorspaces. ;Keyframes: Disallowing inter-prediction means that each frame can be separately decoded. This makes cutting, joining and seeking much easier. These three things, as well as being more efficient at compression than HuffYUV, make it editing stage.
Key claims
No claims recorded.
Discussion questions
- Summarise the article in your own words. Which single claim would you verify first, and why?
- Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
- If two sources disagreed about one of these facts, what would you need in order to trust one over the other?
Bibliography
No sources recorded.
Key claims and bibliography are generated from the same tracked claims and sources as the article page.