Adobe Connect supports most cameras and video cards. Adobe doesn’t maintain a list of supported cameras and video cards because there are too many combinations to test.We essentially have a statement about what we do support in theory.
To broadcast video from the Camera and Voice pod in Adobe Connect Meeting, the operating system must have a valid camera driver. If the operating system doesn’t have a valid camera driver, Adobe Connect cannot use the camera. Adobe Connect uses the operating system API to check for the camera driver. Typically most cameras, including high def and professional cameras will support this.
If your camera or video card doesn’t work with Adobe Connect, you can provide the camera and video card specifications from the manufacturer to us and we can determine if this is compatible.
All that said, we’ve certainly had customers use professional camera setups (multiple cameras with a switch) or video production quality cameras with operators following the action in live events, etc, but at the very end of the setup, the feed has to be going into a PC that is hooked into Adobe Connect and that connection is the one you’d bring into the Camera and Video pod. We have had customers with very high end setups with audio and video mixers, etc. but the camera feed needs to go into a supported video card in a computer that is running an Adobe Connect session, and that feed needs to be brought into the Camera pod.
You can try any type of camera you have access to, as long as there is a valid webcam driver that Flash Player (Connect Meeting Addin) can detect in the Operating System. It’s essentially the same mechanism if you use Google’s Gmail with Video Chat. When you try to select a camera in the dropdown in Gmail settings, it will detect the available camera/drivers. Connect is the exact same thing.
The following webcams don’t work well in the meeting Video Pod.
- Creative VF0260
- Microsoft VX 3000
- Osprey 230 video card
Problem: use osprey 230 video card and publish camera stream and when user resizes the video pod or changes the layout which has a bug video pod the camera stream freezes.
*** This issue is fixed in 9.1 that is coming out later this year (with a new add-in).
Some user might receive HTTP 500 or 505 Internal error when they try to register for an event that has been setup with “Register Without Password” option enabled.
This happens when a user who is trying to register already as an account in the system with an expired password.
Have the user reset his/her password and then try to register.
We’ve identified Adobe Connect Recordings which use screenshare randomly crashing on playback if played using Flash player 11.6
Meetings running on FP 11.6 might also experience crash if hosts use screenshare during the session
Adobe Connect 9 Licensed
We’ve identified this as a bug(Bug#3526202) and is under investigation with our Connect and Flash Engineering Teams. More updates to follow.
We have following recommendations to fix this problem now from Adobe Engineering
1. Disable SS_DYNAMIC_CODEC on your Connect servers by following this article : http://helpx.adobe.com/adobe-connect/kb/disable-dynamic-screen-share-codec.html
2. This should help resolve this issue in new meetings/recordings.
3. Contact Support if you still encounter issues after implementing this change.
Update : This has now been fixed with Flash Player 11.7
– Bandwidth issue.
-Anti-virus/security software issue.
-Tunneled connection (rtmpt) issue.
Steps to Follow:
– Try to take the Test Meeting Connection.URL to test it is: https://admin.acrobat.com/common/help/en/support/meeting_test.htm.That will help us to gather the information about Flash player, Bandwidth, connection speed, Add in.
– To find the version of Flash Player and Add- in version by taking the test Meeting Connection and then click on Send result >> Details .
– Try deleting the flash cookies from the link: http://helpx.adobe.com/adobe-connect/kb/delete-fp-browser-cache.html .
– Verify for user’s system requirement for the meeting. URL to check is: http://www.adobe.com/products/adobeconnect/tech-specs.html .
– Verify if user is using VPN or not. If YES then we can expect latency and user disconnect in the meeting room as VPN makes the bandwidth slow.
– Verify if the user is on wired network or on wireless. Wireless network may cause problems if the user doesn’t have good connection speed.
– You can refer the below link for bandwidth which can help you to prevent users from dropping from the meeting room. URL is: http://helpx.adobe.com/adobe-connect/kb/connect-bandwidth-calculation.html .
– Check if firewall is blocking connect from working. If YES then add an exception for it and then try if it works.
– We can also check if customer is on tunneled connection (rtmpt). To check that click on the help option on the top right hand side corner then hold the Shift key and click on About Adobe Connect. There you will get the data like
Its rtmps as of now but for customers if its rtmpt then that means 1935 port is blocked at their end so ask them to contact there Network Team to unblock that port.