Posts in Category "Recording"

Connect Meeting and Client-side Speaker Audio Output Control

There is a Connect feature request from various customers in place asking for the Connect Meeting GUI to offer an option to choose audio output devices. The request is a complex one because the audio output control options are opaque to Flash; the settings for audio output are in the various operating systems (OS) of the many possible clients. Connect uses what is chosen as the OS default as depicted in our help documents:

Set up audio broadcasting

The feature request number is: CONN-4082570; one customer recently suggested that we add expanded functionality for client speaker audio output control roughly similar to what we already have in Adobe Connect for Microphone and Webcam selection.  A speaker drop-down menu for sound output is desirable for obvious reasons.

There is no set date for implementation of this enhancement in Connect and I will update this blog entry if that changes. In the meantime, if the default client OS audio output option is not the option desired for use with Connect Meeting, the following example may help: I will show how to add a Bluetooth speaker to a Windows client and toggle the audio output in Connect from the built-in laptop Realtek speaker to a new iHome Bluetooth speaker. While audio output options may vary, by showing how it is done with this common example of a Bluetooth output device, it will hopefully help to show how other optional client-side speaker output devices may also be managed in kind.

To see the enabled audio output options on a Windows client, look at the Device Manager under the Control Panel:

sound-dev-mgr.fw

Here we see a Realtek device and this corresponds with the option in the lower right of the desktop tray:

audiowzd-bt5b.fw

Opening the mixer shows more detail:

realtek.fw

If I play music by invoking the Audio Setup Wizard in Connect Meeting, the Realtek speaker will play:

asw.fw

conn-soundoutput.fw

Since our example will be to switch to a Bluetooth speaker, the first step will be to make certain that Bluetooth is enabled. On my Lenovo, that is done by pressing the keys FN>F5 simultaneously. Here we see Bluetooth is enabled:

sound-bt.fw

The next step is to follow the device instructions to pair the Bluetooth speaker with the client computer; these will vary.

See the Bluetooth icon enabled and  highlighted in my system tray:

sound-bt1.fw

After putting the iHome speaker in pairing mode, I am able to search for it from the client:

sound-bt2.fw

sound-bt2a.fw

sound-bt3a.fw

Now we have more than one speaker option to toggle as the Device Manager and the system tray attest:

sound-dev-mgr1.fw

sound-bt5.fw

In Connect we now see the option to use the new audio output device:

sound-fin.fw

Note: The iHome Bluetooth speaker also has a built-in Microphone so the Connect Audio Setup Wizard will see it in the Microphone drop down menu.

Without audio output controls built into Connect, adding and/or changing the default audio output device in the client OS is the way to toggle the audio output option in Connect. The key thing to be aware us is the danger of audio feedback loops. When separate speakers feed back into a microphone and cause echoing in a Connect Meeting. On a mobile device such as an iPAD, without a headset the speaker audio will feed right back in the microphone; it is best practice to use a headset with iPad to prevent audio loop/echos.

CSO: DATE (03-02-2016) – Adobe Connect Meeting/Content Launch Issue – RESOLVED

Update #2:

This issue is now resolved.  The issue was fixed as of 11:01 ET.

Meetings and content should be launching and saving normally.

 

Update #1:

We are investigating a storage issue where existing meetings, recordings, and content aren’t launching/accessible if they are needing to be pulled from the main shared storage infrastructure.

Some meetings and content may launch (if they are recent and still in local server cache) but there may be issues saving the current state of those meetings after they are done.

This is affecting accounts on clusters in the SJ1 datacenter which include: NA1NA2NA6NA8NA9, and NA12.

This appeared to have started about 10:20 ET.

The teams are all involved and troubleshooting the issue as a priority issue.

Updates to follow.

Please see the Status Page for more information.

New Adobe Connect Support Blog Subscription Option

Now you can stay on top of the new articles and posts by subscribing to the Adobe Connect Support Blog. Simply go to the Adobe Connect Support Blog home page and enter your email address and check off the categories about which you would like to be notified. Click “Subscribe me” and you will begin receiving  regular updates:

subscribe.fw

 

 

MP4 Recording Conversion Update

MP4 recording conversion functionality was recently unavailable for all Adobe Connect Hosted Accounts.

Note: Offline FLV recording conversion was unaffected and remains fully operational.

Update: 09 July

There is a workaround in place, as of 10:30 EST, to get the MP4 conversions back on track. Any job that was submitted prior to this may continue to throw an error to the user in the web app. Here is the way ahead:

• If you submitted a job this morning and the web app shows a conversion error, re-submit the job
• The queue is very long right now and it may take longer than normal for the conversions to finish.
• If you recently submitted a job, within the last hour or so, report all any new problems to the adobe support team.

Offline FLV Archives Fast-forward during Playback

With Flash Player version 17.0.0.169, the Nellymoser audio codec used within Connect offline FLV Meeting archives played automatically in fast forward. This issue is resolved in the latest Flash Player.

The solution is to install Flash Player version 17.0.0.188 (or later depending on when you run into this issue) and all effected Connect FLV meeting archives will play normally.

https://get.adobe.com/flashplayer/

 

 

 

XML API TIPS: Moving Archives That Have Been Repaired

One common workaround that customers do (or Adobe support may do on behalf of customers) to fix recordings that have some sort of sync or playback issue, is to download the archive (recording) zip, potentially run it through a repair tool, and then re-upload the zip package back to Connect as a content object in the ‘Content’ directory.  A common request may be to move that archive from the Content directory, to another location or even back underneath the Meeting’s ‘Recording’ directory.  The problem is that with failed recordings (recordings that didn’t fully process) and/or re-uploaded recordings, they will not have a ‘date-end’ parameter for the sco, like normal recordings do.  So when you try to (for example) move the archive to the original Meeting’s Recordings directory (which can really only be done using the API), you will get the following error:

API Call = Sco-Move:

/api/xml?action=sco-move&sco-id=xxxxxxx&folder-id=xxxxxxx

where sco-id = the sco-id of the re-uploaded archive
where folder-id = the sco-id of the original meeting (which is also the sco-id of the Recordings directory for that meeting)

Result:

<results>
<status code=”invalid”>
<invalid field=”sco-id” type=”string” subcode=”recording-is-in-progress“/>
</status>
</results>

This is because the sco does not have a date-end param/value.  You can see this by running the sco-info call on the sco-id.  You will see no date-end.

What you need to do before you can move the sco, is set a date-end param using the sco-update API.  You would set the date-end value to some date in the past.

Here is an example:

/api/xml?action=sco-update&sco-id=xxxxxxxx&date-end=2015-01-01T12:00:00.000-04:00

Result:

<results>
<status code=”ok”/>
</results>

Now, when you do a sco-info on that sco you should see the date-end param and value.

You can now also move the recording to it’s desired location (say back to the Meeting’s recording directory):

/api/xml?action=sco-move&sco-id=xxxxxxx&folder-id=xxxxxxx

Result:

<results>
<status code=”ok”/>
</results>

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
  • 9.0.0.1
  • 8.2.2.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:

chrome-addin.fw

Google Chrome, with the release of Version 40, will no longer use their whitelist to allow NPAPI  plugins to run without requiring approval: http://googleappsupdates.blogspot.com/2015/01/upcoming-changes-to-npapi-support-in.html 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:  http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html

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]” http://www.chromium.org/developers/npapi-deprecation

 

chrome-enable.fw

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.

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″
minSpareThreads=”5″/>

<!– 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″
executor=”clusterThreadPool”
enableLookups=”false”
acceptCount=”100″
connectionTimeout=”20000″
URIEncoding=”utf-8″/>

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”

netstat.fw

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.

serversettings

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:

etc-host.fw

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

netsh firewall show config

firewallsftwr.fw

win-firewall-svc.fw

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

cluster-debug.fw

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: entrsupp@adobe.com 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. http://helpx.adobe.com/adobe-connect/kb/connect-90-patches.html Keep in mind that 9.2 is a full installer and not a patch. For full installers, use LWShttps://licensing.adobe.com

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

Adobe Connect Offline Recording Option Captures and Records Local Client Screen Activity

Adobe Connect Offline Recording Option Captures & Records Local Screen Assets:

While in the process of creating an offline recording in Connect, the recording will capture extraneous desktop application activity if Windows is in Non-Aero mode

To stop extraneous recording,  turn on the Aero theme: Control Panel\All Control Panel Items\Personalization – choose any Aero theme.

aero.fw

This workaround will limit the offline recording to the Connect Meeting archive.

Here is the related forum discussion for reference: https://forums.adobe.com/message/6629306#6629306

Specifications for Offline MP4 Conversion for Connect Recordings

Prior to Connect version 9.5, the specifications for MP4 conversion on Adobe Connect hosted multi-tenancy accounts were similar to our FLV specifications albeit with better compression:

  • Resolution: 1024X768
  • Frames Per Second: 8 FPS
  • Video Bitrate: 1024kbps
  • Audio:
    • Codec – AAC (Advanced Audio Codec)
    • Profile – Main@3.1
    • Bit Rate – ~55Kbps (VBR)
    • Channels – 1 (Mono)
    • Sampling rate – 44.1Khz

With the advent of Connect 9.5, those legacy hosted server-side MP4 conversion options are end of life and the new client side offline conversion options offer a broader range of quality control conversion and output options for all Connect users running 9.5 whether hosted, on-premise or managed ISP. To view the panoply of possible settings, login to Connect Central and select the “Make Offline” option under any Meeting recording as shown below:

offlinerecgeneral.fw

The following dialog box will appear:

offlinerecgeneral1.fw

On clicking Next, offline recording download options appear offering MP4 or FLV,  Video quality presets on a sliding scale and also Advanced Options. With MP4 selected, see how the Video quality presets on a sliding scale affect Resolution, Quality, Profile, Bandwith and FPS:

The Mobile preset option uses:

  • Resolution-480p
  • Quality-70
  • Profile-Basline
  • Bandwith-400 kbps
  • FPS-15

95rec6.fw

The Desktop preset uses:

  • Resolution-600p
  • Quality-80
  • Profile-Basline
  • Bandwith-600 kbps
  • FPS-20

95rec7.fw

The HD preset uses:

  • Resolution-720p
  • Quality-90
  • Profile-Main
  • Bandwith-800 kbps
  • FPS-30

95rec8.fw

The Full HD preset uses:

  • Resolution-1080p
  • Quality-100
  • Profile-Main
  • Bandwith-1.4mbps
  • FPS-30

95rec9.fw

On clicking Advanced Options, you may override the Video quality preset options and customize the output settings:

95rec.fw

The resolution options range from 480p to 1080p:

95rec1.fw

The quality settings drop-down ranges from 50 to 100:

95rec2.fw

The Profile settings are: Baseline, Main and High. The lower the profile setting, the easier it is for a platform to implement (simpler, smaller code-base that puts less demand on resources).  The higher the profile, the more difficult the implementation for the software developer, the more demand it puts on system resources such as battery life while in exchange, the file size is smaller for the same quality of content.

  • Baseline- All platforms and devices support baseline — but since the features are less sophisticated, the file sizes tend to be larger to obtain the same result.  Use this if you need the content to be universally accessible.
  • Main- Used for standard-definition digital TV broadcasts.
  • High- Modern mobile devices support high profile and the file sizes are typically smaller than baseline. High profile is sometimes referred to loosely as broadcast-quality. Desktops and newer mobile devices (all devices supported with iOS 8.4) support generic high profile although there are non-generic flavors in high profile, such as high422 and high444 that are not. Here the generic option is in play.

95rec3.fw

The Bandwidth range is: 400kbps to 1.8gbps. Video encoders target encoding settings dynamically so that, on average, the content is consumable at the specified bandwidth.  This means that when content takes advantage of the encoder’s features (such as when the image is still, or when the camera is doing a simple sweep of a still scene), more detail can be pushed. Alternatively, when there’s an action shot, the detail is typically reigned in.  There may be bursts of time in a video that exceed the specified bandwidth, but the encoder manages it in a way that anticipates that some buffering is taking place while ensuring that the video broadly fits within the specified bandwidth. The general categories of end users are:

  • Corporate intranet bandwidth
  • Broadband consumers
  • Wifi users
  • Mobile users on cellular networks

When specifying bandwidth, you typically would use a value that is less than the bandwidth available.   If a broadband users has a 10Mbps connection that does not mean that there is always 10Mbps available or that other applications aren’t also consuming resources. The ramifications of select uses of QoS is also a relevant variable.

95rec4.fw

FPS options range in increments of 10 up to 30:

95rec5.fw

Note: The FPS set in the offline settings dialog is the maximum that addin will try to achieve during the making of mp4. There are a lot of factors which affect the final FPS such as CPU usage and graphic card capability. The addin may not always achieve the desired FPS if there aren’t enough system resources available.