Using Blackmagic ATEM with GTT

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?

Same problem here in Germany.

ATEM Mini works fine with Zoom, BlueJeans, Skype, LifeSize, etc.

When connected to GoTo audio works fine, video not.

I connected Epiphan AV.io to GoTo and had no problem.

ATEM Mini works fine with the web-app of GoTo (app.gotomeeting.com).

It must be a problem in the desktop app of GoTo and should be solved quickly...

PaulDash - Thanks for taking the time to test and report

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...

In all my forum research, the ATEM Mini will only work with GTW or GTM with a Mac, albeit a potentially cropped image. 
Blackmagic says all they are doing is providing a signal and it is up to the software to accept that. 
Every other service recognizes the ATEM Mini except GTW/GTM.
LogMeIn says it is too "Professional" and say you need to change some settings that most IT teams won't make. 

@AshC  are there any plans for LogMeIn to update the software for GoToWebinar or GoToMeeting to accept what is becoming a wildy popular and powerful piece of equipment? 
Please tell us this is in the works... maybe post-pandemic. 

Chris,

I just gave Zoom a serious workout, and the ATEM worked seemlessly.  There's something about the GoTo app that is preventing it from fully recognizing the ATEM.  I can see the ATEM as a webcam option in GTT, but the video doesn't actually play - in the settings screen, I just get a black background with an infinite circling flower.

The ATEM Mini is a step in the right direction. Maybe competition will heat up and someone else will come up with an alternative that works on all platforms.  I'll keep looking.

Have you seen this?  I have not tried it.

https://www.fakewebcam.com/ 

I noticed that on your post that you didn't load the ATEM software, so I tested the ATEM on a Dell Windows 10 laptop that did not have any of the additional ATEM software loaded on it.  GTT/GTM both failed on the Dell.  The ATEM software doesn't have anyting to do with it.  I truly wish it had.

I spent a long time on the phone with support, and support was able to get the ATEM to work with one combination of GTM online - or at least it recognized the camera during setup.    It didn't work at all with the desktop apps.  He told me there was at least one port conflict with the desktop software that needed to be whitelisted, and that I'd have to hire someone to do the work because it was beyond what support would do.  Sounds to me like the GTT/GTM software has a problem running on Windows 10 that needs to be fixed.

The two systems I worked with were a 4 month old Alienware Area 51-M system, which is more than capable of running all of this equipment, and a Dell Latitutde E5540, both of which are running with all current hardware and Windows 10 updates.

One other thing - because I'd really like this to work - is that on both of the systems above I have a minimum of other software loaded.  I don't run MS Office apps or anything but Adobe CS6 and Streamlabs OBS (and Google Chrome) on the Alienware unit, and the only app on the Dell is Camtasia.  I use both systems exclusively for editing media, GTM and livestreaming.  I intentionally keep them as clean as possible to avoid conflicts.  The whitelisting fix is bogus because it means I'm locked into using only one system that I have custom configured to use with GTM/GTT.  The ATEM Mini seems to work with everything else - Zoom, Skype, the Win10 Camera app - so why won't it work with the GoTo apps?

I used the ATEM Mini right out of the box and did NOT load the software.  It worked fine for me. Anything I plugged into it showed up as a webcam in GoToWebinar.

There must be something in the software that makes it not work with GoTo.

OK - over an hour with Service and the bottom line is that the ATEM doesn't work on the desktop app for GTT or GTM.  We got it to work over the internet app for GTM, but the support session concluded by the rep telling me I have to find an "IT Professional"  who can whitelist certain ports that are blocking the desktop app.

Either that, or I can switch to a different videoconference provider that doesn't require me to pay someone to make registry changes that may or may not fix the app and may or may not screw up other programs.

Hmmm. . . .