Search the Community

Gamebrowser The Gamebrowser plugin brings game support to your living room, GameBrowser fetches game art and metadata automatically, and launches games using supported Emby clients. Get started with the correct folder structure The first thing you will want to do is make sure your games have the ideal folder structure, Start with a ROOT Games folder, then each game console should be in its own folder, with each game in their own subfolders. Games > ATARI > Asteroids > Asteroids.a26 > Pitfall > Pitfall.a26 > SNES > Donkey Kong Country > Donkeykongcountry.smc > Super Mario World > Supermarioworld.smc MAME is the one exception to this structure, as you can have all the game .zip files in the same folder Games > MAME > Aliens.zip > Btoads.zip > Dkong.zip Setting Up the Gamebrowser Plugin on the Server Gamebrowser is added to the server via the plugins tab on the server dashboard by navigating to Plugins > Plugin Catalog > Server > Gamebrowser and then clicking Install. Once it completes restart the server. Platform Configuration Continue setup on the server dashboard by navigating to Plugins > My Plugins > Gamebrowser and click + Add next to Game Systems, This page is where the game systems are configured. Start by choosing the path to one of your game folders, and then choosing the appropriate platform from the drop-down box. Then click Save. A UNC path is recommended if you plan to stream games over LAN/WAN connections. More info on using UNC paths //here Repeat this process for each game platform. Adding games to your Library Games are added to your library on the server dashboard by navigating to Library > and clicking + Add Media Library, choose Games from the drop-down box and name your game library, then click + Add next to Folders. Choose the path to the ROOT of your games folder. After the automatic library scan completes, your games should show up in the web client. Setting up Clients to Launch Games Emby Theater Launching games from Emby theater only requires a simple setup of external players. Open EmbyTheater, in the top right corner click on your profile icon in the top right corner, then navigate to Settings > External Players > Add Player Change the Media Type to Game, and the Game system to whatever system you would like to setup. In the Player Path type or paste the location of your emulator. Enter the correct command line argument for your emulator (listed at the bottom of this guide) Click save, and repeat for each game platform Emby Classic In order for games to be recognized in Emby Classic, you will need to install the GameBrowser-Classic plug-in in that app. GameBrowser-Classic can be installed from inside the Emby-Classic config pages by navigating to Plug-ins tab > Plug-in Catalog > GameBrowser-Classic. The plugin is free but requires the server to have a valid supporter key. After the plugin is installed, navigate to Emby Classic Configurator > Plug-ins tab > GameBrowser-Classic > Configure Select the game system you would like to setup, using the button on the right next to executable location, select the location of your emulator. Repeat for each game platform. For the switches section, most emulators will work using "{rom}", other emulators will require special switches, which will be listed at the end of this tutorial. Extra Setup Windows and DOS Games (Emby Classic only) Due to the client-server nature of Emby, to get Windows and DOS games to be visible to the server, you will need to follow this guide. Navigate to your ROOT Games folder, then create folders for Windows and/or DOS, with each game in their own subfolders. If it's a windows game place a game.gbwin file within each game directory. If its a DOS game place a game.gbdos file within each game directory. This file can be anything such as a blank text document or zip file. Just make sure to change the name to game and the extension to gbwin / gbdos. Games > WINDOWS > Baldur's Gate > game.gbwin > Borderlands > game.gbwin > DOS > Zork > game.gbdos > Wing Commander > game.gbdos After this step navigate to Emby Classic Configurator > Plug-ins tab > GameBrowser-Classic > Configure > Windows Games tab Select a game you wish to setup on the left, then click the button on the right next to Local Executable and select the .exe of the game. Repeat for each game. The setup for DOS games is the same as it is for Windows games. Navigate to Emby Classic Configurator > Plug-ins tab > GameBrowser-Classic > Configure > DOS Games tab Select a game you wish to setup on the left, then click the button on the right next to Local Executable and select the .exe of the game. Repeat for each game. Most DOS games don't run well in modern windows PC's. DOSBox is a great tool to overcome that. If DOSBox is configured in GameBrowser-Classic, then any games with a game.gbdos file will be launched through DOSBox. To use DOSBox follow this extra step. Navigate to Emby Classic Configurator > Plug-ins tab > GameBrowser-Classic > Configure > Miscellaneous tab Click the button on the right next to DOSBox and select the DOSBox.exe Emulator Command Line Arguments EMBY CLASSIC USAGE Atari > Stella > "{rom}" Nintendo 64 > Project64 v1.6 or earlier > {rom} > Project64 v1.7 or newer > "{rom}" Nintendo DS > DeSmuME > "{rom}" Nintendo Gamecube > Dolphin > --execute="{rom}" Nintendo GBA > VisualBoyAdvance > "{rom}" Nintendo NES > VirtuaNES > "{rom}" > NEStopia > "{rom}" Nintendo SNES > ZSNES > -m "{rom}" > snes9x > "{rom}" Nintendo Wii > Dolphin > --execute="{rom}" Sega Genesis > Fusion > -fullscreen "{rom}" Sega Dreamcast > NullDC > -config ImageReader:DefaultImage="{rom}" Sega Saturn > Yabause > -a -f -i "{rom} Sony PS1 > ePSXe > -nogui -loadbin "{rom}" Sony PS2 > PCSX2 > --nogui --fullscreen "{rom}" Sony PSP > PPSSPP > "{rom}" EMBY THEATER USAGE NOTE: Each argument needs to be on its own line, so for instance for SNES/zsnes, -m and {path} should be on 2 seperate lines. Like so: -m {path} Atari > Stella > {PATH} Nintendo 64 > Project64 > [PATH] Nintendo DS > DeSmuME > {PATH} Nintendo Gamecube > Dolphin > --execute={PATH} Nintendo GBA > VisualBoyAdvance > {PATH} Nintendo NES > VirtuaNES > {PATH} > NEStopia > {PATH} Nintendo SNES > ZSNES > -m {PATH} > snes9x > {PATH} Nintendo Wii > Dolphin > --execute={PATH} Nintendo Wii U > Cemu > --rom {PATH} Sega Genesis > Fusion > -fullscreen {PATH} Sega Dreamcast > NullDC > -config ImageReader:DefaultImage={PATH} Sega Saturn > Yabause > -a -f -i {PATH} Sony PS1 > ePSXe > -nogui -loadbin {PATH} Sony PS2 > PCSX2 > --nogui --fullscreen {PATH} Sony PSP > PPSSPP > {PATH} With ePSXE if you get an error "PSX Bios not found", use this switch to specify the location of the bios, just change the path to where your bios is located. EMBY CLASSIC USAGE Sony PS1 > ePSXe bios error > -nogui -bios "C:\Program Files\ePSXe 1.8\bios\scph1001.bin" -loadbin "{rom}" EMBY THEATER USAGE Sony PS1 > ePSXe bios error > -nogui -bios "C:\Program Files\ePSXe 1.8\bios\scph1001.bin" -loadbin {PATH}

Hello, I recently added Live TV to my Emby experience and I've noticed the guide information for TELUS Optik, Rogers Cable, and Bell Cable are missing. The only guides available are for Satellite guide data which doesn't have some of the channels available in regular cable. Is there something I am missing? It seems there are only 3 different guides available for Canada (SHAW Direct, Bell ExpressVu, and TELUS Satellite). Thanks! ***Realized I should have added to "Emby Provided Guide Data". Sorry!*** EDIT ***I found postal codes that work after trial and error.***

Hi guys, I wanted to move from plex to emby since a while for multiple reasons. I decided to make this guide first because I want to give back something to the amazing community behind UNRAID/REDDIT/EMBY and second because I couldn't find a step by step guide so I thought it would be nice to have a lot of useful information in a single place. If you just want to setup the hardware transcoding using intel quick sync video in emby on unraid go directly to STEP 8. I take also the opportunity to thank spaceinvaderone for the amazing videos he made about UNRAID, I learned a lot, and the linuxserver.io guys/gals for the amazing job they do supporting and maintaining the community images. Note: I am not affiliated with anybody nor I get paid to do this, this shows the steps I used to setup emby on unraid so to make it easier for you to do the same. Also english is not my native language so excuse me for any syntax/grammar error. Last premise before we start, if you want to add something or you think some steps needs additional informations to be clearer let me know in the comments. @Mods: I couldn't post it under "tutorial and guides" section. if you can please move it to the appropriate section, thank you. Let the fun begin... PREREQUISITES: -------------------- UNRAID 6.9-RC1 or newer UNRAID COMMUNITY APPLICATIONS (Refer to this post on how to install: https://forums.unraid.net/topic/38582-plug-in-community-applications/) EMBY v4.5 or newer EMBY PREMIERE SETUP: --------- STEP 1 - Setting up a dynamic DNS ----------------------------------------- Use your preferred dynamic dns provider to setup a custom dns tracking service. For example: "emby.hopto.org" where "emby" is the name you want and the rest is fixed depending on the dynamic dns provider. Ex.: "myembysrv.hopto.org" STEP 2 - CREATE A CUSTOM DOCKER NETWORK ---------------------------------------------------------- Inside the unraid web interface, open a terminal by clicking the terminal icon on the top right corner and type docker network create cdocknet where "cdocknet" is the name of our custom docker network. You can name it whatever you want. Press ENTER and then a long string of random characters (network id) should appear meaning the custom network was successfully created. If there is an error message make sure you correctly typed in the command otherwise search google for the error message and fix it before moving onto the next step. If everything is successful you can close the terminal window and proceed to the next step. STEP 3 - Install SWAG (Secure Web Application Gateway) ------------------------------------------------------------------- Inside the unraid web interface, go to apps then in the top right corner inside the search bar search for "swag" (without quotes) Click install and you will be redirected to the container settings. Change the following settings: Network type: -> Select Custom: cdocknet (or watherver name you assigned in step 2) HTTP: -> Change it to 8080 or another port that is not in use either in unraid or any docker you have HTTPS: -> Change it to 8443 or another port that is not in use either in unraid or any docker you have EMAIL: -> Your email address DOMAIN NAME: -> The Dynamic DNS domain name, so if we use the one I setup in the first step it is going to be hopto.org Yours can be different. Ex.: ddns.net, duckdns.org SUBDOMAINS: -> Delete the "www" and replance it with the custom name you chose in step 1, in our case emby. ONLY SUBDOMAINS: -> Set it to true (we tell swag to issue the cert. only for our subdomain as we don't own the top level domain be it hopto.org or whatever else you chose) You can leave the rest as default. Now before clicking "APPLY" open a new tab and go to your router setting and setup a port forward to unraid for the port 80 and 443. I cannot give a specific guidance here as every router setting is different. Try to search for port forwarding [your router model] in google and read how to do it. You should have a table/items like this. You need to setup 2 port forwarding, one for port 80 and one for port 443. NAME/APPLICATION NAME/SERVICE NAME: Swag80 IP ADDRESS: enter unraid ip address PUBLIC PORT: enter the default HTTP port, in this case 80 PRIVATE PORT: enter the custom port you setup for the docker, in our case 8080 PROTOCOL: TCP NAME/APPLICATION NAME/SERVICE NAME: Swag443 IP ADDRESS: enter unraid ip address PUBLIC PORT: enter the default HTTPS port, in this case 443 PRIVATE PORT: enter the custom port you setup for the docker, in our case 8443 PROTOCOL: TCP After you did so go back to unraid and click apply. Once swag is installed check the log setting to make sure everything is done without error thus a certificate is created and valid. Basically you shouldn't have any red/amber warning in the log and at the end you should see a "Server ready." message. If any red/amber shows then check the port are correctly forwarded (make sure the numbers are correct, the unraid server's ip address is correct) otherwise read what the error says and do a search to fix it. STEP 4 - Install Emby -------------------------- As before go under the apps tab in unraid to open the community applications and search for emby. You should see 3 or more emby containers, you can use the one you prefer. For our guide we use the official emby container. Click install and again you'll be redirected to the docker settings. Change the following settings: Network type: -> Select Custom: cdocknet (or watherver name you assigned in step 2; if you have multiple custom network make sure you use the same you setup in swag otherwise the reverse proxy won't work) Host path 2:* -> Path to your media folder share. Ex.: /mnt/user0/Media Then click apply and wait for the docker to be pulled. Once it's complete you can open emby web interface by clicking on the EmbyServer icon and select "WebUI". Emby asks you to setup a username and a password. Note this one will be the admin of the server so use a strong password. Don't worry about Emby connect, this is not required at this moment so you can leave it blank. If you have one feel free to enter it. Click next. You can already setup the library in this part or skip and do it later. For the purpose of this guide we skip it as it's not difficult and there is plenty of documentation on emby website on how to do that. So now you can click finish and you will have emby UI with all the libraries (if you setup any) and the possibility to access the server settings. STEP 5 - Configure SWAG proxy-conf --------------------------------------------- If you didn't change the default appdata config path in swag you will have all the config file under /mnt/user/appdata/swag. So from unraid webui set the appdata share to export with public access type. To do so just click on the appdatashare, then under SMB Security Settings set the following: Export: -> yes Security: -> Public Click apply then done. From your PC/MAC navigate to the appdata share and open the swag folder. In windows would be "This PC-> Network -> unraid_server_name -> appdata -> swag" Inside swag navigate to nginx and then open proxy-conf folder. Search and open a file named emby.subdomain.conf.sample with your preferred text editor be it notepad, notepad++, gedit or whatever. Inside this file you have to change: server_name emby.* to whatever name you setup in step 1 for the dynamic dns. Example if your dynamic dns is myembysrv.ddns.net in this line you would setup server_name myembysrv.* The other line we have to change is the set $upstream_app emby by replacing emby with the container name. If you used the official emby container and you didn't change it then you would set this up to set $upstream_app EmbyServer . You can find the container name in unraid. Now click save and rename the file by removing the ".sample" at the end. So the new file name will be "emby.subdomain.conf". Go back to unraid webui, click on the swag container icon and restart the container. (This reloads the configuration files in swag like the one we just modified) STEP 6 - Configure remote access on Emby --------------------------------------------------- Open emby webui by clicking on the emby docker icon in unraid, go to settings -> network. Tick the "Allow remote connections to this emby server" now some extra settings will appear. Scroll down till you find "Public HTTPS port number" and change it to "443" Right below you find the "External domain:" and set this to the dynamic dns we setup in step 1. In our case is "emby.hopto.org" Then scroll down a bit more till you find "Secure connection mode:" and change it to "Handled by reverse proxy" Then just below it untick the "Enable automatic port mapping" and then scroll at the end of the page and click save. Go back to unraid webui and restart emby docker. STEP 7 - Test the remote connection -------------------------------------------- Open a new tab and go to "https://emby.hopto.org", of course replace this with your custom dynamic dns entry. Ex.: "https://myembysrv.ddns.net" You should see a "Please sign in" page with emby logo asking you for a login and password. If you see a connection timeout then you did something wrong. Go back and re-read all the steps and make sure you did everything correctly. If you see an SSL cert error/browser warning that the connection is not secure then you messed up with the ports or skipped some steps. Again re-read and make sure you did everything properly. STEP 8 - Setting the HW (hardware) transcoding in Emby with intel QSV (Quick Sync Video) ---------------------------------------------------------------------------------------------------------- Requirements: Emby premiere Intel CPU that has Quick Sync Video (search your cpu at https://ark.intel.com/content/www/us/en/ark.html#@Processors) Compatible motherboards (sometimes iGPU has to be enabled in BIOS/UEFI, in some other cases you need a VGA/HDMI plugged-in to have it functional either by plugging in a monitor or by using a dummy VGA/HDMI adapter) If you meet the above requirements please read on... Open a terminal window in unraid (top right corner, click on the terminal icon inside the unraid webui) and type the following: ls /dev/dri and press ENTER If you see something like by-path/ card0 renderD128 this means that the QSV is already enabled in your unraid server and you can skip to the docker setting step otherwise read on. In the terminal window type: modprobe i915 then press ENTER (if there is any error stop and solve this before moving on. Make sure you meet all the requirements) Then type: ls /dev/dri and press ENTER. Now you should see something like this: by-path/ card0 renderD128 Now type chmod -R 777 /dev/dri to set the permission on the folder so we can access to it from the emby docker container. Once that's done close the terminal window, go over Emby docker container icon and click "Edit". This will bring the container settings up like the first time we installed it. Scroll down at the bottom and click on "+ Add another path, port, variable, label or device". A new window/popup will open. Change the following settings: Config Type -> Device Name -> /dev/dri Value -> /dev/dri Description -> Intel Quick Sync Video Then click "ADD" and the "APPLY" and after the container is pulled down again click on "DONE". Now open emby webui, go to "Settings -> Transcoding" and make sure you have "Enable hardware acceleration when available:" set to "Yes" or "Advanced". With advanced you can see the various preferred hardware encoders/decoders emby will use and tick/untick the ones you want. Scroll to the bottom and click on "Save". STEP 9 - Testing the hardware transcoding and make Intel QSV persistent across unraid server reboots ------------------------------------------------------------------------------------------------------------------------- To test if the hardware trascoding is working as intended just go to your library, open a movie and select a different quality. For example you can set it to 480p - 1Mbps and click play. If you go in your server dashboard inside emby webui settings you will see under Active devices the client name that is reproducing the movie and just below informations about wether it is being transcoded or not and which encoder/decoder is being used. For example if you see VAAPI (Video Acceleration Api) means the hardware transcoding is working using the intel QSV by accessing /dev/dri (Direct rendering infrastructure). Finally last step is to go back into unraid webui, open a terminal window and edit the go file to make sure Intel QSV is always on even if we reboot the server. To do so type: nano /boot/config/go and press ENTER Nano editor will open and you will see the content of the file. If you never modified it before it should be similar to: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & Just add the following lines to the bottom of the file modprobe i915 chmod -R 777 /dev/dri Your go file should look like this: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & modprobe i915 chmod -R 777 /dev/dri Save using the CTRL + O and then CTRL + X to exit Done! If you read it this far I thank you for the attention and I hope you found this guide useful. Finally you can enjoy your media on the sofa.

It would be really nice to be able to continue scrolling through the guide and when you hit the bottom it takes you right back to the top. Rather than having to scroll back up threw everything in reverse. Just a suggestion. And maybe it's only me that would like it.

I have a some gripes with the Guide functionality on the Emby for Roku app (version 4.1.15): I can select the Tags in the guide ["Show Only channels with Tag(s)"], however I have to do it every time the Emby app is started on Roku. It would be ideal if the Tags would be remembered after an app re-start. I can select the Sort in the guide ["Sort by:"], however I have to do it every time the Emby app is started on Roku. It would be ideal if the Sort would be remembered after an app re-start. I can set the Sort in the Guide ["Sort by:"] only to a limited number of options. I would really like to have the same options that are available in a Web Browser. I'm specifically referring to the "Favorites, Then by..." options that are available in a Web Browser, but not on Roku. I'm hoping these are something that could be addressed in a future version of Emby for Roku. Thanks

I use the IPTV plugin on Emby. I have the following problem: On the web-based display, I can turn off the display of logos and channel numbers, and it only shows the channel name in the left column in bold. This is very readable at a distance, and that is what I prefer. On the Android TV app, I cannot turn off the display of logos and channel numbers in the left column. When seated in a chair, it's not possible to see the channel logo as it is made smaller to display the channel number, which is very large and bold. For me, channel numbers are useless anyway, since I have so many channels. I use favorites to keep the channels I want listed first. What I want is for the channel name only to be displayed in the left column. That would be readable across the room and USEFUL. Thanks

Hello @jaycedkI have strange situation. I have set everything like You said and today when I check I don't see even VAAPI to choose. Also throttling settings are uncheck. It's because I recreate container?

Is there something wrong with Emby guide sources? Woke up this morning and I’m not able to pull Emby guide data… I noticed there was an Emby guide app update pushed yesterday too.

I removed a playlist from my provider (unrelated to the stations you see below), the next thing I know, I can't update my EPG. Despite everything still being mapped, I can't get my channel information restored. All that hard work. I even replaced a backup of my old TVxml file. I'm using a Linux seedbox (Ubuntu 20.04) with my Roku. I sent the logs through my Roku. I don't know if you guys need me to send my logs from my seedbox; but I can't on this public forum, as the logs contain my IP address as well as my seedbox DNS.

Hi, it will be nice to get option to add full tv guide in home screen instead of just one line. Regards.

Hello, I buy m3u IPTV list and there's that link for EPG: epg.xml. I add that list to Emby and most channels works OK but when I go to Guide tab I don't see any guide. Page is empty. I refresh Guide in Sheduler.

It would be great to be able to configure channel groups in LiveTV, which can be selected in the guide view (maybe as tabs) so that we can more quickly navigate to preferred channels using the d-pad. Perhaps start with Favorites by default, but be able to add custom groups (similar to collections) which we can add channels to (Network, Premium, Basic Cable, Kids, News etc.).

option for QUICKLY viewing tv guide without stopping the video in emby for android app currently this feature only exists on emby for android tv but is nowhere to be seen in emby for android. i would use emby for android tv but it keeps crashing every second time i open it. the other good thing about emby for android tv is i can see even more channels while in the quick view tv guide that is displayed over the video.

Hi - I am using Emby (latest version 4.5.2.0) on a Fire TV and always had this problem for the past year, even with previous versions. I am using Emby's Guide Data. I am currently getting OTA through Locast, but this exact same problem occurred when I had OTA channels with HDHomerun. Here is: - When opening the live tv guide, I see the list of channels and programming starting from the top (see print screen 1) which is for me starts with channel 2.1 CBS since I sort them by channel number. When I scroll down the channels, I see all channels and program data. For example, scrolling down to 9.1 as seen in print screen 2. - Now if I select a channel located down the guide (9.1 for example), and I then I exit Emby, and go back to Emby, it will by default go back to 9.1 when I open the guide. However the problem if when I scroll up, it then shows "No Program Data Available" for the upper channels above 9.1 (as seen in print screen 3). If I select an upper channel, it comes up fine with the data info for that channel I select. If I select 2.1, and exit Emby and go back in Emby, the TV Guide will by default start at 2.1 and the tv guide is back up exactly like it was in print screen 1. This has been the case in all Fire TV's I have tried this on, I basically cannot exit Emby from a lower scrolled down channel if I want to have a TV guide for the upper channels. I have tried to reboot the server, remove and reload the guide, rescan and reload channels, but this problem has always persisted. Does anyone know if there is fix for this - Thank you

I am fairly new to Live TV in Emby, and have only just started to test it out. I have an IPTV service which is working in EMBY, and contains channels for the USA (I live in the UK). Currently I will be keeping these channels, but was wondering, using Emby Guide data, which is the best zipcode & service to pull data from which would give me the most channels (I know some I will have to add other guides) Many thanks inadvance for your help and info

Nvidia Shield 2019 Pro with Android TV The home screen tool bar things. called "Channels" I have one for Emby, "Live TV" It only puts 3 icons there, On Now, Live TV Guide, Recordings. The On Now does not always go to the On Now screen, say if i was in a tv series folder or else where previously, it will just load back to that page and not On Now. Ideally, would like to the list of On Now programs be the "Channels" banner thing on the home screen, so I can just scroll through what is on now on the atv home screen, like i can with the butil in "Channels" live app, or Channels DVR software. Second, but different issue of Emby on Android TV, is that when i load the Guide, the first several channels, it shows No data available, unless i scroll left or so, then back, then it loads it. does this every time i load into the guide or scroll through it at all. Does it in the mini guide too. I am using the beta Emby app btw.

Hi All I have just moved over to Emby from Plex and I have setup my Live TV via IPTV in the App from my supplier. The channels download and play OK but I cannot get the Guide to show what is on....nothing shows only the channel names. The format of my M3U statement is https://website link/my username/password - do I need to get some additional settings from my IPTV supplier? I am using the app on a samsung tv Thanks Phil

Hi All, The recent upgrade to 4.3.3 states "Performance improvement to TV guide', But I am not seeing anything on my setup. My setup is Andriod TV on an Nvidia Shield, connecting directly to a Synology NAS via managed hub on the same VLAN. The NAS runs the Emby Server which also connects to a HD Homerun Quattro, also on the same hub and VLAN. My issue is with scrolling through the TV guide If you scroll through the guide with the BBC channel highlighted, I can scroll forward through programmes for weeks, no problem. But if if I select another channel to be highlighted such as ITV2+1, it will scroll up to 10pm that day then screw up the whole guide with "<No programme Data Available>". Yet if I use the calendar to select a future date, all works fine. So scrolling on certain channels is broken for me Any ideas ?

I’d like there to be an option for the tvguide xmltv to be enhanced using tvdb or moviedb data. Also useful would be to tag the scheduled recordings with a tvdb Id so it fetches the correct metadata and matches shows more easily.

Would it be possible to display the channel alongside (underneath, on top?) the channel logo artwork? It is sooooooo difficult to try to decipher these tiny icons, which usually don't have any channel number info. While logos may have some value, and are pretty, the channel number is indispensable while attempting to scroll through what could be hundreds of possibilities. I understand screen real estate is severely limited, but leaving the channel number out just isn't a good UI decision. Something has to give, even if it means fewer lines of guide per screen. We need the channel number!!

I just noticed that there is a "Emby Guide Data" option to use as source for Guide. How does this compare to Schedules Direct? I deleted S.D and switched to E.G.D. as it seem that is free?? I can't see any differance, or than more tags seem to show up, like NEW and Repeat... (I've been paying for S.D each year now, had no idea Emby had a free data source option)

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

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!

@@ebr KJNKLD6 (GETTV) 25.6 is showing the guide data for KJNKLD (TELE) 25.1 25.6 shows up in the channel map under the correct call sign but guide data is for other channel lineup USA-OTA55426

I have a series recording scheduled. When clicking on the show from the guide while it is currently recording, does not play the recording. It goes straight to live. Once there, you cannot even scrub back to the beginning. It doesn't show up under "Recordings" or "Schedule". Am I doing something wrong? How do I watch a series while it is recording?