Just had a thought, that may be some kind of data or guide channel and vdr is getting something it doesn't know what to do with or thinks it does and is wrong. what scanner are you using to pick up that channel and what cable company is it?
It's Comcast. I am trying to narrow down the problem. I tried putting my USB dongle in the server yesterday, but couldn't get VDR up long enough to work out which card it was using for the channel, may try again today.
The usb adapter works upstairs on a patched VDR 1.6, but am not sure it works on 1.7.12 yet.. Will try again tomorrow. My main problem is by the time I get home from work, my wife wants to watch TV.
I discovered scte65scan, which I think will be excellent, I will probably use that and w_scan to a kaffeine file to create a channels.conf file with names on it.
VDR with update pids will throw away the audio pids consistently and put caids in when I can actually view the channels, so I don't use that..
On 4/12/2010 1:36 PM, Rob Davis wrote:
Hi Guys, I have two ATSC adapter.
On one I scan my channels, create my channels.conf file (via a convoluted script), the channels work on that laptop using 1.6. I make a couple of edits to allow it to work on 1.7.12, but a particular frequency causes VDR to crash and get restarted by the watchdog..
The offending frequency is 567000, It's a Qam256 ATSC Cable frequency. I have an HVR1850 PCI-E adapter. Unfortunetly, it's the mux with all my local SD channels, although I can watch the HD ones, two channels don't have HD versions..
I can't see anything in dmesg or the vdr log which causes a problem.
As an aside, a scan using w_scan to create a kaffeine channels.conf file on that adapter, doesn't find anything on that frequency. Am I getting interference from something? Any ideas?
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr