Leaderboard

You cannot rollback between different branches - i.e. 4.9 > 4.8 (unless you have a full previous version backup) due to db changes, you'll need to rebuild your library. Cause contrary to above, you generally can rollback within same branch - i.e. 4.9.x.y > 4.9.x.x, though not always, db changes will be introduced during beta cycle every now and then, but between versions it's a guarantee.

For those interested in the topic.... I tried it again with 2 TV's and it still doesn't work. As soon as LG makes a PCM out of anything, the AVR switches to "limited mode" with only Stereo. The Denon's don't accept LG's PCMs as a correct raw multichannel signal, even it receives all 6 channels. As I said before, all other devices, mediaplayers I ever tried can send the same file as perfect PCM, so Denon says ok and lets you use all available upmixers, Auro or just the famous "multi CH in". I never could figure out if the problem is with the PCM stream itself or the metadata of the PCM or it is just a EDID Handshake thingy. Neither Denon nor LG support could rudimantarily help, even I tried a hundred times to get to Level3 and 4 support. Denon wasn't even able to read or interpret my logs from the AVR and LG has the dumbest support on this planet. But they know about the problem for years and confirmed it. So I still don't know what affects Denon's behavior with LG PCMs over EARC, while it woks in really every other case.

I took a trip down memory lane and installed Plex after your post. I read that Plex uses musicbrainz's release type. Plex's Artist BIO and Album Description fetching is a joy to consume but no awareness of Musicbrainz multi value [album]artist tags and composer tags is a bit of a deal breaker. Emby's song tab would be more useful if a text sub search could be added to these types of screen IMO.

This is the right way!

Thanks, apparently I've already contributed there and completely fo gotten about it lol

@Luke I created a dedicated "emby" user with restricted permissions on MacOS 15.4. and created a plist-file to start emby-server via launchd at boot under the "emby" user. This seems to work fine. Newer MacOS Versions have a few "annoying" features that need addressing for this to work properly and secure. (For example if the media is on external drives) If anyone is interested, I am happy to post a guide, just let me know. (It might be necessary for someone to double-check, as I am not an expert in this area), but for me it works well. It could be nice to integrate something like this into future macOS installers

I am just about finished flipping from Plex to Emby and 2FA is really the only big hole in the product. I know you are not going to force it but I would love to see a server side setting that we control individually that had the following 2FA: Optional, Required for Admins, Required for all users

Hello, Is it possible that in a version of emby a "ping pong" is performed in websocket to maintain a connection via a reverse proxy? Let me explain. Apart from reverse proxies such as caddy or traefik (for those I know) there is no real timeout for websockets. For reverse proxies like haproxy or nginx, the timeout is defined either by default or by the user. In the case of haproxy or nginx, if someone pauses a video that lasts more than an hour (a movie, for example), the websocket timeout will occur before the end of the movie. Or if, when playing an episode of a series lasting 40 minutes, the viewer pauses the video for 20 minutes, the connection will be closed before the end of the episode. Having the client send a message and the server reply every X seconds/minutes would eliminate the problem and prevent the connection from staying open for 1 hour for no reason, as in the nginx configuration. Also, I saw a message saying that if a connection was closed unexpectedly, for resource reasons, there was no attempt to reconnect. Why not set up a number of reconnection attempts? For example, the client tries to reconnect 3 times, and if none of the attempts work, the connection is aborted. This would, I think, allow better websockets management and avoid connections being open for hours. Or even when changing networks (LTE->wifi or wifi->LTE), this would make it easier to re-establish the connection than quitting the application and reopening it. To avoid sending just a "ping" and a "pong", useful information can be sent through websockets when the client supports them, such as the position of the video playback (which is currently sent via http), because a request via websocket is faster than an http request and sends, with the same information in the body, less data than an http request.

Install The Emby Discord plugin can be installed using the Emby Server plugin catalog. It requires Emby Server version 4.8+. Contribute https://github.com/MediaBrowser/Emby.Notifications.Discord

I've spent months evolving my Emby setup to a state where it is able to reliably play live TV streams from an IPTV provider. Sharing my findings here to help the community and gather feedback in case I can make things even better in the future. Up until I added hls-proxy to the mix I was attempting to use Threadfin as a buffer. It helped stabilize things slightly but issues were still present. Emby clients would randomly seem to drop their channel streams and fall back to the previous screen in the app, it was more prevalent with remote clients than with local, but all clients (web/android/roku) experienced the issues. Clients have no playback issues with local, or remote episode/movie media files. The IPTV service provider I use allows 5 concurrent connections to their service. However, I have noticed that I cannot rely on Emby to enforce this limit. If I set "simultaneous stream limit" to 5 in Emby it will eventually end up in a state where no channels can be played even though there are no active streams (verified by looking at the status page of hls-proxy). I don't know why this happens and I can't seem to correlate it to anything specific. After adding hls-proxy to my setup, I will sometimes see Emby make a secondary connection to the same stream even though a second user has not tuned to that channel, but I'm not sure if that has anything to do with the problem. The workaround I've put in place for this is to set the "maxStreamsPerClientDefault" in hls-proxy to 5, and set "simultaneous stream limit" on the TV source in Emby to 0. I've also configured a cron job to restart my Emby server early each morning to clear out any stuck tuners that might exist. When I set up hls-proxy I noticed a couple things. My provider publishes 5 .ts files in the m3u playlist for a channel. If Emby is able to see a list of 5 .ts files, it will read them but start playback in the client at what I believe is the 3rd or 4th file in the list. This means that Emby is only leaving a 1 or 2 file buffer between the playback position in the client and the stream coming from the provider. If the provider experiences a delay in publishing the latest .ts files for the stream to their servers/CDN, the client will overrun the buffer and this may be why the client stops playback at seemingly random times. I was able to configure hls-proxy to show Emby only 2 of the 5 files at the start of playback which seems to start the client playback at file 1 when starting a stream. When it requests the playlist a 2nd time from hls-proxy the first 2, and next 3 pieces are in the playlist for Emby to fetch. At this point hls-proxy already has another 2-3 .ts files in the buffer that haven't been advertised to Emby yet, so not only does the client have a bit of a buffer to work with inside the Emby server, the Emby server has a 2-3 segment buffer in hls-proxy that it can draw from in the event that hls-proxy needs to retry fetching the stream due to a publishing delay or a temporary error on the server side. The only time a stream drops now if if hls-proxy encounters a provider side error that it can't overcome in a reasonable amount of time. Since Emby is still communicating with hls-proxy when this happens, the stream will freeze, and can recover if hls-proxy is able to retry the connection and fetch files before the retry limits or timeouts are consumed. Some notes on how I'm using these apps. I've tested hls-proxy both in front of, and behind Threadfin with the same result on Linux and Windows. Threadfin - used currently with the buffer disabled so the m3u URLs from the provider are passed to the client. I use it strictly to groom/curate the incoming M3U/XMLTV links from the provider. hls-proxy - Used as a debugging platform and a buffer in-between Emby and the provider. This allows me to get a peek at what is happening between the provider and the Emby server. If there are any errors from the provider side I can see it in the logs. You can view streams directly in their web interface. It also has options available to aggregate provider accounts based on the syntax of the URLs they use to serve content. If you have many single line accounts with the same provider hls-proxy can aggregate them into a pooled resource.

Sure, and that would be great for something like plugins or other standalone type of projects such as integrations with other software. It's not a great approach for something like this that would go into the core product and would affect many workflows, require re-evaluating the entire user interface, etc.

Very cool and thank you for this. I have a lot going on this week, but look forward to trying it this upcoming weekend. I'll report my findings.

I believe I found the problem. It was the Ethernet cable between the router and the access point. I replaced it with a new one and that cleared up the problem. By that time, I had tried several things like rebooting the router and checking space on system drive. I just got lucky when I decided to replace the cable. I thought it was Emby because that's the only app that had a problem. Everything else seems to be working better now, though. So, it's time to mark this as solved. Thanks for the help.

Hi, not currently but it's something that we're interested in for future updates. Thanks.

@ransomshellHonestly I would abandon Android TV version if I were you. They are not making future enhancements to it, and the Android universal app has a lot more functionality.

Updated migration instructions for Emby 4.9.x on TrueNAS 13.1, integrating the instructions from NYPD54's post: Stop and rename your existing Emby jail, so that we can safely access its data directory later on, and so we can reuse its existing IP address. iocage stop emby-server iocage rename emby-server emby-old Create a new base jail with mlock enabled (name will assumed to be "emby-server") using the host shell: (You can safely reuse the same IP as your old jail.) iocage create -r 13.5-RELEASE -n emby-server allow_mlock="on" vnet=1 ip6="inherit" ip4_addr="10.2.3.4/24" Set up your mounts: (Adjust first path for your media dataset. Adjust ro to rw if you want Emby to be able to write to your media dataset.) iocage fstab -a emby-server /mnt/[pool]/[dataset] /media nullfs ro 0 0 Start the jail and connect to its console: iocage start emby-server iocage console emby-server Install packages and configure Emby pkg update -f pkg install dotnet8 libass fontconfig freetype2 mbedtls3 fribidi gnutls iconv opus sqlite3 libtheora libva ocl-icd libvorbis webp libzvbi libraw ImageMagick6 tesseract intel-media-sdk libunwind libinotify openssl icu krb5 libexif libjxl libheif libimagequant openexr openjpeg orc pango tiff pkg add -f https://github.com/MediaBrowser/Emby.Releases/releases/download/4.9.1.80/emby-server-freebsd13_4.9.1.80_amd64.pkg sysrc emby_server_enable="YES" Before starting Emby, if you have existing Emby data in another jail or in a backup, copy it to /mnt/[pool]/iocage/jails/emby-server/root/var/db/emby-server now, and it should get picked up by Emby when it starts: (Outside the jail) cp -R /mnt/[pool]/iocage/jails/emby-old/root/var/db/emby-server /mnt/[pool]/iocage/jails/emby-server/root/var/db/ If you do this, remember to reset the ownership of this directory. (Inside the jail) chown -R emby:emby /var/db/emby-server Start Emby and make sure it's accessible: service emby-server start Finally, if you had any snapshot tasks set up for your emby-server jail, make sure they haven't all been renamed to emby-old, otherwise you will need to configure new ones for the new emby-server jail. Notes: Make sure VNET is enabled, otherwise Emby will think your LAN clients are remote clients. I haven't figured out the commandline arguments for setting IPv6 to auto, nor for enabling/disabling auto-start, so I needed to adjust those manually by stopping and then editing the jails in the TrueNAS UI. I'm not going to delete my old jail just yet, but it looks like 4.9.x is running fine for me so far.

Thnx, this worked for me.

Thank you for your detailed and thoughtful response. I think you misunderstood my posts. I am asking for clarity on how it works, not that it should be designed this way. In fact, if my understanding is correct, I think the downloading feature needs significant adjustment. To be clear, I'm asking about downloading, which differs from transcoding in that it does not need to be real time. This is a good thing, as it provides opportunity to be a little more careful in the way we encode. I agree, however this is how Emby is currently designed for downloads. Here is the window you receive when clicking the 'download' button. If you choose 'custom', you're presented with a field that allows you to enter your own bitrate, without any further explanation. However I can see the logic behind it, as it allows you to control the resulting file size on a mobile device that presumably has limited space. As I said earlier, without understanding the rest of the variables at play, it is impossible to see how an average user will ever achieve an acceptable download quality. Frankly, the average user won't even understand what a bitrate is. And, for those more knowledgeable, it is confusing and largely undocumented. I could well be missing something somewhere in the app that allows better definition on how downloads are handled, and I'm hoping someone from the Emby team can chime in with better detail. Because, from my current understanding, it is a very disappointing 'premiere' feature when you compare it to the exceptional LiveTV/DVR implementation, for example.

no

Certainly! I've updated the plugin but not released as I'm getting a 403 forbidden when I hit the aud and vid files. Watch this space

Well that's frustrating. Having been spammed to remove it, I just backed down and removed the source. I'll add it back in as the secondary source as it can't hurt! Lesson learned! Thanks pal!

Any approximate time on when this will be out? I'm considering getting a m4 mini in the future and what would really be a deal breaker for me is if GPU acceleration isn't possible. Any information would be appreciated.

@Lukemy bad, French people think everyone speaks French ahah i was saying right now if we want our users to be able to reset their own password via self service the option is to have a ldap server with PWM like web interface, an email reset via smtp would be way easier to setup and anyway even PWM would requires to setup an smtp

Does Luke speak French? But LDAP is currently supported? Wild, it's such a niche feature, something way less user would use vs a SMTP email. How many have an active directory at home.... I used to do that, 20 years ago...

Yep, webhook, thanks No idea how I wrote we hook twice

Would absolutely love this

There is none currently. There's a long-standing discussion in the FR forum, you can always lend your support there.

Thanks to you, me and a friend got this made :

I am having the exact problem on macos app. Hope it gets fixed soon.

I setup a github action to use the existing build.sh to build tagged releases. Anyone is free to test out the release, as found here: https://github.com/sydlexius/Emby.SmartPlaylist.Plugin/releases/tag/v2.5.2.4862 Note that I am not a developer. I don't grok js, ts, or c#. If you experience an issue, you're welcome to share relevant log files or browser developer mode console output, but I can't promise I have any ability to fix it. Peter principal through the power of AI!

This is the top feature for me! Really looking forward for this one

I figured it out, forgot to reply, the solution was I needed to mount via nfs rather than smb. After that it worked great.

I did the movie refresh at the parent level - it only fixed about 20% of what was broken. However doing a refresh at the parent level for movies fixed almost everything. So I had a thought. What does emby use for it's database? Is it possible this data was stored in cache and not actually written to the database? I can't image that's the case because it's been running fine for years and I have obviously rebooted emby for all updates.

I gave up on waiting for a working Linux client and I'm now just using the web client and working around the limitations I must say paying linux customers are treated as second class citizens here

Bro this is clean as hell...Thank you. I'm thinking of making an htpc just because web player is so complete ! client app suck.

It's not that hardware detection is running periodically. It's that your Emby server is restarting every 10 minutes and hardware detection runs every time the server starts. That's why you're getting a pair of new logs every 10 minutes. Look into what you might have on your Linux server that's restarting Emby on a schedule.

The issue is fixed now. I can see emby in connected apps on trakt side, and i was able to successfully run the trakt schedule task from emby. Now trakt is synced with emby watch history. I am curious, what was the issue? On my side I did the same steps i have done previously. I think i have reset the PIN 10 times in the past weeks hoping, and it did not do anything until yesterday.

@VicMooreI find it most convenient to add things to channels using playlists. But could we have a few more options/control... What order the content of the playlist is aired. Check for and update changes to playlist. Also, on a different note, could we have a simple list of what is actively being used in a channel, as it's not that clear to me. Just a few ideas. Thanks PS Just found when playing an audio only channel on Roku, it stops playing at the end of the first song, bug maybe?

If you’re new to the world of media servers, you might be wondering what they are, why people use them, and where Emby fits in. Whether you have a collection of movies, TV shows, music, personal videos, photos, or all of the above, a media server helps you take control of your entertainment. Let’s break it down. So, What Is a Media Server? A media server is simply a system that allows you to store your media in one place and access it from anywhere — your TV, phone, tablet, computer, or even while on the go. Instead of hunting through drives, folders, or different apps, a media server organizes and presents your library in a clean, familiar interface with artwork, descriptions, cast info, and more. Think of it as your personal streaming service that is built around your collection, not someone else’s. An important note and one we can not stress enough, is that Emby does NOT provide any movies, shows, channels or other media. Emby is only for organizing and streaming YOUR own content. Why Choose Emby? There may be several media server solutions out there, but Emby has a philosophy that sets it apart: Your Media. Your Way. With Emby, you are in control! Your library is yours, your privacy is yours, and your server is yours. No forced cloud accounts. No data harvesting. No locked-down ecosystem. Emby is built around choice and customization, allowing you to decide: Where your media is store How your library looks Who can access it What devices you stream to Whether you want to manage media manually or automatically All while keeping your experience intuitive and easy. Beautiful and Powerful Emby automatically fetches artwork, metadata, and episode information to make your library look amazing. The apps are clean, fast, and available across: Smart TVs Streaming boxes like Fire TV, Apple TV, Shield, Android TV Android, iOS, and tablets Game consoles Web browsers And with Emby Premiere, there's even more! You can unlock powerful features like: Offline downloads DVR with Live TV Advanced parental controls Hardware transcoding for smooth streaming Whether you're just starting or you're a longtime media enthusiast, Emby scales with you. This Is Just the Beginning Over the next few days, we’ll walk through: How to install Emby How to add your media Tips for organizing your library And how to stream anywhere So stay tuned — your personal media journey is just getting started. Your Media. Your Way. Welcome to Emby. View the full article

Hi, that is our hope, yes. But in the meantime you can always install manually from our website: https://emby.media/download

This statement is from emby dev, while the same dev team is actively working on 20+ different client / platform emby apps ( see download page 22 of them). Some of those clients / platforms are so obscure and have very little number of users compared to Android platform that is nonsense to read this whining about we dont have time....

EmbyWatch - A brilliant app built by a community user! One of the best things about the Emby community is the creativity that comes from it. Every so often, one of our users takes their love for media servers to the next level and builds something that makes life easier for the rest of us. Today, we’re excited to share EmbyWatch, a brand-new Android app developed by community member @asgard25It is an an incredible example of what happens when passion and innovation meet. A User-Built Tool, Made for Admins What makes this story special is that EmbyWatch wasn’t created by a company or a professional app studio. It was created by one of YOU! — just someone who wanted to make managing a server more intuitive and accessible from anywhere. Want to be even more impressed? This is only the second Android app that asgard25 has developed! EmbyWatch is designed to help server admins and advanced users keep track of what’s happening on their Emby setup in real time. It’s not about playback or browsing media, it’s about giving you the tools to monitor, manage, and control your server, all from your phone. Powerful Features at a Glance EmbyWatch brings a surprising amount of functionality for such a young app. Here’s what it can do: Real-time monitoring: See who’s watching what, where they’re streaming from, and how much bandwidth they’re using — all live. User management: View your users, check activity history, and even send messages directly to connected users. Device overview: Identify every connected client, from smart TVs to mobile apps, with connection times and device info. Library insights: Quickly review all your media libraries with detailed counts and metadata. Task control: Run or schedule maintenance tasks like library scans and metadata updates remotely. Plugin visibility: See your installed plugins and available updates. Logs and server details: Access logs, CPU load, uptime, and more — wherever you are. Notifications and widgets: Stay informed with live alerts and optional Android widgets for quick monitoring. For anyone managing a shared server, EmbyWatch feels like having a live dashboard in your pocket. A True Example of Community Ingenuity We love seeing users like asgard25 take their experience with Emby and turn it into something that benefits everyone. EmbyWatch really is a reflection of how open and flexible the Emby ecosystem can be when people put their ideas into action. This project shows exactly what makes our community special, a shared passion for improving and creating! So whether you’re managing your own home setup or running a multi-user server, EmbyWatch offers a simple, powerful way to stay connected to your system. Huge thanks to asgard25 for sharing EmbyWatch with the community and for showing what’s possible when creativity meets passion. We’re proud to see our users building tools like this that make Emby not just a media server, but a thriving ecosystem shaped by its fans. If you’re an admin or an advanced user, check out EmbyWatch on Google Play and see how it can make managing your server easier than ever. We can’t wait to see what asgard25 — and others in our amazing community — build next. View the full article

Hello @Luke we dont have any news about it except « we’re working on it ». Could you please tell us if any problem or explain what happens ? Thanks to share news about it, we’re really waiting this features from few months (years ). Have a good day

Hi. Optional features that most people will not use are the most expensive type of feature we can put in the product in terms of development, maintenance and support and also complexity for the end user so we try to limit these as much as possible. All research for many years has shown that the vast majority of users never turn on optional features so this becomes something that costs a lot but delivers not that much value (to the majority of people - I understand it would deliver value to the ones that want it). Our experience with this feature (we used to have it) was that not many people used it so that just makes it not something that is at the top of our list when you consider all the other features that would deliver value to a larger audience. All that is not to say the we will never have this again. Just that it isn't at the top of the list to spend time on. Thanks.

I'm unsure how to make the OP anymore clear. But if it needs to be summarized again due to age of the request. The OP is imploring much needed improvements to WebSocket connections in Emby by implementing keepalives to maintain the connection during pauses in video playback, such as when watching movies or TV shows. This would prevent timeouts that cause the connection to close prematurely and prevent playback controls from being displayed or used in event the admin wants kill user session(s) for various reasons. Several examples have been provided in previous discussions to illustrate this need.

I released a new version (1.0.2.1) with a couple improvements to the github: https://github.com/oonqt/Emby.Notifications.Discord/releases All further releases will be held on the Github until we make it to the plugin catalog

Small update, but it's something... Added: * Added the ability to choose between `@everyone`, `@here`, or `None` for mentions. You can read more about this by clicking the "help" button on the plugin configuration page Fixed: * Only send test notification to currently selected user, not to every configured used. If you have any ideas of what I should add, please leave some feedback. I'm still working on getting the custom media added embed with info like the media name, description, cover art, etc. THANKS! Emby.Notifications.Discord.Update.1.0.2.0.zip

Just finished an update that adds Mentioning, Embeds, and a help page that explains these things in more detail. You can download the new version from this post or from the OP Emby.Notifications.Discord.UPDATED.zip

Well Discord has plenty of options. You can easily create your own server and/or channel. On top of that maybe family/friends that make use of your emby server also have discord and are in your server/channel and can use some of the data the plugin may post? Personally I use it in my own server, in a private channel just for me and let it send admin messages. I didn't feel the spam that any new show/movie was added, was a great addition so I left that and some other things out.

Very cool, thanks !