Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Up to Date DeckLink Support broken in FFMPEG
Date: Thu, 6 Feb 2025 21:16:40 +0100 (CET)
Message-ID: <ce7fad73-59b5-788f-0363-20509dd1dca8@passwd.hu> (raw)
In-Reply-To: <d0349a39-aa22-47a1-a575-d7775125da76@gmail.com>



On Wed, 5 Feb 2025, Leo Izen wrote:

> On 2/5/25 4:44 PM, ffmpeg@gallery.co.uk wrote:
>>  Hi Folks
>>
>>  It seems like the current decklink code in FFMPEG is no longer fully
>>  compatible with the latest Decklink drivers
>>  The behaviour seen is that output via DeckLink starts OK but very quickly
>>  stalls. Apparently its related to the callbacks.
>>  I believe this broken with BMD drivers 13.3 and later
>>
>>  Has anyone here already fixed the FFMPEG code to work again ?
>>
>>  If no-one has attempted this fix, I will give it a go, but if someone is
>>  ahead of me please let me know
>>
>>  Thanks !!!
>>
>>  Mark.
>> 
>
> Feel free to take a look. The last change to the decklink code in FFmpeg was 
> authored last april (not counting minor one-line bugfixes and the like) and 
> as far as I am aware nobody is currently working on that so you wouldn't be 
> redoing someone else's work.

There is a patch linked in the blackmagic forums:

https://forum.blackmagicdesign.com/viewtopic.php?f=12&t=213592

Regards,
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".

  parent reply	other threads:[~2025-02-06 20:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 21:44 ffmpeg
2025-02-05 22:39 ` Leo Izen
2025-02-05 22:46   ` Marth64
2025-02-06 20:16   ` Marton Balint [this message]
2025-02-06 20:55     ` Devin Heitmueller

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=ce7fad73-59b5-788f-0363-20509dd1dca8@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