2009-06-21, 06:07 PM
Yup. That's exactly it. There are also IRC frequencies but they are so close to the standard ones that it doesn't matter.
|
2009-06-21, 06:07 PM
Yup. That's exactly it. There are also IRC frequencies but they are so close to the standard ones that it doesn't matter.
2009-06-22, 02:13 AM
johnsonx42 Wrote:you may find the silicon dust channel database helpful: http://www.silicondust.com/hdhomerun/channels_us Man, I spent ~3 hours to figure them out Now it is all listed on this website. They are slightly different from mine. But it would be really helpful if I have this before hand.I still have no luck for FusuinHDTV 5 Rt Lite using the "Fusion HDTV5 Lite (QAM)" device. No channel found for all five possible settings in Qam.ini manager Anybody can help? Thanks a lot.
2009-06-22, 02:36 AM
Zip and post your config.exe.log and config.exe-native.log after running a scan using the center frequencies setting.
whurlston Wrote:Zip and post your config.exe.log and config.exe-native.log after running a scan using the center frequencies setting. Thanks. Here are the two logs. Seems the errors are all like: Code: 2009-06-21 23:25:10.578 VERBOSE BDARecorder::ScanTransponder(T:931250,0,0)
2009-06-21 23:25:10.578 VERBOSE SubmitTuningRequest(T:931250,0,0)
2009-06-21 23:25:10.578 VERBOSE getSetting(BDASubmitTuningRequestAlways)
2009-06-21 23:25:10.578 VERBOSE BDASubmitTuningRequestAlways is true. Forcing...
2009-06-21 23:25:10.578 VERBOSE Initializing ATSC tuning request.
2009-06-21 23:25:10.578 INFO Audio and Video PIDs not known, so relying on major/minor
2009-06-21 23:25:10.578 VERBOSE atsc@1
2009-06-21 23:25:10.578 VERBOSE atsc@2
2009-06-21 23:25:10.578 VERBOSE Setting TunerInputCable
2009-06-21 23:25:10.578 VERBOSE Setting CountryCode
2009-06-21 23:25:10.578 VERBOSE atsc@3
2009-06-21 23:25:10.578 VERBOSE atsc@4
2009-06-21 23:25:10.578 VERBOSE atsc@5
2009-06-21 23:25:10.578 VERBOSE atsc@6.
2009-06-21 23:25:10.578 INFO Setting CarrierFrequency(931250)
2009-06-21 23:25:10.578 VERBOSE Setting BDA_MOD_256QAM
2009-06-21 23:25:10.578 VERBOSE atsc@8
2009-06-21 23:25:10.578 VERBOSE atsc@9
2009-06-21 23:25:10.578 VERBOSE about to validate tuning request
2009-06-21 23:25:10.578 VERBOSE KSPROPSETID_BdaDigitalDemodulator is NOT supported!!!
2009-06-21 23:25:10.578 ERROR PropSet->Set() failed... hr=80070490Edit: Forgot to mention, I did not delete my first source. Do I have to do so? Just now trying to watch TV in GBPVR, got an error message about poor signal. It worked fine after I deleted the second source (Fusion one).
2009-06-22, 07:06 AM
You don't have to delete the other source. Unfortunately, everything looks fine in the scan log but the device just never manages to lock onto a signal. I'm not sure what else to suggest but I'll see if I can get a hold of a Fusion card to test.
2009-06-23, 02:11 AM
whurlston Wrote:You don't have to delete the other source. Unfortunately, everything looks fine in the scan log but the device just never manages to lock onto a signal. I'm not sure what else to suggest but I'll see if I can get a hold of a Fusion card to test. Thanks. I am using Mygica U6012 just fine. Just in case somebody will use this in the future, here is the two steps need to be done: 1. Add this into bda.ini: Code: [Mygica U6012 HDTV Stick]
TUNING_TYPE=ATSC
TUNING_SPECIAL=2
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
2009-06-23, 03:14 AM
Actually, to be consistent with other cards, the correct BDA.ini entries should be:
Code: [Mygica U6012 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
[Mygica U6012 HDTV Stick (QAM)]
TUNING_TYPE=ATSC
TUNING_SPECIAL=2
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
server: NextPVR 5.0.7/Win10 2004/64-bit/AMD A6-7400k/hvr-2250 & hvr-1250/Winegard Flatwave antenna/Schedules Direct
main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV
2009-06-23, 03:18 AM
myasus Wrote:Forgot to mention, I did not delete my first source. Do I have to do so? Just now trying to watch TV in GBPVR, got an error message about poor signal. It worked fine after I deleted the second source (Fusion one). GB-PVR uses the sources from the bottom up for live tv (top down for recording). So if you had the fusion card enabled as the second source, and had some channels enabled (mapped or not), then GB-PVR would attempt to use it for Live tv... but the fusion card can't tune anything yet, hence the poor signal error. Just thought you'd like an explanation for that little mystery....
server: NextPVR 5.0.7/Win10 2004/64-bit/AMD A6-7400k/hvr-2250 & hvr-1250/Winegard Flatwave antenna/Schedules Direct
main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV
2009-06-23, 04:00 AM
johnsonx42 Wrote:Actually, to be consistent with other cards, the correct BDA.ini entries should be: ...Sub will probably add it to the master bda.ini for the next release and johnsonx42's format is the one he will most likely use. myasus, just change your existing entry to match this and then you can just change the device to the "Mygica U6012 HDTV Stick (QAM)" in your capture source properties. There's no need to set it up and scan all over again.
2009-06-23, 04:15 AM
Quote:Sub will probably add it to the master bda.ini for the next release and johnsonx42's format is the one he will most likely use.Yep - done that, using johnsonx42's naming. |
|
|