v1.1.15 Release
Forum rules
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html ★
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html ★
-
- Posts: 1708
- Joined: Fri Aug 24, 2012 7:35 pm
- Location:
- HTPC Specs:
v1.1.15 Release
Any compelling reasons to go from v1.1.13 to v1.1.15? I don't see any errors reported here so I assume there hasn't been any issues with it? TIA
- garyan2
- Posts: 7438
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
v1.1.14 had a short life (~6 hours). I removed it when I found out I didn't completely fix the null entry issue.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
- Posts: 1708
- Joined: Fri Aug 24, 2012 7:35 pm
- Location:
- HTPC Specs:
Yes but are there advantages / drawbacks to v1.1.15 for old time users or is this mainly an update for those importing their Rovi Recording Database? The description doesn't tell me this other than fixing "null" stations.garyan2 wrote:v1.1.14 had a short life (~6 hours). I removed it when I found out I didn't completely fix the null entry issue.
- garyan2
- Posts: 7438
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
The updates I pushed out for v1.1.14/15 were to address something that could potentially affect everyone. There were some changes to the response message from SD for channel mapping that my code wasn't designed/ready for.
The null entry in the json response would cause you to fail to update ... couldn't get past building your lineup for download. I know of at least 2 lineups that were impacted by the null entry issue and I assume this could happen when a provider changes their lineup to force a change. The null entry is the remnant/tombstone of the change.
The QAM/Cable channel number issue is currently being mitigated by SD. They changed the response to not include QAM channel numbers to avoid what happened to some people. Anyone with a cable lineup that also has QAM information could potentially lose that guide channel due to a change in the channel number and channel id. v1.1.15 will protect that from happening if/when SD turns that information back on.
So just because you weren't affected by these issues doesn't mean you won't be in the future.
The null entry in the json response would cause you to fail to update ... couldn't get past building your lineup for download. I know of at least 2 lineups that were impacted by the null entry issue and I assume this could happen when a provider changes their lineup to force a change. The null entry is the remnant/tombstone of the change.
The QAM/Cable channel number issue is currently being mitigated by SD. They changed the response to not include QAM channel numbers to avoid what happened to some people. Anyone with a cable lineup that also has QAM information could potentially lose that guide channel due to a change in the channel number and channel id. v1.1.15 will protect that from happening if/when SD turns that information back on.
So just because you weren't affected by these issues doesn't mean you won't be in the future.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
- Posts: 1708
- Joined: Fri Aug 24, 2012 7:35 pm
- Location:
- HTPC Specs:
I am all up to date. Did a manual run this morning with no issues.