Jump to content

Search the Community

Showing results for tags 'server'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

  1. Hi guys, If anyone can help me find a solution it would be wonderful. Accessing my domestic Emby server on my TV worked well until I changed my configuration for practical reasons. My new setup is like this : - TV wired to the router A provided by my ISP. Router A is directly plugged into the wall to receive fiber network - Router B (this one I once bought for wifi expanding) wired to router A - PC server wired to router B. So my guess is that the PC server is not on the same LAN as the TV. How can I setup router B so that my TV can "see" the good IP address and port ? I don't have a very good knowledge in networks. Thanks a lot
  2. @@cayars In my main settings for Emby, under Library/Advanced, I have a metadata path set up that points to a spare SSD. I created a test 'movies' folder and placed a movie in there and checked the box for "...metadata saver to .nfo" and also checked the box to save artwork into this folder. First (maybe dumb) question is, when Emby scanned that test folder and saw the movie in there, why wasn't the artwork save into that folder? But now onto the main point of my post; with Plex, whenever I would hop to a new distro, I would follow the instructions for backing up all the necessary files and moving everything to a new Linux install. I would never back up my cache or metadata since it seemed to just take hours and hours vs. just letting my new Plex install rebuild everything from scratch. The problem with this approach however was that in my movie library, I would always have to manually fix metadata on dozens of movies due to mismatches. I think the metadata manager in Emby is 100x better than Plex. BUT, for movies like 'Wonder', Emby wants to identify it as 'Wonder Woman' and I'll need to manually intervene and fix it, which I'm totally fine with, BUT.... once I get all my movies fixed in Emby, how do I make sure those metadata corrections are backed up in case I ever have to load Emby on a new box? I was reading the guide for backing up the server and see that backing up metadata is not a feature of the 'Server Configuration Backup' plugin. Then I see this sentence in that guide: This will not backup library contents and metadata. To keep a permanent copy of metadata, we suggest enabling saving of local metadata to media folders. ....... and I think this is what I'm after, correct? Unfortunately, I don't see that exact wording anywhere. I found this thread: https://emby.media/community/index.php?/topic/73693-how-do-i-save-local-metadata-to-media-folders/ .... and it looks like 'save artwork into media folders' is the new equivalent to 'saving of local metadata to media folders', right? Which finally brings me to my last question............ in the admin dashboard, on the 'Nfo metadata' tab, I see "Save user watch data to nfo's for"..... and you can select a user. How can you tell Emby to record ALL users' watch data to an nfo file? Hope I articulated my question(s) correctly.
  3. Is there any way to renew the thumbnails for a Movie Libary?
  4. I don't know if this is the right forum, but I will try here. When I log in to the website and want to delete the old servers, I can't do it. Is there another way to clear the server list? German--------- Ich weiß nicht, ob dies das richtige Forum ist, aber ich versuche es mal hier. Wenn ich mich auf der Webseite einlogge und die alten Server löschen will, gelingt mir das nicht. Gibt es einen Weg die alten Server über die Webseite zu löschen. bkh
  5. One of the supported TV file naming conventions is: 02 Episode Name.extFor a show that airs every weekday, the episode number often grows to three digits. For example: /Some Show/Season 2/123 Some Title.m4v Emby mis-identifies the file above as Some Show, Season 1 (even though it is in the Season 2 folder), Episode 23 (even though the filename has the number 123 in it). Is it really not possible to support this format for three digit episode numbers?
  6. NANO SHELL

    Downloading subtitles

    Hi, Is there any way to download subtitles when downloading a movie from the server? If I access my library from a friends house and download a movie, the subs don't download with it.
  7. So, I've got a baffling issue. I cannot remotely connect to the MB server I have running on a Windows 10 machine. I've tried all suggestions on the connectivity page. But even with the firewall temporarily off, I cannot connect. Local connections work fine. I don't have access to router settings due to the apartment complex having all the routers locked down (whitelist probably). But I even tried using my mobile hotspot and no dice. Canyouseeme reported no response on port 8096 or 8920 using either internet service. I even tried each connection again with a VPN (PIA) turned on on the host machine, though I didn't expect any good results from that.
  8. I just got a notification that there was an update for the server on my Shield, 4.4 I believe. Downloaded it through Chrome but after the 'staging app' screen when I click Install I immediately get an 'App not Installed' message. Tried downloading it to various places, internal drive, connected drive but exactly the same behaviour. I then tried the beta as well, but again exactly the same thing. I'm not really sure what else I can try other than uninstall the current version, which is 4.3.1.0 but obviously that's a last resort as it's going to mean setting everything up again and will take a long time.. Has anyone else had a similar issue or have a fix? Maybe I'm being stupid? I should say I'm on the Hotfix path on the Shield 8.0.2 as I was losing HDMI sync constantly, which the hotfix seems to have sorted, but I'm not sure whether this would make any difference?
  9. Przemek

    Remote access to local folder

    Hi, I have Emby server installed on my VPS with Debian in ArubaCloud. On that VPS I have also openvpn installed. In my home network I have Raspberry Pi with OSMC (kodi) with media library. I have openvpn client on my Raspberry Pi and I'm connect to that vpn. My question is that: can I add media library folders from my local network (raspberry - kodi) to my Emby server? I don't have public IP in my network provider. Regards, Przemek
  10. Przemek

    Downloading Subtitles

    Hi, I've installed Emby Server on my Debian VPS. I install opensubtitles and addicted with logins and passwords. I have only "edit subtitles" option in 3 dots menu. Is there's option in Emby to download subtitles or only play with subtitles that I download and copy to folder manualy?
  11. Arkapravo

    I think i broke every thing...

    hey sorry at first place i may hear stupid.. but apparently i was so frustrated about not able to use samba(not of the emby's) on my pc after a furious uninstallation, i removed every file with a 'samba' in it. then i realized i deleted a whole lot of emby server files also.. :'''( i am completely screwed up right now... i have tried everything from uninstalling with 'apt remove' then installing, 'apt --autoremove remove' then installing, even 'apt --autoremove purge' then installing again.. nothing is working whatsoever. the server is firing up and i can browse it through http://localhost:8096 in my pc but that's it. cant access from any other device in my network. please fix anyway.. _/\_ please don't say it can't be fixed. thanks in advance
  12. h0ttz

    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
  13. The oddest thing happens. I see multiple entries of the same library multiple times and have no idea on how to get rid of that. Anyone with an idea?
  14. Hey all, Having trouble access media on newly installed Emby server on Debian linux. Emby was able to detect the media folder and everything in it but when I try and play a file it gives me this "No compatible streams are currently available. Please try again later or contact your system administrator for details" I changed the permissions on the folder to 777 to troubleshoot and it is still giving the same error. In the logs it looks like it is say permission denied when I try and access a file and I am now at a lost of what it could be. LogError.txt
  15. Hi, I have my Emby server on Shield TV, and everything works fine unless I want to transcode files bigger than ~2GB. The transcoding process causes the Shield to run out of memory (RAM) and it restarts the Emby Server. No error is displayed on logs since the restart is caused by the lack of memory (I checked that trough adb access to my Shield). This problem occurs during conversion (sync) or transcoding during playback. I have already tried the following Emby versions: 4.1.1.0 4.2.0.18 4.2.0.19 4.2.0.20 You can check the transcoding log in attachment. Tips for developers: I don't know, but the -rtbufsize keyword for ffmpeg could limit the amount of RAM used in the process. Could this trick be an easy way to overcome this issue? Thank you very much. ffmpeg-transcode-.txt
  16. killianbe

    Crash Emby Server Linux lastest

    Hi (Sorry i'm bad in english!) I've error when i've update my docker emby *** Error Report *** Version: 4.3.1.0 Command line: /app/emby/EmbyServer.dll -programdata /config -ffdetect /app/emby/ffdetect -ffmpeg /app/emby/ffmpeg -ffprobe /app/emby/ffprobe Operating system: Unix 4.9.0.11 64-Bit OS: True 64-Bit Process: True User Interactive: True Runtime: file:///app/emby/System.Private.CoreLib.dll Processor count: 4 Program data path: /config Application directory: /app/emby SQLitePCL.pretty.SQLiteException: Busy: database is locked - PRAGMA journal_mode SQLitePCL.pretty.SQLiteException: Exception of type 'SQLitePCL.pretty.SQLiteException' was thrown. at SQLitePCL.pretty.SQLiteDatabaseConnection.PrepareStatement(String sql, String& tail) at SQLitePCL.pretty.DatabaseConnection.PrepareStatement(IDatabaseConnection This, String sql) at Emby.Sqlite.BaseSqliteRepository.PrepareStatement(IDatabaseConnection connection, ReadOnlySpan`1 sql) at Emby.Sqlite.BaseSqliteRepository.CreateConnection(Boolean isReadOnly) at Emby.Server.Implementations.Data.SqliteItemRepository.Initialize(SqliteUserDataRepository userDataRepo, IUserManager userManager) at Emby.Server.Implementations.ApplicationHost.InitDatabases() at Emby.Server.Implementations.ApplicationHost.Init() at EmbyServer.HostedService.StartAsync(CancellationToken cancellationToken) Source: SQLitePCL.pretty TargetSite: SQLitePCL.pretty.IStatement PrepareStatement(System.String, System.String ByRef) Info Main: Shutdown complete Can you please help me to resolve that ? Thx error emby.txt
  17. To whom it may concern, I'm running Emby Server version 3.2.36.0 on Windows Server 2012 R2 Standard. The problem that I'm having, while minor, is still annoying. First a little background on my Folder arrangement — which is necessary to illustrate the problem. On my sever I have a folder called Media, under which I have several sub-folders — each of which is a network share — named Books, Films, Images, Music, Shows and Video, respectively. Under both the Films and the Shows sub-folders I have 27 additional sub-folders — each of which has a one-character name, starting with 'A' and continuing on through 'Z', with the 27th having a name of '#'. For films, for example, all of the titles that start with a number (e.g.—2 Days in the Valley (1996); 7th Voyage of Sinbad, The (1958); 9 (2009); 12 Angry Men (1957)) has a correspondingly named sub-folder under Media\Films\#, which contains its video file, and all of its other related metadata files. I do this for all of my movies: Titles starting with "A", are located in sub-folder A under Media\Films, titles starting with "B", are located in B, and so on, for the rest of the alphabet. No problem. Emby Server recognizes this structure, and handles the metadata for each movie in its self-titled sub-folder with absolutely no trouble. When it comes to TV Shows, on the other hand, Emby Server is not so accommodating! As mentioned earlier, my Shows sub-folder has the same arrangement as my Films sub-folder (i.e.—sub-folders named "A" through "Z", plus "#") — however, Emby Server treats each of the "A" through "Z", and the "#", sub-folders as though it were the primary repository for a TV Show! Even though there are other sub-folders within each of the "A" through "Z" sub-folders for actual TV Shows, Emby Server still place images and .nfo files directly into the "A" through "Z" sub-folders! Plus, when I go into the Emby Metadata Manager, the "A" through "Z" sub-folders are themselves identified as TV Shows! For example, sub-folder "L" is designated as the resting place for The L-Word, sub-folder "Z" for Dragon Ball Z, and so on. Deleting the files and changing the designations in the Metadata Manager does no good, as Emby Server simply changes them back and re-adds the files! I have to "lock" each of these sub-folders to prevent Emby Server from re-applying the designations — of course, this has the undesired side-effect of disabling metadata updates in all of the sub-folders that reside therein (with each sub-folder containing an actual TV Show)! Also, this problem has appeared in all of the versions of the Emby Server that I have used (I started, years ago, with, what I think was, version 1.something). I find it odd that no one else appears to be having the same problem. I doubt that I'm the only one who has this folder arrangement. In any case, thanks for an otherwise nice product.
  18. we_r_mighty

    Building a Nas help

    I recently upgraded a mini pc for my parents and I have the old one its an hp elitedesk 705 g3 mini and dont really know what to do with it was thinking of using it as the heart for a nas to run my emby, now not sure if it would be best to keep it with windows 10 and install emby to it and run it that way or to just make it a nas and just connect a large das via usb 3.0 to it and house it all in my media center under my tv as its open with good air flow, more of a project than anything else and but would like it to work well if I start it any thoughts or suggestions?
  19. pullormadamHome

    Advanced Filtering

    Hi, Can we have more options in filtering like directed by, writer, producer, cast, tags? Also I don't see any value addition in having video and audio codec filtering in client apps (thinking as a layman user). Also can I edit the filter system by my own provided I have some technical and coding skills?
  20. meatball

    3rd party plugins for Emby server

    Hi, I'm fairly new to Emby and was curious - do people or 3rd parties develop/host plugins or apps for emby or is it just what's hosted on the catalog on the server? There's no wrong answer and I'm not being rhetorical; I'm honestly asking. For example sites that host movie or tv metadata and have an open API, can someone theoretically develop a server plugin for that and say host it on Github? Was just curious, it's not a complaint. Thanks
  21. hi my server in windows can't update plugins! it shows me emby updates without any problems. I have to update DLNA plugin from 1.0.31 to 1.0.33 manually. connected with a vpn, but problem is still alive! restarted emby and PC but doesn't work logs.zip
  22. Hi I just observed since upgrading to 4.3.0.30 that hardware transcoding fails and falls back to software transcoding on hevc main 10 10 bit profile. I not totally sure, but I think this was working before. Server info: Emby server 4.3.0.30 running on ubuntu server 18.04.3 LTS, kernel 4.15.0-72-generic Intel NUC8i5BEH1 with Core i5-8259U processor (Intel Iris Plus Graphics 655), 8GB RAM Attached, hardware detection logs and ffmpeg logs. Is that normal to fallback to software encoding with this media? thank you ffmpeg-transcode-c7b4b3f8-38f2-4da6-8ff6-609047fa1cae_1.txt hardware_detection-63710875568.txt
  23. I've been using Emby for a few months now and I love it. A few days ago the power went out at my house and now my server can't be accessed on external networks. I've checked canyouseeme and port 8096 is open. I'm running Emby on openmediavault. I appreciate any help! Howe
  24. I am having trouble accessing my Emby server from outside my network. I have opened ports on router and Windows firewall. Is it my computer not being up to specs? The computer specs: AMD Vision CPU Toshiba Satellite All Realtek Drivers Please and Thank you!
  25. alberto.bracci

    emby -ffmpeg issue

    Hello everyone, first post here so if anything should be edited just tell me. Anyway, I am running emby on a Manjaro linux machine, everything has been working out of the box until now. I am watching an episode of a series I already watched tons of episodes on emby without any problem, and suddenly the media reproduction stops towards the end. If I reload the episode it will keep stopping around the same time. Other episodes seem to be fine for now. I attach the log embyserver.txt, it seems to be an error with starting ffmpeg, but I don't really see the reason as everything has been working ok until now. I have seen some other older posts with similar issue and I tried reloading the whole series, rescanning the library each time, but nothing changed. Hope you can help, thanks in advance! UPDATE I managed to watch some other episodes and also some films, the problem happens suddenly towards the end of some apparently random episodes of just this series. It might have something to do with the files themselves but I cannot understand what since they all come from the same source. Log log-ffmpeg.txt
×
×
  • Create New...