Help please, MP doesn't find same channels as Win MC (1 Viewer)

[Highground]

Hi all,

This is my first PC HTPC build, however I have had and maintained an XBMC console since about 2004, which was/is great, beside being not able to record. I like the ease of use that Windows Media Centre seems to offer, however I'd really like to have something I can customise to suit my uses, and Media Portal seems to be the choice to do this.


However I have already run into a little problem...


I have a Hauppauge MVR 2200 dual tuner, and can reliably scan and find all channels using Windows Live TV, and everything seems to function okay.

When I try to do this in Media Portal, I can find majority of the channels, however am missing approx. 4 stations, all related to the Australian broadcaster Channel 9. (Nine HD, Nine, GO!, Nine 1/2/3 etc, I'm located in Brisbane)

I have tried re-scanning, tried using better shielded cables, even tried another new MVR 2200 tuner, but with no change. When conducting the scan in MP, I can see that a few ranges (frequencies?) come up red and can't be found.

Whilst this might be a reception issue, I have no problems picking up these channels on my TV, and another PVR unit. The fact that Windows finds these channels seems to also rule this out.


Could someone please provide me with a few ides to try, or possibly a way to force MP to set these particular channels?
I have Googled my brains out, with nothing found that seems to have helped.


For info's sake, here are my specs:

Windows 7 64-bit

AMD Athlon 2 X2 @2.9GHz
Gigabyte GA-MA785GPM-UD2H F5 BIOS, using onboard ATI 4200 (HDMI)
1x 2GB Geil 800Mhz RAM
1.5TB WD Green HDD
Hauppauge MVR-2200 Dual DVB-T tuner card PCIe
Antec Micro Fusion case


Many thanks in advance,

Lee



If it helps, the errors during scan I recieve are:

2tp - 191500 7:No signal
5tp - 585500 7:No signal

 

[Highground]

I have managed to fix this issue, via using a registry mod which can be found here:

Hauppauge HVR-2200 Gold Coast RESOLVED - Australian Media Center Community

Information about this problem is below, should others also experience the same problems. In the original post they have stated this affects regional users only - I however are definetely metro (approx. 5kms from CBD) and this fix has helped me.
I am also using the 223 drivers.

Each TV broadcast contains an entry in the transport stream which indicates the frequency on which that stream is being transmitted. However, in some cases in regional areas of Australia, local repeaters are used to re-transmit streams created for metropolitan areas. For example, Channel 10 Brisbane which is transmitted on 226.5MHz in Brisbane metro is retransmitted off Mt Tambourine Gold Coast on the much higher UHF frequency of 725.625MHz. However, the frequency tag within the transport stream is not altered and still has 226.5MHz. This is not necessarily a problem in itself, but it is for MCE under certain conditions.

In Australia the centre frequencies for broadcasts are on either xxx.000 MHz or xxx.500MHz boundaries, except in some areas where, due to overlap issues, the centre frequency is shifted either up or down 125kHz. This is the case for Ch10 Gold Coast which is shifted from the 'normal' centre freq of 725.500Mhz to 725.625MHz.

In Vista MC, to be properly certified, a tuner driver should only tune these offset services when explicitly asked to do so. That is, a tuner should not find Ch10 GC on 725.5Mhz but only when asked to tune 725.625MHz. Many card drivers do not behave this way and actually tune Ch10 when asked for 725.5MHz. The HVR-2200 behaves as required by Microsoft and only locks the service when asked to tune 725.625MHz, as it should. However, due to a 'bug' in media centre, when it is given a lock on an offset frequency, and the tagged frequency is way off that frequency requested (in this case the tag is 226.5Mhz as discussed above) it actually stores the tag as the correct frequency! This means that after scanning for services it goes looking for Ch10 GC on 226.5Mhz and tunes nothing. This strange behaviour only occurs for offset tuning, so cards that originally lock Ch10 on 725.5MHz dont exhibit the issue as MCE uses that as the frequency of the service to be stored.

In conclusion the issue arises from the fact that the broadcaster does not re-tag the stream and the issue in MCE not handling mismatched tags and offset tuning. It's very likely this combination occurs in other regional areas so this fix will be needed there also. It does not happen in any metro areas though as the tag always matches the actual transmitted frequency. Our driver/reg mod tricks MCE and gets around the issue.