The GoTo Community is currently experiencing some technical issues affecting new posts and comments. We are actively working with our service provider and apologize for the frustration.
Forum Discussion
Quick_Cutter
6 years agoActive Contributor
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...
- 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.
- Install OBS (Open Broadcaster Software)
- In OBS create a scene setup with 1280x720@30fps
- Make sure the Blackmagic device is on and connected.
- In OBS add a Video Capture Device to the scene, open its properties and select Blackmagic device (1280x720)
- In OBS now select Start Virtual Camera
- In the GoTo desktop software you may now select OBS Virtual Camera as an input device
Quick_Cutter
6 years agoActive Contributor
Well, I got the ATEM Mini and haven't been able to configure it with GTT. It sees the Blackmagic device as a webcam, but when I try to switch it to be my webcam, all I get is a blank preview screen and the spinning circle of infinite waiting.
I've gone into my ATEM settings to change things around to see if it will link up, but no joy yet. I hope I can get this to work - it will improve my trainings immeasurably. Getting this to work is going to be a key factor as to whether I stick to the GTT platform.
PaulDash
6 years agoActive Contributor
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...
- GeorgB6 years agoNew Contributor
Same here - like Paul is saying - this is a software issue! Not only the Blackmagic Mini is not working, we are also using the Roland VR-4HD, also connected via USB - same issue, input displays correctly with MS Teams, Zoom, Skype, basically in all apps I tested, but not in GoToWebinar, just a black screen, and no option available under "advanced". The stupid part is when using app.gotomeeting.com with Google Chrome, it is possible to share the USB-connected ATEM, but I could not get app.gotowebinar.com running, webpage opens but nothing happens. Is somebody from LogMein reading this forum? Is somebody working already on a bug-fix - or shall we switch to Zoom?
- GeorgB6 years agoNew Contributor
OK, it is not a bug, it is a feature, it looks like :-(. When switching the "camera" to a lower resolution, the GoTo-Desktop app is connecting via USB. It looks like GTW/GTT is supporting only a maximum resolution of 1280x720 - a joke in times of 4k cameras and high-speed internet connections. As I could not find information, when high-res cameras will be supported, at least for me it is clear we need a more modern web conferencing solution...
- PaulDash6 years agoActive Contributor
Georg, when you say <<switching the "camera" to a lower resolution>>, you're not able to achieve this with the ATEM Mini, right?
My temporary solution is to load the ATEM as a source in OBS and use its virtual camera add-in to use the image within GTM. This is of course not optimal due to the number of decode and encode operations that are being performed.
- PaulDash6 years agoActive Contributor
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?
- Chris Droessler6 years agoRespected Contributor
PaulDash - Thanks for taking the time to test and report
- KlausCzich6 years agoNew Member
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...