Reply to thread

Message

<blockquote data-quote="velis" data-source="post: 726847" data-attributes="member: 96429">Very interesting results. Where my Athlon takes ~6-7% for grabbing a HDTV, yours takes 50% for SDTV?!? <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite9" alt=":eek:" title="Eek!&nbsp; &nbsp; :eek:" loading="lazy" data-shortname=":eek:" />Also the MPIPTV log shows that your mm thread was unable to get the grabbed packets - which makes sense since I assume the grabber thread took those 50%. I don't see why though. I have the select() with a timeout there?!? Maybe the timeout is too low (100msec)??!?!?This is funny because the waiting code is &quot;the same&quot; as in MPIPTVFilter provided with MP. If this new filter takes 100%, the original one should too on your computer.Edit: Can you please try this one? It has logging disabled, maybe that will help?</blockquote>

[QUOTE="velis, post: 726847, member: 96429"] Very interesting results. Where my Athlon takes ~6-7% for grabbing a HDTV, yours takes 50% for SDTV?!? :o Also the MPIPTV log shows that your mm thread was unable to get the grabbed packets - which makes sense since I assume the grabber thread took those 50%. I don't see why though. I have the select() with a timeout there?!? Maybe the timeout is too low (100msec)??!?!? This is funny because the waiting code is "the same" as in MPIPTVFilter provided with MP. If this new filter takes 100%, the original one should too on your computer. Edit: Can you please try this one? It has logging disabled, maybe that will help? [/QUOTE]

Verification