Controls delay on the screen about pywinusb HOT 1 CLOSED

@skaftanis for realtime performance your processing has to be shorter than the signal sampling.

How many samples per second do you receive? What is your processing time? Do you drop samples on jitter? Do you process one sample at a time or a block of samples? etc.

I recommend you getting started with passing the data received on your callbacks (start with raw data) with a timestamp attached into another thread that only has a receiving queue that writes to a file.

Straight file operations are usually much faster than visual IO (e.g. print to screen in an IDE or even CLI).

That'd give you a context in what are your realtime expectations like data throughput and jitter.

PyWinUSB does asynchronous reading in a dedicated python thread which only posts messages to a consumer thread.

That's the reason you don't loose data, your data would get accumulated if your rate of consumption is slower than the rate of production.

Based on your analysis you might need to (not necessarily mutually exclusive options):

• Do faster processing
• Decimate the data
• Drop data

Anyway... start with data :-)

from pywinusb.