From: Michael Riedl <michael.riedl@nativewaves.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] libavdevice/decklink: extend available actions on signal loss
Date: Thu, 2 Nov 2023 16:42:43 +0100
Message-ID: <e272677c-9bad-4d9d-9450-ae3d298543fd@nativewaves.com> (raw)
In-Reply-To: <CAHGibzGj=MEptmMCTk=E-ipVeFOiwthJJsDgevpcSbKnFs_ttQ@mail.gmail.com>
> Hi Michael,
>
> I haven't tried your patch, but a quick review suggests that while
> you've declared the option as deprecated that it no longer works.
> Presumably somewhere in there should be a line of code that says
> something like "if (ctx->draw_bars == 0) then ctx->signal_loss_action
> = SIGNAL_LOSS_NONE"
>
> Even though the option is deprecated, it should still continue to work
> until it is completely removed.
>
> Devin
Hi Devin,
thank you for reviewing.
I just tested the code again and can confirm that the old option draw_bars still
works as intended (as describe in the table below). If the users explicitly uses
"-draw_bars false" then we set signal_loss_action to SIGNAL_LOSS_NONE (if the
option was not set by the user) and emit a deprecation warning to the user. If
the users leaves draw_bars to the default value, the option signal_loss_action
has priority.
I think this is the best solution for now that keeps the old behavior and allows
us to remove the option in the future.
| draw_bars | signal_loss_action | new action |
| -------------- | ------------------ | -------------- |
| true (default) | bars (default) | bars |
| true (default) | none | none |
| true (default) | repeat | repeat |
| false | bars (default) | none |
| false | none | none |
| false | repeat | conflict error |
_______________________________________________
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:[~2023-11-02 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 11:58 Michael Riedl
2023-11-02 13:01 ` Michael Riedl
2023-11-02 14:14 ` Devin Heitmueller
2023-11-02 15:42 ` Michael Riedl [this message]
2023-11-28 9:22 ` Michael Riedl
2023-11-28 15:48 ` Devin Heitmueller
2024-01-09 10:08 ` Michael Riedl
2024-03-05 8:03 ` Michael Riedl
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=e272677c-9bad-4d9d-9450-ae3d298543fd@nativewaves.com \
--to=michael.riedl@nativewaves.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