With the caveat that I haven't actually tried it, would it make more sense to be streaming the movie data to a local file, then specifying the URL/path to the file in the initializer method of one of the movie player classes? If the player can handle the case where not all the movie data is present then it should just "do the right thing." The benefit is that you can use the same code to play the movie, no matter how much of it is local.
On Jul 5, 2011, at 8:03 PM, John Michael Zorko wrote: > I'm interested in caching a movie as I play it from the internet, so that the > next time the user asks for the movie, it can play it from the device > filesystem. I'm thinking capturing frames and audio and using an > AVAssetWriter like I would when recording from the camera, but i'm not sure > if this will work when "recording" from a playing asset. Would anyone > illuminate me as to whether this is possible, or if I need to explore other > ways of doing this (which would probably be a lot less cool and efficient > than doing it this way, alas)? _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
