| |||
| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
No technical reason. It just seems a bit kludgey. Also since I have to make a temp file in which to store the data and then later flatten it to another file, it wastes time and requires scratch disk space that would otherwise not be needed. Also, with that technique one has to keep track of the temp file and delete it once the file is flattened (which QTKitCreateMovie doesn't do) since QT files could potentially be quite large and it seems very impolite to leave huge files around in the user's temp directory. In my case, that's not a big deal since I don't need to keep the QTMovie around after I've finished making it, but in a document-based application it means an extra ivar and some additional logic in the saving routines.
Yep, that's weird. GetMovieStickyError is not likely to be terribly useful when used in conjunction with QTKit method calls.
What am I doing wrong?
updateMovieFile looks at certain instance variables of the QTMovie to determine whether it can successfully update the movie file, and those ivars are not being set appropriately by your code. I think you need to follow the pattern of QTKitCreateMovie until QTKit provides a method call that will do exactly what you want. Sorry. Is there some technical reason you cannot follow that pattern?
Derrick
_______________________________________________ Do not post admin requests to the list. They will be ignored. QuickTime-API mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quicktime-api/email@hidden
| References: | |
| >Re: Creating a movie from scratch with QTKit (From: Tim Monroe <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.
