Posts in Category "Recording"

Specifications for MP4 Conversion for Connect Recordings

Here are the specifications for the MP4 conversion; they are 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

Estimating the Size of Archive Meeting Recordings

I was recently asked if I had any test data showing how big a recording becomes based on the use case during the Connect Meeting being recorded. While plenty of anecdotal information exists,  I thought it prudent to begin a list of use cases and show what the size was after five minutes of each use case. This article will be a work in progress as I add different use cases in order to offer various concrete examples to use as a basis to estimate recording size based on what is being recorded, whether multiple Video pod camera feeds or screen-sharing or VoIP, etc. Among its purposes, this exercise will help meeting hosts to avoid exceeding the 2GB limit on Adobe hosted clusters for recording size.

Most relevant among the variables considered is the notion that recording size is affected by the streams present in the meeting being recorded. Typically a Video pod with VoIP (640X480) shared per hour will result in an FLV of around 200MB. Sharing a screen in a meeting (1680X1050) will result in an FLV size of around 150 MB. PPT/PPTX files uploaded to a meeting room and displayed while recording will not play a significant part in recording size because the recordings link to external content rather than contain that content intrinsically. For example,  a meeting with two Video pod streams could have recording size of around 400MB and a meeting having a single Video pod stream with VoIP and screen-sharing could end up around 350MB. The actual results may differ as the screen resolution of the publisher, the type of sharing and the amount of movement are all variables that can affect recording size: If there is little movement on screen or in the Video pod stream, the recording size will be less than it would be with a lot of movement.

Here are some concrete examples to use for planning; each recording is approximately five minutes in length:

A meeting with a single video feed for the Presenter to display and scroll through an uploaded PowerPoint file while using integrated telephony:Title: Recording Size Test_0
Type: Recording
Duration: 00:05:31
Disk usage: 8335.3 KB

rec-size1.fw

 

A recording of a meeting with six video feeds and an uploaded PowerPoint file
Title: Planning Troubleshooting and Support Meeting Room _15
Type: Recording
Duration: 00:05:48
Disk usage: 13873.8 KB

rec-size2.fw

 

A recording of a meeting with four video feeds and screen sharing an application with normal activity
Title: Planning Troubleshooting and Support Meeting Room _16
Type: Recording
Duration: 00:05:56
Disk usage: 21660.8 KB

rec-size3.fw

More examples to follow.

How long does it take to publish Connect recordings as MP4s?

An MP4 recording will be published and posted within 24 hours of invoking the conversion.

  • the actual amount of time it takes to convert a recording depends on many factors including:
  • the length of recording
  • the queue of recordings to be published on the publishing servers
  • the queue of recordings within Connect prior to transfer to the publishing servers (they are submitted in parallel to the conversion servers)
  • the time it takes to download the converted MP4s from the conversion servers back to Connect
  • and variables commensurate with asynchronous processing

Note also that if for any reason the conversion to MP4 should fail,  we will retry multiple times depending on the cause of the failure. Retries will extend the processing time required before the recording is available. The two most significant variables are the length of the recording and how many recordings are ahead in the queue.

Controlling Recording Playback through the URL

When added to a Connect archive recording URL, the following suffixed commands will force the prescribed behavior. This may help with projects that include the embedding of archive recording URLs.

  • pbEIOpen=true – the event index would come up opened
  • pbEIOpen=false – the event index would come up closed
  • pbEIOverlay=true – the event index would show up in overlay mode
  • pbEIOverlay=false – the event index would show up in persistent mode
  • pbMode=normal – open in normal playback mode
  • pbMode=edit – open in editing mode
  • archiveOffset=parameter in milliseconds – open to a specific time in the recording

You can modify the URLs along these lines; use an “&” to concatenate multiple parameters.

Every recording will automatically append ?launcher=false&fcsContent=true. You cannot play a recording in the Connect Meeting addin; if you append ?launcher=true, it will toggle to ?launcher=false and open the recording in the browser:

This URL is an example of what a normal URL would look like during recording playback:

https://connect.mydomain.com/recording1/?launcher=false&fcsContent=true&pbMode=normal

To change this to open with the index closed, append pbEIOpen=false like this:

https://connect.mydomain.com/recording1/?launcher=false&fcsContent=true&pbMode=normal&pbEIOpen=false

Demystifying Mixing VoIP and Telephony in a Meeting

With Unified Voice (UV) enabled and selected from within a meeting room:

The host may choose: Meeting>Preferences>Audio Conference>Allow participants to use Microphones: When Allow participants to use Microphones is checked, participants have power to enable their own microphones within the meeting. When it is unchecked, the host must enable microphones first and then the participant can enable the microphone with host permission within the meeting:

uv-1.fw

In either case, checked or unchecked, the host needs to first start the audio conference within any meeting:

uv-1b.fw

And the participant needs to choose the microphone option and enable it (even though the host has enabled it manually within the meeting or set it as permanently enabled within the room):

uv-1a.fw

Note that by default, when UV is in use, the telephony option is checked for the participant:

UV2.fw

The participant must select the microphone option in order to use the microphone instead of the phone; this will allow the microphone to broadcast to the users in the meeting using UV telephony:

UV3.fw

With all these settings in place, VoIP microphones can talk to telephony and telephony to VoIP and both will be audible in an archive recording for playback on demand.

Using iframe to Invoke an Adobe Connect-hosted URL

Make sure that the iframe reference is formatted correctly.

When referencing an a meeting archive recording, it is best to first move an archive from under its parent meeting to the Connect Central content library before referring to it via iframe.

Do not let the URL of the archive recording redirect to Connect Central login page. To bypass the login screen you may either parse a username and password as a parameter in the URL or you may set permissions on the referenced content URL in Connect Central to allow for public viewing.  The latter option is usually the best. To avoid exposing the genuine user’s password as plain text in a GET request, it is usually best to simply make the recording public in Connect Central then link it. Alternatively, you may also create a new user in Connect Central with no other permissions except access to the referenced URL.

Referencing content in Connect Central that is set to public viewing:

<iframe src=http://connectdomainname.adobeconnect.com/customurl1″></iframe>

Referencing content by parsing a username and password:

<iframe src=”http://connectdomainname.adobeconnect.com/username?login=username@adobe.com&password=userpassword&account-id=12345678” width=”600″ height=”600″></iframe>

When referring to multiple URLs whether archives or MP4s or other Connect-hosted links, be sure to use a separate iframe reference for each Conenct URL rather than attempting to wrap all URLs in a single iframe reference. For example, two public links together in a table might look like this:

  <tr>
    <td width=”600″><iframe src=”http://connectdomainname.adobeconnect.com/customurl1″></iframe></td>
  </tr>
  <tr>
    <td><iframe src=”http://connectdomainname.adobeconnect.com/customurl2″></iframe></td>
  </tr>

Public MP4 is redirecting to login page on Android and iOS devices

Currently as of Adobe Connect (hosted) 9.1.2, there is an issue with accessing public MP4 recordings on Android and iOS devices.  By design, the public content should not present a login screen to the user.  However, users are getting the login page on those devices when they try to access these public MP4 recordings.  The fix for this has been identified and it is slated to be rolled out in the 9.2 upgrade of the Adobe Connect hosted system.  Until then, the following workaround below should be followed.

The ‘workability’ of it depends on how you provide your users with the link to the MP4s.  iOS users in particular, are most likely not getting these links from the web app (Connect Central) but are instead getting them from an email or other portal that is provided to them.  If that is the case (for either iOS or Android), then you would just need to update the URLs (as indicated below) until we release 9.2 and provide a resolution.  Here is the workaround:

  1. Locate the MP4 in the Content Library.
  2. Click to view the ‘Edit Information’ page for the recording.
  3. Click the ‘Download Content’ link.
  4. Under ‘Download output file(s)’ there is a link to download the file. Copy this URL
  5. Paste the URL to a notepad or document.
  6. You will have a URL that looks something like this example: https://myCompany.adobeconnect.com/localmp4/output/Local-z1.mp4?download=Local-z1.mp4
  7. Remove everything after the ‘?’ and your URL will be something like this example: https://myCompany.adobeconnect.com/localmp4/output/Local-z1.mp4
  8. You can provide the modified URL to your users, and the recording will stream without stopping them to ask for permissions, though it will honor any permissions settings you have on content that is not public.

 Again, this issue is resolved in the upcoming 9.2 Adobe Connect release.

7.x Recordings Not Playing after Upgrading to 9.1.1

If you have recently upgraded an Adobe Connect on premise deployment from version 7.x to 9.1.1 (with various 8.x steps possibly in-between), you may encounter an issue where older recordings no longer launch.  However, newly created recordings open and playback without issue.

If this is the case, please check the following directories…

First check:

[Root Connect Install]\9.1.1\appserv\common\meeting\shell

This directory should contain the following SWF files:

  • BreezeUIComponents.swf
  • CorePodCollection.swf
  • meeting.swf
  • meeting_sgn.swf
  • shell.swf
  • shell_sgn.swf
  • StamperSymbols.swf

If they do NOT exist in that directory (but just the ‘breezeLive’ folder and xml files are the only files present), please download the files from here and place into the directory.

Then check:

[Root Connect Install]\9.1.1\appserv\common\meeting\launcher

This directory should contain the following SWF files:

  • listener.swf
  • openmeeting.swf
  • openmeetingversioncheck.swf

If they do NOT exist in that directory, please download the files from here and place into the directory.

After confirming these files are now in those directories, retry launching an older Connect recording.  No restart is required.

Increase the volume/Remove a part of recorded audio from a recorded session

Many-a-times people face an issue where the volume in a recorded session isn’t loud enough to be clearly audible to everybody.. Similarly there may be times when you may want to remove a part of the recorded audio from the recording.. Here is a solution which although may not be the easiest but definitely a working one for most of the users..

After the recording is finished, pull down the recording source files by adding ‘output/yournamehere.zip?download=zip‘ to the recording URL. In the zip that comes down, there will be either a MP3 audio file (if you recorded your audio via an integrated phone bridge) or a FLV file labeled cameraVoip_X_X (if you recorded your audio via VoIP or Universal Voice).

The MP3 file is easy to modify and place back into the zip file, while the FLV may take some work since you will have to extract the MP3 from the FLV and then put it back in the FLV before placing it back in the ZIP. Once you have modified the audio, re-upload the zip to Connect(as Content in Content library) and you will have a new version of your recording with improved audio.

If you need to remove audio, just replace it with silence.

* Word of caution, don’t change the length of the audio file or it will be out of sync with the rest of your recording.

XML API Tips: Setting/Changing Recording Permissions

One of the undocumented workflows for Adobe Connect with regards to the XML API is working with permission levels of recordings (archives).  A recording can either be Public or Private.

The workflow is similar to that of the permission level for Meetings.  See below for the steps for making a recording Public or Private in Adobe Connect 9.1:

How do I make a Private Adobe Connect Recording Public?

https://connectURL/api/xml?action=permissions-update&principal-id=public-access&permission-id=view&acl-id=XXXXXXX

Where:
action=permissions-update
acl-id= ‘sco-id’ of the recording.
principal-id=public-access
permission-id=view

Results:

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

 

How do I make a Public Adobe Connect Recording Private?

https://connectURL/api/xml?action=permissions-update&principal-id=public-access&permission-id=remove&acl-id=XXXXXXX

Where:
action=permissions-update
acl-id= ‘sco-id’ of the recording.
principal-id=public-access
permission-id=remove

Results:

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