Loading...

quicktime-api@lists.apple.com

[Prev] Thread [Next]  |  [Prev] Date [Next]

Re: [QTTrack addImage:] and memory usage Tim Monroe Thu Apr 26 12:04:02 2007


On Apr 26, 2007, at 12:06 PM, Daniel Kennett wrote:

Looks like I spoke too soon!

It's much better, but after a while I still get malloc errors. I think the movie is simple taking up too much memory as it's being built. Are there any other techniques to try, such as caching the video to disk as it's being built? I've watched the program in ObjectAlloc and I'm not leaking anything in my code.

And another Tim replied:

Are you using a temporary file as your movie backing store? If not, there's a good example using QTKit here

        http://developer.apple.com/samplecode/QTKitCreateMovie/


Good advice. Another thing to keep in mind is that QTTrack's addImage does not currently perform any interframe (or temporal) compression on the images added to the specified track. If the images you are adding are sufficiently similar to one another from frame to frame, you are probably better off ditching addImage and dipping down into the QuickTime C API for this part of your application.


Tim Monroe
QuickTime Engineering
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
QuickTime-API mailing list      ([EMAIL PROTECTED])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quicktime-api/alexiscircle%40gmail.com

This email sent to [EMAIL PROTECTED]