From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avfilter/vf_subtitles: pass storage size to libass
Date: Tue, 22 Mar 2022 13:45:20 -0300
Message-ID: <147fd7d8-a587-dca3-cef1-62a75fcd293b@gmail.com> (raw)
In-Reply-To: <DM8P223MB03656E6A5ABA475DC4F59F32BA179@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
On 3/22/2022 1:42 PM, Soft Works wrote:
>
>
>> -----Original Message-----
>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
>> Oneric
>> Sent: Tuesday, March 22, 2022 5:28 PM
>> To: FFmpeg development discussions and patches <ffmpeg-
>> devel@ffmpeg.org>
>> Subject: Re: [FFmpeg-devel] [PATCH] avfilter/vf_subtitles: pass
>> storage size to libass
>>
>> On Mon, Mar 14, 2022 at 20:06:39 +0100, Oneric wrote:
>>> Due to a quirk of the ASS format some tags depend on the exact
>> storage
>>> resolution of the video, so tell libass via ass_set_storage_size.
>>> [...]
>>
>> On Mon, Mar 14, 2022 at 20:21:47 +0000, Soft Works wrote:
>>> [...]
>>>
>>> Ah, alright, the blur setting goes deeper. Thanks for the
>> explanation.
>>>
>>> LGTM, then!
>>
>>
>> ping
>
> It's not on me. I would have merged it, but I don't have push
> permissions.
>
> softworkz
Will apply it unless someone is against it.
_______________________________________________
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".
next prev parent reply other threads:[~2022-03-22 16:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 19:06 Oneric
2022-03-14 19:35 ` Soft Works
2022-03-14 19:49 ` Oneric
2022-03-14 19:57 ` Soft Works
2022-03-14 20:07 ` Oneric
2022-03-14 20:21 ` Soft Works
2022-03-22 16:27 ` Oneric
2022-03-22 16:42 ` Soft Works
2022-03-22 16:45 ` James Almer [this message]
2022-03-23 20:26 ` Oneric
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=147fd7d8-a587-dca3-cef1-62a75fcd293b@gmail.com \
--to=jamrial@gmail.com \
--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