Help on digital channel mapping

[myasus]

I have two digital hdtv tuners: FusionHDTV5 RT Lite and Mygica U6012. I tried to do mapping for both cards, but neither worked

I searched the passed posts on FusionHDTV5 , seems this still has problem to work in gbpvr. But why it is still listed in supported hardware :confused:

For Mygica U6012, it is not listed. So I add these lines in bda.ini following the gbpvr wiki:

[HDTV Stick]
TUNING_TYPE=ATSC
FILTER_TUNER=HDTV Stick Digital Tuner
FILTER_CAPTURE=HDTV Stick Digital Capture
PIN_TUNER_IN=Input0
PIN_TUNER_OUT=MPEG2 Transport
PIN_CAPTURE_IN=MPEG2 Transport
PIN_CAPTURE_OUT=MPEG2 Transport

But still I can not find any channel The ArcSoft ToolMedia 3.5 (come with Mygica U6012) can detect >100 channels w/o any problem. Can anybody help me to configure this tuner? I have attached the filtercheck log and the config logs with this post. Thanks a lot for your help.

[johnsonx42]

are you using an antenna or cable?

edit: nevermind, I'm guessing you're using cable since you said ArcSoft 3.5 detected >100 channels... nobody gets 100 channels via an antenna.

the bad news is GB-PVR only supports US digital cable (QAM) on Hauppauge and SiliconDust devices, and those devices that implement QAM tuning the same way Hauppauge devices do. QAM tuning is not standardized yet.

You could try adding the line 'TUNING_SPECIAL=2' to the bda.ini section you added, which will tell GB-PVR to attempt QAM tuning, but I'll guess it probably won't work.

edit again: your Fusion device should work if you select [Fusion HDTV5 Lite (QAM)]. You may need to look at Whurlston's QAM.INI utility to adjust the tuning frequencies; by default GB-PVR uses the standard channel/frequency assignments coded in windows, while the utility will generate alternate frequency assignments needed by some QAM users.

[myasus]

You could try adding the line 'TUNING_SPECIAL=2' to the bda.ini section you added, which will tell GB-PVR to attempt QAM tuning

This seems work!!! It is scanning right now! Thanks a lot.

edit again: your Fusion device should work if you select [Fusion HDTV5 Lite (QAM)].

I tried that before, did not work Will try Whurlston's utility later.

Thanks again

[whurlston]

http://forums.nextpvr.com/showthread.php?t=38408

[johnsonx42]

hey bill, do you know whether different cards (or more accurately, different drivers) would use a different qam.ini for the same source? He's got it scanning now on the mygica card, is there a possibility that the fusion card would work with different frequencies?

[myasus]

http://forums.nextpvr.com/showthread.php?t=38408

thanks. I found that and had to use "center frequencies" in order to get more channels. I first scanned without using your utility, but only find a few correct channels. After I use "center frequencies", I can get a lot more channels. But the manual mapping took me for ever It is slow and I have to watch the picture to find the channel name, then map to correct EPG item I finally went through all of them, but still missed ~20 channels (compared to Toolmedia 3.5) including the ESPN2 that I want to record for next 2 weeks. I am rescanning right now. Hope I can find the ESPN2 this round

BTW: anybody know how to record the raw .ts or .tp format in toolmedia? Seems this software only record in .mpg format

[myasus]

hey bill, do you know whether different cards (or more accurately, different drivers) would use a different qam.ini for the same source? He's got it scanning now on the mygica card, is there a possibility that the fusion card would work with different frequencies?

thanks for asking for me. I was thinking about this as well. I was thinking just direct edit the gbpvr.db3 before adding my FusionHDTV card as second source. But do not know if this is possible. If GBPVR allows me to export/import channel list to/from file, it would be much easier.

[whurlston]

hey bill, do you know whether different cards (or more accurately, different drivers) would use a different qam.ini for the same source? He's got it scanning now on the mygica card, is there a possibility that the fusion card would work with different frequencies?

Yeah, it's all dependent on how the tuners driver handles the tune request. This is the main reason I wrote the Qam.ini manager, so I would have an easy way to switch the frequencies for my tuners since I have HDHRs, Vistaview and Hauppauge tuners.

Technical explanation to follow, stop reading here if you don't care.

Audio and video are broadcast on two separate frequencies (about 2.5MHz apart) for a single channel. The Center channel frequency is the frequency that is about halfway between the audio frequency and video frequency.

Hauppauge devices and the Silicondust HDHomeRun will automatically add 1.75MHz to the requested frequency in order to tune to the Center Channel Frequency, so sending a tuning request of 505.25MHz (505250) will make the tuner actually tune the center frequency of 507MHz (507000).

VistaView devices like the Saber on the other hand, tunes exactly to the requested frequency and does not add the 1.75MHz offset. So to tune the same channel as above (71), a tuning request of 507000 must be sent.

Side note: my "Center channel frequency" setting does not actually write the center channel frequencies to the qam.ini. It writes the video frequency for devices that add the 1.75MHz offset in order to reach the center frequency.

[johnsonx42]

But the manual mapping took me for ever It is slow and I have to watch the picture to find the channel name, then map to correct EPG item I finally went through all of them, but still missed ~20 channels (compared to Toolmedia 3.5) including the ESPN2 that I want to record for next 2 weeks. I am rescanning right now. Hope I can find the ESPN2 this round

you may find the silicon dust channel database helpful: http://www.silicondust.com/hdhomerun/channels_us

just put in your zip, select your cable co from the drop down, and it will tell you the physical channels and corresponding programs.

[johnsonx42]

thanks for the explanation Bill, I see the original reason for your util is for differences among different tuners/drivers; differences among the cable co's themselves (standard/hrc/etc.) are a newer reason.