The GoTo Community is currently experiencing some technical issues affecting new posts and comments. You may need to reload the page you are on before you can post a comment. We are actively working with our service provider and apologize for the frustration.

Forum Discussion

Quick_Cutter's avatar
Quick_Cutter
Active Contributor
6 years ago
Solved

Using Blackmagic ATEM with GTT

Has anyone tried the new Blackmagic ATEM Mini with GTT?  I've been using GTT for two years with logitech webcams, and I want more control over focus, zoom and picture.  The ATEM mini plugs into the t...
  • AshC's avatar
    AshC
    5 years ago

    I wanted to update the Community on some recent testing we've done with Blackmagic hardware and current Mac operating systems!

     

    This solution should work with Mac OS + Blackmagic ATEM Mini + any HDMI input.  The key is to use OBS (Open Broadcaster Software) as a virtual camera driver to map Blackmagic device output to a proper format to use it in G2W.

     

    1. Install OBS (Open Broadcaster Software)
    2. In OBS create a scene setup with 1280x720@30fps
    3. Make sure the Blackmagic device is on and connected.
    4. In OBS add a Video Capture Device to the scene, open its properties and select Blackmagic device (1280x720)
    5. In OBS now select Start Virtual Camera
    6. In the GoTo desktop software you may now select OBS Virtual Camera as an input device
PaulDash's avatar
PaulDash
Active Contributor
6 years ago

Same situation here. Tried to use ATEM Mini as input for GoToMeeting. Latest version of ATEM firmware into latest Windows 10 build running latest GoToMeeting. None of the framerate options give anything but a black screen.

 

Obviously this is a software issue, as same input displays correctly with OBS, Skype, etc.

 

Oh, and I am an IT professional and I can't immagine what ports would need to be white-listed for things to work. The ATEM Mini doesn't connect to the host using a network, but a USB cable. Maybe if they tell us what registry tweaks to perform...

PaulDash's avatar
PaulDash
Active Contributor
6 years ago

Exploring this a little further in the GTM log files (by default in %userprofile%\AppData\Local\Temp\LogMeInLogs\gotomeeting\<build>\<session date>), I found a few interesting entries:

 

i: [g2mvideoconference] <vcw(G2MVideoConferenceThread::startLocalPreview())(0)> VideoEngine::setHighResCapture_() - High resolution capture set to false
i: [g2mvideoconference] <2136> RTC: [114] <date> L1 Info rtc::rve::core VideoSrc.cpp:231 SetMaxResolution SetMaxResolution for Blackmagic Design to: 1280x720

...

i: [g2mvideoconference] <2355> RTC: [568] <date> L0 DEFAULT rtc::rve::device devicedirectshow.cpp:1175 ERROR: 80004005 (ignored, we only can't set video parameters like contrats, hue, ...)

s: [g2mvideoconference] <2355> RTC: [597] <date> L1 Stat rtc::rve::core Engine.cpp:382 VideoCapDeviceError VideoCapDeviceError - reason=5 device=Blackmagic Design

 

It seems that they are trying to restrict the H.264 encoder to reduce CPU load by demanding that the camera switch to a 720p resolution. I'm running on a 12-core system so could cope with the encoder down-converting from a 1080p input just to get it to work!

 

Anybody at LogMeIn can say how to invoke setHighResCapture to set it to True?