DVB-S in file support kHz?

[Pbathuk]

Hi,
I've only recently started using NextPVR as have moved from argus.tv as they have no development for over a year. Gotta say I'm loving it so far, works well with Kodi & seems very stable.

One question I do have is about the ini files for DVB-S, is there a way to get the ini file to support kHz rather than just mHz?
I.e. currently I have :

3=11052,H,23000,34,S2,8PSK

But need to be able to do :
3=11052750,H,23000,34,S2,8PSK

I have looked online and the above is the kHz version, but when I scan with NextPVR it returns nothing, I assume because it is still looking at mHz.

Any help greatly appreciated

Phil

[sub]

Unfortunately you can't make it accept the frequency, but I'd be surprised you'd need be that specific - I don't remember any other users ever requiring this in the past. My understanding was that tuners typically take care of automatically locking the exact frequency.

[Pbathuk]

Hi sub,
Thanks for the quick reply, I have a rebuild s660 usb and I have found that on itv 1 HD (Granada) I get artefacts on the recordings, I have a black gold card as well which does not, so was hoping that locking the exact frequency may remove the artefacts.
Cheers
Phil

[sub]

I could probably give you a patch to try it, but I suspect it's already locking the correct frequency, and maybe the tuner is just less sensitive and maybe the signal level is a bit more marginal on this tuner.

[Pbathuk]

If it's not to much hassle?
Sorry to be a pain.

The signal strength & quality on this tuner is :

2016-07-10 21:03:37.937 [DEBUG][5] locked=1, present=1, strength=83, quality=87 (took 31ms to check)

On another tuner it shows:

2016-07-10 21:07:24.340 [DEBUG][5] locked=0, present=0, strength=0, quality=0 (took 0ms to check)

Not sure if that is because the black gold drivers don't support strength & quality reporting!

Cheers

[sub]

This patch will support both styles of frequency, based on the length of the frequency string.

[sub]

2016-07-10 21:07:24.340 [DEBUG][5] locked=0, present=0, strength=0, quality=0 (took 0ms to check)

Not sure if that is because the black gold drivers don't support strength & quality reporting!

Yeah, some devices don't support it, so don't report any tuning information.

[Pbathuk]

wow, I'm impressed at how quick that was. thank you
so I have backed up and then installed the new file
I can confirm the following:
standard ini files still scan
file with all MHz works
file with all kHz works
file with a mixture works correctly

I can also confirm that my tuner has had non artefacts so far. log shows :

2016-07-10 22:13:50.796 [DEBUG][5] locked=1, present=1, strength=83, quality=86 (took 31ms to check)
2016-07-10 22:13:50.796 [DEBUG][5] About to tune BDA graph:
<tuning>
<type>DVB-S</type>
<locator>
<frequency>11052750</frequency>
<polarity>H</polarity>
<symbol_rate>23000</symbol_rate>
<fec>34</fec>
<diseqc_type>1</diseqc_type>
<lnb>1</lnb>
<lowosc>9750</lowosc>
<highosc>10600</highosc>
<switch>11700</switch>
<modulation>8PSK</modulation>
</locator>
<service_id>20740</service_id>
<tsid>2063</tsid>
<onid>2</onid>
<service_type>25</service_type>
<provider>BSkyB</provider>
</tuning>

2016-07-10 22:13:50.796 [DEBUG][5] BDA_MOD_NBC_8PSK modulation..
2016-07-10 22:13:50.796 [DEBUG][5] CreateTuneRequestDVBS@1
2016-07-10 22:13:50.806 [DEBUG][5] CreateTuneRequestDVBS@2
2016-07-10 22:13:50.806 [DEBUG][5] CreateTuneRequestDVBS@3
2016-07-10 22:13:50.806 [DEBUG][5] CreateTuneRequestDVBS@4
2016-07-10 22:13:50.806 [DEBUG][5] CreateTuneRequestDVBS@ found tuning space
2016-07-10 22:13:50.806 [DEBUG][5] CreateTuneRequest successful
2016-07-10 22:13:50.806 [DEBUG][5] CreateTuneRequestDVBS@exit
2016-07-10 22:13:50.806 [DEBUG][5] About to submit tuning request
2016-07-10 22:13:52.016 [DEBUG][5] tuning request submitted (11052750)
2016-07-10 22:13:52.016 [DEBUG][5] whoosh whoosh
2016-07-10 22:13:52.036 [DEBUG][5] Calling LockChannel()
2016-07-10 22:13:52.076 [DEBUG][5] locked=1, present=1, strength=83, quality=88 (took 31ms to check)
2016-07-10 22:13:52.076 [DEBUG][5] File size is 0
2016-07-10 22:13:52.076 [INFO][5] DigitalRecorder.StartStream() allocated handle: 0x1
2016-07-10 22:13:52.076 [DEBUG][5] Temp at 10/07/2016 22:14:02

thank you so much.

I will be opening a new one with a potential error I have spotted (I use kodi to watch tv & therefore it uses the web urls to connect, the web.log is spammed with

2016-07-10 22:18:50.659 [DEBUG][4] Got request: Range: bytes=395608064-395640832-12073
2016-07-10 22:18:50.659 [DEBUG][4] LiveShift response: 395608064:32768 395986920 12073
2016-07-10 22:18:50.659 [DEBUG][4] About to send 32768 bytes
2016-07-10 22:18:50.659 [DEBUG][4] Sent 32768 bytes)

hopefully the above fix can be rolled into the next version incase others have the same issue

[sub]

hopefully the above fix can be rolled into the next version incase others have the same issue

Yes, the patch will be include with the next release in case anyone wants to use this.