no device-adapter0-qam.cfg

[donbrew]

I have decided to declare "there is something wrong with the .deb fie.". I will give a manual install a shot, after a while.

[mvallevand]

Seems like a bad decision and a waste of your time. Clear QAM is not very widely used in general and in Linux less so. Your time likely be better served sending the requested full mux for sub so he can look at the issue.

I have suggested to sub that the whole process of scanning clear QAM needs to be reviewed for one it is not acceptable to keep a browser page open for one hour. Also the fact that DeviceHostLinux needs a special library but TV Headend works with the standard library seems that there is something else going on. I wrote a manual program that reduces the list to clear QAM before scanning but I think it would useful to offer an offline scan using a dvbv5-scan conf file that NextPVR could import.

Martin

[donbrew]

I have been trying to get npvr working on linux since 5 was released with no luck. On different machines, different Ubuntu editions and installations.
I really appreciate you trying to help. I guess it boils down to I am the only one with the problem, I will go back to trying to force tvheadend to act friendly.

[mvallevand]

Why not just send the one minute file that sub asked for? You've come this far. My clear QAM scan works so I can't help sub, and there is no clear QAM in NZ.

Martin

[donbrew]

Here are some log files after scanning.  /var/opt/nextpvr/adapter0-QAM-channels.conf was NOT created in eitherr case.

Using dvbv5-scan created dvb_scan.conf
Using US-Cable-Standard-Center-Frequencies-QAM256 with the first 10 entries deleted.

I scanned for ATSC channels and adapter0-ATSC-channels.conf was created.

This seems to be relevant from nrecord.log

2021-05-26 14:43:17.838 [DEBUG][58]   bodyContentType: application/json
2021-05-26 14:43:17.838 [DEBUG][58] setting.scan.save
2021-05-26 14:43:18.013 [DEBUG][58] PreSave()
2021-05-26 14:43:18.013 [DEBUG][58] 1: /var/opt/nextpvr/adapter0-QAM-channels-scan.conf
2021-05-26 14:43:18.013 [DEBUG][58] 2: /var/opt/nextpvr/adapter0-QAM-channels.conf
2021-05-26 14:43:20.246 [ERROR][58] Unexpected error finalizing Linux scan: System.IO.FileNotFoundException: Could not find file '/var/opt/nextpvr/adapter0-QAM-channels-scan.conf'.
File name: '/var/opt/nextpvr/adapter0-QAM-channels-scan.conf'
  at System.IO.File.Move(String sourceFileName, String destFileName, Boolean overwrite)
  at System.IO.File.Move(String sourceFileName, String destFileName)
  at NShared.Recorders.DigitalScannerLinux.PreSave()
2021-05-26 14:43:21.456 [DEBUG][57] ReloadSettings()
2021-05-26 14:43:21.603 [DEBUG][57] Checking for new capture devices
2021-05-26 14:43:21.603 [DEBUG][57] CaptureSource.LoadAll()
2021-05-26 14:43:23.931 [DEBUG][57] {"stat":"ok"}

[mvallevand]

Sub asked for a full ts capture from the channel that was failing, I suspect you have a similar crash before the conf file is written so avoiding the crash will be important.

I will also check to see if QAM scanning is broken through a regression. (I hate testing QAM)

You can probably just rename the dvb_scan.conf to adapter0-QAM-channels.conf if the channels are written to the database.

Martin

[mvallevand]

It turns out there is a regression and I see it in your logs too

Code:

2021-05-26 14:43:17.838    [DEBUG][58]    setting.scan.save
2021-05-26 14:43:18.013    [DEBUG][58]    PreSave()
2021-05-26 14:43:18.013    [DEBUG][58]    1: /var/opt/nextpvr/adapter0-QAM-channels-scan.conf
2021-05-26 14:43:18.013    [DEBUG][58]    2: /var/opt/nextpvr/adapter0-QAM-channels.conf
2021-05-26 14:43:20.246    [ERROR][58]    Unexpected error finalizing Linux scan: System.IO.FileNotFoundException: Could not find file '/var/opt/nextpvr/adapter0-QAM-channels-scan.conf'.
File name: '/var/opt/nextpvr/adapter0-QAM-channels-scan.conf'
   at System.IO.File.Move(String sourceFileName, String destFileName, Boolean overwrite)
   at System.IO.File.Move(String sourceFileName, String destFileName)
   at NShared.Recorders.DigitalScannerLinux.PreSave()

Martin

[mvallevand]

There is another bug in QAM scanning, each of the channels created a new individual group so I end up with 250+ new groups.

Coping the dvbv5-scan conf file does work.

sudo cp dvb_channel.conf /var/opt/nextpvr/adapter0-QAM-channels.conf

Martin

[donbrew]

I tried that before, didn't work. I will make a new one and try again.

Is there supposed to be a /var/opt/nextpvr/adapter0-QAM-channels-scan.conf?

[mvallevand]

I think the scan file gets made and then in theory becomes the standard conf file.

Basically I think there is a lot broken with clear QAM right now on linux. I notice in Settings that I have an enabled QAM LocalRecorder with 42 channels on adapter0 that doesn't exist and another QAM device on adapter1/frontend0 that shows disabled that has no devices. The one marked LocalRecorder adapter0 goes to adapter1/frontend0 and works.

2021-05-26 19:39:35.770 [DEBUG][5] "/opt/nextpvr/system/DeviceHost/x64/DeviceHostLinux" -listen:38015 -type:QAM -device:"adapter1/frontend0" -instance:1 -parent:15806

Probably all part of the LocalRecorder to adapter/frontend migration.

Martin