I have a video player built using MediaPlayer and MediaPlayerSprite that plays HTTP Dynamic streams. Sometimes the aspect ratio of the stream changes and AFAICT, the aspect ratio change is not recognized by the OSMF framework. The video dimensions stay the same as the first frame of *rendered* video. The MediaPlayerSprite instance's scaleMode property is set to letterbox, so that's not the issue. I can confirm that the MediaPlayer instance knows nothing about a changed aspect ratio by polling mediaWidth and mediaHeight and MediaPlayer doesn't dispatch any DisplayObjectEvent.MEDIA_SIZE_CHANGE events.
As an aside, the behavior has changed between 1.0 and 1.6. In 1.0, the dimensions in the manifest were respected, but with 1.6, the dimensions of the inital frame of rendered video stick. My player actually seeks upon receiving a MediaPlayerStateChangeEvent with state MediaPlayerState.PLAYING, so there can be a mismatch between the dimensions of the inital frame of rendered video and the manifest. This is not the source of the problem; it occurs whether or not the inital rendered frame dimensions match the manifest.
Any advice as to whether this is a bug/missing feature or whether there's a way to detect this?
Mediaplayersprite is used for simple applications.
Please use MediaContainer for more complex applications (See helloworld8, for example).
You can inspect the SMP code for DisplayObjectEvent.MEDIA_SIZE_CHANGE events - they are indeed dispatched.
I don't believe that this is related to MediaPlayerSprite vs. MediaContainer, as I've attached listeners to the MediaPlayer and am polling its mediaHeight and MediaWidth. Furthermore, the aspect ratio does not change with the SMP player currently available for download, nor do I see events dispatched other than the initial resize event:
org.osmf.events::DisplayObjectEvent (oldHeight:NaN newHeight:352 newWidth:625 type:mediaSizeChange oldWidth:NaN )
The issue is that the aspect ratio of the content changes while playing back and the initial dimensions are no longer correct. For example: the initial aspect ratio of the content is 16:9. The player correctly starts showing the content at 16:9. The content switches aspect ratio to 4:3, but the player continues to display at 16:9 and there is no resize event triggered.
The size changes appear for MBR assets (please check the SMP debug.html page).
If you encountered it on adifferent use case, please raise an issue at http://bugs.adobe.com/jira/browse/FM with a code snippet allowing to reproduce it.
Europe, Middle East and Africa