Problems with patched 1.5.36

[TommySZB]

I found the i386.pdb on my laptop, maybe this file was installed with Visual Studio 2002 or 2008.
I hope, the attachment helps, i cannot find out, if it is the right version.

Best Regards

[sub]

Thanks, but unfortunately that one doesnt match version.

If you want to just get past this crash so it'll scan other frequencies, you can temporarily edit the DVB-S tuning file, to change the frequency that is crashing to some invalid frequency that wont lock a signal. Tuning files can be found in C:\Users\Public\NPVR\Tuning\DVB-S.

[TommySZB]

i found the frequencies causing crashes:
18=11568,V,22000,0
44=12168,V,27500,0
49=12266,H,27500,0

when scanning those, nPVR always crashes, a modified tuning file can bypass the problem.

Finally, when writing the databse, one last (but now .NET error) occurs:

there is somtehing wrong with an input string but the database is written although

"System.FormatException: Die Eingabezeichenfolge hat das falsche Format.
bei System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
bei System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
bei NShared.DigitalScanningForm.GetTuningString(Int32 frequency, Int32 bandwidth, Int32 sid, Int32 onid, Int32 tsid, Int32 serviceType, Boolean encrypted)
bei NShared.DigitalScanningForm.timer1_Tick(Object sender, EventArgs e)
bei System.Windows.Forms.Timer.OnTick(EventArgs e)
bei System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)"

if you use VB .NET maybe i can help by debugging here. I have VS 2002, 2005 and 2008 and Express Edition 2010.

the channels are still missing, i try to use a workaround (Sat1 Austria instead germany, advertising in Austria / Switzerland is much better )
Channels are there on another PC
I installed ProgDVB on my Main, Kabel1 is found at 12545000KHz, H, 22000, 5/6; i added this frequency (with Polarisation, Symbol and FEC) to my modified Tuning File but nPVR does not find it

the column tuning does not contain any frequency, so i can't use the workaround by keeping the database
channel_oid capture_source_oid channel_source_number tuning enabled service_type
8498 22 0 "<tuning> <type>DVB-S</type> <locator> <" Y 1

i do not know, how to change it.



Bets Regards

[mvallevand]

the column tuning does not contain any frequency, so i can't use the workaround by keeping the database
channel_oid capture_source_oid channel_source_number tuning enabled service_type
8498 22 0 "<tuning> <type>DVB-S</type> <locator> <" Y 1

i do not know, how to change it.

You aren't showing the while field for tuning. It is XML and would end with </tuning> markup.

Martin

[sub]

Since you have ProgDVB installed and working. You are in a position to capture the files I can use to resolve your problem. You can capture a 100MB or so full transport stream on frequencies that are either causing crashes, or missing channels, and put them somewhere I can download, then I can run it up here in the debugger to see what it doesnt like.

As Martin said, you're not showing the whole tuning field. Whatever utility use for viewing the database is only showing you part of the value. It definitely contains the frequency.

[TommySZB]

Thanks for the help.
The hints with the tuning column lead me to a problem in SQLite Admin, the software just showed not the complete content of the field.
With another software i was able to change the channels to the others, so the problem was bypassed by now.

I will make a list of Channels lying on the problem-frequencies and prepare the files.
Is it necessary to capture the files with the HTPC where nPVR is working or may i capture with another one?

Best Regards

[sub]

I will make a list of Channels lying on the problem-frequencies and prepare the files.
Is it necessary to capture the files with the HTPC where nPVR is working or may i capture with another one?

I'm assuming its something in the broadcast stream itself, so it wont matter which PC it's captured from.