Posts in Category "Meeting"

Disabling “Raise Hand” Feature

Emoticons (status options) are a way for participants to communicate with the meeting host or presenter.  Emoticons can be used to give a host or presenter feedback on their presentation- such as applause, requests to speak louder /slow down.  They are also used to ask and answer questions.  Adobe Connect includes the following emoticons:

  • Raise Hand
  • Agree/Disagree
  • Step Away
  • Speak Louder/Softer
  • Speed Up/Slow Down
  • Laughter
  • Applause

A participant’s emoticon appears next to their name in the Attendee Pod.

We can disable “Raise Hand” feature in the meeting room.

 

Below are the steps to disable the Raise Hand feature.

 

Step 1

Open the meeting in which we want to disable the Raise Hand feature

image1

Step 2

Go to “Meeting” menu at the top left corner of the meeting then Click on “Preferences”

image2

Step 3

Click on “Attendees Pod” option then click on “Disable Raise Hand” check box and Click on done

image3

Step By Step Video

You can refer to the below screen capture (video tutorial)

Setting pod in meeting to full screen

Full screen is a good feature when presenter wants the attendees to pay attention to a specific pod.  This helps in increasing the engagement of participants.

There are two ways to make a pod full screen.

First -The Maximize button in pod options when clicked makes the pod full screen into the meeting room.

image1image2

image3

image4

To restore that pod to original size, click on restore button which restores the pod.

image5

Second :pods like video and share pod (when we are sharing something) have a button from where we can make it full screen.

image6

image7

Step By Step Video

Delete duplicate users from “Attendee Pod”

Attendee Pod has the information about all the attendees.  Sometimes there are duplicate attendees in the meeting which is caused by user error when a user opens two instances of the meeting room.  In the below screenshot, we can see that a participant with the name “Adobe” appears twice in the meeting.

We can remove the duplicate users by following the below mentioned steps:

Step.1

Click on the duplicate attendee which you want to remove from meeting in attendee pod.

2014-08-02 01_29_24-image1.jpeg - Windows Photo Viewerimage2

Step.2

Click on the first icon which has four bars present at the top of attendee pod -> then select “Remove Selected user”

image3

 

Change meeting room background

One of the greatest feature Adobe Connect offers is that we can change the look and feel of the Meeting room.  We can change and create the new layouts, we can change the pods name and even can change the background of the meeting rooms.  Mentioned below are the steps to change the background of the meeting room.

Step.1

Open the meeting and click on the Meeting button

image1

Step.2

Click on the Preferences in drop down menu

2014-08-01 23_33_22-Change meeting room background.docx - Microsoft Word

Step.3

Under the General menu we will get the option “Room appearance where we can click on the upload button

2014-08-01 23_34_04-Change meeting room background.docx - Microsoft Word

Step.4

There are two ways to select the file either we can select it from previous uploaded file or we can upload a file from our computer by selecting “Browse My Computer option.

4.A Selecting file from previous uploaded files.

2014-08-01 23_34_27-Change meeting room background.docx - Microsoft Word

4b.Browsing file from computer, by clicking on the Browse My Computer

2014-08-01 23_36_12-Change meeting room background.docx - Microsoft Word

Note: File’s dimensions should be 1024×768

Step.5

Here we can select the Alignment of file from drop down menu, file can be aligned :-

Top-Left, Top-Right, Bottom-Left, Bottom-Right

Click on Done

2014-08-01 23_37_28-Change meeting room background.docx - Microsoft Word

Final look of meeting

2014-08-02 01_01_39-Change meeting room background.docx - Microsoft Word

 

 

H.264 encoded FLV not displayed when it is reshared again in share pod

Issue: H.264 encoded FLV not displayed when it is re-shared again in share pod.

Steps to reproduce:

1. Share H.264 encoded FLV in a share pod.
2. Stop sharing (without viewing it completely).
3. Share the FLV again from the share history.

Result:Video bar progresses but the audio and video is not rendered.

Reason: The FLV encoded in H.264 has this limitation that unless initialized from beginning it will not render video (and audio)  frames. When we share it from ‘recently shared content’ it is not initialized from the beginning. Server tries to play it from the last cue point, which causes this issue. If we seek it to a position it starts to play well.
The behavior is not seen in VP6 encoded FLVs.

Workaround:

  1. Seek to start of the recording. Once initialized, we can seek to any point and it will play just fine.
  2. Re-encode the FLV with VP6 codec.

Unable to share images and flash files in meeting room after changing the default port from 80 to another port

We have recently discovered a new problem where you might run into an error when trying to share any content in a meeting room, eg images, flash files etc., if you have changed the default HTTP port of the Connect server from 80 to any other port.

Environment : On Premise Installation

Method: Follow this blog procedure to change the default http port of the Connect server : http://blogs.adobe.com/connectsupport/configure-your-adobe-connect-8-server-to-override-the-default-http-port-80/

Result: On-demand contents work fine but any contents shared in the meeting room are blank

Workaround: Use only default ports to avoid this issue.

Additional Information:  The meetings should launch fine but you might not be able to view any content in the meeting room. If you launch a content from content library it works fine. Changing the default http port is only supported for on demand contents as of now. Contents might not work if accessed from a meeting room.

We have logged a Feature Enhancement Request regarding this targeted as #3744993. Engineering is currently reviewing the feasibility of including this feature in a future release.

Admin user enters into the meeting room as participant.

 

Problem: Admin user enters into the meeting room as participant.  This issue only occurs in “Named Host Pricing Model”.

Environment: Hosted/ Licensed

Reason: In Named Host Pricing Model users have to be part of Meeting Hosts Group in order to enter into the meeting as Host.  Only being member of Administrator group will not allow the user to enter as a host in his own meeting.

Solution:

  • Make sure that you are listed as a host for the meeting room under Edit Participants link.

Image-1

  • Make sure that you are a part of Meeting Hosts group. In order to know your group membership click on my profile>group membership. If you don’t see meeting hosts listed there then follow the instructions given below.
  • Go to Administration>Users and Groups.
  • Select Meeting hosts>Choose Information>View group members.  Add your name to this group.

Image-22

 

You can now try to enter the room.  If you are still getting the same issue contact Adobe Connect Support.

 

Ensuring that Email Generated by Adobe Connect Servers is Received

There have been more than a few incidents reported on the topic of email messages from Adobe Connect servers not getting delivered. These include messages generated by the Adobe Connect Events module as well as system email messages such as that generated by changing a password.

The first thing to avoid to prevent this problem is that of using special characters in the host’s name. This is scheduled to be fixed in Connect 9.3, but currently, in 9.2, if you place a comma in the Event host’s name such as Frank D., El Presidente’  it will cause an error identified in our server logs by a messaging exception.

The second thing to avoid is inviting over 20,000 participants to an Event. This generates an operation size error and causes problems with email messages being sent out. We also plan to address this ceiling tentatively in Connect 9.3.

With specific reference to Adobe Connect Hosted accounts, we just made the following change to ameliorate email problems: As of April 28th, 2014, administrative email notifications sent from Adobe Connect servers will now be coming from admin@adobeconnect.com instead of admin@acrobat.com This will help by disassociating Connect-generated email from that of the Acrobat domain which could be potentially blocked by virtue of its identification with document storage. We also made some internal changes to the way the Connect servers handle email and we worked with our Web infrastructure partners to insure that Connect generated email was not being treated as SPAM on the Web.

There is a bit of a conundrum here. If Adobe Connect Events email invitations are sent out in massive mailings to those who perceive the email as SPAM, then the Adobe Connect servers could be tagged as producing SPAM by those end-user recipients. An overzealous Events manager may cause Gmail and other providers to treat Adobe Connect email as SPAM. When an Event that is capped at 500 participants sends out 5000 email invitations, it is expected that many recipients will at best ignore the inbound email traffic and many more may consider the traffic to be a nuisance. We are investigating possible approaches to ameliorate this problem and plan in 9.3  to add an opt-out option for Events invitations that will offer a convenient alternative to any SPAM reply option for recipients to invoke.

We love large Events and Adobe Connect handles them very well; this is a case when our success can potentially lead to some problems. Currently the Adobe Hosted Service is green for SPF record checks.  We pass all major email providers and are not blacklisted according to common checker tools on the internet.  This should resolve the lion’s share of current email issues and the upcoming changes in 9.3 will serve to harden this capability for future Events.

Connect 9.1.x on-premise server – “Send Invitations” checked by default

When creating a new meeting you are asked if you want to send out meeting invitations by email.

In Connect 9.1.x the option to send invitations is selected by default.

If you do not wish to send out invitations for your meetings you have to select “Do not send invitations” every time you create a new meeting.

sendInvitations

You can change this behavior to make  “Do not send invitations” the default when creating a new meeting.

To do so, edit the notify.xsl file which is located in \Connect\9.1.1\appserv\apps\meeting\  ( but please remember to take a backup copy of the file).

1. Open the notify.xsl in an xml-friendly editor such as notepad++

2. Find this section:

<table cellpadding=”0″ cellspacing=”0″>
<xsl:call-template name=”input”>
<xsl:with-param name=”title”   select=”‘send-invitations’”/>
<xsl:with-param name=”name”    select=”‘date-scheduled’”/>
<xsl:with-param name=”type”    select=”‘radio’”/>
<xsl:with-param name=”value”   select=”/results/common/date”/>
<xsl:with-param name=”checked” select=”true()”/>
</xsl:call-template>

<xsl:call-template name=”input”>
<xsl:with-param name=”title”   select=”‘no-invitations’”/>
<xsl:with-param name=”name”    select=”‘date-scheduled’”/>
<xsl:with-param name=”type”    select=”‘radio’”/>
<xsl:with-param name=”value”   select=”‘ignore’”/>
<xsl:with-param name=”checked” select=”false()”/>
</xsl:call-template>
</table>

3. Change “false” to “true” and “true” to “false” to swap the selection.

It should now look like this:

<table cellpadding=”0″ cellspacing=”0″>
<xsl:call-template name=”input”>
<xsl:with-param name=”title”   select=”‘send-invitations’”/>
<xsl:with-param name=”name”    select=”‘date-scheduled’”/>
<xsl:with-param name=”type”    select=”‘radio’”/>
<xsl:with-param name=”value”   select=”/results/common/date”/>
<xsl:with-param name=”checked” select=”false()”/>
</xsl:call-template>

<xsl:call-template name=”input”>
<xsl:with-param name=”title”   select=”‘no-invitations’”/>
<xsl:with-param name=”name”    select=”‘date-scheduled’”/>
<xsl:with-param name=”type”    select=”‘radio’”/>
<xsl:with-param name=”value”   select=”‘ignore’”/>
<xsl:with-param name=”checked” select=”true()”/>
</xsl:call-template>
</table>

 

4. Save the file and restart the services.

5. Check your changes by creating a new meeting. If you encounter any issues, restore the original file.

 

 

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