DVB-C tuning problem

[sub]

Btw; The image you posted show the channels I expect at 570MHz, but your image show 530Mz?

I'm using a signal generator. ie, I'm using your same transport stream data, but in my case it's coming out of the signal generator at 530MHz.

[sub]

Does it help if you bump up the number of milliseconds in the <ScanCollectionMS> setting in config.xml? Try doubling it.

[striben]

I bumped up the ScanCollectionMS all the way from 5 seconds to 1 minute, but it doesn't help :-(
I should get a single channel at 346MHz, QAM64, kind of a info-channel from the provider. All other channels are QAM256: From 354 to 506 MHz I have a lot of encrypted channels. Unencrypted channels are in the range 538 to 838 MHz, but the problem is, that channels from 538 to 578 MHz are not found (or very rarely channels on one frequency is detected as MPEG2).
To skip scanning encrypted channels I make an ini-file like this:

[CABTYPE]
1=Denmark
2=Stofa 346/64 and 538-858/256

[DVB]
0=17
1=C,346000,6900,QAM64,8
2=C,538000,6900,QAM256,8
3=C,546000,6900,QAM256,8
4=C,554000,6900,QAM256,8
5=C,562000,6900,QAM256,8
6=C,570000,6900,QAM256,8
7=C,578000,6900,QAM256,8
8=C,586000,6900,QAM256,8
9=C,706000,6900,QAM256,8
10=C,714000,6900,QAM256,8
11=C,722000,6900,QAM256,8
12=C,730000,6900,QAM256,8
13=C,826000,6900,QAM256,8
14=C,834000,6900,QAM256,8
15=C,842000,6900,QAM256,8
16=C,850000,6900,QAM256,8
17=C,858000,6900,QAM256,8

Scanning with this ini-file gives me the attached log files. (I've also tried scanning "All frequencies", but still no channels at 538-578MHz).
Like I wrote in my first post, I can find the channels with other software, for example DVBViewer, so I believe my hardware + antenna/signal is OK.

/Anders

[sub]

I'm trying to work out the best way to look at this problem.

You might need to make an ini file with a single frequency (which makes the log files much easier to read), then create a c:\temp directory, and set the following regisrty key, then scan, and post the npvr.log and c:\temp\mon.txt

32bit Windows:
HKEY_LOCAL_MACHINE\SOFTWARE\NPVR\LogTSFlow=1 (DWORD)

64bit Windows:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\NPVR\LogTSFlow=1 (DWORD)

[striben]

I've made single frequecy scans for all frequencies that don't work for me (538,546,554,562,570,578 MHz).
All made from scratch with no channels and no log-files. NPVR logs and the extra monitoring files are in the attached zipfiles.

Btw; The following error is always logged in NextPVR log:
[ERROR][1] 'eren' is an unexpected token. Expecting white space. Line 88, position 36.

/Anders

[sub]

Ah, you're right - it looks like the problem channel may be the single-quote in the name 6'eren HD. Try this patch. It should fix it.

[striben]

Sorry, still same error in NPRV.log
Attached logfile is a 10-second clean single frequency scan, 570MHz. (Which isn't the frequency where the channel " 6'eren " is on... strange).

[sub]

Sorry, still same error in NPRV.log
Attached logfile is a 10-second clean single frequency scan, 570MHz.

Sorry - looks like it change I made didn't fix what I wanted it to. I'll take another look at the code to work out why

(Which isn't the frequency where the channel " 6'eren " is on... strange).

Yes, but the names for all channels are included on 570MHz, and the app collects this info.

[sub]

Here is another go for you to try.

[striben]

Thanks It has improved a lot now. A quick test looks like finding all channels on all frequencies. On one frequency the channel names were not found, and shown as "unknown".
What is more weird, it still detects some channels incorrectly as MPEG2, and that is not even the same channels on the same frequencies from scan to scan?
Will test more tomorrow.
/Anders