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.
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:
To change this to open with the index closed, append pbEIOpen=false like this:
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:
In either case, checked or unchecked, the host needs to first start the audio conference within any meeting:
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):
Note that by default, when UV is in use, the telephony option is checked for the participant:
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:
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.
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:
Referencing content by parsing a username and password:
<iframe src=”http://firstname.lastname@example.org&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:
<td width=”600″><iframe src=”http://connectdomainname.adobeconnect.com/customurl1″></iframe></td>
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…
[Root Connect Install]\9.1.1\appserv\common\meeting\shell
This directory should contain the following SWF files:
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.
[Root Connect Install]\9.1.1\appserv\common\meeting\launcher
This directory should contain the following SWF files:
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.
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.
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?
acl-id= ‘sco-id’ of the recording.
How do I make a Public Adobe Connect Recording Private?
acl-id= ‘sco-id’ of the recording.
More often than not people find it difficult to edit their recordings effectively, specially in cases where only one second needs to be cut out from the recording. It may take a lot of time to place the triangular cursors exactly at the position you want them to be.
Here is a small tip that will make your life a lot simpler:
1. Pause the recording from where you want to start your editing.
2. Double Click on the LEFT marker. It will take both the markers to that point on the recording timeline.
3. Play the recording and pause the recording again at the point till where you want to edit the recording.
4. Double Click on the RIGHT marker. It will take the right marker to the end point of your to-be-recording.
5. Cut and Save.
PS: Please note that this tip is for Adobe Connect 9.1 and may/may not work with other versions of Connect.
Issue: Anything that may happen during a meeting which has a pejorative effect on end-user experience.
Solution: In Connect 9.1 we have a great diagnostic option in the meeting room. You can immediately pull logs from any meeting to diagnose:
If you click Help>About Adobe Connect, while holding down the Ctrl key, the debug logs will appear int he meeting room and you will have the option to copy them to your clipboard.
Sending me these, along with the RTMP string Help> About Adobe Connect, while holding down the Shift key – this will be most helpful from the client experiencing the extreme latency.
Now if you want to take it even one step further and provide a client-side view of the meeting:
The instructions for enabling client-side logging are here: http://helpx.adobe.com/adobe-connect/kb/enable-logging-acrobat-connect-professional.html
Providing all this data along with the date and time (including timezone) and Meeting URL of any issue, will greatly expedite analysis and solution.