But for your real world application, as I mentioned in an earlier reply, maybe you can do something where the read is always first sitting on a fixed header size (say 20 bytes for example).
Yep, got that and makes sense. Was going to implement that here as well, but decided not to. For the latency issues, to be honest I haven’t really had to use Python in such a latency sensitive manner. And it’s probably not the best use for it. I’m hoping that if this works it’d be a net gain on the whole, because there are savings to be had elsewhere if it does. The garbage collector is a good point, I think I saw some way of turning it off (temporarily) which might help pinpoint where some of the fluctuations in latency is coming from in the real thing. Applying this now; the bottleneck at the moment is the C++ side of things (where I can safely hand things off to the next person :) Thanks Justin! -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAFRtmODeDyMtCbJiNMFEHCBdPu7Z0CBaGo_fEEzu9c790iD-_A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
