Posts in Category "Meeting"

Adobe Connect Add-in Compatibility with the Google Chrome Browser

Updated January 27, 2015:

Note: This article only applies to Adobe Connect on-premise server deployments. Adobe Connect hosted clients are unaffected.

The Google Chrome browser is currently shipping with two versions of the Flash plugin.  The default PPAPI and also the NPAPI Flash plug-in. The following versions of Adobe Connect installations are incompatible out of the box with the default PPAPI plug-in:

  • 9.1.2
  • 9.1.1
  • 9.0.1 – 9.0.4
  • 8.2.2

PPAPI plug-in incompatibility results in the Adobe Connect Add-in not being detected and launched in Chrome when invoked in a Connect Meeting. Even if the Add-in is installed, the meeting opens in the browser and not in the Connect Add-in. Upon attempting to share ones screen (a Connect feature supported in the Add-in but not in the browser), the following message appears:


Google Chrome, with the release of Version 40, will no longer use their whitelist to allow NPAPI  plugins to run without requiring approval: Chrome users will not be able to use the Adobe Connect Add-in for the above listed versions of Connect. To address this problem, Adobe is patching the following Connect versions for use with Chrome:

  • 9.1.2
  • 9.1.1
  • 9.0.4
  • 8.2.2

These patches will fix the incompatibility problems with the PPAPI plug in. Adobe Connect servers that are not running one of these versions (or a later version) will need to be upgraded to the nearest later version to the one currently installed and then apply the appropriate Connect PPAPI patch.

There should not be any change in the behavior for Flash Player NPAPI in January because Flash Player is not listed among the applications  that are going to be removed in January:

Workarounds until the patches are available:

  • You can attend Adobe Connect Meetings without the Adobe Connect Add-in, however the Add-in is required for enhanced functionality like screen sharing and making offline recordings.
  • Turn off auto-upate in Chrome so that you do not upgrade to a version of Chrome that is problematic.
  • Alternatively you can use any browser other than Chrome with Adobe Connect.
  • Manually enable NPAPI by clicking on the “Plug-in blocked” message in the URL bar and choosing “Always allow plug-ins on [website]”



Note: In April 2015, this will no longer be an option as NPAPI support will be disabled by default in Chrome and Google will un-publish extensions requiring NPAPI plugins from the Chrome Web Store. Google will however provide an override for advanced users in the form of an ‘enable-npapi’ flag and enterprise policy to temporarily re-enable NPAPI.

XML API TIPS: Moving Virtual Classrooms to Meetings

You may have a situation arise where you want to move Virtual Classrooms (VCs) over to the Meeting area of Adobe Connect.  You may notice that if you try to move Virtual Classrooms, you only have the ability to move them within the confines of the Training module and not out to the Meetings area if you are using the UI.  There is an option however.  The API can be used to move VC’s either one by one or an easier way is to put them all into folders inside of the training area (in either Shared or User training folder) and then move the folders themselves (which in turn will move all the VCs inside of it).

The API process for doing this is:

https://{connect domain} /api/xml?action=sco-move&sco-id=xxxxxxx&folder-id=xxxxxxx


sco-id = the sco-id of the VC (or folder that contains all the VCs you want to move)
folder-id = the folder-id of the destination folder you want to move the VC to.

** DO NOT move any main User Training folder or the Shared Training folder itself. ONLY move user-created folders or individual VCs themselves.


The process is not done however.  For each VC you move, you have to do one more step.  You need to change the icon of the VC to a meeting icon.  If you do not do this, the VC’s will NOT launch.  You won’t even be able to get to the information page for the VC once it’s moved.  The link to the VC information will simply refresh the meeting list page if you do not change the icon.

To finish the process change the icon by making this call:

https://{connect domain} /api/xml?action=sco-update&sco-id=xxxxxxx&icon=meeting


sco-id = the sco-id of the VC you just moved.


Now, the VC link will work and you will be able to get into the information page and access the links, content, reports, and archives.

Your application can handle building a list of VCs to move by using the sco-contents or sco-expanded-contents API calls (filtering on ‘icon=virtual-classroom’) to list out all VC’s in a specific folder or across the account as a whole, should you want to move everything for example.  Then your application would loop through and not only move the VCs but then also loop through each and change the icon.  If you only want to move one or two, you can simply do this in the browser with the API calls above.

It’s important to note that the uploaded content and any archives associated with this will be retained, HOWEVER in the reports, you will notice you are missing the ‘By Course’ report.  That is LOST with the move.  ‘By Course’ report is essentially the difference between a meeting and a VC.  So if you move VCs to meetings, that report is gone.  You still will have ‘By Attendees’ , ‘By Session’, and ‘By Questions’ (which are poll pod questions, not courses) reporting that will be retained.

Of course moving meetings to training will work the opposite way.  You finish that process off by changing the icon from ‘meeting’ to ‘virtual-classroom’.


Connect Meetings do not inherit the properties from its base template.

We have optimized meeting utilization of available bandwidth in Connect Version 9.2.2c and made some changes to retain these settings.

Earlier than 9.2.2c:

New meetings retained their preference settings (for ex., Bandwidth configuration LAN/DSL/MODEM) from its base template).

9.2.2c and above:

New meetings do not retain their preference settings (bandwidth settings in 9.2.2c and video settings in 9.3+) from base templates.


On Connect 9.2 and previous versions:
1.       Create a template and change the Room bandwidth to Modem.
2.       Moved the meeting in shared template folder.
3.       Create a new meeting using the above template and the Room bandwidth should be Modem.

Test with Connect 9.2.2c
a.      Created a new Room with base template as Step 1 above.
b.      Now, the room bandwidth will be DSL (default setting).
c.      Note: preferences in the Template created in Step 1 are still set to Modem

Bandwidth settings are removed from the User Interface in Connect 9.3.  Video and screen-share settings can be adjusted according to bandwidth/requirement.

Frames Per Second during screen-sharing in Connect Meeting

How many frames per second (FPS) are broadcast during Connect live meetings?

Frame rate, also known as frame frequency and frames per second (FPS), is the frequency (rate) at which an imaging device produces unique consecutive images called frames. The term applies equally well to film and video cameras, computer graphics, and motion capture systems. Frame rate is most often expressed in frames per second (FPS) and is also expressed in progressive scan monitors as hertz(Hz).” –Wiki.

We can change the Video quality from a meeting room by going to Meeting – Preferences – Screen Share: Low, Medium, Standard (default) and High.

The data in tabular format:

Bandwidth/Video Quality Quality FPS Max Resolution
LAN/High 90 20 640*480
LAN/Standard (Default) 80 15 640*480
LAN/Medium 75 10 320*240
LAN/Low 70 8 320*240
DSL/High 85 15 640*480
DSL/Standard 80 10 320*240
DSL/Medium 75 8 320*240
DSL/Low 70 4 320*240
Modem/High 80 15 320*240
Modem/Standard 75 10 320*240
Modem/Medium 70 8 320*240
Modem/Low 70 4 160*120

Note: In C9.2, there were 12 quality levels:  480p will still be the max @ 20fps.

In C9.3, only Low, Medium, Standard and High quality options are available dependent on the level set for video quality in meeting preferences:

Video Quality Quality FPS Max Resolution
High 90 20 640*480
Standard (Default) 80 10 320*240
Medium 75 8 320*240
Low 70 4 160*120

Adobe Connect Supported Video Input Resolution Option Questions and Answers

An interesting question came up that others may have: What are the supported video input resolutions for Connect? I am testing a Matrox MXO2 Mini that allows me to send a variety of different resolutions through a USB shim that can be used in Connect. I have tried a number of resolutions that will either not show a full frame of video or no video at all. Can I get a list of the supported video input resolutions?


For 4:3:


For 16:9:


Another question came up on the same topic that will be of interest. Similar to something Hippasus might ask Pythagoras: If there are three supported resolutions per aspect ratio why are there four settings for video quality under video preferences?


Answer: Apart from Video  Resolution, there are other parameters as well which define the video quality such as Frames/sec and Video Compression Quality. These four settings have different combinations of these variables:

                                           Resolution                      Frames/sec                Video Compression %

High                                      640×480                               20                                                           90

Standard                              320×240                               10                                                           80

Medium                               320×240                               8                                                              75

Low                                        160×120                               4                                                              70

For the 16:9 aspect ratio, the settings are the same as their 4:3 counterparts. For example, if 4:3 resolution for any quality setting is 320×240, then its 16:9 counterpart will always be 427×240.


VoIP Bandwidth and Microphones

When using the Nellymoser codec, one microphone might produce more bandwidth over against another. Nellymoser accepts five different microphone rates values: 5, 8, 11, 22 and 44. Each of these rate values consumes bandwidth of roughly double its value. For example the 8kHz setting consumes roughly 16kbps and 11kHz setting consumes roughly 22 kbps. The default rate value is 8kHz. This may vary depending on the sound capture device in use.

The Flash Player microphone reference documentation reads:

“The default value is 8 kHz if your sound capture device supports this value. Otherwise, the default value is the next available capture level above 8 kHz that your sound capture device supports, usually 11 kHz.”

It is possible for two different microphones to consume different amounts of bandwidth.

In case of the Speex codec, it has a fixed sampling rate of 16kHz. Speex allows control of the quality by offering us 11 different encoding quality options. See the following reference table :


Speex NellyMoser
Quality (EncodeQuality)Mic rate is fixed at 16 Bandwidth(kbps) Quality (Mic Rate) Bandwidth (kbps)
0 3.95 5 11.025
1 5.75 8 16
2 7.75 11 22.05
3 9.80 22 44.1
4 12.8 44 88.2
5 16.8
6 20.6
7 23.8
8 27.8
9 34.2
10 42.2


Adobe Connect supports three Speex settings:

  • Fast : Encode Quality 4
  • Good : Encode Quality 6
  • Best : Encode Quality 8

Increasing the encoding quality will increase the quality of the stream but will also require greater bandwidth. The Speex codec is optimized for voice and also includes voice activity detection that allows it to reduce bandwidth.

PDF document does not upload into Adobe Connect

Problem: Adobe Connect could not process this document for viewing. (Either the full document does not upload or some pages of within a document do not upload)



Adobe Connect Hosted/Licensed


Use the “Sanitize Document” Feature to get rid of all the following types mentioned in the image attached below. Depending on the version of Acrobat you are running, you may need to install a trial version of Adobe Acrobat Pro to use this feature.



Make Certain that Content is Replicated Across All Servers in a Connect Cluster

Occasionally a specific piece of content may be intermittently available in a cluster. It could be Presenter or Captivate published on-demand content or even content within a Meeting room. Sometimes in these cases, the content published on one server is not replicated to all servers in the cluster. There are a few quick things to check:

First: Note that with Adobe Connect 9, the installer includes a cluster option. If you begin with a single server installation and expand later to a clustered environment by adding a server or servers, you will need to manually make the following change in the /appserv/conf/server.xml file in order to enable communication over port 8507 among clustered servers. It is prudent to double check this in the server.xml file after installing even if the cluster option was selected during installation:

<Executor name=”clusterThreadPool”
namePrefix=”cluster-8507-” maxThreads=”150″

<!– Define a non-SSL HTTP/1.1 Connector on port 8507 –>
<!– Used for HTTP access for intra-Cluster communications. –>
<!– Equivalent to JRun CLUSTER_PORT –>
<!– Uncomment for clustered deployments
<Connector port=”8507″ protocol=”HTTP/1.1″

Second: Test the 8507 port communications on each server: From a command prompt on each server, type netstat –an|find “8507” and check to be sure that 8507 is active and listening on each.

netstat -an|find “8507”


Use telnet to test connectivity on  8507 between Connect servers. Use telnet to check both IP and machine-name as well.

telnet server-machine-name 8507

telnet 8507.fw

Note: The machine name appears to the left of the FQDN under the Connect Servers Setting on port 8510 locally on any server in the cluster; here I have artificially designated them as server1 and server2.


Be sure to check telnet connectivity from and to every server in the cluster:

telnet 8507.fw

If the IP works with telnet and the machine-name does not work, it may be necessary to add entries in DNS or add hosts files to each server:


Check the software-based firewall on the server to see if it is potentially blocking replication traffic:

netsh firewall show config



Note: Connect does not support dual stack ipv6 and ipv4 on the same server.

Note: If problems are noticed in the Meeting rooms, check port 8506; it is used for Meeting communication among the servers.

Third: Examine the Connect logs: Look first in the debug.log under the \logs\support directory and search on the string: cluster-  If replication is taking place, you will see this repeating cluster- entry logging the replication activity. Absence of these log entries will indicate that replication is not working:

[10-1 12:00:00,009] cluster-8507-630 (INFO) CLUSTER Sent file: \7\xxx-xxxx\fcs-meeting\public\all\224_XXX_4.fso 9978 bytes 12 ms 6371 kbps to: server1


Check for any error messages in these replication log entries. Search also for the word lucene. If you see a preponderance of lucene lock errors, contact Adobe Enterprise Support: and provide a log snippet to expedite diagnosis.

Also check the error.log files for the entry  CLUSTER_CON_BROKEN

2014-10-02 15:28:48 “Server server1 unable to reach server2 on port 8507 to perform cluster operations.” CLUSTER  CLUSTER_CON_BROKEN

Fourth: Check the timing of active anti-virus scanning of the content directories \content\7\ on each server; compare the directory sizes on each server to see is there if a significant size delta. Antivirus software can impede replication in manner that is not uniform across servers; active scanning of the content directory during replication may lock the content files. Active scanning after hours or during a window when publishing is unlikely is prudent.

Fifth: Check the updater page. Make sure you are on the latest patches servers-side. Keep in mind that 9.2 is a full installer and not a patch. For full installers, use LWS

These steps will solve most replication problems that you encounter. If problems persist, contact our  Enterprise Support Team.

Avoiding Inaccurate Completion Reports when a Meeting is Part of a Curriculum

When a meeting is part of an Adobe Connect Curriculum, a trainee can click on the Meeting and complete the Meeting task prescribed in the Curriculum prior to the Meeting taking place.



One way to help manage this is to choose the Meeting options to block Meeting access illustrated in the screen captures below:





The Meeting access options may be inconvenient to use, so here is another option to add a Meeting to a curriculum, while at the same time restricting the ability for a trainee to complete the Meeting task prior to the Meeting taking place:

Step one: The first step is to set a date and time under the Meeting properties. Make sure the date and time correspond to when the Curriculum task takes place. Note that this date and time has no effect on when the Meeting can be used. It is strictly an administrative tool to help with Meeting invitations and has no effect on when the meeting can be opened, Meeting persistence, etc. In this example I have set the meeting to October 22, 2014 at 12:45 for 1 hour:



 Step two: Download and unzip the Meeting Curriculum Wrapper:

Note that it is zipped twice to facilitate download:


Step three: Identify the Meeting sco ID from the Meeting that you wish to add to the Curriculum and copy it to the clipboard:

The Meeting SCO is in the Meeting URL:


Note: You can also see the Meeting sco ID by pasting ?mode-xml at the end of the Meeting URL and reading it from the output:


Step four:  Edit the index.htm in the unzipped LaunchMeetingInCurriculum folder by pasting in the Meeting sco ID from the Meeting that you wish to add to the Curriculum. Use your favorite text editor such as notepad or textpad. Where the index.htm reads,  Enter the SCO of the Meeting, Virtual Classroom or Seminar var meetingScoID_str = ‘1660065186’; change the default Meeting sco ID, 1660065186, to the Meeting sco ID of the Meeting that you wish to add to the curriculum, in the case of my example here, the Meeting sco ID is: 502114549. Be sure to save the changes:


Step five: Zip all the edited contents of the LaunchMeetingInCurriculum folder and rename it to represent the Meeting that you wish to add to the Curriculum. This will help you identify it and differentiate it from other Meetings with which you use this wrapper:



Step six: Upload the edited zip file to the Adobe Connect Content Library:




Step seven: Import the wrapper from the Content Library into the Curriculum:


Note: Import options; the wrapper is Content and points to the Meeting:





Step eight: Test the Curriculum item; unless the time and date coordinate with the actual Meeting schedule, the pop up will deter the trainee from gaining premature access to the Meeting and skewing the Curriculum completion report:


 Conclusion: With proper management and administration, an Adobe Connect Curriculum accurately measure the progress and completion of trainees. There are two ways to prevent a trainee from completing a Meeting curriculum task prior to the meeting taking place, the first is to block access to the Meeting and the second is to use the Meeting Curriculum wrapper.

Deleting base templates will lead to Meeting corruption

Some users may get into this trouble after deleting the base or default Meeting templates from Adobe connect.


After deleting the default Meeting template any meeting that was created from the default/base template launches with the error message, “The template you are looking at is the one we use if the default template feature is not working.”

Environment : Connect Hosted/Licensed

Method via which issue can be re-produced :

1.     Create a meeting template using Default Meeting Template
2.     Launch the template created in step 1 and move it to the Shared Templates location.
3.     Create two meetings (M1 and M2) using the custom template created in step 1.
4.     Launch the Meeting M1 and End Meeting. Do not run M2.
5.     Delete the custom template.
6.     If you launch Meeting M1 it will launch successfully.  However, Meeting M2 will show the grey screen with error.

Meeting room opens with a grey screen and the error message appears, “The template you are looking at is the one we use if the default template feature is not working”.

Solution :

Avoid deleting the default/base templates.  In order to recover the templates please contact Adobe support team.  We can recover the templates on case by case basis.