PaulDash
Active Contributor
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: Using Blackmagic ATEM with GTT
Hello AshC! Great for someone from LogMeIn to contribute to this thread! What you wrote mirrors my entry from April 19 of last year, however it shouldn't be presented as asolution. The issue is with the GTM software not supporting 1080p webcam input. Putting OBS and OBS Virtual Camera, two 3rd-party pieces of software, in the middle is merely a temporaryworkaround. What can we do to help you solve the issue? What can you tell us to enable the FullHD support?3.2KViews1like2CommentsRe: Using Blackmagic ATEM with GTT
mobilejoelwrote: My current workaround for the ATEM Mini and GotoMeeting Involves OBS Studio. Hi Joel, Exactly what I did back in April, but the problem is that this becomes a software solution, prone to fail. During whole-day sessions either the GTM software or OBS would crash at least once. Another drawback is the quality loss: you're going from a 1080p to 720p to whatever it is that GTM optimizes for. That's an encode-decode-encode chain that would be otherwise unnecessary if only GTM could handle the output of the ATEM Mini. My workaround ultimately involved spending more money on hardware and I now run through the Blackmagic Web Presenter, which has 720p on the USB webcam connection. -Paul3.6KViews0likes4CommentsRe: Using Blackmagic ATEM with GTT
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.4.4KViews0likes0CommentsRe: 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 invokesetHighResCaptureto set it to True?4.5KViews0likes0CommentsRe: Using Blackmagic ATEM with GTT
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...4.5KViews0likes6Comments