I was not aware of this one, so probably not known. Any chance you could send me your app so I could verify it internally? Feel free to contact me directly at firstname.lastname@example.org. In addition, could you 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.
Is there any update?
I faced the same problem and need a fast solution.
We're actively working on this bug, unfortunately I do not have any workarounds for you at this time (other than rolling back to the previous AIR runtime).
If you have a minute, please visit bellesoft's bug and cast your vote.
My testing team reported a bug which said there was a problem with seeking the video. I am using mx:VideoDisplay component and the problems surfaced after upgrading to 3.2 runtime. Why I am saying this is I have 3.1 sdk with my FB and this problem is not there when I debug the app, but when I export a build and install it, the problem begins with 3.2 runtime runtime. I was not aware of this difference as the update happens automatically. Is there any solution to go around this one? Also, I am now downloading the 3.2 sdk so that I can try debugging with 3.2 environ.
Video display is straight forward, but the problem occurs only when I try to seek it or maximize the display, ie, when we have to deal with playheadtime.
Message was edited by: evyavan