Search the Community

Hello, Lately when I add new media, it takes a long time for it to identify it and pull the metadata etc. This is because in the logs I can see the Info QuickSingleImageExtractor: ProcessRun 'quick-extract-image' running. It's running through evey movie I have even though I've had them for years and they already have such images. I've attached the server log, if anyone could tell me why this is happening. Thanks embyserver.txt

Currently running Windows 10 Pro with all updates. Emby Server is working fine. Question is : how to clear the Alerts from the Server Dashboard screen (upper Right Quad of the layout). Old alerts do not appear to drop off from the list. How is it reset to clear the list and start a new Alert list?

Hi, First, as french speaking, I apologize if unclear english. I've a syno 218 play on DSM 7.2.1-69057. Before moving to 7.2.2 and having DS Video removed, I trie to install emby server as described on Synology: https://kb.synology.com/fr-fr/DSM/tutorial/How_to_transfer_video_files_from_Video_Station_to_Emby Everything went well untill the moment I completed a value in field LAN networks as shown below with the local IP of my synology Since then, when I launch Emby, another window open with http://192.168.1.18:8096/web/index.html -> this blank shown 'Forbidden'. Searching in the forum, I discovered that other people what the same kind of issue but solution is unclear/incomplete: editing teh system.xcml and changing what ? I'm a noob in ssh but I succeed to download that file and ready to adapt it. I only need need to know what to change -> file is attached Any help is warmly welcome Tx. Mich25 system.xml

The Mult-Select in the Server web app is super-useful (I'm so grateful to those that introduced me to it!). But given that the Server web app has some excellent filtering functions (eg, in my case I make use of filtering by Tags) it would be very handy to have a "Select All" functionality, so that I can filter down to the results I'm looking for and then easily add them to a Collection (or, when eventually we have Bulk Editing abilities, open a Bulk Edit view on all the Selected items). Thanks! PS - If this is something you might like to see implemented, be sure to "Like" this top/first post (as well as any subsequent posts in this thread that highlight particular aspects of what you are interested in) -- "Liking" the top/first post helps the Devs to know how much interest there is in a given Feature Request.

我自己有很多需要登陆的独立系统，多个账户的密码管理是非常麻烦的一件事 将Emby Server作为OAuth提供商，只需要授权即可访问第三方应用，这会非常方便

Okay I am new to this and was told to purchase the emby premiere at $5 per month to access VOD on my 2 firesticks at home. I can not access the emby dashboard, i have the emby application on my iphone. Where do I locate the server? Is this something I need to do on my desktop HP computer or can I do it from my iphone. Where do I enter in the registry key? HELP!! Not that tech savvy.

Hi Emby Community, I am currently running an Emby server on a system with the following specifications: Processor: Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz RAM: 128 GB Machine Type: Rack Mount Chassis Operating System: Ubuntu 20.04.6 LTS Storage: HP P440, HP P840ar, HP LOGICAL VOLUME (multiple disks) Display Resolution: 1024x768 pixels My Emby server primarily handles transcoding for both LAN and some remote network devices. However, I've been facing significant performance issues during transcoding, where CPU usage spikes to 90% or higher, making the server laggy. On average, there are 20-30 active devices, but this number can sometimes exceed 100. Given this situation, I'm considering adding a dedicated GPU to improve transcoding efficiency. I've heard that Nvidia GPUs are highly recommended for this purpose due to their NVENC support. Here are my specific questions: Will adding a dedicated GPU help with my transcoding performance? Which Nvidia GPU model would you recommend for handling a high number of simultaneous streams, including some 4K streams? Are there any particular configuration steps or considerations I should be aware of when setting up the GPU for Emby transcoding? I've seen recommendations for various Nvidia GPUs such as the Quadro P2000, GeForce GTX 1660 Super, and RTX series. My goal is to find a balance between performance and cost, ensuring that the server can handle multiple 1080p and 4K streams efficiently. I appreciate any insights, recommendations, or experiences you can share regarding the best GPU choice and setup for this scenario. Thank you!

Hi, I can't enable user playlists under Users > User > Access > Playlists The option appears greyed out with all users.

Hello I'm facing an issue with connecting to my Emby server, and I could use some help in troubleshooting. Here's the problem I'm facing: When attempting to access my Emby server, I'm facing an error message stating "Unable to connect to server" or a similar message. This happens continuously across different devices and browsers. So far, I've tried restarting both my Emby server and the client devices, ensuring that the server is running and accessible on the network. I've also checked firewall settings and checked that port forwarding is correctly configured on my router. https://emby.media/support/articles/Installation.htmlinfo Despite all this , I'm still unable to establish a connection to the Emby server. Any suggestions or troubleshooting steps would be greatly appreciated. Thank you for your help! Thank you stevediaz

Hello, I have a few ideas for enhancements to the Live TV system. 1 Support for more headers in m3u files... eg.live (1/0) - disable/enable live stream flag, so play and seek controls can be enabled or disabled tvg-group - to set network/studio group of radio and tv streams for easier grouping tvg-url - so xmltv guide data can be bound directly to a channel or m3u file, bypassing the built-in gui method #bg-color and #bg-size - to alter the background color and size of the channel tile metadata display - eg. jQuery Stream, embedded m3u/8 comment, Icy-Metadata, Icecast CORS/ACAO headers. I have a ttached an m3u file which I tried to directly add as m3u tuner, but the server would not load it properly, possibly because it is one stream with multiple chunks ( also has metadata)... it can be called from another m3u tuner though. https://wz3web.scahw.com.au/live/3sea_32.stream/playlist.m3u8?listeningSessionID=5bdda753c87a2e78_303254_9A8QlPM3__00000001t29&downloadSessionID=0 #EXTM3U #EXT-X-VERSION:3 #EXT-X-TARGETDURATION:6 #EXT-X-MEDIA-SEQUENCE:40 #EXTINF:5.015,Lukas Graham - Love Someone fRjAPQ6Q9DEp-308311271-5015.aac #EXTINF:4.969,Lukas Graham - Love Someone lR52ZCSwo0Yp-308311272-4969.aac #EXTINF:5.015,Lukas Graham - Love Someone j6TateebXsLp-308311273-5015.aac tv (0/1) - enable/disable tv (must specify either radio or audio-only options if set to 0) radio (true) - enable radio-specific stream with rich metadata (only use if tv=0, can not be used with audio-only) audio-only (true) - enable audio only stream without rich metadata (only use if tv=0, can not be used with radio) 2 Add support for Icecast streams/tuners

Hey Emby team, After about 3 months of trying out Emby, I'm a bit disappointed. As a web developer, I have a basic technical understanding and know what work it takes to produce good software. For a user, however, it is annoying when this software only works poorly. I was initially impressed by how well you can manage your music archive with Emby, it's a really nice solution. But listening to music with Emby is very disappointing. I'd better describe this briefly: My music archive consists mainly of self-produced MP3 files from my CD collection, they are usually encoded at 320 kBit. For newer purchases, I tend to look for the availability of FLAC or other lossless formats. I use 2 ChromeCast speakers, one of which is about 6 years old and 3 meters (about 10 feet) away from the wireless router. I bought the other one a few months ago, it's in another room and there are two walls in between. I only use the 5-GHz band because of too much neighbour traffic on 2,4 GHz. Initially, the Emby server ran on my MacBook with Big Sur, where I streamed to the two ChromeCast speakers using the Google Chrome browser. The long pauses (sometimes 5 seconds or longer) between the tracks are very annoying. In addition, the connection to the ChromCast speakers repeatedly breaks off for seconds. I have noticed that FLAC files are played back more stably than MP3 files. Then I set up an old iPad as a media player with the Emby app to stream the music from the MacBook to the ChromeCast speakers. Here, too, I have the same problems as when streaming with the MacBook: very long pauses and an unstable connection to ChromeCast. Also the play queue is disappearing, while still playing music. Wouldn't it be better to have a possibility to show the play queue, no matter if there are tracks listed or empty? In the meantime, I have moved Emby to my home server with Ubuntu 22.04 to try my luck there - unfortunately, no luck. Here, too, it is hardly possible to listen to music with Emby for any length of time without interference. Both the MacBook and the Linux server are connected to the router via cable (1 GBit). So it cannot be due to insufficient bandwidth. I know from MP3 that it is not possible per se to play the next track without interruption due to the format design. Some players solve the problem with a crossfade. Shouldn't this also be possible with a player in the browser? I have noticed that FLAC files seem to be streamed much more stable than MP3. I have started to convert some of the MP3 albums with freac to gapless/lossless FLAC files with CUE-Sheet, but this is too much work for my complete archive. And above all, the data then takes up 3-4 times the space. In the meantime, I listen to my music archive on Ubuntu with Elisa and stream the output to the speaker group with Mkchromecast. This all works smoothly and with MP3 I only have minimal interruptions between tracks (< 250 ms). Streaming to ChromeCast from the Apple system is apparently a pain in the a**e, no matter how you try it. Nevertheless, I will keep an eye on Emby. Thank you very much for your work, I really appreciate it. Kind regards, Achim

It would be helpful if Media Stubs that have online metadata would automatically download (or there be an option to make set it as automatic) additional metadata that normally would be derived from the video file, particularly Duration / Length / Runtime of the video (and then of course actually display that metadata in Emby Theater). I realize that the online metadata may not always exactly match the true duration (eg, a special edition DVD with extra scenes not in the official theatrical length), but anything would be more useful than nothing here. If I'm trying to decide on something to watch it is unfortunate to have to go dig up the physical DVD/Blu-ray (or switch to the online service provider, if is something I have on Vudu, iTunes, etc.) in order to find out how long it is (particularly since movies can vary in length from ~1.5 hours to 2.5+ hours). Thanks!

So after the recent privacy controversy with Plex I've started looking elsewhere for media servers with remote access. It seems Emby is a decent alternative however I'm having issues using it with a VPN. I've had these issues with Plex so I'll explain further. The problem Plex had with the VPN is that it had the wrong IP address for me (it was displaying the VPN IP, as it should do) and because of that, when I was attempting to connect remotely via the VPN IP it could not find the Plex server. The way to get around this was to set up a static port with my VPN provider, which they did, then enter this port into the "Manually specify public port" setting on Plex. After this, the server was remotely accessible, as the VPN provider would listen for incoming connections on the specified port, forward it to my server and all was good. I'm not having any success running this with Emby. I can see that there are settings where I can manually set the public and local ports to access the server (it is listing my VPN IP rather than my real IP, just as Plex did) but I may not be entering my static VPN IP in the right box? I've tried remote access without the VPN running and it worked (though I did have to set up port forwarding in my router). I've tried entering my static VPN IP in the "Public HTTP port number" box in Advanced Settings but this hasn't worked. To be clear, as I seem to be different to most others, I am looking to run Emby behind the VPN and not bypass it. Can anybody assist? There must be some way to do this as it works fine with Plex.

I have a Emby server on Windows with port 8098 and a Nginx server before it with port 2345, they are on same machine then I install Emby Android app on my mobile phone and configure server address: http://192.168.51.39:2345, and everything is ok But after I restart Emby Android app, the server address has been changed to http://192.168.51.39:8098 automatically !! I want to know why the app change the server address？ It seems the app use the Nginx upstream address as the server address, am I make some mistakes in configuration ？ All the devices are in the same LAN Arch: Emby Android -> Nginx -> Emby Server Emby server version: 4.8.0.54 Emby Andrord version: 3.3.39 ========== Nginx Conf Begin ============= server{ gzip on; listen 2345; listen [::]:2345; server_name default; ## The default `client_max_body_size` is 1M, this might not be enough for some posters, etc. client_max_body_size 20M; add_header 'Referrer-Policy' 'no-referrer'; set $emby http://192.168.51.39:8098; #emby/jellyfin address # Proxy sockets traffic for jellyfin-mpv-shim and webClient location ~ /(socket|embywebsocket) { # Proxy emby/jellyfin Websockets traffic proxy_pass $emby; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Protocol $scheme; proxy_set_header X-Forwarded-Host $http_host; } location ~* /web/index.html { proxy_buffering off; js_body_filter addExternalUrl.incloudUrl buffer_type=string; proxy_pass $emby; proxy_pass_request_body off; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Protocol $scheme; proxy_set_header X-Forwarded-Host $http_host; proxy_set_header Accept-Encoding "identity"; proxy_set_header X-Original-URI $request_uri; js_header_filter addExternalUrl.HeaderFilter; } location @backend { proxy_pass $emby; } ... } ========== Nginx Conf Begin =============

Tengo un NAS Synology DS1815+ con DSM 7. Tenía instalado Emby Server 4.7.11.0 y lo he desinstalado para volver a instalarlo en otro volumen del NAS, tras la nueva instalación el servidor Emby no permite ser ejecutado, la ejecución se detiene al momento sin llegar a poder abrir la web del servidor. He podido recuperar el log desde SSH, lo adjunto para ver si pueden ayudarme a saber porque no puedo volver a ejecutar mi Emby Server: 2023-09-14 16:57:13.469 Info Main: Application path: /volume1/@appstore/EmbyServer/system/EmbyServer.dll 2023-09-14 16:57:14.073 Info Main: Emby Command line: /volume1/@appstore/EmbyServer/system/EmbyServer.dll -programdata /var/packages/EmbyServer/var -ffdetect /var/packages/EmbyServer/target/bin/ffdetect -ffmpeg /var/packages/EmbyServer/target/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/bin/ffprobe -nolocalportconfig -ignore_vaapi_enabled_flag -pidfile /var/packages/EmbyServer/var/EmbyServer.pid -defaultdirectory /volume1/Public -updatepackage emby-server-synology7_{version}_x86_64.spk Operating system: Linux version 3.10.108 (root@build3) (gcc version 8.5.0 (GCC) ) #42962 SMP Mon May 29 14:36:28 CST 2023 Framework: .NET 6.0.8 OS/Process: x64/x64 Runtime: volume1/@appstore/EmbyServer/system/System.Private.CoreLib.dll Processor count: 4 Data path: /var/packages/EmbyServer/var Application path: /volume1/@appstore/EmbyServer/system 2023-09-14 16:57:14.073 Info Main: Logs path: /var/packages/EmbyServer/var/logs 2023-09-14 16:57:14.073 Info Main: Cache path: /var/packages/EmbyServer/var/cache 2023-09-14 16:57:14.074 Info Main: Internal metadata path: /var/packages/EmbyServer/var/metadata 2023-09-14 16:57:14.074 Info Main: Transcoding temporary files path: /var/packages/EmbyServer/var/transcoding-temp 2023-09-14 16:57:14.075 Info Main: PID file: /var/packages/EmbyServer/var/EmbyServer.pid 2023-09-14 16:57:14.214 Info App: Application version: 4.7.10.0 2023-09-14 16:57:14.222 Info App: Loading assemblies 2023-09-14 16:57:14.281 Info App: File /var/packages/EmbyServer/var/plugins/Emby.XmlTV.dll has version 1.0.9.0 2023-09-14 16:57:14.281 Info App: File /volume1/@appstore/EmbyServer/system/plugins/Emby.XmlTV.dll has version 1.0.9.0 2023-09-14 16:57:14.282 Info App: File /var/packages/EmbyServer/var/plugins/Fanart.dll has version 1.0.13.0 2023-09-14 16:57:14.282 Info App: File /volume1/@appstore/EmbyServer/system/plugins/Fanart.dll has version 1.0.13.0 2023-09-14 16:57:14.282 Info App: File /var/packages/EmbyServer/var/plugins/MovieDb.dll has version 1.6.2.0 2023-09-14 16:57:14.282 Info App: File /volume1/@appstore/EmbyServer/system/plugins/MovieDb.dll has version 1.6.2.0 2023-09-14 16:57:14.283 Info App: File /var/packages/EmbyServer/var/plugins/OpenSubtitles.dll has version 1.0.31.0 2023-09-14 16:57:14.283 Info App: File /volume1/@appstore/EmbyServer/system/plugins/OpenSubtitles.dll has version 1.0.31.0 2023-09-14 16:57:14.283 Info App: File /var/packages/EmbyServer/var/plugins/BlurayMounter.dll has version 1.0.0.0 2023-09-14 16:57:14.283 Info App: File /volume1/@appstore/EmbyServer/system/plugins/BlurayMounter.dll has version 1.0.0.0 2023-09-14 16:57:14.284 Info App: File /var/packages/EmbyServer/var/plugins/StudioImages.dll has version 1.0.3.0 2023-09-14 16:57:14.284 Info App: File /volume1/@appstore/EmbyServer/system/plugins/StudioImages.dll has version 1.0.3.0 2023-09-14 16:57:14.284 Info App: File /var/packages/EmbyServer/var/plugins/Emby.Dlna.dll has version 1.0.91.0 2023-09-14 16:57:14.285 Info App: File /volume1/@appstore/EmbyServer/system/plugins/Emby.Dlna.dll has version 1.0.91.0 2023-09-14 16:57:14.285 Info App: File /var/packages/EmbyServer/var/plugins/Emby.Server.CinemaMode.dll has version 1.0.40.0 2023-09-14 16:57:14.285 Info App: File /volume1/@appstore/EmbyServer/system/plugins/Emby.Server.CinemaMode.dll has version 1.0.40.0 2023-09-14 16:57:14.285 Info App: File /var/packages/EmbyServer/var/plugins/MusicBrainz.dll has version 1.0.22.0 2023-09-14 16:57:14.285 Info App: File /volume1/@appstore/EmbyServer/system/plugins/MusicBrainz.dll has version 1.0.22.0 2023-09-14 16:57:14.286 Info App: File /var/packages/EmbyServer/var/plugins/Tvdb.dll has version 1.3.3.0 2023-09-14 16:57:14.286 Info App: File /volume1/@appstore/EmbyServer/system/plugins/Tvdb.dll has version 1.3.3.0 2023-09-14 16:57:14.286 Info App: File /var/packages/EmbyServer/var/plugins/EmbyGuideData.dll has version 1.0.9.0 2023-09-14 16:57:14.286 Info App: File /volume1/@appstore/EmbyServer/system/plugins/EmbyGuideData.dll has version 1.0.9.0 2023-09-14 16:57:14.286 Info App: File /var/packages/EmbyServer/var/plugins/AudioDb.dll has version 1.0.16.0 2023-09-14 16:57:14.287 Info App: File /volume1/@appstore/EmbyServer/system/plugins/AudioDb.dll has version 1.0.16.0 2023-09-14 16:57:14.287 Info App: File /var/packages/EmbyServer/var/plugins/NfoMetadata.dll has version 1.0.70.0 2023-09-14 16:57:14.287 Info App: File /volume1/@appstore/EmbyServer/system/plugins/NfoMetadata.dll has version 1.0.70.0 2023-09-14 16:57:14.287 Info App: File /var/packages/EmbyServer/var/plugins/OMDb.dll has version 1.0.18.0 2023-09-14 16:57:14.287 Info App: File /volume1/@appstore/EmbyServer/system/plugins/OMDb.dll has version 1.0.18.0 2023-09-14 16:57:14.287 Info App: File /var/packages/EmbyServer/var/plugins/DvdMounter.dll has version 1.0.0.0 2023-09-14 16:57:14.288 Info App: File /volume1/@appstore/EmbyServer/system/plugins/DvdMounter.dll has version 1.0.0.0 2023-09-14 16:57:14.311 Info App: Loading Emby.XmlTV, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null from /var/packages/EmbyServer/var/plugins/Emby.XmlTV.dll 2023-09-14 16:57:14.311 Info App: Loading Fanart, Version=1.0.13.0, Culture=neutral, PublicKeyToken=null from /var/packages/EmbyServer/var/plugins/Fanart.dll 2023-09-14 16:57:14.311 Info App: Loading MovieDb, Version=1.6.2.0, Culture=neutral, PublicKeyToken=null from /var/packages/EmbyServer/var/plugins/MovieDb.dll 2023-09-14 16:57:14.311 Info App: Loading OpenSubtitles, Version=1.0.31.0, Culture=neutral, PublicKeyToken=null from /var/packages/EmbyServer/var/plugins/OpenSubtitles.dll 2023-09-14 16:57:14.312 Info App: Loading BlurayMounter, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from /var/packages/EmbyServer/var/plugins/BlurayMounter.dll 2023-09-14 16:57:14.312 Info App: Loading StudioImages, Version=1.0.3.0, Culture=neutral, PublicKeyToken=null from /var/packages/EmbyServer/var/plugins/StudioImages.dll 2023-09-14 16:57:14.312 Info App: Loading Emby.Dlna, Version=1.0.91.0, Culture=neutral, PublicKeyToken=null from /var/packages/EmbyServer/var/plugins/Emby.Dlna.dll 2023-09-14 16:57:14.312 Info App: Loading Emby.Server.CinemaMode, Version=1.0.40.0, Culture=neutral, PublicKeyToken=null from /var/packages/EmbyServer/var/plugins/Emby.Server.CinemaMode.dll 2023-09-14 16:57:14.312 Info App: Loading MusicBrainz, Version=1.0.22.0, Culture=neutral, PublicKeyToken=null from /var/packages/EmbyServer/var/plugins/MusicBrainz.dll 2023-09-14 16:57:14.313 Info App: Loading Tvdb, Version=1.3.3.0, Culture=neutral, PublicKeyToken=null from /var/packages/EmbyServer/var/plugins/Tvdb.dll 2023-09-14 16:57:14.313 Info App: Loading EmbyGuideData, Version=1.0.9.0, Culture=neutral, PublicKeyToken=null from /var/packages/EmbyServer/var/plugins/EmbyGuideData.dll 2023-09-14 16:57:14.313 Info App: Loading AudioDb, Version=1.0.16.0, Culture=neutral, PublicKeyToken=null from /var/packages/EmbyServer/var/plugins/AudioDb.dll 2023-09-14 16:57:14.313 Info App: Loading NfoMetadata, Version=1.0.70.0, Culture=neutral, PublicKeyToken=null from /var/packages/EmbyServer/var/plugins/NfoMetadata.dll 2023-09-14 16:57:14.313 Info App: Loading OMDb, Version=1.0.18.0, Culture=neutral, PublicKeyToken=null from /var/packages/EmbyServer/var/plugins/OMDb.dll 2023-09-14 16:57:14.313 Info App: Loading DvdMounter, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from /var/packages/EmbyServer/var/plugins/DvdMounter.dll 2023-09-14 16:57:14.313 Info App: Loading Emby.Api, Version=4.7.10.0, Culture=neutral, PublicKeyToken=null 2023-09-14 16:57:14.313 Info App: Loading Emby.Web, Version=4.7.10.0, Culture=neutral, PublicKeyToken=null 2023-09-14 16:57:14.313 Info App: Loading MediaBrowser.Model, Version=4.7.10.0, Culture=neutral, PublicKeyToken=null 2023-09-14 16:57:14.313 Info App: Loading MediaBrowser.Common, Version=4.7.10.0, Culture=neutral, PublicKeyToken=null 2023-09-14 16:57:14.313 Info App: Loading MediaBrowser.Controller, Version=4.7.10.0, Culture=neutral, PublicKeyToken=null 2023-09-14 16:57:14.313 Info App: Loading Emby.Providers, Version=4.7.10.0, Culture=neutral, PublicKeyToken=null 2023-09-14 16:57:14.313 Info App: Loading Emby.Photos, Version=4.7.10.0, Culture=neutral, PublicKeyToken=null 2023-09-14 16:57:14.313 Info App: Loading Emby.Server.Implementations, Version=4.7.10.0, Culture=neutral, PublicKeyToken=null 2023-09-14 16:57:14.313 Info App: Loading Emby.LiveTV, Version=4.7.10.0, Culture=neutral, PublicKeyToken=null 2023-09-14 16:57:14.313 Info App: Loading Emby.ActivityLog, Version=4.7.10.0, Culture=neutral, PublicKeyToken=null 2023-09-14 16:57:14.313 Info App: Loading Emby.Server.MediaEncoding, Version=4.7.10.0, Culture=neutral, PublicKeyToken=null 2023-09-14 16:57:14.313 Info App: Loading Emby.LocalMetadata, Version=4.7.10.0, Culture=neutral, PublicKeyToken=null 2023-09-14 16:57:14.313 Info App: Loading Emby.Notifications, Version=4.7.10.0, Culture=neutral, PublicKeyToken=null 2023-09-14 16:57:14.313 Info App: Loading Emby.Codecs.Dxva, Version=4.7.10.0, Culture=neutral, PublicKeyToken=null 2023-09-14 16:57:14.313 Info App: Loading Emby.Codecs, Version=4.7.10.0, Culture=neutral, PublicKeyToken=null 2023-09-14 16:57:14.313 Info App: Loading Emby.Server.Connect, Version=4.7.10.0, Culture=neutral, PublicKeyToken=null 2023-09-14 16:57:14.313 Info App: Loading Emby.Server.Sync, Version=4.7.10.0, Culture=neutral, PublicKeyToken=null 2023-09-14 16:57:14.313 Info App: Loading EmbyServer, Version=4.7.10.0, Culture=neutral, PublicKeyToken=null 2023-09-14 16:57:14.835 Info SqliteUserRepository: Sqlite version: 3.39.2 2023-09-14 16:57:14.837 Info SqliteUserRepository: Sqlite compiler options: ATOMIC_INTRINSICS=1,COMPILER=gcc-10.3.0,DEFAULT_AUTOVACUUM,DEFAULT_CACHE_SIZE=-2000,DEFAULT_FILE_FORMAT=4,DEFAULT_JOURNAL_SIZE_LIMIT=-1,DEFAULT_MMAP_SIZE=0,DEFAULT_PAGE_SIZE=4096,DEFAULT_PCACHE_INITSZ=20,DEFAULT_RECURSIVE_TRIGGERS,DEFAULT_SECTOR_SIZE=4096,DEFAULT_SYNCHRONOUS=2,DEFAULT_WAL_AUTOCHECKPOINT=1000,DEFAULT_WAL_SYNCHRONOUS=2,DEFAULT_WORKER_THREADS=0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOKENIZER,ENABLE_FTS4,ENABLE_FTS5,ENABLE_GEOPOLY,ENABLE_MATH_FUNCTIONS,ENABLE_PREUPDATE_HOOK,ENABLE_RTREE,ENABLE_SESSION,ENABLE_UNLOCK_NOTIFY,ENABLE_UPDATE_DELETE_LIMIT,LIKE_DOESNT_MATCH_BLOBS,MALLOC_SOFT_LIMIT=1024,MAX_ATTACHED=10,MAX_COLUMN=2000,MAX_COMPOUND_SELECT=500,MAX_DEFAULT_PAGE_SIZE=8192,MAX_EXPR_DEPTH=1000,MAX_FUNCTION_ARG=127,MAX_LENGTH=1000000000,MAX_LIKE_PATTERN_LENGTH=50000,MAX_MMAP_SIZE=0x7fff0000,MAX_PAGE_COUNT=1073741823,MAX_PAGE_SIZE=65536,MAX_SCHEMA_RETRY=25,MAX_SQL_LENGTH=1000000000,MAX_TRIGGER_DEPTH=1000,MAX_VARIABLE_NUMBER=250000,MAX_VDBE_OP=250000000,MAX_WORKER_THREADS=8,MUTEX_PTHREADS,OMIT_LOOKASIDE,SECURE_DELETE,SYSTEM_MALLOC,TEMP_STORE=1,THREADSAFE=1 2023-09-14 16:57:14.838 Info SqliteUserRepository: Opening sqlite connection to /var/packages/EmbyServer/var/data/users.db 2023-09-14 16:57:14.882 Info SqliteUserRepository: Default journal_mode for /var/packages/EmbyServer/var/data/users.db is wal 2023-09-14 16:57:15.160 Info ActivityRepository: Opening sqlite connection to /var/packages/EmbyServer/var/data/activitylog.db 2023-09-14 16:57:15.162 Info ActivityRepository: Default journal_mode for /var/packages/EmbyServer/var/data/activitylog.db is wal 2023-09-14 16:57:15.177 Info SqliteDisplayPreferencesRepository: Opening sqlite connection to /var/packages/EmbyServer/var/data/displaypreferences.db 2023-09-14 16:57:15.178 Info SqliteDisplayPreferencesRepository: Default journal_mode for /var/packages/EmbyServer/var/data/displaypreferences.db is wal 2023-09-14 16:57:15.210 Info App: Adding HttpListener prefix http://+:8096/ 2023-09-14 16:57:15.246 Info NetworkManager: Detecting local network addresses 2023-09-14 16:57:15.246 Info NetworkManager: networkInterface: Ethernet eth0, Speed: 1000000000, Description: eth0 2023-09-14 16:57:15.247 Info NetworkManager: GatewayAddresses: 2023-09-14 16:57:15.248 Info NetworkManager: UnicastAddresses: 2023-09-14 16:57:15.248 Info NetworkManager: networkInterface: Ethernet eth1, Speed: 1000000000, Description: eth1 2023-09-14 16:57:15.248 Info NetworkManager: GatewayAddresses: 2023-09-14 16:57:15.248 Info NetworkManager: UnicastAddresses: 2023-09-14 16:57:15.248 Info NetworkManager: networkInterface: Ethernet bond0, Speed: 2000000000, Description: bond0 2023-09-14 16:57:15.248 Info NetworkManager: GatewayAddresses: 192.168.1.1 2023-09-14 16:57:15.249 Info NetworkManager: UnicastAddresses: 192.168.1.8,fe80::211:32ff:fe40:abd7%7 2023-09-14 16:57:15.250 Info NetworkManager: networkInterface: Loopback lo, Speed: -1, Description: lo 2023-09-14 16:57:15.250 Info NetworkManager: GatewayAddresses: 2023-09-14 16:57:15.250 Info NetworkManager: UnicastAddresses: 127.0.0.1,::1 2023-09-14 16:57:15.253 Info NetworkManager: Detected local ip addresses: 192.168.1.8, fe80::211:32ff:fe40:abd7%7, 127.0.0.1, ::1 2023-09-14 16:57:15.589 Debug XmlSerializer: Deserializing file /var/packages/EmbyServer/var/config/users/6918fa36d13c448eb10dfadab579e35e/policy.xml 2023-09-14 16:57:15.726 Info AuthenticationRepository: Opening sqlite connection to /var/packages/EmbyServer/var/data/authentication.db 2023-09-14 16:57:15.727 Info AuthenticationRepository: Default journal_mode for /var/packages/EmbyServer/var/data/authentication.db is wal 2023-09-14 16:57:15.735 Info SqliteItemRepository: Opening sqlite connection to /var/packages/EmbyServer/var/data/library.db 2023-09-14 16:57:16.324 Info SqliteItemRepository: Default journal_mode for /var/packages/EmbyServer/var/data/library.db is wal 2023-09-14 16:57:16.326 Info SqliteItemRepository: cache_size is -122880 2023-09-14 16:57:16.326 Info SqliteItemRepository: page_size is 4096 2023-09-14 16:57:21.945 Error Main: Error in appHost.Init *** Error Report *** Version: 4.7.10.0 Command line: /volume1/@appstore/EmbyServer/system/EmbyServer.dll -programdata /var/packages/EmbyServer/var -ffdetect /var/packages/EmbyServer/target/bin/ffdetect -ffmpeg /var/packages/EmbyServer/target/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/bin/ffprobe -nolocalportconfig -ignore_vaapi_enabled_flag -pidfile /var/packages/EmbyServer/var/EmbyServer.pid -defaultdirectory /volume1/Public -updatepackage emby-server-synology7_{version}_x86_64.spk Operating system: Linux version 3.10.108 (root@build3) (gcc version 8.5.0 (GCC) ) #42962 SMP Mon May 29 14:36:28 CST 2023 Framework: .NET 6.0.8 OS/Process: x64/x64 Runtime: volume1/@appstore/EmbyServer/system/System.Private.CoreLib.dll Processor count: 4 Data path: /var/packages/EmbyServer/var Application path: /volume1/@appstore/EmbyServer/system SQLitePCL.pretty.SQLiteException: Error: no such column: IsFolder - create index if not exists idx_MediaItems36 on MediaItems(SeriesPresentationUniqueKey,Type,IsFolder,IsVirtualItem) where SeriesPresentationUniqueKey not null;create index if not exists idx_MediaItems10 on MediaItems(Type,TopParentId,Id);create index if not exists idx_MediaItems11 on MediaItems(Type,TopParentId,PresentationUniqueKey);create index if not exists idx_MediaItems46 on MediaItems(TopParentId,IsVirtualItem) where TopParentId not null;create index if not exists idx_MediaItems47 on MediaItems(TopParentId,Type,IsVirtualItem,PresentationUniqueKey,DateCreated) where TopParentId not null;create index if not exists idx_MediaItems48 on MediaItems(TopParentId,IsFolder,IsVirtualItem,PresentationUniqueKey,DateCreated) where TopParentId not null;create index if not exists idx_MediaItems49 on MediaItems(TopParentId,MediaType,IsVirtualItem,PresentationUniqueKey) where TopParentId not null;create index if not exists idx_MediaItems50 on MediaItems(Type, TopParentId, AlbumId) where TopParentId not null;create index if not exists idx_MediaItems51 on MediaItems(Type,IsSeries) where Type=27;create index if not exists idxItemLinks_1 on ItemLinks(LinkedId, Type, ItemId) SQLitePCL.pretty.SQLiteException: Exception of type 'SQLitePCL.pretty.SQLiteException' was thrown. at SQLitePCL.pretty.SQLiteDatabaseConnection.PrepareStatement(String sql, String& tail) at SQLitePCL.pretty.DatabaseConnection.PrepareAllEnumerator(IDatabaseConnection This, String sql)+MoveNext() at SQLitePCL.pretty.DatabaseConnection.ExecuteAll(IDatabaseConnection This, String sql) 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)

For the past week or so, manually triggered scans of my media library fail to complete. I do not have a scheduled task for full scans, only folder watching. Logs attached. There are no other discernable errors or limited/unavailable functionality, but until the server is restarted, folder watching is not reactivated. The scans consistently get to the completion percentage indicated in the clip below. I am running the current stable (4.7.11.0) build of Emby Server as Windows service via NSSM on a headless Windows Server 2016 server powered by an Intel Core i9-9900K CPU with16Gb of DDR4 memory. Prior to posting, both the service and server have been restarted several times as I attempted to troubleshoot. I have also attempted the library scan after terminating the service and running Emby in a normal desktop session with the same results. embyserver.txt

We have a couple of Samsung TVs in the house, which are not very "smart" out of the box. To solve that problem we have installed nVidia Shield devices for each of these TVs. This solved the problems with the built in functionality. Streaming apps are working perfectly now ... with the exception of Emby. The problem is that the Emby client for Android TV cannot manage a server that is in the Sleep State. I'm respectfully requesting for a feature that can manage the sleep/wake state of the Emby Server (in my case the host is Windows 10). This can be done by: - Sending a WOL magic packet to the server when a client requests a video to be streamed (and the server is in the sleep state). - Keeping the server awake during streaming. Really love the Emby server, as it provides many benefits over its competitors, like Plex, but the absence of this feature really limits its usability in the Android TV space.

i have been having a problem with the remote connection for emby for about two weeks now. with no warning the server will no longer be up to log into. as in the server at my house is up and running and i can watch stuff when im at my house. but many of the people that use my server have been telling my that the server is offline and not working. so i try to log in and the app tells me the server is offline. well I'm at work and i have TeamViewer installed on the server. so i log in and emby says that it is running fine. i have found that after i reset the emby server that the problem goes away for about a hour or 2 then it drops once more. i have no idea what is going on as it was working fine a few weeks ago with no problems. i have added all the emby server logs from today, embyserver.txt embyserver-63787898535.txt embyserver-63787862424.txt embyserver-63787863423.txt embyserver-63787870271.txt embyserver-63787876017.txt embyserver-63787883820.txt

I'm looking for a way to select songs from my Emby Server using voice commands on a Google Home device such as the Google Home Mini or the Google Nest. I want to play the music directly on the Google Home device that issues the voice command, rather than routing it to my phone or a DLNA-compatible "player." However, there doesn't seem to be an option to simply play the selected music directly on the Google Home device's speaker. Am I overlooking something? I have successfully installed and configured the Emby for Android app and linked it to my Emby Server using Emby Connect. I can start a session by saying "Hey Google, talk to Emby Home." I can then say "Play <a song title> by <artist name>. Google finds the song on my Emby Server and asks which player I want to use. (Right now there are only two choices—my android phone or a DLNA device that I never use.) To test the feature, I selected my phone and it does play the song as expected, but not on the speaker I would like to use. (If the Emby team wants to pursue improving Emby for Google Home, you might take a look at a product called MyMedia, which is an Amazon Echo "skill." Their approach is elegant and it works flawlessly. The software "watches" and indexes local music folders on a PC to create a lightweight music server that is compatible with Alexa. I wish something similar existed for use with Google Home products.)

Assuming that there is memory to spare, placing Emby's data and/or cache to RAM offers significant advantages. Even though opting for the partial route is an improvement by itself, the latter can make Emby even more responsive compared to its stock configuration. Benefits include, among others: - reduced drive read/writes; - heightened responsive feel; - many operations within Emby, such as quick search are nearly instantaneous. To do so we can make use of a tmpfs. Because data placed therein cannot survive a shutdown, a script responsible for syncing back to drive prior to system shutdown is necessary if persistence is desired. On the other hand, only relocating the cache is a quick, less inclusive solution that will slightly speed up user experience with Emby. In this post is provided an example of script to move and sync the "data" folder (where is stored the emby db) to RAM. Be sure that rsync is installed and save the "executable" script to /opt/emby-server/bin/emby-data_sync.sh, for example: #!/bin/sh # The script will first move emby's data to a new static location, # make a sub-directory in /dev/shm, softlink to it and later populate it with the contents of data. # The second time the script runs, it will then preserve the RAM profile by copying (sync) it back to disk. PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin static=data-static link=data volatile=/dev/shm/emby-data IFS= set -efu cd /var/lib/emby if [ ! -r $volatile ]; then mkdir -m0700 $volatile fi if [ "$(readlink $link)" != "$volatile" ]; then echo "--> Emby: Init RAM Disk" mv $link $static ln -s $volatile $link fi if [ -e $link/.unpacked ]; then echo "--> Emby: Sync Disk" rsync -av --delete --exclude .unpacked ./$link/ ./$static/ else echo "--> Emby: Sync RAM" rsync -av ./$static/ ./$link/ touch $link/.unpacked fi It is best to add a cron job to guarantee the sync between RAM and disk, for example the following entry will run the sync process every 30min. */30 * * * * /opt/emby-server/bin/emby-data_sync.sh Then it is necessary to change the service: /lib/systemd/system/emby-server.service to guarantee the initial and final sync, as follow: [Unit] Description=Emby Server is a personal media server with apps on just about every device. After=network.target [Service] TimeoutSec=5min EnvironmentFile=/etc/emby-server.conf WorkingDirectory=/opt/emby-server ExecStartPre=/opt/emby-server/bin/emby-data_sync.sh ExecStart=/opt/emby-server/bin/emby-server ExecStopPost=/opt/emby-server/bin/emby-data_sync.sh RestartForceExitStatus=3 User=emby [Install] WantedBy=multi-user.target After this change it is necessary reload the service with the command: systemctl daemon-reload Finally it is possible to activate the shared-memory for Emby with the command systemctl restart emby-server It is possible to verify the execution of the script with the command: systemctl status emby-server ● emby-server.service - Emby Server is a personal media server with apps on just about every device. Loaded: loaded (/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2019-01-01 09:46:44 CET; 7min ago Process: 8310 ExecStopPost=/opt/emby-server/bin/emby-data_sync.sh (code=exited, status=0/SUCCESS) Process: 8315 ExecStartPre=/opt/emby-server/bin/emby-data_sync.sh (code=exited, status=0/SUCCESS) Main PID: 8320 (EmbyServer) Tasks: 23 (limit: 4915) Memory: 676.5M CGroup: /system.slice/emby-server.service └─8320 /opt/emby-server/system/EmbyServer -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg More details can be found with the command: journalctl | grep emby-data_sync.sh emby-data_sync.sh[23844]: sending incremental file list emby-data_sync.sh[23844]: activitylog.db-wal emby-data_sync.sh[23844]: authentication.db-wal emby-data_sync.sh[23844]: library.db emby-data_sync.sh[23844]: library.db-wal emby-data_sync.sh[23844]: users.db-wal emby-data_sync.sh[23844]: ScheduledTasks/6330ee8f-b4a9-57f3-3981-f89aa78b030f.js emby-data_sync.sh[23844]: ScheduledTasks/81267bb8-bb49-51de-4b1b-446262cc7365.js emby-data_sync.sh[23844]: ScheduledTasks/d459f39d-7abb-81f5-fcce-03048a7ecf4d.js emby-data_sync.sh[23844]: SyncData/Emby.Kodi.SyncQueue.I.1.40.json emby-data_sync.sh[23844]: sent 255,467,606 bytes received 227 bytes 30,055,039.18 bytes/sec emby-data_sync.sh[23844]: total size is 257,320,410 speedup is 1.01 emby-data_sync.sh[23852]: sending incremental file list emby-data_sync.sh[23852]: sent 4,561 bytes received 44 bytes 9,210.00 bytes/sec emby-data_sync.sh[23852]: total size is 257,320,410 speedup is 55,878.48 The paths used in this post are the default ones for a Debian installation, in the case the distribution used is different could be necessary to change some path. But the main concept remain the same. On my installation I was able to speed up the "quick searches" by 100 times. This improvement is mainly due to the increase of speed obtained by moving the SQLite databases to RAM. In this article: https://www.directionsmag.com/article/3794 is reported an interesting comparison on memory access vs disk access speed and is stated that: "If you have a problem with slow database access, placing the entire database in RAM can instantly provide a factor-of-100-thousand increase in access speed with no other programming or data structure changes required".

Hi guys, for reasons not worth explaining here I am currently without my dedicated server hardware. So I decided to install Docker to my Synology NAS and install the Emby image. My reasons for using the Docker Emby image and not the native Synology Emby app are various. DSM 6.2.4-25556 Update 2 Docker 20.10.3-0554 Emby latest (4.7.0.9) When I entered my premier key I got an error. After a bit of digging I found that if I turned off my Synology firewall then the key worked fine. Not ideal but to turn off the firewall for a few seconds while my premier key is validated and verified is not a deal breaker. What I found next is that when scanning my video library it doesn't download any metadata unless the firewall is off. I've tried a few different firewall rules but to no avail. Does anyone here have any ideas or the answer? Many thanks in advance! Container Log emby-1.html Container Settings emby.json embyserver.txt

I am trying to use Emby through roku, which I haven't done in a few months, and it is telling me that I have to update it. I am notified of an update on the dashboard and I tried both restarts and shutdowns but it still doesn't update and I still can't get into the server on the roku app. I tried disabling automatic updates and I still can't login. I tired a download but it is wanting to set up a new instance and not update the current one. How do I update emby or bypass the update? I have version 4.4.3.0 installed on Windows.

nvm, i found the option =P

Hallo, ich habe auf meiner NAS Terramaster F2-210 den Emby Server Version 4.1.0.26 installiert (das ist die aktuellste Version, die mir dort zum Installieren angeboten wird). Nach dem Installieren habe ich den Emby Server aktiviert. Greife ich aber mit anderen Geräten (Smartphone, Tablet) auf den Emby Server zu, habe ich kurzzeitig Zugriff. Dann schließt sich aber der Server selbstständig. Im Desktop-TOS akitviere ich ihn wieder. Das Spiel kann ich stundenlang so machen. Kann ich das Problem lösen? Für meine NAS scheint es die aktualisierte Version nicht zu geben? Schöne Grüße

Hello, I can no longer invite users, when I click add user Emby Server does not bring up the dialog to Add Local User or Invite with Emby Connect. Has Emby Connect or inviting been removed again?