When to use "add sd channel lineup" button

[bluesight]

I think this is just a mismatch of expectations. I would expect to need a scan of my tuners first to see if they can find at least the channels I want. Then, I could manually prune off the extra channels that I don't want (typically from 34 down to 9), or I would expect to use this button the automatically prune down to my pre-selected 9 channel lineup in SD. I now limit the scans to only the channels on my SD lineup, so I no longer need to worry about paring the lineup down. I am just looking to see if my tuners can find the channels I want (per other post trying to find channel 3.1).

If I would expect to use this button first (right after I log in to SD), I would then need to expect that my tuner scans would subsequently automatically be pared down to my SD lineup. I don't think that is what happens. Or maybe I should not subsequently do tuner scans.

Just overthinking it I guess...(or over misunderstanding...)

B

[mvallevand]

A scan of ATSC is typically done once with very rare repacks. The only reason I created a local list was I test NextPVR on many setups. I don't think the average user should waste all that energy especially when they are trying to learn how to use NextPVR at the same time.

Also remember channel number and frequencies are not the same thing. Schedules Direct does provide an API that gives the frequencies with major minor but we'd have to rely on their database which is unproven. It would be a nice feature when sub has the time. However many cheap users in North America don't use it so an alternate scan is still required so sub has to focus on features that can be used by everyone.

Martin

[rkulagow]

I think this is just a mismatch of expectations. I would expect to need a scan of my tuners first to see if they can find at least the channels I want. Then,  I could manually prune off the  extra channels that I don't want (typically from 34 down to 9), or I would expect to use this button the automatically prune down to my pre-selected 9 channel lineup in SD.

B

Is that the point of confusion? There are two services that Schedules Direct offers; the legacy XML, and the JSON service.

The XML service is configured on the Schedules Direct website. You select which channels you want to receive data for.

The JSON service is configured through an API. Everything is done in the application, because then the application can make things nice and pretty, and you're not trying to configure in multiple places.

So on the JSON service, there are no "pre-selected 9 channel lineup in SD", because we're only storing the name of the lineup that you're interested in; which channels you want to download data for is left for the application UI.

[mvallevand]

I am pretty sure rather than scanning he wants NextPVR to implement the SD JSON auto mapping API as an option to reduce the number of frequencies scanned. I don't think the XML interface is useful for this without physical frequencies.

You won't be seeing that in your testing because the linux NextPVR HDHR implementation doesn't scan, it uses HDHR prescanning.

Martin

[rkulagow]

Ah; well, where possible, we have the uhf/vhf information included in the lineup mapping, so it's available. But as you said, scans aren't done all that often, and don't take long to complete.

[sub]

Ultimately the user needs to scan their device to find the channels. For most users outside North America, that it - it's all setup and ready to use, with DVB EPG. For users in North America, they can then optionally associate a guide source, usually Schedules Direct, but could also be xmltv.

If I'd been building NextPVR explicitly targeting North America, and I knew a Schedules Direct account was always going to be available, the process for somethings might have been slightly different, but that isn't the case.

[mvallevand]

Sub on linux when you have to use the dtv-scanning table you don't associate anything until after the scan. For the OP coming from WMC where Microsoft did everything then it probably does seem complicated and slow to wait 8 minutes for a scan. User don't care that it takes you hours to implement this.

Martin

[bluesight]

I clearly have a problem...can't seem to let this (NextPVR/Kodi project go). So I decided on a NextPVR reinstall on my 18.04 system...like maybe 45 minutes...tops. Half day later...it seems to work even on my "bad" channel (3.1) and even with both tuners...sorry for the whine...

Anyway, with the reinstall, for grins, I tried doing the "add sd channel lineup" right after logging into SD..and got the same error with no result. Not a biggy...just another point of info. And I forgot that what I can get with my local (us-WI-Madison) file wasn't the 9 actual channels of interest, but the limited subset of 30 or so from the 7 odd frequencies from which to select my 9 (as you all mention above...thanks). The main benefit is that I don't have to wait to scan bunches more frequencies and then select out of about 50 possible locals (when my tuners can get them).

By the way, the work you two do is golden and your responses much appreciated...sorry to bring newbie confusion into it...

b

[sub]

Anyway, with the reinstall, for grins, I tried doing the "add sd channel lineup" right after logging into SD..and got the same error with no result.

I'm still trying to picture exactly what you're describing.

On the Settings->Guide page, do your Schedules Direct lineups listed at the top of the page? (might take a few seconds to appear when you first visit the page)

[sub]

Can you supply the logs after doing the 'add sd channel lineup'? We'll check for errors.