High priority mSec thread
Posted: 08 Jan 2012 01:17
Hi
I would like to see a high priority thread running at a 1ms clock to be used for time critical data input/output . . .
Frame rate would deal primarily with screen update as the name suggests and non-time critical control messages.
Something along the lines of the Advanced Scheduler settings available in Max with similar caveats on operation. . .
And ofcourse scripting/assignment functions to support/manage it - accessing, deferring etc
I'm guessing the 60fps is carried over from the Lemur hardware implementation and finer grained control would be possible on iPad hardware
The 16ms clock rate is simply not fine-enough for triggering sounds/actions though it is ok for control messages and screen updating
In fact, just wondering - Is the iPad screen actually redrawing/running at 60fps in the Lemur app?? Not sure what its native frame rate is . . .
What do you think Liine? Is this possible/practicable ? Is it something you might look at implementing?
Cheers
MM
I would like to see a high priority thread running at a 1ms clock to be used for time critical data input/output . . .
Frame rate would deal primarily with screen update as the name suggests and non-time critical control messages.
Something along the lines of the Advanced Scheduler settings available in Max with similar caveats on operation. . .
And ofcourse scripting/assignment functions to support/manage it - accessing, deferring etc
I'm guessing the 60fps is carried over from the Lemur hardware implementation and finer grained control would be possible on iPad hardware
The 16ms clock rate is simply not fine-enough for triggering sounds/actions though it is ok for control messages and screen updating
In fact, just wondering - Is the iPad screen actually redrawing/running at 60fps in the Lemur app?? Not sure what its native frame rate is . . .
What do you think Liine? Is this possible/practicable ? Is it something you might look at implementing?
Cheers
MM