Posts in Category "Recording"

Adobe Connect – Meetings/Recordings crash with Flash Player 11.6

Posted on April 3, 2013 by Sushma | Comments (2)

Problem :

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

Environment :

Adobe Connect 9 Licensed

Reason :

We’ve identified this as a bug(Bug#3526202) and is under investigation with our Connect and Flash Engineering Teams. More updates to follow.

Solution :    

**  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.

 

Adobe Connect 9 | Pause and Resume Recordings

Posted on March 21, 2013 by Sushma | Comments (0)

With the launch of Adobe Connect 9, we have introduced some great new features in Adobe Connect Recordings like pause and resume recordings, which is expected to make them more customizable and exciting for everyone.

Here’s a short demo for some of these new features in Connect 9 :

http://my.adobeconnect.com/p7g052544vl/

http://www.youtube.com/watch?v=LpA6kpEO68M&feature=plcp

 

Connect Recording Playback Issues with Flash Player 11.4

Posted on October 27, 2012 by Jim Johnson | Comments (2)

We have just released a technote outlining a known issue with Flash Player 11.4 and Connect Meeting recording playback.

Please review the technote here:

http://helpx.adobe.com/adobe-connect/kb/connect-recording-playback-issues-flash.html

New Support Webinar: Recording Architecture and Basic Edits

Posted on October 17, 2012 by lgardner | Comments (3)

On September 28th we conducted what we hope to be the first of many public webinars hosted by the Adobe Connect support team. The first was presented by Lauren Gardner and Jaydeep Chakravarty, a recording of which can be found here:

https://my.adobeconnect.com/p8ob93tnx3x/

Support teams from Adobe’s other products are also participating in this webinar initiative; future webinars can be found on our main events page, although we hope to make a separate page for support webinars in the future.

Adobe Events: http://www.adobe.com/events/main.jsp

Adobe Connect Offline Recording FLV plays incorrectly; audio track fails to get recognized

Posted on September 16, 2012 by Sushma | Comments (6)

Problem :

I have made my Adobe Connect recording offline and when I attempt to play the FLV, the audio doesn’t get recognized by my audio player.

The audio in this file is not recognized even with most standard FLV players. If I attempt to convert it to any other format like MP4, MOV etc, the converted file doesn’t have any audio in that case.

 

Environment :

Adobe Connect 7.x,8.x,9.x Hosted/Licensed

 

Reason :

You might sometimes end up creating such an FLV file by making Connect Recording Offline. You are likely to run into this issue if you happen to resize the Adobe Connect  add-in window while your recording is being made offline.

Audio tracks in the offline recording FLV might become unrecognizable partially or completely at varying timestamps within the FLV, in any normal player. The offline FLV might also fail to play correctly sometimes on some standard players like VLC.

Our research indicated that this can be caused to happen because of resizing the Connect add-in window during the process while a recording is being made offline.

To avoid running into this problem of generating a corrupt FLV as a result of your offline recording process, you should ensure you only resize the connect add-in window prior to starting the offline making process. You can set the add-in window size to whatever size/resolution suits your requirement, however you should only do this before the offline making process starts. You can do this before hitting the button of “Proceed with offline recording” that shows up as a prompt in the below screenshot  :

 

Offline Recording Prompt

Offline Recording Prompt

 

Note that you certainly can minimize and restore the Connect add-in window while making a recording offline, however you should always avoid doing so. The reason behind this is the fact, that the size of the Connect add-in window, while making recording offline, determines the video resolution of the offline FLV being created.

Resizing it during the process, causes inconsistency of video resolution in the FLV file. And this inconsistency, sometimes results in an unrecognizable audio track in the FLV file (especially if this inconsistency is there before any audible audio in the recording).

You may also find such audio inconsistencies if you decide to edit/split the output FLV file into parts.

 

 

Adobe Connect Recording Grey pod | Displays Nothing is being shared

Posted on August 24, 2012 by Sushma | Comments (0)

Problem :

I have an Adobe Connect recording that does not display the content that was shared in the meeting. It comes up with a grey pod instead which says : “Nothing is being shared”

My content was visible to everyone during the live session, however, its now blank in the recording.

Reason:

You might be running into this issue when the content that was being brought in the share pod, has some permission conflicts, with the permissions of the user, who brought it to the room, or with the meeting.

Steps to avoid the problem :

The permissions issue has been seen to occur in such cases, where, if the host of the meeting was not a part of actual Meeting Hosts group, but, rather was a promoted guest. Such user, although gets permissions to facilitate the meeting with complete host rights, however, the user is not able to get proper permissions on the content which is being brought in the meeting and which is why the content fails to display in the share pod.

This issue can also surface if the host of the affected meeting room was not a host of the meeting template, where this content was originally uploaded.