Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Soham Kute via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: sw@jkqxz.net, jamrial@gmail.com, d.frankiewicz@samsung.com,
	michael@niedermayer.cc, Soham Kute <officialsohamkute@gmail.com>
Subject: [FFmpeg-devel] [GSoC 2026] APV Hardware Acceleration, VideoToolbox & VAAPI, - Interest & Mentor Request
Date: Mon, 23 Feb 2026 00:25:05 +0530
Message-ID: <CAFxoRw35vv0Y7vyH4743b=z9RyWDNVO42DpvLJ-0rr=J-Rf9AQ@mail.gmail.com> (raw)

Hello FFmpeg developers,

My name is Soham Kute. I am a pre-final year undergraduate student at
Veermata Jijabai Technological Institute (VJTI), Mumbai. I am writing
to express interest in GSoC 2026 with FFmpeg and to discuss a project
I have been studying.

I enjoy reading codec specifications, finding edge case bugs in decoders,
and understanding how bitstream parsing maps to actual implementation.
This is what drew me to FFmpeg.

Project Idea:

I would like to propose implementing hardware accelerated decoding for
the APV (Advanced Professional Video) codec, specifically targeting
Apple VideoToolbox (macOS/iOS) and Intel/AMD VAAPI (Linux).

APV's native software decoder (apv_decode.c) and liboapv based encoder
were merged in FFmpeg 8.0. However, no hwaccel path exists yet no
videotoolbox_apv.c, no vaapi_apv.c, no hwaccels.h declaration, and no
configure entry for any hardware target. Given that Google has adopted
OpenAPV for Android 16 and Samsung cameras already record in APV.

Technical Approach:

I have studied videotoolbox_av1.c and vaapi_av1.c as templates and
understand the full implementation path:

  VideoToolbox:
  - ff_videotoolbox_apvc_extradata_create() using CBS-parsed
    APVRawFrameHeader fields (profile_idc, chroma_format_idc,
    bit_depth_minus8) from the existing cbs_apv.c infrastructure.
  - Tile accumulation in decode_slice, mirroring AV1 tile_group handling.
  - CVPixelBuffer mappings for 4:2:2 and 4:4:4 at 10-bit and 12-bit.

  VAAPI:
  - Profile/entrypoint probing via vaQueryConfigProfiles().
  - VAPictureParameterBufferAPV + VAIQ atrixBufferAPV from CBS frame header.
  - Per-tile VASliceParameterBufferAPV submission loop.

Qualification Task:

I understand that completing a qualification patch is a prerequisite
for GSoC consideration. I would appreciate guidance from the mentors
on an appropriate task,  whether that is a robustness fix in the
existing APV decoder, an improvement to the CBS APV infrastructure,
or any other area the mentors feel would best demonstrate readiness
for this project.

I am ready to start immediately.

Mentor Request:

I would like to request that Mark Thompson consider mentoring this project,
given his authorship of the native APV decoder and expertise in FFmpeg
hardware acceleration. I have also CC'd James Almer (APV encoder and parser
co-author) and Dariusz Frankiewicz from Samsung Electronics.

If the scope needs adjustment or if I have misunderstood any aspect of
the APV hwaccel design, I would very much welcome feedback before the
application deadline.

I am subscribed to ffmpeg-devel and active on #ffmpeg-devel (Libera.chat)
as SohamK.

Thank you for your time.

Best regards,
Soham Kute
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

             reply	other threads:[~2026-02-24 21:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-22 18:55 Soham Kute via ffmpeg-devel [this message]
2026-02-22 19:09 Soham Kute via ffmpeg-devel

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='CAFxoRw35vv0Y7vyH4743b=z9RyWDNVO42DpvLJ-0rr=J-Rf9AQ@mail.gmail.com' \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=d.frankiewicz@samsung.com \
    --cc=jamrial@gmail.com \
    --cc=michael@niedermayer.cc \
    --cc=officialsohamkute@gmail.com \
    --cc=sw@jkqxz.net \
    /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