From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] Add float user_rdiv[4] to allow user options to apply correctly
Date: Sun, 25 Feb 2024 03:03:55 +0100 (CET)
Message-ID: <ebe71f8a-17e0-a2bd-151a-9d995e386dc3@passwd.hu> (raw)
In-Reply-To: <CAHpaCCg8jMWSFXN9g0zf219duOu3L521Uas67ftjJS8VFHfEPA@mail.gmail.com>
On Sat, 24 Feb 2024, Stone Chen wrote:
> On Sat, Feb 24, 2024 at 6:34 PM Marton Balint <cus@passwd.hu> wrote:
>
>>
>>
>> On Sat, 24 Feb 2024, Stone Chen wrote:
>>
>>> On Sat, Feb 24, 2024 at 3:56 PM Marton Balint <cus@passwd.hu> wrote:
>>>
>>>>
>>>>
>>>> On Sat, 24 Feb 2024, Stone Chen wrote:
>>>>
>>>>> Previously to support dynamic reconfigurations of the matrix string
>>>> (e.g. 0m), the rdiv values would always be cleared to 0.f, causing the
>> rdiv
>>>> to be recalculated based on the new filter. This however had the side
>>>> effect of always ignoring user specified rdiv values.
>>>>>
>>>>> Instead float user_rdiv[0] is added to ConvolutionContext which will
>>>> store the user specified rdiv values. Then the original rdiv array will
>>>> store either the user_rdiv or the automatically calculated 1/sum.
>>>>>
>>>>> This fixes trac #10294, #10867
>>>>
>>>> Have you tested?
>>>>
>>>> Thanks,
>>>> Marton
>>>>
>>>
>>>
>>> Hi Marton,
>>>
>>> Yes I've tested that
>>>
>>> - the original behavior works (automatically calculate rdiv if
>> user_rdiv
>>> = 0)
>>> - setting the rdiv value works
>>
>> It does not work for me even after applying your patch.
>>
>> Regards,
>> Marton
>>
>
> Hi Marton,
>
> Sorry about that, was it with the attached patch in the second email? I had
> botched my initial patch, I've re-attached the second to this email.
Oh, sorry, I missed that the second patch is different. Use versions in
email subjects, such as [PATCH v2] for new versions of the same patch.
Looking good now, will apply.
Thanks,
Marton
_______________________________________________
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".
prev parent reply other threads:[~2024-02-25 2:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3601973235488930945@unknownmsgid>
2024-02-24 15:49 ` Stone Chen
2024-02-24 16:16 ` Stone Chen
2024-02-24 20:56 ` Marton Balint
2024-02-24 22:09 ` Stone Chen
2024-02-24 23:34 ` Marton Balint
2024-02-25 0:02 ` Stone Chen
2024-02-25 2:03 ` Marton Balint [this message]
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=ebe71f8a-17e0-a2bd-151a-9d995e386dc3@passwd.hu \
--to=cus@passwd.hu \
--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