#10577: add support for ay10 pixel format
-------------------------------------+-----------------------------------
             Reporter:  micolous     |                    Owner:  (none)
                 Type:  enhancement  |                   Status:  new
             Priority:  normal       |                Component:  swscale
              Version:  git-master   |               Resolution:
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-----------------------------------
Description changed by micolous:

Old description:

> `ay10` is used by a bunch of ATEM video switchers for still image frames.
> It's a bit-packed (non-planar) variant of `yuva422p10` (similar to
> `y210`?), where every two pixels are stored in two big-endian `uint32`s,
> with 4:2:2 subsampling:
>
> `(msb)2_ 10A 10U 10Y(lsb)` `(msb)2_ 10A 10V 10Y(lsb)`
>
> I will attach a sample frame to this ticket once created.
>
> The frames don't come in any proper container format – but they are
> normally transferred with run-length encoding. I've unrolled the attached
> frame and compressed it in a more "traditional" format.
>
> The naming is just what their software calls it. I don't work for
> Blackmagic Design, so I don't have any insight or influence into that. :)
>
> I've attempted to write a patch for this, which I'll also attach.
> Unfortunately, `git send-email` doesn't seem to work with
> OAuth2-authenticated IMAP/SMTP servers – it relies on application-
> specific passwords, which are an unacceptably-large security hole for
> 2023. :)

New description:

 `ay10` is used by a bunch of ATEM video switchers for still image frames.
 It's a bit-packed (non-planar) variant of `yuva422p10` (similar to
 `y210`?), where every two pixels are stored in two big-endian `uint32`s,
 with 4:2:2 subsampling:

 `(msb)2_ 10A 10U 10Y(lsb)` `(msb)2_ 10A 10V 10Y(lsb)`

 I will attach a sample frame to this ticket once created.

 The frames don't come in any proper container format – but they are
 normally transferred with run-length encoding. I've unrolled the attached
 frame and compressed it in a more "traditional" format.

 The naming is just what their software calls it. I don't work for
 Blackmagic Design, so I don't have any insight or influence into that. :)

 I've attempted to write a patch for this (it's currently broken), which
 I'll also attach. Unfortunately, `git send-email` doesn't seem to work
 with OAuth2-authenticated IMAP/SMTP servers – it relies on application-
 specific passwords, which are an unacceptably-large security hole for
 2023. :)

--
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/10577#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Reply via email to