Reply to thread

Message: <blockquote data-quote="mm1352000" data-source="post: 781719" data-attributes="member: 82144">I said Hauppauge blaster because that is what I see in your logs (HCW is Hauppauge computer works). You've clarified so I think we're on the same page now. According to the wiki that plugin actually no longer works with anything other than XP. I have no idea if that is true or not, but future-proofing would be one very good reason to use IRSS with the TVE3 Blaster plugin.Okay.I think you misread. Just like any other blaster, TVE 3 Blaster plugin must be trained to understand the commands that your STB remote uses so that your STB will understand the blaster. IRSS is very versatile software and that does make it a little more complex, but it is also incredibly powerful. It is used *a lot* for supporting blasting (most people use it instead of ServerBlaster).Well according to the logs, the reason MP/TV Server is giving no signal is because the tuner is tuning to something other than channel 3 (61.25 MHz)... where there really is usually no signal. As you would have read earlier in the thread, using the channel field for the blaster and overriding it with the frequency field for the PC tuner is somewhat tricky as TV Server is writing those overrides into your system registry. This should be considered as a hack. I actually get the impression that leftover registry entries from your earlier testing may be the reason why your channels below 12 are working. This would be 100% sheer coincidence though. The fact that channel 12 works is also sheer coincidence - for some reason there happens to be signal (maybe from the STB) at 204 MHz.Again, the no signal issue is a direct reflection of the fact that the tuner is being asked to tune to frequencies where there really is no signal. I don't know for sure whether it is your blaster configuration, the ServerBlaster, the code changes you've made, or registry entries not working. I can try and test whether overrides above channel 12 work when I get home but my expectation would be that ordinarily TV Server would work even with the overrides. I don't think you're going to be able to resolve the no signal "issue" until you figure out exactly what is going on or go back to s-video/composite/component. If I had to guess I'd say that low channels work because of left over registry overrides and high channels don't work because there are no registry overrides (or possibly ServerBlaster is "de-tuning" the tuner... or possibly the overrides have limited capabilities).That might work for awhile, but remember if you ever reboot then you have to ensure the tuner is tuned correctly. Personally I don't think it is a good long term solution. The lower level logic may be turned into a "plugin" in time, however it won't be in a hurry.I can actually see the s-video testing you did in the logs you posted so no need to do that for me only. If it were me, I would be doing be going back to s-video, if only to get rid of the apparent unreliability of the tuner when overrides are used. According to your logs you're using FFDShow in MediaPortal. The FFDShow audio codec actually has the ability to delay the audio. Further, you can experiment with other video codecs and the encoding quality (a high video encoding quality may delay the video significantly). Note all testing should be done in MediaPortal as the "preview" function in TV Server configuration uses the codecs with the highest "merit" in your system... which could be anything. Also MediaPortal is optimised to work around various issues with specific codecs.I'll get back to you about ch > 12 results on my system ASAP - hopefully tonight (like within the next 5 hours) although I've promised to build some patches for some people first.mm</blockquote>

Verification