Guide Time Right, Content Title Right, Actual content Wrong

#1

The guide is showing correct time (it's 9:30pm now, guide is listing for 9:30 onward). And what is on at 9:30 time slot is the correct title. But when I click on it, it either plays different content that doesn't match the title or it comes up with the record option showing the content title start at a time tomorrow.
Setup: VMWare 7.0 running 18.04 Ubuntu VM guest which hosts Channels DVR(latest). Guide connections: Philo, Pluto, Locast.
VMware set correctly at UTC (can't change to a specific time zone in the free VMWare), Linux VM set correctly for my timezone. Both sync with NIST NTP servers.

Any thoughts on this issue (other than us tech support world's best kept secret fix: reboot the server :-))

#2

All channels do this?

#3

I’ve also had this issue recently, specifically with NBC’s Late Night with Seth Meyers coming off of a HDHomeRun Prime.

#4

Urgh, apologies and thanks tmm1. After your post I checked a bigger number of channels. The issue is only happening with the Pluto source channels. The Locast and Philo channels I just checked are playing correctly with the listed titles.

#5

Robbie, how did you resolve it?

#6

Which Pluto xmltv are you using?

#7

This is the URLin my source settings: https://techzyon.com/epg/plutotv.m3u
I am not using a Docker Container.

#8

Well there you go. That's why.

1 Like
#9

Thanks tmm. So the fix is I need to get the Docker container running?

#10

Yes, or find another unique source for the M3u. Sharing a source m3u with multiple users causes problems.

1 Like
#11

Thanks Macnbaish. While my Channels DVR runs on Linux (hosted with VMWare) I also have a Windows 2016 Server (HyperV). I wanted to keep the Linux/Channels DVR server as absolutely thin and clean as possible, only apps/services that are absolutely needed to run Channels DVR. So I tried making the Docker container work on the 2016 server (it already has Docker installed). I just couldn't get that working (a cache failure error message). So I'm going to try it on the Linux server.

fyi, refreshing the Pluto source XMLTV has fixed the original issue for the time being -- that'll work until I get Docker up this weekend. Thanks

1 Like
#12

Issue has been fixed by installing Docker and using/installing the Docker Pluto image. Because I started without using Docker container, any recordings I had referencing Pluto channels fail (using Docker the Pluto channels are not the same channel number as before). Other than that looking great. Anyone new to Docker (and running on Linux) message me, I can give you pretty simple step by step link.

1 Like