I still have te same issue with a black magic capture card.Sorry for the late answer. We fixed this issue in 3.2.
It's a windows 10 system based on i5 with gtx1050ti."keep camera running" means that even if the camera is not shown on any surface or preview, MadMapper will not stop the video streaming / decompression process, so it's always running and ready to use, without waiting for half a second for the capture process to start in the driver/hardware. So it won't help.
How long does it take to freeze ?
Can you tell us your setup ? Which Blackmagic device, OS version, MadMapper version etc.
Does it happen it you let BlackMagic Media Express running for the same amount of time ?
I have the latest drivers.I'm starting tests with a blackmagic card right now.
Be sure you are up to date with BlackMagic Desktop Video
I'm not using demo, i'm using demo on my Macpro. (running 3 or 4 licenses on 6 or 8 pc's i've kind of lost track )When it freezes, is it only the backmagic, or is it all the outputs ? You are using demo version right ? Why not using 3.3.1 ?
Done all of that, but it seems to freeze somewhere between 10 and 19 hours.I've been running a test on Windows with PCI card Intensity Pro for 72 hours without problem. Since the API calls are the same whatever the device, MadMapper seems to handle the API correctly and the issue .
Your issue with BlackMagic is not related to the original issue of this thread, which was related to cameras handled with DirectShow API (part of DirectX), bug that we fixed since.
BlackMagic devices are handled with BlackMagic Video SDK, a native implementation, except if you unchecked "Enable BlackMagic devices" in MadMapper Preferences / Misc.
Is it running for a long time if you let BlackMagic Media Express capture the stream for a few hours ?
I don't know how OBS handles BlackMagic. However I think of another possible issue: on macOS only one application can open the SDK, on Windows it's different. I had BlackMagic Media Express running and capturing my stream and when I started MadMapper, Media Express stopped and MadMapper could display the stream. So be sure you don't start any other application that uses BlackMagic SDK or even a BlackMagic Direct Show filter. Basically you should test running just MadMapper and doing nothing else on the machine.
Did the test with a inogeni 4k capture card and this thing works like a charm!Done all of that, but it seems to freeze somewhere between 10 and 19 hours.I've been running a test on Windows with PCI card Intensity Pro for 72 hours without problem. Since the API calls are the same whatever the device, MadMapper seems to handle the API correctly and the issue .
Your issue with BlackMagic is not related to the original issue of this thread, which was related to cameras handled with DirectShow API (part of DirectX), bug that we fixed since.
BlackMagic devices are handled with BlackMagic Video SDK, a native implementation, except if you unchecked "Enable BlackMagic devices" in MadMapper Preferences / Misc.
Is it running for a long time if you let BlackMagic Media Express capture the stream for a few hours ?
I don't know how OBS handles BlackMagic. However I think of another possible issue: on macOS only one application can open the SDK, on Windows it's different. I had BlackMagic Media Express running and capturing my stream and when I started MadMapper, Media Express stopped and MadMapper could display the stream. So be sure you don't start any other application that uses BlackMagic SDK or even a BlackMagic Direct Show filter. Basically you should test running just MadMapper and doing nothing else on the machine.
Only running MM and somehow it stops.
Will try another capture card since my feeling says it's a blackmagic issue instead of the pc's.
Also quality of blackmagic is terrible, max 1080i
Users browsing this forum: No registered users and 23 guests
Copyright 2017 © garageCube. All Rights Reserved. Powered by phpBB® Forum Software © phpBB Limited.