> You've got re-entrancy problems. You'll need to keep your own separate
> queue of files waiting to be converted, and when Quicktime finishes one,
> hand it the next. If the user adds more files while this is going on,
> just add them to the queue. Quicktime will see only the single thread of
> work it is supposed to do, and its conversion pipeline won't get
> scrambled.
Hello
Can u plz tell me what u meant by re-entrancy problem exactly.
If i initialize QuickTime media layer once in my application then
can't i have two threads running simultaneously one retriving mov file
properties and the other converting mov files.
Did u mean that QuickTime can do one work at a time?
Do u know of any way where in i can have two threads running at the
same time,
one getting the mov file properties and the other converting mov
files?
Further light on this problem will help me
Thank You
Jon Summers - 28 May 2004 14:04 GMT
> If i initialize QuickTime media layer once in my application then
> can't i have two threads running simultaneously one retriving mov file
> properties and the other converting mov files.
No, you get re-entrancy problems.
> Did u mean that QuickTime can do one work at a time?
Yes
> Do u know of any way where in i can have two threads running at the
> same time,
> one getting the mov file properties and the other converting mov
> files?
Use a mutex/semaphore between your threads anywhere you call QuickTime.
Grab/release the mutex/semaphore for the ConvertMovieToFile() call
and grab/release the mutex/semaphore for retrieving mov properties
> You might have better luck asking questions like this on a list where
> people are using VC++.
Try the Apple quicktime api list
<http://www.lists.apple.com/mailman/listinfo/quicktime-api>
IMHO VC++ is the more productive debugging environment for Windows QuickTime
development. Thankfully I have no plans to do any

Signature
jons(AT)vrtools(DOT)com