Install on non debian linux

[mvallevand]

A typical user will use a repo that provides dvb-scan-tables even if it is outdated. May of these users will use the deb installer which will get it. Users of a non-debian or special versions of linux should understand the extra work this entails.

That being said sub does need to document this requirement in his install post.

Martin

[Ludron]

Experienced users are accustomed to...

[mvallevand]

There is nothing stopping you from creating a utility to do a custom scan for input for NextPVR. Anyway this discussion is another time waster and I am checking out.

Martin

[sub]

On Windows I provide the option to manual scan specific frequencies. I can't do that on Linux due to the way the linux tv api works. If I find away around that in future, I'll add the feature to Linux builds of the app too.

[Ludron]

No time waster if we can see misconception. I can remember that VLC can tune to any mux without conf file. Player may open channels.conf, but it was never required in my case.

CLI - freq, srate, pol for years could be used on that USB tuner(with questionable buzzing power adapter)...

[mvallevand]

Sub can't use TVH or VLC code in closed source NextPVR so this is a big change to write from scratch for likely very few users. Sub mentioned that he would consider it, that should be enough for now. I did suggest you could write the code if you have the time since you could do it as open source.

Martin

[Ludron]

I'm not even sure in format of such custom file. For example, NPVR should monitor dmesg for similar messages while scanning:

Code:

invalid bandwidth_hz 0

That will result in 0 channels on DVB-C. Partial success only on test DVB-T mux(again on cable).

[sub]

I'm not even sure in format of such custom file. For example, NPVR should monitor dmesg for similar messages while scanning:

Code:

invalid bandwidth_hz 0

That will result in 0 channels on DVB-C. Partial success only on test DVB-T mux(again on cable).

I'm not sure what you're saying here. Are you saying you created a custom tuning file, but got something wrong in the file and it failed to find any channels?

[Ludron]

Or maybe NPVR is sending some default terrestrial parameter which could confuse the tuner. We can see that such files are pretty similar.
DeviceHost should display which frontend is used for scanning:

Code:

[DEBUG] >>> Scanning 394000000
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
      (0x00)
[DEBUG] >>> Scanning@continue3
[DEBUG] >>> Scanning@next

[Ludron]

Apparently NPVR is still trying to use frontend0 which results in error at line 471. Instead another frontend should accept correct params to line 77

Code:

    <type>DVB-C</type>
    <filter>adapter0</filter>
    <instance>1</instance>
    <resource>adapter0</resource>

In #3 we can see that friendly name is same for both fronends. That name also should be used instead of "local recorder".