On 5/15/24, 5:59 AM, "ffmpeg-devel on behalf of Michael Niedermayer"
mailto:ffmpeg-devel-boun...@ffmpeg.org> on
behalf of mich...@niedermayer.cc <mailto:mich...@niedermayer.cc>> wrote:
On Wed, May 01, 2024 at 09:10:51PM +, Tom Vaughan wrote:
> When I attempt to pas
3324.81
x265 [info]: frame P:318, Avg QP:35.26 kb/s: 21643.30
x265 [info]: frame B: 1091, Avg QP:37.73 kb/s: 8003.99
x265 [info]: Weighted P-Frames: Y:11.6% UV:9.4%
encoded 1439 frames in 937.04s (1.54 fps), 11962.94 kb/s, Avg QP:37.09
Tom Vaughan
__
Any further details you or others could provide to help the x265 dev team
resolve the issue would be appreciated.
Can you share your steps to reproduce this issue? What parameters were changed?
Max CTU size?
Is this documentation inadequate?
https://x265.readthedocs.io/en/master/api.html#build
Soft Works said... "the CC data needs to get into the video frames - so that it
exists as input to the video encoder.
For the same reason, it is also not possible to add CCs at the muxer level. It
always requires video encoding because the data needs to get into the video
stream itself, so there
sage-
> From: ffmpeg-devel <mailto:ffmpeg-devel-boun...@ffmpeg.org>> On Behalf Of Tom
> Vaughan
> Sent: Friday, February 7, 2025 7:36 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org <mailto:de...@ffmpeg.org>>
> Subject: Re: [FFmpeg-devel] Cap
I'm excited to see this discussion. There are many leading video distributors
(streaming services, etc.) that would love to see solid support in FFMPEG for
closed captions. No promises, but my sense is that additional money can be
raised to sponsor this development.
WebVTT as a sidecar captions
video stream for the full A/53 Part 4 dataset will be required.
Zach
On Sun, Feb 9, 2025 at 6:03 AM Devin Heitmueller <
devin.heitmuel...@ltnglobal.com <mailto:devin.heitmuel...@ltnglobal.com>> wrote:
> On Sat, Feb 8, 2025 at 10:39 PM Tom Vaughan <mailto:t...@tvaughan.com&
