Skip to main content
Participant
May 15, 2012
Answered

VideoDisplay got issues in AIR 3.2?

  • May 15, 2012
  • 3 replies
  • 946 views

We have an application which is kind of an e-learning platform. This app has classrooms where we play video and audio files separately for language independence. No streaming of video or audio.

We use mx:VideoDisplay component to display video so that we can use custom sliders (progress bar) to seek through the video. This was working fine till AIR 3.1. But with AIR 3.2 this is acting up. When seeked with the progress bar the video gets stuck, and may/may not play after sometime.

The same is with maximising the video. When the user opts to maximize the video we pass the playheadtime value to a separate player in another canvas. Then also the video gets stuck and may play after sometime.

In both these cases when the video finally plays, it looks like its on steroids! It keeps jumping through frames till it reaches current playheadtime specified when seeked.

Anyone else got similar issues?

<mx:VideoDisplay id="player"

     click="maximize()" autoPlay="false"

     maintainAspectRatio="true" playheadUpdate="videoDisplay_playheadUpdate(event);"                                                   volume="0.0"/>

<mx:ProgressBar id="progressBar" click="navigateVideo(event);" mode="manual"  width="200"

                                    visible="true" height="10" buttonMode="true"/>

private function navigateVideo(evt:MouseEvent):void

            {   

                if(!stopFlag)

                {

                    var temp:Number=(evt.localX/progressBar.width) * player.totalTime;

                    temp = Number(temp.toFixed(3));

                    player.playheadTime = temp;

                }               

            }

*Flex 4.5.1

*Flash Builder 4.5

*Windows 7

This topic has been closed for replies.
Correct answer chris.campbell

Could you give this a try with our AIR 3.3 beta 3 release?  If it still occurs, Please open a new bug report on this over at bugbase.adobe.com.  Please post back with the URL so that others affected can add their comments and votes.

3 replies

chris.campbell
chris.campbellCorrect answer
Legend
May 16, 2012

Could you give this a try with our AIR 3.3 beta 3 release?  If it still occurs, Please open a new bug report on this over at bugbase.adobe.com.  Please post back with the URL so that others affected can add their comments and votes.

evyavanAuthor
Participant
May 16, 2012

Thank you Chris. It works perfectly in 3.3 beta.

chris.campbell
Legend
May 17, 2012

Great, thanks for the feedback!