Rescan but keep customised channel numbers (LCNs)? (3 Viewers)

[mm1352000]

I mean when there's a lot of new channels - instead of scanning several transponders manually, it's easier to just rescan all transponders. But then that resets all of the LCNs which makes the job even longer...

Okay, understood... and this is the thing that I'm saying will probably be possible for you after the patch is merged.

Names aren't reset right now though. It seems strange that LCNs are reset upon scanning but channel names aren't!

As previously mentioned, this is because the LCN is stored on the tuning detail and the name that you see is stored on the channel, and this is what the patch is designed to resolve. Actually you probably aren't aware of this but if you check the TuningDetail table in the DB you'll see there is a name on the tuning detail as well that does get automatically updated on scan. In other words, the current approach is that TuningDetail details get updated; channel details do not. The tuning detail name is used as the starting channel name, but never shown after that.

The strategy that you suggest has been suggested internally for keeping channel names up to date. The comparison would be between the name on the tuning detail with the name on the channel. The same could be applied to the LCN. All of the pieces are there, it is just a matter of time before it happens...

 

[DragonQ]

Well that's good news. I don't think I'll be using 1.3.0 until its final version on my main machine so hopefully it'll be included in that.

 

[Benoire]

I mean when there's a lot of new channels - instead of scanning several transponders manually, it's easier to just rescan all transponders. But then that resets all of the LCNs which makes the job even longer...

Okay, understood... and this is the thing that I'm saying will probably be possible for you after the patch is merged.

Names aren't reset right now though. It seems strange that LCNs are reset upon scanning but channel names aren't!

As previously mentioned, this is because the LCN is stored on the tuning detail and the name that you see is stored on the channel, and this is what the patch is designed to resolve. Actually you probably aren't aware of this but if you check the TuningDetail table in the DB you'll see there is a name on the tuning detail as well that does get automatically updated on scan. In other words, the current approach is that TuningDetail details get updated; channel details do not. The tuning detail name is used as the starting channel name, but never shown after that.

The strategy that you suggest has been suggested internally for keeping channel names up to date. The comparison would be between the name on the tuning detail with the name on the channel. The same could be applied to the LCN. All of the pieces are there, it is just a matter of time before it happens...

Hi mm,

Is this likely to be a feature of 1.3 final, or is it likely to come with another release? I always struggle when Sky update their channels as I have to manually renumber everything :-(

 

[mm1352000]

Probably 1.3b...
Having said that, a better solution for you is probably to have TV Server support grabbing the Sky NZ LCN.
I wasn't aware of this until just this week, but Sky NZ actually use a custom descriptor tag for their LCNs. This is why TV Server currently doesn't support grabbing them. The TsWriter rework that I've been working on over the last month or so will support grabbing them.

mm

 

[Benoire]

Hey mm, that is awesome news. Looking forward to trying this out!

Now where was the donation button again...