robbieb43
New member
Can someone educate me please in regard to how service identity/numbering is handled on reboot?
I have had an issue that has spanned several releases of v6.6 and it relates to some timers failing after a reboot. The timers are for channels that are SatIP streams from my local server (DVB-T). I have exteplayer3 installed and use 4097 for these streams. Here is an example:
(You can see I have encoded the special characters in the url portion also, but I cannot remember what past issue this was to address
)
Since the timer in the timers.xml file is identical both before and after rebooting, I wondered whether something happens to the identity in Lamedb or the service list? I recall an answer to another question which implied that numbering was calculated on each boot(?) for instance.
The timer works correctly if I manually update the Channel name in the timer (and save), but again no change seem to occur to timers.xml.
I have had an issue that has spanned several releases of v6.6 and it relates to some timers failing after a reboot. The timers are for channels that are SatIP streams from my local server (DVB-T). I have exteplayer3 installed and use 4097 for these streams. Here is an example:
Code:
#SERVICE 4097:0:1:1A:0:0:0:0:0:0:http%3A//192.168.0.23%3A8875/%3Ffreq%3D546%26bw%3D8%26msys%3Ddvbt%26tmode%3Dauto%26mtype%3Dauto%26gi%3Dauto%26fec%3Dauto%26pids%3D0%2C16%2C500%2C501%2C503%2C504%2C505%2C202:TV CANARIA
(You can see I have encoded the special characters in the url portion also, but I cannot remember what past issue this was to address
Since the timer in the timers.xml file is identical both before and after rebooting, I wondered whether something happens to the identity in Lamedb or the service list? I recall an answer to another question which implied that numbering was calculated on each boot(?) for instance.
The timer works correctly if I manually update the Channel name in the timer (and save), but again no change seem to occur to timers.xml.