We have released v0.91.54 into production and staging.
Here are the release notes from (Also viewable here).
New Features
- Method to upgrade Flash Player. The JavaScript library now includes a TB.upgradeSystemRequirements() method. This provides an interface for the user to update to the latest version of Flash Player. See TB.upgradeSystemRequirements()
- Event when video pauses in the Player. The JavaScript library now includes a playbackPaused event, dispatched by the Player when video playback is paused. See Player events.
- New streamNotRecording and sessionNotRecording events. In the JavaScript library, the Session object dispatches these events if you call Session.stopRecording() or Session.stopRecording() for an archive that is not recording. See Session events.
- New invalidDeviceName event. If you specify an invalid name for the microphoneName or cameraName property of the properties parameter of Session.publish(), the Publisher object dispatches an invalidDeviceName event (a DeviceEvent object). See the documentation for Session.publish() (ActionScript docs/JavaScript docs) and Publisher events (ActionScript library/JavaScript docs).
Fixed Issues
- If you repeatedly create, record, and close an Archive, the recording indicator icon does not appear in the Publisher. We have fixed this issue.
- Videos published from iOS devices stutter when viewed in a web client with Flash Player 11.2. We have fixed this issue. Use the latest version of the OpenTok iOS SDK.
- Cannot connect to a session after disconnecting from another session using the OpenTok ActionScript library.We have fixed this issue.
- The Recorder UI was sometimes stuck in an infinite loading state after saving an archive. We have fixed this issue. If you continue to see this issue, after updating to the latest version of the OpenTok JavaScript library, please contact bizdev@tokbox.com.
- The Stream.quality property was not set in the ActionScript 3 library. We have fixed this issue.
- In the OpenTok ActionScript library, Stream property values were not changed after a corresponding streamPropertyChanged event was dispatched. We have fixed this issue.
- Microphone control UI repositioning in the Publisher UI when you publish with a stream name. We have fixed this issue.
Known issues
- Stream names not appearing in Subscribers in the ActionScript library. Using the OpenTok ActionScript library, the stream name (if one is set) is not displayed in the Subscriber video.
- The Session.capabilities property is set to null when using the OpenTok ActionScript library.
- Spurious trace output when debugging with the OpenTok ActionScript library. The trace output when debugging may include extraneous content that begins with "typecheck com.tokbox.util::Helper/getEnhancedMicrophone()".
- In Firefox running on Mac OS, you sometimes cannot click the Allow and Deny buttons in the Flash Player camera acquisition dialog box. If the users resizes the browser window slightly, the controls become available. This happens if the OpenTok Publisher or Device Panel is automatically positioned on the page. To workaround this issue, use absolute positioning, or ensure that the x and y coordinates of these widgets are integers. (This issue is fixed in Firefox 4.)
- Mic volume meter initially non-responsive. The microphone volume meter in the publisher display is non-responsive when you first display it.
- Camera conflict with Gmail. The camera in an OpenTok app may disconnect or stop streaming when you open or close Gmail in another browser tab.
- A Publisher or Subscriber is destroyed when I set the CSS style of the container DIV to display:none This is a known issue in Firefox and Chrome (see Mozilla bug 90268).
- An application can hang when using the device panel if the user detaches a camera or microphone. This is an issue with Flash Player, and a bug has been filed with Adobe.
- The status property of a Camera object in the list of cameras for the deviceStatusEvent object is sometimes incorrectly reported as "unknown."
- High white balance in the Motorola Xoom camera. When publishing from an AIR app for Android on the Motorola Xoom, the camera white balance can become unacceptably high. This appears to be an issue with Adobe AIR and it has been reported to Adobe.
- Flash Player crashes upon publishing a video when using certain camera drivers. We are researching this issue.
- Support in AIR for iOS. Adobe AIR for iOS does not support H.264 video delivered on RTMP, which includes video streams published in browsers that have Flash Player 11 installed.
