On Aug 16, 2012, at 11:08 AM, James Sentman <[email protected]> wrote:
> Going to take a short break from hammering on this for sanity sake ;) Perhaps
> read up on the underling quicktime documentation, though i've paged through
> this part of it before without having any ah ha moments.
Ah ha :) I've got it working at least even if it a stupid hack.
spent lunch connecting it to other rtsp streams to make sure that it wasn't
just something goofy with my camera stream here that I'm connecting to and it's
not. It seems that you can't get the current frame image of a streaming movie
of any kind. And depending on the stream type all sorts of weird things happen
like it can stop and rebuffer with each call to get the NSImage even though the
returned NSImage is nil. Very weird.
BUT the QTFrameExtractorMBS WILL work if you convert the QTKitMovie to a
regular RB movie object and pass it to it. Then you can use that to extract the
frames.
The gotcha is that once you do that it will no longer honor a change of size
for the movie, so the work around is to just check the naturalmovieheight and
if the height/width are 120/140 which is currently the default quicktime
loading animation size, you just do nothing but wait. once the movie reports a
different size THEN assign the movie to the exporter and it will work. This is
a hack because those values might change at any moment of course, but it's
working for now.
Thanks,
James
James Sentman http://sentman.com
http://MacHomeAutomation.com
_______________________________________________
Mbsplugins_monkeybreadsoftware.info mailing list
[email protected]
https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
