Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
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>
Subject: Re: [FFmpeg-devel] APV codec with OpenAPV support
Date: Tue, 22 Apr 2025 09:58:45 -0100
Message-ID: <CABGuwEmCjQRc0RgW00UZUmhakmUzJdfMZHnE1qAw8FPESuLcEg@mail.gmail.com> (raw)
In-Reply-To: <000001dbb373$824dcf70$86e96e50$@samsung.com>

On Tue, 22 Apr 2025, 09:44 , <d.frankiewic@samsung.com> wrote:

> Hi,
>
>
>
> I'm Dariusz from Samsung Electronics, you can know me from last VDD in
> Korea, I was presenting APV.
>
>
>
> I'm glad that Mark created native APV decoder. As you might know we're also
> working on APV implementation for FFmpeg.
>
> Our approach is different from yours but they can exist in FFmpeg in
> parallel. We're using external library OpenAPV for encoding and decoding:
> https://github.com/AcademySoftwareFoundation/openapv
>
> This OpenAPV implementation will be also used by Google in next Android 16:
> https://developer.android.com/about/versions/16/features#apv
>
> In our approach we have implemented: encoding, decoding and mp4 muxing.
> Today we will send patches.
>
>
>
> So I think now it's a good moment to review both implementations and
> integrate them in parallel in FFmpeg.
>
>
>
> What's your opinion about that?
>
>
>
> Regards,
>
> Dariusz
>

Hi Dariusz,

The general "policy" is that external libraries are not used if we already
have a native implementation. Unless that native library has capabilities
(e.g encoding in this case) that we don't have.

Regards,
Kieran Kunhya

>
_______________________________________________
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:[~2025-04-22 10:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250422104422eucas1p27648689ef0681426b08b047ab9fb185f@eucas1p2.samsung.com>
2025-04-22 10:44 ` d.frankiewic
2025-04-22 10:58   ` Kieran Kunhya via ffmpeg-devel [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=CABGuwEmCjQRc0RgW00UZUmhakmUzJdfMZHnE1qAw8FPESuLcEg@mail.gmail.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=kieran618@googlemail.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