<br><br><div><span class="gmail_quote">On 4/18/07, <b class="gmail_sendername">cyrille henry</b> <<a href="mailto:cyrille.henry@la-kitchen.fr">cyrille.henry@la-kitchen.fr</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>><br>><br>> Depends on what codec you use. All of the DV codecs use multiple<br>> threads to<br>> decompress and so does Apple Intermediate Codec.<br><br>i made a test patch that should decompress and display about 10 DV
<br>quality movie.<br>the activity monitor says that pd use more than 30 threads.<br>BUT, pd use 25% of every core, and GEM display 3 images /s.<br>there is a problem somwhere, but i can't find what.</blockquote><div>
<br>Which version of GEM? There is a problem with the QT DV component looping the audio track that will do exactly what you describe. I disabled the first audio track in any movie file in the GEM code but your clip might have more than one audio track.
<br><br>Also at a certain point you will hit the limit of what the machine will do. The Mac 'Pro' isn't as fast as Apple's marketing wants it to be. The Intel chips have serious memory bus speed problems and the OSX kernel likes to destroy any CPU affinity.
<br><br>If you do not need any pix_ objects for processing then use pix_movie. That will improve performance quite a bit since it uses the fastest texturing path. <br></div><br><br></div><br>