Although we don't support this type of set up directly, I will as some colleagues if anything has changed recently within GoToMeeting that may have affected the webcam feeds.
Today I have had another look, when opening the camera from Go-To-Meeting the LED goes on as well.
So it looks to me that Go-to-Meeting is able to access the camera.
We are having the same issue which is becoming a real problem when broadcasting live events and our attendees cannot see the presenter.
We have tried reinstalling the software, reinstalling the cam etc. and it is constantly shows as loading but doesnt ever switch on. However, if you go into the camera settings it will work in the preview box (but still doesnt work for the actual webinar)
I have found one way around it which is still a bit hit and miss but works sometimes. Instead of launching the webinar, go to 'practice webinar' and the camera works. Launch the live meeting from there and it works. Its worth a try.
I am hoping that Go to will be able to solve this one soon
The version is 10.14.0 Build 18962
The LED is active and camera keeps loading
is there more you need to see/ know?
We had a support case on 18/11/2020
This could be related to an Apple security change this year that requires specific permissions for webcam, microphone, and desktop sharing for individual apps. In this case if re-installing GoToMeeting does not trigger the request, it may also help to check the GoToMeeting settings to confirm the webcam feed selected (again) while in session.
I have the same problem with my HP laptop w/integrated webcam.
I have checked the following:
1) Camera works with Zoom.
2) Driver is up to date.
3) Windows 7 Pro is up to date.
4) Permissions appears to be set correctly.
5) Re-installed GoTo Meeting.
6) The webcamtest website says my camera is fine and working.
How can I get this working?
@RobbP Do you see your webcam visible in the GoToMeeting desktop software preferences?
Do you see other peoples webcam feeds while in session? If not, do you have any local security software that may be blocking the local port #1853?