From 0c6dc2d487bef23ec4f80a007f5fd5d3e610f920 Mon Sep 17 00:00:00 2001 From: MysticExile <30736337+MysticExile@users.noreply.github.com> Date: Fri, 4 Dec 2020 01:53:27 +0100 Subject: [PATCH] Undo fuck up --- site/content/entry/yuzu-mini-dev-3/index.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/site/content/entry/yuzu-mini-dev-3/index.md b/site/content/entry/yuzu-mini-dev-3/index.md index bd07cd1e..5bfe2f6a 100644 --- a/site/content/entry/yuzu-mini-dev-3/index.md +++ b/site/content/entry/yuzu-mini-dev-3/index.md @@ -67,13 +67,14 @@ In order to decode VP9, I needed the frame data along with a "compressed" and "u The Switch GPU provided me with the frame data, but the headers needed to be manually constructed based on meta data provided by the GPU. I found myself spending countless hours reading the VP9 specification, and analyzing the video frame-by-frame in a tool that displays each frame's headers. Ultimately, it paid off, and many VP9 videos are decoded accurately. -{{< imgs - "./ssbu_2.mp4| Footage of Super Smash Bros. Ultimate's intro video early in development." - >}} + **Q: Quite the task I imagine. Why did you opt for the FFMpeg library instead of other alternatives?** -**E:** [FFmpeg](https://ffmpeg.org/) was kind of a no-brainer. It's fast, it's open sourced, and it's well documented. It handles decoding with little effort on the programmer's part. +**E:** FFmpeg was kind of a no-brainer. It's fast, it's open sourced, and it's well documented. It handles decoding with little effort on the programmer's part. It also provides API's to re-scale and convert video formats, which proved to be useful. The other alternative would have been writing my own software decoder from scratch, but there's no point in reinventing the wheel!