Channel list editing.

[mame]

You asked about the fields for "Channel Editing" for ediitng the name and number.  You are looking at unrelated EPG data.

Martin

I'm not looking at EPG data, but at the npvr data base.
Did you read the post #5?
The initial discrepancy on the channels originated from the unexpected absence of a string in the db3 which created to me an invalid report, hence the subsequent posts.

[mvallevand]

You are actually looking the EPG source information field, not the channel name and number fields. There doesn't seem to be much more to say, you have the information you need.

Martin

[Graham]

The initial discrepancy on the channels originated from the unexpected absence of a string in the db3 which created to me an invalid report, hence the subsequent posts.

I am sorry but I do not understand.

What do you want to do with NextPVR?  What happens when you try to do it?  What do you see in the NextPVR Web App or in nextpvr.exe that is unexpected or incorrect?

[sub]

What is never in the database?
Here two reports exported from the databases and opened with excel
in the past the string <readable_source> was always there for all the channels, in the last npvr some channels have not it
(look, for an example only, at the channels TELENORD and Telecittà, currently without the previous string).

===  csv exported from npvr.db3 on 22/05/2020:

oid,name,number,epg_source,epg_mapping,minor
……
11376,LA7,7,DVB/ATSC EPG,"<epg>
  <source>DVB/ATSC EPG</source>
  <capture_source>21</capture_source>
  <readable_source>711:263:8572 LA7</readable_source>
  <mapping>711:263:8572</mapping>
</epg>
",0
11377,TELENORD,9,DVB/ATSC EPG,"<epg>
  <source>DVB/ATSC EPG</source>
  <capture_source>21</capture_source>
  <readable_source>1:17002:8572 TELENORD</readable_source>
  <mapping>1:17002:8572</mapping>
</epg>
",0
11378,Primocanale,10,DVB/ATSC EPG,"<epg>
  <source>DVB/ATSC EPG</source>
  <capture_source>21</capture_source>
  <readable_source>1:16515:8572 Primocanale</readable_source>
  <mapping>1:16515:8572</mapping>
</epg>
",0
11379,TelecittΩ,11,DVB/ATSC EPG,"<epg>
  <source>DVB/ATSC EPG</source>
  <capture_source>21</capture_source>
  <readable_source>2:16515:8572 TelecittΩ</readable_source>
  <mapping>2:16515:8572</mapping>
</epg>
",0
11380,E'TV LIGURIA,12,DVB/ATSC EPG,"<epg>
  <source>DVB/ATSC EPG</source>
  <capture_source>21</capture_source>
  <readable_source>5:16515:8572 E&apos;TV LIGURIA</readable_source>
  <mapping>5:16515:8572</mapping>
</epg>
",0


===  csv exported from npvr.db3 on 02/06/2020:

oid,name,number,epg_source,epg_mapping,minor
………..
11376,LA7,7,DVB/ATSC EPG,"<epg>
  <source>DVB/ATSC EPG</source>
  <capture_source>21</capture_source>
  <readable_source>711:263:8572 LA7</readable_source>
  <mapping>711:263:8572</mapping>
</epg>
",0
11377,TELENORD,13,DVB/ATSC EPG,"<epg>
  <source>DVB/ATSC EPG</source>
  <capture_source>21</capture_source>
  <mapping>1:17002:8572</mapping>
</epg>
",0
11378,Primocanale,10,DVB/ATSC EPG,"<epg>
  <source>DVB/ATSC EPG</source>
  <capture_source>21</capture_source>
  <readable_source>1:16515:8572 Primocanale</readable_source>
  <mapping>1:16515:8572</mapping>
</epg>
",0
11379,Telecittà,11,DVB/ATSC EPG,"<epg>
  <source>DVB/ATSC EPG</source>
  <capture_source>21</capture_source>
  <mapping>2:16515:8572</mapping>
</epg>
",0
11380,E'TV LIGURIA,12,DVB/ATSC EPG,"<epg>
  <source>DVB/ATSC EPG</source>
  <capture_source>21</capture_source>
  <readable_source>5:16515:8572 E&apos;TV LIGURIA</readable_source>
  <mapping>5:16515:8572</mapping>
</epg>
",0

I thought you were talking about channel names/numbers info (and I interpreted this as being the <readable_source> info that is shown on the channel list, which isn't stored in the database). This info shown above is different data related to the EPG mapping.

It's probably just missing on channels after you've gone in and changed the EPG source (like if it had been temporarily set to something, then you changed back to the DVB EPG). Ultimately the app doesn't need it, and sometimes it wont be there.

[mame]

Well, OK, this is a good explain, I was thinking it might be an anomaly.
No problem, if needed those data are also in the <mapping> string.
May we close this thread?