long flattenFlags = flattenAddMovieToDataFork |
flattenForceMovieResourceBeforeMovieData;
if (mCompress)
flattenFlags |= flattenCompressMovieResource;
long fileFlags = createMovieFileDeleteCurFile |
createMovieFileDontCreateResFile;
::FlattenMovieData(theMovie, flattenFlags, theFile, creator,
scriptTag, fileFlags);
// hmmm, even FlattenMovieData with the appropriate flags creates an
empty resource fork. this sucks.
// So we'll kill it. 286 bytes is 286 bytes!
if (::FSpOpenRF(&mMovieFile, fsRdWrPerm, &mRefNum) == noErr)
{
::SetEOF(mRefNum, 0);
::FSClose(mRefNum);
}
On 25-May-06, at 3:55 PM, Chuck Bueche wrote:
Hi folks,
For a Windows app, I'm using FlattenMovieData after adding a custom
track to a movie/file created with CreateMovieFile. Everything
is peachy, except that the call to FlattenMovieData is generating a
resource file that I don't want.
I found a thread from 2001 that had a couple of suggestions,
neither of which was useful (flatten* flags, which didn't work, and
deleting an empty resource fork, which had no example the I could
identify in spite of stating in the note that it did).
CreateMovieFile doesn't create the resource file. FlattenMovieData
does. The flags I'm using are:
_______________________________________________
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
