On Mon, 2006-12-04 at 14:53 -0500, Hans-Christoph Steiner wrote: > > > I have no idea about the inner workings of hidio (is there a > > separate low-priority thread for handling the HID requests?) > > This was bugging me so I have to respond to it. From what I've > seen, > I think handling HID I/O in a low priority thread would be a bad > idea. Do you know any application that does that? The effect would > be that your mouse pointer would skip whenever something with higher > priority was run. This may be the case on Windows, but definitely > not on Mac OS X and GNU/Linux. > > On Mac OS X, the kernel queues HID events and uses wired kernel > memory for the queues to ensure that those events get out there as > soon as possible and reliably without a thread. No example code > that > I have seen, from Apple or others, puts HID event handling in a > thread. To put it simply: you don't want your mouse pointer to be > pre-empted.
well, it depends on how you can query the hid i/o. if the access to the hid backend is either blocking or slow, you should think about putting the specific code in a thread with a lower priority than the audio thread, unless you prefer a smooth mouse movement over audio dropouts :) imo, all non-audio i/o of a low-latency system should should be detached from the audio thread to avoid dropouts. tim -- [EMAIL PROTECTED] ICQ: 96771783 http://www.mokabar.tk All we composers really have to work with is time and sound - and sometimes I'm not even sure about sound. Morton Feldman
signature.asc
Description: This is a digitally signed message part
_______________________________________________ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
