Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: TADANO Tokumei <aimingoff@pc.nifty.jp>
To: ffmpeg-devel@ffmpeg.org
Cc: TADANO Tokumei <aimingoff@pc.nifty.jp>
Subject: [FFmpeg-devel] [PATCH v3 0/1] lavfi/vf_gopromax_opencl: add GoPor Max 360 video filter
Date: Mon, 29 Jul 2024 19:47:21 +0900
Message-ID: <20240729104722.330900-1-aimingoff@pc.nifty.jp> (raw)

This is updated patch of:
https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=3943
I contacted to Ronan LE MEILLAT and agreed with him to submit new patch.

Abstruct of GoPro Max .360 video file format is described in:
https://gopro.com/news/max-tech-specs-stitching-resolution

The specification is little bit buggy.
The format is based on EAC (Equi-Angular Cubemap), and there are overlapped
pixels at boundaries of front and rear cams.
Probably, the desinger intended to add 2 x 32 (= total 64) ovelapped pixels.
But actual format has 2 x 64 pixels overlapped area.
Thus the width will be 2 x 32 pixels shorter than standard EAC format after
blending overlapped area.

This filter blends overlapped area, stretches the width of the cube,
and combine two streams into single stream with standard format.

v3 modifies `configure` file to add dependency on opencl.

TADANO Tokumei (1):
  lavfi/vf_gopromax_opencl: add GoPro Max 360 video filter

 configure                        |   1 +
 doc/filters.texi                 |  78 +++++++
 libavfilter/Makefile             |   2 +
 libavfilter/allfilters.c         |   1 +
 libavfilter/opencl/gopromax.cl   | 280 ++++++++++++++++++++++++
 libavfilter/opencl_source.h      |   1 +
 libavfilter/vf_gopromax_opencl.c | 351 +++++++++++++++++++++++++++++++
 7 files changed, 714 insertions(+)
 create mode 100644 libavfilter/opencl/gopromax.cl
 create mode 100644 libavfilter/vf_gopromax_opencl.c

-- 
2.39.2

_______________________________________________
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:[~2024-07-29 10:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 10:47 TADANO Tokumei [this message]
2024-07-29 10:47 ` [FFmpeg-devel] [PATCH v3 1/1] lavfi/vf_gopromax_opencl: add GoPro " TADANO Tokumei

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=20240729104722.330900-1-aimingoff@pc.nifty.jp \
    --to=aimingoff@pc.nifty.jp \
    --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