[jitter] 2 movies - 4 cores - Best way to use them

Wed Sep 19 06:52:57 MDT 2007

sounds like a very reasonable method :)

On Sep 19, 2007, at 7:23 AM, yrp wrote:

>
> Hello,
>
> I'm working on a movie player for a show (like a lot of people  
> here), and I'm looking for the best way to get the smoothest  
> possible playback (like everybody here &#8230;), considering some  
> posts, I've got some ideas, but I'm asking for some advice&#8230;
>
> There's no complex image processing, I just need to play back  
> simultaneously 2 movies (768 x 576 pixels, 25 fps) from 2 playlists  
> and display them in 2 jit.window (to 2 videoprojectors).
> The computer will be a Mac Pro with 2 x 3.0GHz Dual-Core Intel  
> Xeon, 2 GB of RAM and 2 x Nvidia Geforce 7300 GT.
>
> So,
> in order to make the best use of the 4 cores, I'm thinking of  
> implementing 4 patches running in 4 instances of Max Runtime which  
> will intercommunicate with udpsend/udpreceive :
> - one instance/patch would be dedicated to the (light) graphical  
> interface (transport commands, basic monitoring, playlist in a  
> jit.cellblock)
> - another instance/patch would be the software core (ui logic,  
> management and transmission of the commands&#8230;)
> - 2 instances/patches would be the movie players themselves, each  
> of the two is based on the Poly~ForMovies.pat example (jit.qt.movie  
> in poly~) and a jit.window (jit.qt.movie are in directwindow mode).
>
> My first question to the experts is : am I on the right way or am I  
> totaly wrong ??
>
> then, I'm asking if there's a benefit to use a unique clock (metro)  
> placed in the "software core" instance and transmitted to the  
> players instances with netsend or if it would be better to put one  
> metro in each of the two players instances.
>
> any advice is welcome, many thanks !
>
> yann
>
> _______________________________________________
> jitter mailing list
> jitter at cycling74.com
> http://www.cycling74.com/mailman/listinfo/jitter

v a d e //

www.vade.info
abstrakt.vade.info


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.cycling74.com/pipermail/jitter/attachments/20070919/07983258/attachment.htm