Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v26 1/9] avcodec/evc_parser: Added parser implementation for EVC format
Date: Thu, 15 Jun 2023 12:01:35 -0300
Message-ID: <d11fde9b-2f1e-6530-0782-e98e5add65bd@gmail.com> (raw)
In-Reply-To: <20230615114643.635-1-d.kozinski@samsung.com>

On 6/15/2023 8:46 AM, Dawid Kozinski wrote:
> - Added constants definitions for EVC parser
> - Provided NAL units parsing following ISO_IEC_23094-1
> - EVC parser registration
> 
> Signed-off-by: Dawid Kozinski <d.kozinski@samsung.com>
> ---
>   configure               |   2 +
>   libavcodec/Makefile     |   2 +
>   libavcodec/evc.h        | 155 ++++++++
>   libavcodec/evc_parse.c  | 767 ++++++++++++++++++++++++++++++++++++++++
>   libavcodec/evc_parse.h  | 357 +++++++++++++++++++
>   libavcodec/evc_parser.c | 235 ++++++++++++
>   libavcodec/parsers.c    |   1 +
>   7 files changed, 1519 insertions(+)
>   create mode 100644 libavcodec/evc.h
>   create mode 100644 libavcodec/evc_parse.c
>   create mode 100644 libavcodec/evc_parse.h
>   create mode 100644 libavcodec/evc_parser.c

I have pushed patches 1-3 and 6-9. I want to look at the decoder and 
encoder patches a bit more before applying them.
I'll also send a patchset with some fixes in a bit.

Thanks.
_______________________________________________
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".

      reply	other threads:[~2023-06-15 15:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230615114653eucas1p2cf47c740971323ba92f3873f4206d982@eucas1p2.samsung.com>
2023-06-15 11:46 ` Dawid Kozinski
2023-06-15 15:01   ` James Almer [this message]

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=d11fde9b-2f1e-6530-0782-e98e5add65bd@gmail.com \
    --to=jamrial@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    /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