From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Kieran Kunhya <kieran618@googlemail.com>,
Romain Beauxis <romain.beauxis@gmail.com>
Subject: Re: [FFmpeg-devel] [PATCH v0] Implement promeg decoder.
Date: Wed, 22 Jan 2025 17:03:03 +0000
Message-ID: <CABGuwEnRpA77Jen-M+WbhmrydDSG3myXS52dhdShkjbSoyUDvQ@mail.gmail.com> (raw)
In-Reply-To: <20250116200826.33624-1-romain.beauxis@gmail.com>
On Thu, Jan 16, 2025 at 8:15 PM Romain Beauxis <romain.beauxis@gmail.com> wrote:
>
> This patch implements the decoding logic for the FEC error-
> correction method described in the Pro-MPEG CoP #3-R2 FEC[1]
>
> We are still in the process of testing this patch with our encoders but
> I wanted to send it now in case it could use some early review.
>
> The code seems clean enough and straight forward:
> * The decoder stores packet using their index.
> * Packets relevant to the decoding of the current packet are kept,
> using the received row and column FEC packets to determine the FEC
> matrix within with the current packet belongs to.
> * Beside that, the decoder keeps a maximum number of packets and FEC
> packets.
I don't see any evidence of wraparound handling unless I miss
something. An FEC matrix can span a wraparound.
Kieran
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-01-22 17:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250116200826.33624-1-romain.beauxis@gmail.com>
[not found] ` <CABGuwEnazYSuZj5DDDg4T57Qp6jtM8puA7zE=pnq1kC3gCa04Q@mail.gmail.com>
[not found] ` <CABWZ6OQLiA-g_+2YaEqrTDuT0PShLQcDtu4ihKUeiEzf9joPRg@mail.gmail.com>
[not found] ` <CABGuwEkSD7hTNKVhwU_OXJ6Zku20OtdL=VqK2a4uDQATVYi90g@mail.gmail.com>
[not found] ` <CABWZ6OQeQNGy2o40L=-xLm=JhZVNNsbYm=w6ynUfovrMB4co9w@mail.gmail.com>
[not found] ` <CABGuwEk62V+yucDsv=yxKADwgk5d3snX2hX=Jg9SjPCb5RxXVw@mail.gmail.com>
[not found] ` <CABGuwE=u91r5E+jq=6dMp=hCiM03T-V67ejpqffhBFMC3QfSzQ@mail.gmail.com>
[not found] ` <CABWZ6OQOEmmVxDc8S5T6F1P9GAdUXRJ_GYNrbfjyqQjqR6viiw@mail.gmail.com>
2025-01-18 2:22 ` Kieran Kunhya via ffmpeg-devel
[not found] ` <a129ff9f-6472-40a9-900f-cf58e133799b@gmail.com>
[not found] ` <Z4psWx-rzcXuLu1Y@phare.normalesup.org>
[not found] ` <082f12b8-2319-47d2-8854-f361d2039748@gmail.com>
2025-01-20 14:30 ` Nicolas George
2025-01-20 15:07 ` James Almer
2025-01-20 16:22 ` Marth64
2025-01-21 22:16 ` Romain Beauxis
2025-01-22 20:36 ` Nicolas George
[not found] ` <CABGuwEmJbZwGTtn6AtttqYDPpgowuYm-3dX0OrJWs07cr-4usQ@mail.gmail.com>
[not found] ` <20250117170823.GM4991@pb2>
[not found] ` <CAHGibzFvmw6EjUMhym29AWhEOkgK7ReuWDiWwzC-+csQr-T1GQ@mail.gmail.com>
2025-01-19 22:22 ` Michael Niedermayer
2025-01-20 6:05 ` Kieran Kunhya via ffmpeg-devel
2025-01-20 6:46 ` Kieran Kunhya via ffmpeg-devel
2025-01-22 15:33 ` Michael Niedermayer
2025-01-22 16:29 ` Kieran Kunhya via ffmpeg-devel
2025-01-22 16:53 ` Romain Beauxis
2025-01-22 16:57 ` Kieran Kunhya via ffmpeg-devel
2025-01-20 14:48 ` Nicolas George
[not found] ` <CABGuwE=Xza3-Jisr1U3AEtLAh2yLLWofsLC+Hbwc_4c1QjLtYA@mail.gmail.com>
[not found] ` <20250117170321.GL4991@pb2>
[not found] ` <CABGuwEndw2y1cLi-rTnYD1teWuTfd7YCr9_mQkgggqAa0e4jbA@mail.gmail.com>
2025-01-20 14:50 ` Nicolas George
2025-01-20 15:00 ` Kieran Kunhya via ffmpeg-devel
2025-01-22 16:36 ` Michael Niedermayer
2025-01-22 16:55 ` Kieran Kunhya via ffmpeg-devel
2025-01-22 16:59 ` Kieran Kunhya via ffmpeg-devel
2025-01-22 17:09 ` Kieran Kunhya via ffmpeg-devel
2025-01-22 17:03 ` Kieran Kunhya via ffmpeg-devel [this message]
2025-01-23 18:01 ` Romain Beauxis
2025-01-23 18:31 ` Kieran Kunhya via ffmpeg-devel
2025-01-24 18:14 ` Romain Beauxis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABGuwEnRpA77Jen-M+WbhmrydDSG3myXS52dhdShkjbSoyUDvQ@mail.gmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=kieran618@googlemail.com \
--cc=romain.beauxis@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git