I agree!<br>It would guarentee better results but would increase the chance of a cpu lock up I think!<br><br>Tom<br><br><div><span class="gmail_quote">On 10/11/07, <b class="gmail_sendername">Roman Haefeli</b> <<a href="mailto:reduzierer@yahoo.de">
reduzierer@yahoo.de</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;">On Fri, 2007-10-12 at 01:49 +0200, Roman Haefeli wrote:
<br>> On Fri, 2007-10-12 at 00:48 +0200, cyrille henry wrote:<br>> ><br>> > Thomas O Fredericks a écrit :<br>> > > "sync to vblank will sync swapping buffer with the screen frame rate, but<br>
> > > that's not the original question.<br>> > > to my knowledge, there is no possibility to sync gem rendering with the<br>> > > screen frame rate.<br>> > > if you fix both at 60Hz, you can have jitter (not a lot, but some)."
<br>> > ><br>> > > You are not technically syncing gem to the screen frame rate.<br>> > yes<br>> > > You are<br>> > > syncing the open gl redraw to the framerate.<br>> > yes
<br>> > >The GPU takes care of that.<br>> > ><br>> > i don't understand this.<br>> ><br>> > if you get gem to render a 60FPS, you will have 60fps based on the pd (cpu) clock.<br>>
<br>> i don't know this by reading the code, but for me it would only make<br>> sense to get the clock from the audio-card, nothing else. this is also<br>> what i experienced, when pd was running on jackd, while jackd was
<br>> believing to be running at 44100Hz, while it was actually at 48000Hz.<br>> all [metro]s were too fast and all pitches too high. the only objects,<br>> that seems to work not with the audio-clock, that come to my mind, are
<br>> [cputime] and [realtime] (is that true?)<br>><br>> > if you set your screen at 60fps, you will have 60fps based on the gpu.<br>> > there is no way to make the cpu clock to be exactely the same speed as the gpu clock.
<br>> > so, sometime (specially with big patch), you can have desincronisation between this 2 clocks, even if they should be at the same speed.<br>> > (there is a also a lot's of jitter in pd clock)<br>>
<br>> what makes you think that? i 'd claim, that pd's clock is stable, unless<br>> you get audio drop-outs.<br><br>yo, it seems, that [gemhead] uses pd's logical time, which probably<br>makes a lot of sense for many applications.
<br><br>but for many other applications it would be better (read: the result<br>would look nicer), if [gemhead] would get it's tick from the gpu and not<br>from pd/audiocard, i think.<br><br>is that something that would be possible to do and might be worth a
<br>feature request on gem-dev?<br><br>roman<br><br><br><br><br><br>___________________________________________________________<br>Telefonate ohne weitere Kosten vom PC zum PC: <a href="http://messenger.yahoo.de">http://messenger.yahoo.de
</a><br><br><br>_______________________________________________<br><a href="mailto:PD-list@iem.at">PD-list@iem.at</a> mailing list<br>UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list">
http://lists.puredata.info/listinfo/pd-list</a><br></blockquote></div><br>