HI jfk,
"But I wish I could choose the codec and do the overwrite confirmation automaticly"
- Windows is probably not going to let you do that automatically. It has to search for codecs then offer them to the user (- you did spot that function, didn't you?).
"Do you know a commandline tool that is capable of adding sound to an avi?"
- Sorry, no.
"BlitzMovie creates a BlitzCC crash when the program ends"
- The author's currently rewriting it. If I hear anything I'll keep you posted.
"it still sometimes fails to deliver the requested 1-frame movie"
- Unfortunately I have no need to get a single frame, so I've not investigated this sort of functionality.
"Maybe I should try MCISendstring"
- Like you I'm really frustrated about MCISendstring.
I used it for years with varying degrees of success (professionally for 8 years) but it always was a pig.
It's multi-tasking really is mutitasking: you issue one instruction and before it can complete it, it's already tackling the next. Usually the "wait" parameter cured that, but probably now screws up since MCI's probable point of view is that the Blitz window is a DOS window (?).
Ongoing frustration for everyone who needs to use movies.
I've emailed Blitz Support (a couple of months ago) about the memory leak in OpenMovie()/CloseMovie(), but no reply so far.
"But I wish I could choose the codec and do the overwrite confirmation automaticly"
- Windows is probably not going to let you do that automatically. It has to search for codecs then offer them to the user (- you did spot that function, didn't you?).
"Do you know a commandline tool that is capable of adding sound to an avi?"
- Sorry, no.
"BlitzMovie creates a BlitzCC crash when the program ends"
- The author's currently rewriting it. If I hear anything I'll keep you posted.
"it still sometimes fails to deliver the requested 1-frame movie"
- Unfortunately I have no need to get a single frame, so I've not investigated this sort of functionality.
"Maybe I should try MCISendstring"
- Like you I'm really frustrated about MCISendstring.
I used it for years with varying degrees of success (professionally for 8 years) but it always was a pig.
It's multi-tasking really is mutitasking: you issue one instruction and before it can complete it, it's already tackling the next. Usually the "wait" parameter cured that, but probably now screws up since MCI's probable point of view is that the Blitz window is a DOS window (?).
Ongoing frustration for everyone who needs to use movies.
I've emailed Blitz Support (a couple of months ago) about the memory leak in OpenMovie()/CloseMovie(), but no reply so far.