From 1fd122380754c6241e2fc3f07f11c1492a6cd3f2 Mon Sep 17 00:00:00 2001 From: Kiriti Gowda Date: Fri, 9 Feb 2024 10:38:31 -0800 Subject: [PATCH] decodingPipeline.md - update Fix Image --- docs/tutorial/decodingPipeline.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tutorial/decodingPipeline.md b/docs/tutorial/decodingPipeline.md index b3b9e61c15..0321891c49 100644 --- a/docs/tutorial/decodingPipeline.md +++ b/docs/tutorial/decodingPipeline.md @@ -1,6 +1,6 @@ # Video decoding pipeline -

+

There are three main components in the rocDecode shown in the figure above: Demuxer, Video Parser APIs, and Video Decode APIs. The Demuxer is based on FFMPEG. The demuxer extracts a segment of video data and sends it to the Video Parser. The parser then extracts crucial information such as picture and slice parameters, which is then sent to the Decoder APIs. These APIs submit the information to the hardware for the decoding of a frame. This process repeats in a loop until all frames have been decoded. @@ -15,4 +15,4 @@ Steps in decoding video content for applications (available in rocDecode Toolkit 6. Execute HIP kernels in the mapped YUV frame (e.g., format conversion, scaling, object detection, classification, etc.) 7. Un-map decoded HIP YUV frame. -The above steps are demonstrated in the sample applications included in the repository. \ No newline at end of file +The above steps are demonstrated in the sample applications included in the repository.