Linux scan options different from Windows scan options

[sub]

Thanks for the fast reply!

So I need to convert the qam.ini file into the linux format and place it in the appropriate directory?

edit: Isn't the scan the same in Win and Linux, NextPVR is asking the tuner to check a frequency.

Unfortunately no, it doesn't work like that in Linux. It does in Windows. In Linux the TV tuner framework needs specifically format files, and it needs to read from them. (ie, NextPVR can't just pass in info from it's windows ini files)

Or since I already scanned on Win 10, took about 20 min.  Is there a way to copy my channel list from Win to linux and use that? Then I wont have to scan again.

Unfortunately no, the tuning info is different between the two platforms. (windows is more like the contents of the ini files with frequencies etc, and linux points at a tuning file and indexes entries by name)

Doesn't make sense to me. Ultimately whats the flow look like?

I'd expect at a point in the flow there is a common format:

Win 10: NextPVR -> ini.file -> NextPVR -> Win DVB driver -> DVB card -> Scans frequencies

Linux: NextPVR -> linuxtv dvbfiles -> linuxtv -> linux DVB driver -> DVB card -> Scans frequencies

At the bare minimum the DVB drivers must send the same commands to the hardware to scan the frequencies, regardless of OS.

Simplified, a channel (perhaps the correct term is mux) is a frequency and encoding.

The ini files look like standard channels naming (1,2,3...) while the linux dvb files have frequency and additional parameters. I would expect, NextPVR or something else fills in the blanks to send to the driver.

But from what you're saying, it sounds like the inputs to the drivers are completely different. Am I understanding that correctly?

Exactly as Martin says, the tuner api on both systems is very different.

On Linux they provide a very abstract interface, which is trying to be super flexible in allowing for different tuning systems like ATSC/DVB-C/DVB-T/DVB-S/ISDB-T/DMB-T or whatever might come along in the future. All these types of tuning systems use very different types and numbers of tuning parameters, and tuning parameters come from the files. The application doesn't deal directly with frequencies etc.

On Windows, yes the application deals with frequencies directly (and other attributes, like symbol rates, modulations, segments, bandwidth, etc, which are required from some types of tuners)