wrench

As the topic suggests, I'm trying to load a StageVideo via VideoLoader and setting a repeat property of -1 and when the video completes, it simply stops. Disabling the StageVideo and using the Video allows the repeat property to work (though it is a bit jerky). Has anyone else been using VideoLoader with StageVideo and experienced the same thing. I can kind of work around it listening for the netstreams NetStatusEvent's (NetStream.Play.Stop) but there's a black frame that appears between the repeats then and it's far from seamless. Any assistance much appreciated.

Just found the following information in the Support for H.264 encoded video in AIR for iOS section of the Adobe documentation for NetStream which corroborates what I mentioned above: help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/net/NetStream.html

I can't get a normal video instance to work on iOS so StageVideo is all I'm able to test with. I guess the idea of VideoLoader is to abstract away all of the inconsistencies that exist in the NetStream codebase, and it would appear that there's a bunch more introduced by StageVideo and Air for mobile development. ImageLoader is working fine for me on iOS. Using Air 3.3Beta causes the video to not display at all. I'm still investigating things and will reports back if I have any breakthroughs.

Logging another oddity with the VideoLoader class when used to load StageVideo on the iPad. When calling cancel on Air for Desktop (and the normal Flash plugin) the loader stops it loading, but does nothing to the video stream it is loading. Calling the same method when on iOS seems to remove the stream all together, effectively causing the video to disappear immediately. Would love to get some feedback from others using this framework to load video into iPad via Air.

Just a bit of a heads up for any folks using Air on iOS to be careful of relying on the VideoLoader's complete and progress events. Is looks like netStream's attached to a StageVideo instance on iOS never report anything their bytesLoaded as being 0, and thus the mechanism for VideoLoader to report on it's loading progress is lost. Took me a while to figure out that that was what was going on, so hopefully this post will help somebody else. If there's any workarounds for this, I'm all ears