<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Isadoras frame timing.]]></title><description><![CDATA[<p>it would be great to have some solid way of triggering events with frame timing. <br /></p><p>Let’s say I have a tap tempo that I want to use to flash a video on a screen (this was my actual setup when I encountered this). <br /></p><p>It feels like the events became really lose and the timing between flashes was quite uneven. I know that some calculations will not land on a frame but these seemed to be more off than just landing on the next frame. <br /></p><p>To be sure I was running with 300 cycles and mostly 24.9 fps and 50% load. </p><p><br />I understand that a lot needs to happen but this patch was simple, it just used 3 large NDI screens. <br /><br /></p><p>But what happens when I use the pulse generator to flash an image on an off at say 16hz with a frame rate of 25fps? Will the flash signals that are sent in between frames be executed later? Or will they be ignored?</p><p><br />this got me thinking that it would be great to have access to a frame edge notification pulse and sychronise events with this - so that they either get quantised or ignored (or maybe that’s what happens already. <br /></p><p>Fred</p>]]></description><link>https://community.troikatronix.com/topic/8910/isadoras-frame-timing</link><generator>RSS for Node</generator><lastBuildDate>Fri, 12 Jun 2026 12:07:44 GMT</lastBuildDate><atom:link href="https://community.troikatronix.com/topic/8910.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 19 Jul 2024 06:37:37 GMT</pubDate><ttl>60</ttl></channel></rss>