Search the Community

Good afternoon My provider use channel number with 6 digit . Only 5 of them are displayed in the EPG, is there a config somewhere that I can change to view more digit or adjust the font or have the logo on another line Best regards, Sylvain

Recent Premier Emby user in USA and Emby Guide (14 days of data) seemed to be working great until MCE (Win 8.1) EPG Guide data went away. Now I can only get OTA EPG guide data (via NextPVR, i believe) for one day at most! I don't have officially supported tuners so apparently I cannot map channels either? because I don't receive OTA EPG data in Emby for ZIP 46808 (Fort Wayne, IN) I thought that Emby Premier included EPG guide data? Sorry if I'm confused but I couldn't find my exact problem in the forums Thanks!

I have my Emby Server configured to get two files from my provider: - "channels.m3u" (playlist) - "guide.xml" (EPG) I scheduled to update once a day 11:30pm ET. I was checking my provider (IIS log file), there is 1 request for the channels.m3u file and there are 220 requests for the guide.xml in 25min. I don't think this is correct behavior for the guide.xml (EPG)... it is requesting too many times.... this process should download once and parse the XML data. As you can see the channels.m3u file it was okay, There was only one request to get the file. I asked a friend to set up his Emby Server to get those files from my provider and we had the same issue. Here is the IIS log: 2019-11-23 03:30:03 207.180.???.?? GET /playlist/channels.m3u - 80 - 172.69.63.140 Levesque-Server/4.2.1.0 - 200 0 0 341 2019-11-23 03:30:08 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.140 Emby/3.0 - 200 0 0 4671 2019-11-23 03:30:19 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.249 Emby/3.0 - 200 0 0 3499 2019-11-23 03:30:27 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.61 Emby/3.0 - 200 0 0 3531 2019-11-23 03:30:34 207.180.???.?? GET /epg/guide.xml - 80 - 172.68.65.243 Emby/3.0 - 200 0 0 3156 2019-11-23 03:30:42 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.243 Emby/3.0 - 200 0 0 3454 2019-11-23 03:30:49 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.55 Emby/3.0 - 200 0 0 2984 2019-11-23 03:30:56 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.252 Emby/3.0 - 200 0 0 3218 2019-11-23 03:31:02 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.61 Emby/3.0 - 200 0 0 3281 2019-11-23 03:31:09 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.73 Emby/3.0 - 200 0 0 3234 2019-11-23 03:31:16 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.193 Emby/3.0 - 200 0 0 3156 2019-11-23 03:31:24 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.88 Emby/3.0 - 200 0 0 3468 2019-11-23 03:31:31 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.168 Emby/3.0 - 200 0 0 3687 2019-11-23 03:31:37 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.243 Emby/3.0 - 200 0 0 3015 2019-11-23 03:31:44 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.160 Emby/3.0 - 200 0 0 3218 2019-11-23 03:31:50 207.180.???.?? GET /epg/guide.xml - 80 - 172.68.65.243 Emby/3.0 - 200 0 0 2562 2019-11-23 03:31:56 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.78 Emby/3.0 - 200 0 0 3062 2019-11-23 03:32:03 207.180.???.?? GET /epg/guide.xml - 80 - 172.68.65.243 Emby/3.0 - 200 0 0 3253 2019-11-23 03:32:10 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.73 Emby/3.0 - 200 0 0 3116 2019-11-23 03:32:17 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.205 Emby/3.0 - 200 0 0 3421 2019-11-23 03:32:24 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.61 Emby/3.0 - 200 0 0 3156 2019-11-23 03:32:31 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.25 Emby/3.0 - 200 0 0 3046 2019-11-23 03:32:39 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.25 Emby/3.0 - 200 0 0 3250 2019-11-23 03:32:46 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.55 Emby/3.0 - 200 0 0 3078 2019-11-23 03:32:52 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.193 Emby/3.0 - 200 0 0 2531 2019-11-23 03:33:01 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.42 Emby/3.0 - 200 0 0 3484 2019-11-23 03:33:09 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.61 Emby/3.0 - 200 0 0 3390 2019-11-23 03:33:16 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.37 Emby/3.0 - 200 0 0 3234 2019-11-23 03:33:22 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.37 Emby/3.0 - 200 0 0 3145 2019-11-23 03:33:29 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.124 Emby/3.0 - 200 0 0 3109 2019-11-23 03:33:37 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.243 Emby/3.0 - 200 0 0 3218 2019-11-23 03:33:44 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.160 Emby/3.0 - 200 0 0 3578 2019-11-23 03:33:50 207.180.???.?? GET /epg/guide.xml - 80 - 172.68.65.57 Emby/3.0 - 200 0 0 2984 2019-11-23 03:33:57 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.252 Emby/3.0 - 200 0 0 3156 2019-11-23 03:34:02 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.128 Emby/3.0 - 200 0 0 3031 2019-11-23 03:34:10 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.88 Emby/3.0 - 200 0 0 3265 2019-11-23 03:34:17 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.193 Emby/3.0 - 200 0 0 3593 2019-11-23 03:34:25 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.20 Emby/3.0 - 200 0 0 3640 2019-11-23 03:34:32 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.61 Emby/3.0 - 200 0 0 3406 2019-11-23 03:34:37 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.42 Emby/3.0 - 200 0 0 2578 2019-11-23 03:34:44 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.122 Emby/3.0 - 200 0 0 3078 2019-11-23 03:34:50 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.160 Emby/3.0 - 200 0 0 2640 2019-11-23 03:34:57 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.200 Emby/3.0 - 200 0 0 3140 2019-11-23 03:35:04 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.61 Emby/3.0 - 200 0 0 3187 2019-11-23 03:35:11 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.110 Emby/3.0 - 200 0 0 3203 2019-11-23 03:35:18 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.200 Emby/3.0 - 200 0 0 3156 2019-11-23 03:35:25 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.37 Emby/3.0 - 200 0 0 3234 2019-11-23 03:35:32 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.160 Emby/3.0 - 200 0 0 3437 2019-11-23 03:35:39 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.86 Emby/3.0 - 200 0 0 4484 2019-11-23 03:35:47 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.122 Emby/3.0 - 200 0 0 3343 2019-11-23 03:35:53 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.160 Emby/3.0 - 200 0 0 2468 2019-11-23 03:36:00 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.26 Emby/3.0 - 200 0 0 3203 2019-11-23 03:36:08 207.180.???.?? GET /epg/guide.xml - 80 - 172.68.65.243 Emby/3.0 - 200 0 0 3296 2019-11-23 03:36:14 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.128 Emby/3.0 - 200 0 0 3031 2019-11-23 03:36:21 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.25 Emby/3.0 - 200 0 0 3062 2019-11-23 03:36:27 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.205 Emby/3.0 - 200 0 0 3031 2019-11-23 03:36:33 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.61 Emby/3.0 - 200 0 0 2531 2019-11-23 03:36:41 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.160 Emby/3.0 - 200 0 0 3484 2019-11-23 03:36:48 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.243 Emby/3.0 - 200 0 0 3187 2019-11-23 03:36:54 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.42 Emby/3.0 - 200 0 0 3031 2019-11-23 03:37:01 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.42 Emby/3.0 - 200 0 0 3046 2019-11-23 03:37:08 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.252 Emby/3.0 - 200 0 0 3484 2019-11-23 03:37:15 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.37 Emby/3.0 - 200 0 0 3031 2019-11-23 03:37:21 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.140 Emby/3.0 - 200 0 0 3234 2019-11-23 03:37:28 207.180.???.?? GET /epg/guide.xml - 80 - 172.68.65.57 Emby/3.0 - 200 0 0 3046 2019-11-23 03:37:35 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.243 Emby/3.0 - 200 0 0 3031 2019-11-23 03:37:41 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.52 Emby/3.0 - 200 0 0 2999 2019-11-23 03:37:48 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.168 Emby/3.0 - 200 0 0 3343 2019-11-23 03:37:54 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.80 Emby/3.0 - 200 0 0 3406 2019-11-23 03:38:01 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.110 Emby/3.0 - 200 0 0 3171 2019-11-23 03:38:08 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.128 Emby/3.0 - 200 0 0 3265 2019-11-23 03:38:14 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.86 Emby/3.0 - 200 0 0 3343 2019-11-23 03:38:21 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.249 Emby/3.0 - 200 0 0 2921 2019-11-23 03:38:29 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.168 Emby/3.0 - 200 0 0 4109 2019-11-23 03:38:35 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.61 Emby/3.0 - 200 0 0 2549 2019-11-23 03:38:43 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.37 Emby/3.0 - 200 0 0 3546 2019-11-23 03:38:49 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.80 Emby/3.0 - 200 0 0 3250 2019-11-23 03:38:56 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.124 Emby/3.0 - 200 0 0 3312 2019-11-23 03:39:03 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.61 Emby/3.0 - 200 0 0 3406 2019-11-23 03:39:08 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.61 Emby/3.0 - 200 0 0 2547 2019-11-23 03:39:16 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.61 Emby/3.0 - 200 0 0 3469 2019-11-23 03:39:23 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.157 Emby/3.0 - 200 0 0 3093 2019-11-23 03:39:30 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.55 Emby/3.0 - 200 0 0 3921 2019-11-23 03:39:37 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.86 Emby/3.0 - 200 0 0 3421 2019-11-23 03:39:43 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.128 Emby/3.0 - 200 0 0 3093 2019-11-23 03:39:50 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.61 Emby/3.0 - 200 0 0 3234 2019-11-23 03:39:56 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.73 Emby/3.0 - 200 0 0 3265 2019-11-23 03:40:03 207.180.???.?? GET /epg/guide.xml - 80 - 172.68.65.243 Emby/3.0 - 200 0 0 3656 2019-11-23 03:40:10 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.252 Emby/3.0 - 200 0 0 3328 2019-11-23 03:40:18 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.52 Emby/3.0 - 200 0 0 3515 2019-11-23 03:40:25 207.180.???.?? GET /epg/guide.xml - 80 - 172.68.65.243 Emby/3.0 - 200 0 0 3328 2019-11-23 03:40:32 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.140 Emby/3.0 - 200 0 0 3578 2019-11-23 03:40:39 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.157 Emby/3.0 - 200 0 0 3468 2019-11-23 03:40:45 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.80 Emby/3.0 - 200 0 0 3406 2019-11-23 03:40:52 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.55 Emby/3.0 - 200 0 0 3390 2019-11-23 03:40:58 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.243 Emby/3.0 - 200 0 0 3281 2019-11-23 03:41:05 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.20 Emby/3.0 - 200 0 0 3343 2019-11-23 03:41:11 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.20 Emby/3.0 - 200 0 0 3093 2019-11-23 03:41:18 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.42 Emby/3.0 - 200 0 0 3140 2019-11-23 03:41:24 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.110 Emby/3.0 - 200 0 0 3249 2019-11-23 03:41:31 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.200 Emby/3.0 - 200 0 0 2968 2019-11-23 03:41:37 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.80 Emby/3.0 - 200 0 0 3125 2019-11-23 03:41:43 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.122 Emby/3.0 - 200 0 0 3218 2019-11-23 03:41:50 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.4 Emby/3.0 - 200 0 0 3343 2019-11-23 03:41:56 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.80 Emby/3.0 - 200 0 0 2515 2019-11-23 03:42:03 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.55 Emby/3.0 - 200 0 0 3046 2019-11-23 03:42:09 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.193 Emby/3.0 - 200 0 0 3078 2019-11-23 03:42:17 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.78 Emby/3.0 - 200 0 0 3343 2019-11-23 03:42:23 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.73 Emby/3.0 - 200 0 0 3202 2019-11-23 03:42:30 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.124 Emby/3.0 - 200 0 0 3187 2019-11-23 03:42:37 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.61 Emby/3.0 - 200 0 0 3124 2019-11-23 03:42:44 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.157 Emby/3.0 - 200 0 0 3093 2019-11-23 03:42:51 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.124 Emby/3.0 - 200 0 0 3375 2019-11-23 03:42:58 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.168 Emby/3.0 - 200 0 0 3187 2019-11-23 03:43:04 207.180.???.?? GET /epg/guide.xml - 80 - 172.68.65.243 Emby/3.0 - 200 0 0 2906 2019-11-23 03:43:11 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.157 Emby/3.0 - 200 0 0 3171 2019-11-23 03:43:18 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.160 Emby/3.0 - 200 0 0 3203 2019-11-23 03:43:25 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.86 Emby/3.0 - 200 0 0 3343 2019-11-23 03:43:32 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.52 Emby/3.0 - 200 0 0 3375 2019-11-23 03:43:38 207.180.???.?? GET /epg/guide.xml - 80 - 172.68.65.57 Emby/3.0 - 200 0 0 3203 2019-11-23 03:43:45 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.168 Emby/3.0 - 200 0 0 3281 2019-11-23 03:43:51 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.88 Emby/3.0 - 200 0 0 3156 2019-11-23 03:43:57 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.157 Emby/3.0 - 200 0 0 2374 2019-11-23 03:44:03 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.80 Emby/3.0 - 200 0 0 3375 2019-11-23 03:44:08 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.61 Emby/3.0 - 200 0 0 3312 2019-11-23 03:44:16 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.200 Emby/3.0 - 200 0 0 3203 2019-11-23 03:44:24 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.157 Emby/3.0 - 200 0 0 3124 2019-11-23 03:44:31 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.55 Emby/3.0 - 200 0 0 3593 2019-11-23 03:44:36 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.124 Emby/3.0 - 200 0 0 2530 2019-11-23 03:44:43 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.160 Emby/3.0 - 200 0 0 3546 2019-11-23 03:44:50 207.180.???.?? GET /epg/guide.xml - 80 - 172.68.65.243 Emby/3.0 - 200 0 0 3373 2019-11-23 03:44:57 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.249 Emby/3.0 - 200 0 0 3218 2019-11-23 03:45:03 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.193 Emby/3.0 - 200 0 0 3343 2019-11-23 03:45:10 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.205 Emby/3.0 - 200 0 0 3140 2019-11-23 03:45:17 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.42 Emby/3.0 - 200 0 0 3187 2019-11-23 03:45:24 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.61 Emby/3.0 - 200 0 0 3031 2019-11-23 03:45:30 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.122 Emby/3.0 - 200 0 0 3078 2019-11-23 03:45:36 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.193 Emby/3.0 - 200 0 0 2499 2019-11-23 03:45:42 207.180.???.?? GET /epg/guide.xml - 80 - 172.68.65.243 Emby/3.0 - 200 0 0 3046 2019-11-23 03:45:49 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.26 Emby/3.0 - 200 0 0 3187 2019-11-23 03:45:56 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.20 Emby/3.0 - 200 0 0 3203 2019-11-23 03:46:03 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.252 Emby/3.0 - 200 0 0 3156 2019-11-23 03:46:09 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.122 Emby/3.0 - 200 0 0 3062 2019-11-23 03:46:15 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.205 Emby/3.0 - 200 0 0 3281 2019-11-23 03:46:22 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.205 Emby/3.0 - 200 0 0 3296 2019-11-23 03:46:28 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.86 Emby/3.0 - 200 0 0 3531 2019-11-23 03:46:36 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.20 Emby/3.0 - 200 0 0 3781 2019-11-23 03:46:42 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.193 Emby/3.0 - 200 0 0 3125 2019-11-23 03:46:49 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.252 Emby/3.0 - 200 0 0 3124 2019-11-23 03:46:56 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.55 Emby/3.0 - 200 0 0 3359 2019-11-23 03:47:02 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.124 Emby/3.0 - 200 0 0 3390 2019-11-23 03:47:09 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.140 Emby/3.0 - 200 0 0 3422 2019-11-23 03:47:16 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.128 Emby/3.0 - 200 0 0 3062 2019-11-23 03:47:22 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.25 Emby/3.0 - 200 0 0 3203 2019-11-23 03:47:29 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.61 Emby/3.0 - 200 0 0 3531 2019-11-23 03:47:36 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.61 Emby/3.0 - 200 0 0 3281 2019-11-23 03:47:42 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.4 Emby/3.0 - 200 0 0 3093 2019-11-23 03:47:49 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.243 Emby/3.0 - 200 0 0 3578 2019-11-23 03:47:57 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.25 Emby/3.0 - 200 0 0 3671 2019-11-23 03:48:03 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.124 Emby/3.0 - 200 0 0 2640 2019-11-23 03:48:10 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.20 Emby/3.0 - 200 0 0 3531 2019-11-23 03:48:17 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.25 Emby/3.0 - 200 0 0 3203 2019-11-23 03:48:24 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.160 Emby/3.0 - 200 0 0 3281 2019-11-23 03:48:32 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.249 Emby/3.0 - 200 0 0 3921 2019-11-23 03:48:37 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.128 Emby/3.0 - 200 0 0 3406 2019-11-23 03:48:45 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.168 Emby/3.0 - 200 0 0 4296 2019-11-23 03:48:51 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.88 Emby/3.0 - 200 0 0 3187 2019-11-23 03:48:58 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.4 Emby/3.0 - 200 0 0 3296 2019-11-23 03:49:05 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.88 Emby/3.0 - 200 0 0 3624 2019-11-23 03:49:13 207.180.???.?? GET /epg/guide.xml - 80 - 172.68.65.243 Emby/3.0 - 200 0 0 3499 2019-11-23 03:49:19 207.180.???.?? GET /epg/guide.xml - 80 - 172.68.65.243 Emby/3.0 - 200 0 0 3156 2019-11-23 03:49:25 207.180.???.?? GET /epg/guide.xml - 80 - 172.68.65.57 Emby/3.0 - 200 0 0 2937 2019-11-23 03:49:32 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.193 Emby/3.0 - 200 0 0 3265 2019-11-23 03:49:39 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.26 Emby/3.0 - 200 0 0 3203 2019-11-23 03:49:46 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.124 Emby/3.0 - 200 0 0 3078 2019-11-23 03:49:52 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.55 Emby/3.0 - 200 0 0 3062 2019-11-23 03:49:59 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.42 Emby/3.0 - 200 0 0 3796 2019-11-23 03:50:05 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.37 Emby/3.0 - 200 0 0 3218 2019-11-23 03:50:13 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.4 Emby/3.0 - 200 0 0 3124 2019-11-23 03:50:20 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.128 Emby/3.0 - 200 0 0 3453 2019-11-23 03:50:26 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.252 Emby/3.0 - 200 0 0 3218 2019-11-23 03:50:33 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.26 Emby/3.0 - 200 0 0 3312 2019-11-23 03:50:39 207.180.???.?? GET /epg/guide.xml - 80 - 172.68.65.57 Emby/3.0 - 200 0 0 2999 2019-11-23 03:50:46 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.128 Emby/3.0 - 200 0 0 2890 2019-11-23 03:50:53 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.78 Emby/3.0 - 200 0 0 3249 2019-11-23 03:51:01 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.73 Emby/3.0 - 200 0 0 3281 2019-11-23 03:51:08 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.160 Emby/3.0 - 200 0 0 2999 2019-11-23 03:51:14 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.4 Emby/3.0 - 200 0 0 3187 2019-11-23 03:51:21 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.193 Emby/3.0 - 200 0 0 3109 2019-11-23 03:51:28 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.140 Emby/3.0 - 200 0 0 3703 2019-11-23 03:51:34 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.205 Emby/3.0 - 200 0 0 3312 2019-11-23 03:51:41 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.52 Emby/3.0 - 200 0 0 3171 2019-11-23 03:51:48 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.25 Emby/3.0 - 200 0 0 3234 2019-11-23 03:51:55 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.168 Emby/3.0 - 200 0 0 3750 2019-11-23 03:52:02 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.37 Emby/3.0 - 200 0 0 3484 2019-11-23 03:52:08 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.37 Emby/3.0 - 200 0 0 2781 2019-11-23 03:52:15 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.78 Emby/3.0 - 200 0 0 3374 2019-11-23 03:52:22 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.42 Emby/3.0 - 200 0 0 3578 2019-11-23 03:52:29 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.252 Emby/3.0 - 200 0 0 3140 2019-11-23 03:52:35 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.25 Emby/3.0 - 200 0 0 3281 2019-11-23 03:52:42 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.26 Emby/3.0 - 200 0 0 3218 2019-11-23 03:52:50 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.78.55 Emby/3.0 - 200 0 0 3468 2019-11-23 03:52:56 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.205 Emby/3.0 - 200 0 0 2578 2019-11-23 03:53:03 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.140 Emby/3.0 - 200 0 0 3765 2019-11-23 03:53:10 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.80 Emby/3.0 - 200 0 0 3546 2019-11-23 03:53:17 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.168 Emby/3.0 - 200 0 0 2734 2019-11-23 03:53:25 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.80 Emby/3.0 - 200 0 0 3281 2019-11-23 03:53:31 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.205 Emby/3.0 - 200 0 0 2796 2019-11-23 03:53:39 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.80 Emby/3.0 - 200 0 0 2843 2019-11-23 03:53:45 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.252 Emby/3.0 - 200 0 0 3296 2019-11-23 03:53:51 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.249 Emby/3.0 - 200 0 0 3265 2019-11-23 03:53:58 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.61 Emby/3.0 - 200 0 0 3187 2019-11-23 03:54:06 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.52 Emby/3.0 - 200 0 0 4015 2019-11-23 03:54:13 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.42 Emby/3.0 - 200 0 0 3625 2019-11-23 03:54:20 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.86 Emby/3.0 - 200 0 0 3781 2019-11-23 03:54:27 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.168 Emby/3.0 - 200 0 0 3265 2019-11-23 03:54:34 207.180.???.?? GET /epg/guide.xml - 80 - 162.158.79.200 Emby/3.0 - 200 0 0 3218 2019-11-23 03:54:41 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.88 Emby/3.0 - 200 0 0 3406 2019-11-23 03:54:49 207.180.???.?? GET /epg/guide.xml - 80 - 173.245.54.80 Emby/3.0 - 200 0 0 3218 2019-11-23 03:54:54 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.62.205 Emby/3.0 - 200 0 0 2406 2019-11-23 03:55:00 207.180.???.?? GET /epg/guide.xml - 80 - 172.69.63.52 Emby/3.0 - 200 0 0 2437

Hello, I'm creating my own EPG data using WebGrab+Plus, the XML loads fine however in chrome and on android it looks strange for certain channels, while in Emby Theater all looks fine all the time. See attachments! Someone experienced the same perhaps, i'm coming over from plex and on Plex it worked great but it had other issues so wanted to give emby a shot. Best Regards, Toetje

Hi, I recently moved over from Plex to Emby & hoping i can get some help with EPG artwork using an XMLTV file generated by EPG Collector. Im using EPG collector with the 'lookup' tab enabled to gather poster images for Freesat UK. Data is being collected successfully and i have a fold full of fanart. I cannot seem to get this to display in Emby? Update: I have managed to get rid of the block colours under Movie, can get all details and a poster sized image outline, but their is no fanart. If i try to reload nothing happens. When i copy the link address i see this message: "Only 'http' and 'https' schemes are allowed. Parameter name: requestUri"

Even though I've set it to 7 days, then I tried 5...but I can't seem to get more than 1 day's worth of guide data. I've tried using my IPTV provider's XML TV URL, same as a local file. I think I've tried a combination of the XML file & the Emby guide..but I can't recall. I'm about to try that again. If I have more than one source, how does it determine the priorities? Will it choose one or the other, or try to merge the data? Otherwise, anyone else experiencing the same issue?

Hello, Recently purchased Emby. As a whole I was able to install and configure the server without issues. It is installed and configured with hdhomerun and one m3u source, 2 EPG each dedicated to their own tuner. The issue is with the client apps. At first I was using an older 1/4GB Android 7 TV box but am now upgraded to a Quad 4/64GB Android 9 box. Navigation is really difficult with the remote. I can't seem to be able to select and click with the standard remote as pressing left, right, up down seems to focus on groups rather than tiles. When I use the mouse function I can however navigate and select. Other part is EPG which takes a couple of minutes to display and it is close to imposible to navigate (imposible with keys and takes forver with mouse) At first I had the server on a Linux VM but then moved it to a linux PC ..... then a Windows 10. Nothing helped so I blamed Wifi, wired everything in and connected them to the same switch but still it is horribly slugish. Any tips on how to optimize performance ? Thanks.

Hi *, the following problem seems not to be a general problem of the LG app, I have 3 LG TVs and one is displaying the guide correctly while the other two do not The attached screen is taken from my LG OLED65C7... it seems it tries to display to many rows so the current selected show that is shown at the bottom of the epg is overwritten by the epg grid. On the TV in my bedroom (LG 43UK6300LLB) it is displayed correctly. don't know if this behavior is already known to you ;-) greetz

I really like the option that I can list my Favourite channels in the Live TV Guide first. However, on the Home Screen the "On Now" does not respect this preference, and there is no other setting than (as suggested in a different post) to manually remove the non-favoured channels from EPG. This is obviously not an option and goes against the logic of EPG as such. I use manually generated xmltv file for EPG from webgrabplus. Would it be please possible to provide an option for On Now to sort the favourites first?

The image previews in library News feed are distorted. Instead in the continue watching section, the pictures have the right format. How is it possible to show the previews in the right format?

I think this is due to the latest update to 4.0.1, but suddenly, some of my IPTV channels (only a handful) have stopped populating the guide info even though I checked the epg.xml provided by my IPTV provider (Vaders) and there is EPG data for those channels. Specifically they are ABC, NBC, CBS and Fox. IPTV is on one tuner and regular antenna tv through hdhomerun is on another tuner getting its EPG straight from Schedules Direct. No issue with the hdhomerun tuner or its guide. Is there suddenly an issue with having the same channels listed with different tuners and different guide providers? Or do they ultimately all have the same XML ID which is causing a conflict? I can't tell. All I know is that everything was working well for about a month and suddenly no more guide info for the IPTV channels that have an equivalent channel on another tuner. I am not sure where emby stores the EPG data it pulls from Schedules Direct. I would like to compare XML data and see if I consolidate this all somehow. Should I try disabling the antenna tuner and its guide? (I only use it as a backup if IPTV is not working because aerial reception is garbage) Any advice on a resolution or suggestions on a better setup would be appreciated.

Title says it all. On some channels icons are missing. On others the icons on there. When I first set up Emby on Jan 29 all of the icons were there. Anyone know how to fix it? To rule out mobile client issues (even though I noticed it on iOS), I opened up a Chrome browser and the issue is still there. I am using Emby's built-in guide (since I didn't want to pay for a guide and emby provides it so I figured it would be the "most supported" option) These channels are at the top of the guide (there are more with no icons but this is just a subset). And here are some with icons. I can't imagine the guide doesn't recognize the channels with no icons. Like I said they were working on Jan 29 when I purchased Emby Premiere. Anyone know what's going on?

Is there a way to force an EPG update via command line? I'm currently doing a workaround right now where I'm externally downloading an XML file and would optimally like to script in a way for emby to refresh the EPG.

hi, using emby 4.0.2 and using the xtream-editor service to sort my M3U + XML (EPG) from them. But emby is not able to get the XML correct, Error Log: 2019-01-19 09:21:02.886 Info App: xmltv path: https://xtream-editor.com/en/get/epg/ID 2019-01-19 09:21:02.886 Info App: Downloading xmltv listings from https://xtream-editor.com/en/get/epg/ID 2019-01-19 09:21:02.886 Info HttpClient: GetTempFileResponse url: https://xtream-editor.com/en/get/epg/ID 2019-01-19 09:21:04.067 Error App: Error adding metadata *** Error Report *** Version: 4.0.0.2 Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3 Operating system: Unix 4.4.59.0 64-Bit OS: True 64-Bit Process: True User Interactive: True Processor count: 2 Program data path: /config Application directory: /system System.Xml.XmlException: System.Xml.XmlException: Root element is missing. at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.ParseDocumentContent() at System.Xml.XmlTextReaderImpl.Read() at System.Xml.XmlReader.ReadToDescendant(String name) at Emby.XmlTv.Classes.XmlTvReader.GetChannels() at Emby.LiveTV.Listings.XmlTv.XmlTvProvider.GetChannels(ListingsProviderInfo info, CancellationToken cancellationToken) at Emby.LiveTV.EmbyTV.GetEpgChannels(IListingsProvider provider, ListingsProviderInfo info, Boolean enableCache, CancellationToken cancellationToken) at Emby.LiveTV.EmbyTV.AddMetadata(IListingsProvider provider, ListingsProviderInfo info, List`1 tunerChannels, Boolean enableCache, CancellationToken cancellationToken) at Emby.LiveTV.EmbyTV.GetChannelsAsync(Boolean enableCache, CancellationToken cancellationToken) Source: System.Private.Xml TargetSite: Void Throw(System.Exception) at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.ParseDocumentContent() at System.Xml.XmlTextReaderImpl.Read() at System.Xml.XmlReader.ReadToDescendant(String name) at Emby.XmlTv.Classes.XmlTvReader.GetChannels() at Emby.LiveTV.Listings.XmlTv.XmlTvProvider.GetChannels(ListingsProviderInfo info, CancellationToken cancellationToken) at Emby.LiveTV.EmbyTV.GetEpgChannels(IListingsProvider provider, ListingsProviderInfo info, Boolean enableCache, CancellationToken cancellationToken) at Emby.LiveTV.EmbyTV.AddMetadata(IListingsProvider provider, ListingsProviderInfo info, List`1 tunerChannels, Boolean enableCache, CancellationToken cancellationToken) at Emby.LiveTV.EmbyTV.GetChannelsAsync(Boolean enableCache, CancellationToken cancellationToken)

Hi, since updating to Emby 4.0.0.2 in combination with MediaPortal Plugin 1.88 I'm having the problem that the EPG Data is displayed exactly one hour to early. e.g. the daily german news normaly starts at 20:00 emby shows it starting time at 19:00 :/ The Mediaportal guide in Mediaportal Application and the MediaPortal Webinterface displays all times correctly. When I access the guide on emby (and the plugin) the times are incorrect. I even did a complete clean emby installation, same problem :/

So I tried searching for "emby gzip" and came across this thread: https://emby.media/community/index.php?/topic/53404-xmltv-guide-providers-gz-zip-support/ Apparently gzip is supported, but I can't get it to work. I can download the gzip externally and load the extracted file in manually which works fine, but using the URL directly doesn't seem to work. I figured I'd check the logs and came up with this. The URL to the actual EPG has been edited. If it's required, I can PM it. 2019-01-19 08:23:53.970 Info App: xmltv path: https://url.to/epg 2019-01-19 08:23:53.973 Error App: Error adding metadata *** Error Report *** Version: 4.0.0.2 Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb Operating system: Unix 4.15.0.43 64-Bit OS: True 64-Bit Process: True User Interactive: True Processor count: 4 Program data path: /var/lib/emby Application directory: /opt/emby-server/system System.Xml.XmlException: System.Xml.XmlException: Root element is missing. at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.ParseDocumentContent() at System.Xml.XmlTextReaderImpl.Read() at System.Xml.XmlReader.ReadToDescendant(String name) at Emby.XmlTv.Classes.XmlTvReader.GetChannels() at Emby.LiveTV.Listings.XmlTv.XmlTvProvider.GetChannels(ListingsProviderInfo info, CancellationToken cancellationToken) at Emby.LiveTV.EmbyTV.GetEpgChannels(IListingsProvider provider, ListingsProviderInfo info, Boolean enableCache, CancellationToken cancellationToken) at Emby.LiveTV.EmbyTV.AddMetadata(IListingsProvider provider, ListingsProviderInfo info, List`1 tunerChannels, Boolean enableCache, CancellationToken cancellationToken) at Emby.LiveTV.EmbyTV.GetChannelsAsync(Boolean enableCache, CancellationToken cancellationToken) Source: System.Private.Xml TargetSite: Void Throw(System.Exception) at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.ParseDocumentContent() at System.Xml.XmlTextReaderImpl.Read() at System.Xml.XmlReader.ReadToDescendant(String name) at Emby.XmlTv.Classes.XmlTvReader.GetChannels() at Emby.LiveTV.Listings.XmlTv.XmlTvProvider.GetChannels(ListingsProviderInfo info, CancellationToken cancellationToken) at Emby.LiveTV.EmbyTV.GetEpgChannels(IListingsProvider provider, ListingsProviderInfo info, Boolean enableCache, CancellationToken cancellationToken) at Emby.LiveTV.EmbyTV.AddMetadata(IListingsProvider provider, ListingsProviderInfo info, List`1 tunerChannels, Boolean enableCache, CancellationToken cancellationToken) at Emby.LiveTV.EmbyTV.GetChannelsAsync(Boolean enableCache, CancellationToken cancellationToken) If further logs are required, I can also post them.

This is a request to expand / explain the XMLTV supported tags / features Currently, the XMLTV supported tags seem quite basic. As far as I can tell, they are being read, but aren't being used to their full extend. There is no documentation on which tags Emby supports and how they are implemented. So, I'm just going from personal experience here. As @@Luke mentioned: Feature requests work best with examples, so here goes. Consider this current piece of XMLTV: <programme start="20181217135500 +0000" stop="20181217142500 +0000" channel="Comedy Central HD"> <title lang="nl">Family Guy</title> <sub-title>The Peter Principal</sub-title> <desc lang="nl">Amerikaanse animatieserie. Meg maakt gebruik van Peter's positie als tijdelijke directeur van de school om wraak te nemen op haar pestkoppen. Brian en Stewie openen een B&B. </desc> <date>20170430</date> <category lang="nl">TV Drama</category> <category lang="en">Drama</category> <category lang="nl">Komedie</category> <category lang="en">Comedy</category> <icon src="somesite.com/1.png" width="180" height="260"/> <icon src="somesite.com/2.png" width="180" height="260"/> <icon src="somesite.com/3.png" width="75" height="108"/> <icon src="somesite.com/4.png" width="210" height="303"/> <icon src="somesite.com/5.png" width="110" height="159"/> <icon src="somesite.com/6.png"/> <episode-num system="onscreen">S15E18</episode-num> <episode-num system="thetvdb.com">series/75978</episode-num> <episode-num system="thetvdb.com">episode/6021539</episode-num> <rating system="Kijkwijzer"> <value>6</value> <icon src="https://somesite.com/1.png"/> <icon src="https://somesite.com/2.png"/> <icon src="https://somesite.com/3.png"/> </rating> <star-rating> <value>7.2/10</value> </star-rating> <credits> <director>Greg Colton</director> <director>Dominic Bianchi</director> <writer>Seth MacFarlane</writer> <actor role="Peter Griffin">Seth MacFarlane</actor> <actor role="Lois Griffin">Alex Borstein</actor> </credits> </programme> This will generate the following in the Emby guide : This seems to be missing, or at least not utilizing, some of the data that is available. Recording this, also seems to record to an "Unknown" season. What if we utilize some of the data available. Consider the following (badly done) mockup of mine: This incorporates much of the available data. This is just an idea of what can be done. The tags used in the XMLTV file conform to the standard set out in https://github.com/XMLTV/xmltv/raw/master/xmltv.dtd. I could imagine that with working season/episode information, Emby could give an indicator to show if this program is in the library and if it has been watched. Perhaps we could get some documentation up in how the Emby XMLTV implementation supports certain tags? Currently unused in ui tags: credits (director, writer, actor[role], etc episode-num[onscreen, thetvdb.com, imdb.com] rating[icon*] With the implementation of Gracenote for some countries, I would expect the Emby UI to start showing more and more data that is available. Please chime in with your thoughts and possible examples

I'm currently using server wmc, but the windows media center guide is always dumping, leaving me with "NO DATA AVAILABLE". This happens maybe every 6wks. I've tried all of the tricks, but ultimately end up having to rebuild everything - which is a real headache. What's everybody using? I'd prefer a free service that I can also integrate into my KODI build, but would consider paying for a robust application. Thanks..

Hi, I use XML files (xmltv.xml) generated using the zap2epg python script to map my channels. It works great for all channels except I'm running into an issue with ABC EPG data. It seemed to be working fine, but it appears that something in the XML file for ABC, maybe it's a special character that is causing a problem with SQ lite and the library.db file, I don't know. I have attached the xmltv.xml and embyserver.txt files. I pulled out just what I believe should be needed. When looking at the guide through the Emby client, doesn't matter if I'm using the Fire Stick TV, my phone app, or doing it on the server, for ABC it shows guide data properly all the way up to and including Jimmy Kimmel Live that starts at 11:35PM on 11/1/18 and ends at 12:37AM on 11/2/18, but then it shows nothing after that. It just shows <No Program Data Available> or blank depending on the client being used. All my other channels, and I have 45 Channels from HDHomerun Premium, and 30 OTA channels, guide data works fine. The EPG data after Jimmy Kimmel Live clearly exists in the xmltv.xml file, and I can't figure out what's wrong with it. The only thing I can think of is that there is something in it that SQ lite does not like, so when it imports that data into the library.db file, it messes up the EPG feed for ABC, and once it happens it is broke for good for that channel. I thought I could just shutdown the Emby server and rename the library.db file, and that would fix it, but I tried that once and it didn't, so I ended up completely uninstalling/reinstalling the Ember server to fix it... but at that time I had no data at all showing up for ABC, so I didn't really have any information to go on for root cause. I just did the uninstall/reinstall last night, and it looked like it fixed the problem because EPG data for ABC was showing up just fine, or so I thought. I realized earlier today that it was only showing guide data up to and including Jimmy Kimmel Live tonight, and that was it... the problem has returned after that. I appreciate you looking at this data below, and log file, and any insight you can provide to the root cause and permanent fix. Thanks in advanced. Brady embyserver.txt Sample_xmltv.xml

Hi all, Has something changed recently regarding xmltv EPG import? Recently, parts of my EPG info is no longer showing in Emby. /Jennice

Hi Emby team, If I have two EPG sources, and some channels are present in both, then how do I prioritize / choose between them when merging? Also, daylight saving time seems to be different in UK and DK, so for periods in spring and fall, English channels are off-set by 1 hour when watching in DK. Is there a way to compensate the EPG (which then is 1 hour off)?

Hello folks, I've been running my emby server for several months on the same IPTV provider service, and until lately its been working great. The problem I've run into now is that the XMLTV guide no longer downloads automatically from the HTTP link. If I post that same link in a browser, download the XMLTV file manually, then load it locally - it works just fine and the guide fills in completely. If it is trying to load from the HTTP link automatically, no guide information shows up at all. Any guidance would be appreciated. I'm running win 10 pro 1803 latest updates and Emby server latest release (I've also tried the latest beta, .16 at the time of this writing). Thanks, T.J. Emby-Server.zip

This may sound like a strange request, but when I first added my M3U file the channels and guide populated with some very nice (I believe default) Channel Icon with the Flag of the country it was from behind it. I actually kind of liked it because it allowed me to know what country the Channel was from (A&E with USA vs A&E with Spanish Flag for example) What happened though is after EPG refreshed after 24 hours, then the icons were replaced by just the channel icons, the png that were bigger, perhaps more poppy and they look nice, but I would love to see if there is a way to retain the Flag Backed Ones somehow, or to have the Flag in the background of the newer ones. I can provide screenshots if needed.

So I switched to using XMLTV for guide data (using EPG123) primarily because the data correctly displayed the "premiere" indicator in the guide listings - I lose the "HD" but I can live with that. Updated to 3.3.1.3 and now the premiere indicator is no longer getting displayed in the EPG. Switched back to 3.3.1.2 and the premiere indicator is displayed in the EPG. Can this be fixed? Also is it possible to get all of the indicators displayed when using XMLTV as the guide source - HD program, Live broadcasts, New episodes, Premieres, Repeat episodes together when all are checked? I am currently missing HD Program and Live broadcast when viewing the EPG (along with Premiere as I mentioned with 3.3.1.3). Like I said I can live without the HD being displayed, would be nice to have them all. Alternately is it possible to get the premiere tag displayed when using the SD JSON data as the guide source? Thanks!

Hello, is there a way to make it to where the epg just shows what is on at this moment? my mom who lives in new york, her epg is different than mine and is not showing the correct data for what is on. its 3 hours in the future, but the stream is not. Is there anyway around this?