Windows > Third Party Plug-ins, Programs, and Skins
Blackmagic decklink Capture Filter Testing
mattkhan:
your log is dotted with lines like this
--- Code: ---19:31:39.674156592 [7632] bmcapture.cpp:779 LOG_WARNING filter [BlackmagicCaptureFilter] Video capture discontinuity detected, 1 frames missed at frame 292
--- End code ---
I suspect it explains the motion problem, it's a function of the need to convert the format of every single frame received. I didn't expect to need to do this & for it to be so slow so I'm doing it in the wrong place atm. A subsequent release should fix this (but that is a bit more involved so will take some days to get done)
claw:
--- Quote from: mattkhan on April 19, 2025, 02:49:29 pm ---your log is dotted with lines like this
--- Code: ---19:31:39.674156592 [7632] bmcapture.cpp:779 LOG_WARNING filter [BlackmagicCaptureFilter] Video capture discontinuity detected, 1 frames missed at frame 292
--- End code ---
I suspect it explains the motion problem, it's a function of the need to convert the format of every single frame received. I didn't expect to need to do this & for it to be so slow so I'm doing it in the wrong place atm. A subsequent release should fix this (but that is a bit more involved so will take some days to get done)
--- End quote ---
Yes, still have the motion issue. Also maybe related is that I have to set 450 ms audio delay in my AVR. Audio is split out by HDfury VRROOM before sending to capture card.
Good progress, though.
mattkhan:
--- Quote from: claw on April 19, 2025, 02:55:22 pm ---Yes, still have the motion issue. Also maybe related is that I have to set 450 ms audio delay in my AVR. Audio is split out by HDfury VRROOM before sending to capture card.
--- End quote ---
fwiw, based on what I've seen, I'd expect a decklink card to be delayed somewhat relative to a magewell card in the same system for 2 reasons.... 1) the magewell sdk provides a low latency mode which means it should take less time to capture a frame, 2) decklink supports a v limited set of formats which require conversion (done on the cpu) before handing them to the renderer
overall i would think it means higher cpu usage & need to handle a somewhat larger delay vs a magewell card (but they're generally a fair bit cheaper so....)
claw:
--- Quote from: mattkhan on April 19, 2025, 03:11:09 pm ---fwiw, based on what I've seen, I'd expect a decklink card to be delayed somewhat relative to a magewell card in the same system for 2 reasons.... 1) the magewell sdk provides a low latency mode which means it should take less time to capture a frame, 2) decklink supports a v limited set of formats which require conversion (done on the cpu) before handing them to the renderer
overall i would think it means higher cpu usage & need to handle a somewhat larger delay vs a magewell card (but they're generally a fair bit cheaper so....)
--- End quote ---
I am using a less powerful PC for the DeckLink installation. An i5 instead of i7, and an RTX2080Ti instead of a 3080Ti.
Hendrik:
--- Quote from: mattkhan on April 19, 2025, 02:45:52 pm ---interesting that it reports HDR10, never seen that before
@Hendrik what triggers JRVR to show that?
--- End quote ---
Its just the PQ transfer. 0 nits means a lack of static metadata.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version