I cannot for the life of me, despite being a fairly decent developer, get the AIR API to successfully display/play a video saved locally in any of the following locations: ApplicationStorageDirectory, system CameraRoll, system Tempspace (where the video is saved when delegation is complete using CameraUI.
I can manipulate the -file- using the API file classes/methods all I want, but I cannot get it to open/view/display/play in my app using either the Video or StageVideo classes.
I actually want to -initially- use the Video class because the StageVideo class doesn't make the BitmapData available and I need to harvest a screen capture to store as a thumbnail. Then I believe I wish to use the advantages of GPU and whatnot available via the StageVideo class.
Using Netstream of course.
This does work (somewhat) within Android (my code/logic, I mean).
I should also note that these videos are, of course, in the device's -native format-, not some random downloaded format, because all video content is created using the system camera delegated via CameraUI.
It occurs to me, now, after weeks of playing with it off and on, that someone out there might have a good working example and I should stop trying to re-invent the wheel, or at the very least they might tell me of pitfalls, device/OS specific limitations that aren't in the documentation, or, best of all, ways in which the mobile AIR API just fails.
Cheers and much gratitude for any examples.
Dev Environment: 32" iMac Quad-core, Bootcamp Windows 7 Enterprise, Flashbuilder 4.7, Flex SDK 4.6.0 (build 23201), AIR SDK 3.6, compiler arg: -swf-version=19.
Dev Targets: Samsung Galaxy Tab 10.1 (Android 4.0.4), Apple iPad2 (iOS 6.1.2), Apple iPad1 (iOS 5.1.1), Apple iPod Touch Gen4 (iOS 6.1.2), Apple iPhone 3GS (iOS 6.1.2)
To be honest, I'm wondering if the lack of examples/tutorials (where I usually find some on most any subject) is due to a) 'duh, this is simple, nobody else is making the sow's ear of it that you are mate' or b) people are asking and nobody has a solution (seems terribly unlikely).
I cannot for the life of me, despite being a fairly decent developer, get the AIR API to successfully display/play a video saved locally in any of the following locations: ApplicationStorageDirectory, system CameraRoll, system Tempspace (where the video is saved when delegation is complete using CameraUI.
I can manipulate the -file- using the API file classes/methods all I want, but I cannot get it to open/view/display/play in my app using either the Video or StageVideo classes.
I actually want to -initially- use the Video class because the StageVideo class doesn't make the BitmapData available and I need to harvest a screen capture to store as a thumbnail. Then I believe I wish to use the advantages of GPU and whatnot available via the StageVideo class.
Using Netstream of course.
This does work (somewhat) within Android (my code/logic, I mean).
I should also note that these videos are, of course, in the device's -native format-, not some random downloaded format, because all video content is created using the system camera delegated via CameraUI.
It occurs to me, now, after weeks of playing with it off and on, that someone out there might have a good working example and I should stop trying to re-invent the wheel, or at the very least they might tell me of pitfalls, device/OS specific limitations that aren't in the documentation, or, best of all, ways in which the mobile AIR API just fails.
Cheers and much gratitude for any examples.
Dev Environment: 32" iMac Quad-core, Bootcamp Windows 7 Enterprise, Flashbuilder 4.7, Flex SDK 4.6.0 (build 23201), AIR SDK 3.6, compiler arg: -swf-version=19.
Dev Targets: Samsung Galaxy Tab 10.1 (Android 4.0.4), Apple iPad2 (iOS 6.1.2), Apple iPad1 (iOS 5.1.1), Apple iPod Touch Gen4 (iOS 6.1.2), Apple iPhone 3GS (iOS 6.1.2)
To be honest, I'm wondering if the lack of examples/tutorials (where I usually find some on most any subject) is due to a) 'duh, this is simple, nobody else is making the sow's ear of it that you are mate' or b) people are asking and nobody has a solution (seems terribly unlikely).
0 commentaires:
Enregistrer un commentaire