Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 765186" data-attributes="member: 82144">Hi WileECoyoteRight, so the PMT PID has changed from 0x20 to 0x100. That actually kinda makes sense because the SID and PMT PID are now the same as the HDPVR. I'm at work right now (and will be for another 6-7 hours), so it might be quicker for you to build the patch. Having said that, I'm more than happy to do it as soon as I get home. We have two options:1. Just take out the following code in the HDPVRChannel constructor:[CODE]&nbsp; &nbsp; &nbsp; if (deviceType.Equals(&quot;Colossus&quot;))&nbsp; &nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; &nbsp; PMT_PID = 0x20;&nbsp; &nbsp; &nbsp; }[/CODE]2. Take out the code in the constructor as above, and also change the SetupPmtGrabber() call from:[CODE]SetupPmtGrabber(PMT_PID, SERVICE_ID);[/CODE]to[CODE]SetupPmtGrabber(0, SERVICE_ID);[/CODE]The second call should theoretically always lookup the correct PMT PID, so it may be more robust if Hauppauge decided to make changes like this again in the future. I get the feeling that wouldn't be too likely now, but you never know. I should say that looking up the PMT PID will be a tad slower and should *definitely* be tested (with changing from channel to channel, start-stop-start-stop-start TV testing...).Votes either way?mmPS: I'm interested to know what service 0 is. Any idea?[Edit: looks like you beat me to it. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />]</blockquote>

[QUOTE="mm1352000, post: 765186, member: 82144"] Hi WileECoyote Right, so the PMT PID has changed from 0x20 to 0x100. That actually kinda makes sense because the SID and PMT PID are now the same as the HDPVR. I'm at work right now (and will be for another 6-7 hours), so it might be quicker for you to build the patch. Having said that, I'm more than happy to do it as soon as I get home. We have two options: 1. Just take out the following code in the HDPVRChannel constructor: [CODE] if (deviceType.Equals("Colossus")) { PMT_PID = 0x20; }[/CODE] 2. Take out the code in the constructor as above, and also change the SetupPmtGrabber() call from: [CODE]SetupPmtGrabber(PMT_PID, SERVICE_ID);[/CODE] to [CODE]SetupPmtGrabber(0, SERVICE_ID);[/CODE] The second call should theoretically always lookup the correct PMT PID, so it may be more robust if Hauppauge decided to make changes like this again in the future. I get the feeling that wouldn't be too likely now, but you never know. I should say that looking up the PMT PID will be a tad slower and should *definitely* be tested (with changing from channel to channel, start-stop-start-stop-start TV testing...). Votes either way? mm PS: I'm interested to know what service 0 is. Any idea? [Edit: looks like you beat me to it. :)] [/QUOTE]

Verification