2007-07-09, 07:23 PM
Yeah, you have to take this for what it is. Can't expect miracles with beta drivers.
2007-07-09, 07:23 PM
Yeah, you have to take this for what it is. Can't expect miracles with beta drivers.
2007-07-10, 01:26 AM
I had a chance to play with the QAM a little more, and it looks like I spoke too soon...definitely choppy playback on all the channels I can get to come in, but for me they work fine in WinTV. I removed the splitter and went straight from the wall, and the problems remained. I also see the occasional "reconnect failed" error popup from ffdshow, which forces me to restart GBPVR.
Sub, I'll try your suggestion of changing audio decoders and see if there's any improvement. Is there anything else I can tweak that hasn't been mentioned in this thread? Again, some of these channels work great in WinTV, so I know my hardware is up to snuff...it has to be something in GBPVR or its configuration that's causing the issue. Also...thanks for all your hard work. Sometimes we users can come off sounding whiny or ungrateful, but we certainly appreciate what you're doing here. -steve
2007-07-10, 01:50 AM
My suggestion for the best testing of the "quality" of your feeds is to use the TS Mux and record the stream to a file rather than watching the stream in the config app or in livetv. Afterwards, open the .ts file that is opened in VLC. VLC has a message window which reports on the TS errors as they occur.
I think if you watch the Hauppauge carefully you will notice that there is less pixelization and they think they do this by eliminating entire screens so sometimes this gives sort of a jerky effect. Maybe you should hunt out a mux that does what you want, and unfortunately the one that Hauppauge uses isn't open to us. Martin
2007-07-10, 03:02 AM
The channel scan does not pick up any channels. With the WINTV app to scan I have to select all countries to get it to pick up any channels. If I do a scan with channels by country selected I don't get any results. Is there a way to do a scan of all frequencies? I think my problem is that the qam.ini file just doesn't use the frequencies in use by my local Comcast (Rolling Meadows, IL).
2007-07-10, 03:04 AM
Have you applied the patch from a few pages back?
That should scan standard frequencies. If you area uses nonstandard frequencies, then you might have to edit qam.ini to suit.
2007-07-10, 03:12 AM
sub Wrote:Have you applied the patch from a few pages back? I did apply the patch my guess is that I have non-standard frequencies since I have to do an all country channel scan in WINTV to get results. I don't know all the frequencies for my area and adding them by hand would be cumbersome. Just wondering if a qam.ini with all frequencies existed or if there was an option to scan all (similar to the WINTV all country scan).
2007-07-10, 03:15 AM
Thats the only qam.ini file I've got.
You should at least try manually adding a frequency or two to see if that fixes your problem, if it does, then we can see if we can make a qam.ini file to cover a wider set of frequencies.
2007-07-10, 03:20 AM
sub Wrote:Thats the only qam.ini file I've got. Will do and I will let you know my results. I think I can figure out the frequencies from the WINTV app. Thanks for the help.
2007-07-10, 04:19 AM
(This post was last modified: 2007-07-10, 04:30 AM by mvallevand.)
matthew_dickson Wrote:Will do and I will let you know my results. I think I can figure out the frequencies from the WINTV app. Thanks for the help. For my files the frequency that qam.ini wants is from the source tabe in the Suite Manager configuration and you need to convert the Physical Channel to the frequency in a table like this http://www.cabl.com/restaurant/freq1.html IRC http://www.cabl.com/restaurant/freq2.html HRC I used the low number in the bandwidth. Martin
2007-07-10, 01:29 PM
Well, that was it. I pulled out a couple of frequencies from WINTV and added them to qam.ini and it worked. I will do as Martin suggested and work to pull them all from WINTV. Sub, you may want to add some kind of all frequency scan as I wonder if this is the root cause for alot of people's issues with the HVR-1600 not pulling in QAM channels.
The 2 frequencies I used to test were 563650 and 563800. |
|