All Activity

I would ask the dev, in devs forum topic.

makes sense, so a bug to correct

Okay, well, some of you astute users may notice that your old installs of the TV app are actually updating now. We have finally cleared the Google hurdles to be able to release this app again. So, you no longer need to be on the beta in order to get the support for the new upcoming server features. The rollout is going gradually right now just because it has been so long since many of you have seen an update.

100% agree. It is extremely easy to build a super low powered NAS these days from off the shelf parts for cheaper than a premade. You can get an N100/N150 board and then get a diskshelf or Jonsbo case and set your drives to sleep when not being in use. Your HBA (if you go this route) will use more power than your processor in this case scenario as the N100 tops out at about 6 watts. For the record, the N100 can handle about 8 1080p transcodes, and 2-3 4k transcodes with tone mapping.

Sounds like the app is trying to reach out on the HTTP port and getting redirected to HTTPS due to requiring secure connection and during the HTTPS upgrade is being manipulated into a GET, whereas when it's not open it gets connection refused and tries HTTPS on its own.

I'm not sure if did read those recommendations when 4.9 came out. I didn't seem to be having an issue with a cache size of 1024MB. So I just kept the setting as is and moved forward obliviously. Anyway, I'll lower the cache to 128MB. Also, my library.db size is 200MB, not 200GB.

i missed asking about that. For some reason I had assumed you have come across the recommendations after 4.9 came out Yes with 5 connections to the database now as from 4.9 and with each using that amount of cache - my new recommendation is to go with the default for cache which is 128 Mb Unless you have tons of memory

@sa2000This may be a stupid question, but would the database settings be worth taking a look at? I set Database cache size and Analysis row limit at 1024 and 1000, respectively, when the option to adjust them was added to Emby. That seemed to be the general consensus at the time amongst users. I've never revisited those settings until now. I've just read: It is recommending 1.5 to 2 times the library.db size for the cache setting. My library.db file is currently around 200MB. So 1024MB for the cache size is likely overkill. Would lowering it to 512MB (or lower) be advised?

With the new update newly added content just shows the title, but no actual video and audio information. Nothing mentioned at the end of the episode or movie information as well, below 'Media Info'. Trying to play the video also gives the 'no compatible streams' error. Everything before the update seems to work just fine.

Yeah, I would say there is a pretty significant difference there. We should be able to clean that up in the standard app I would think.

How are they going to navigate the library? You don't want anyone to be able to sort or filter either? Why?

Hi. What does "convert to 8" mean?

Hi, there's already an open request for this or something functionally equivalent. Please join in and contribute to the existing discussion at:

Will do. A new Beta version dropped anyway so this will give me a chance to install it. I'll report back with my observations.

I just set up Jellyfin 2FA thru Jellyfin Security plugin with OIDC / SSO Providers. Also plugin supports passkeys and app passwords. A lot advanced features. With Quick Connect, every tv and what not is able to login when your account is 2FA protected. WT* is emby doing?? The paid tier is more joke every day

Hum interesting and weirdo, while doing some checks on the server running Emby, I discovered that the fw was off and so I reactivated it and now problem of read/unread not updating has disappeared instantly. It looks like if the http port is reachable the android app is not able to push these updates.... very very strange

Two things to try - Change the interval to 8 hours and see if that is sufficient time for previously allocated memory to get released by the memory garbage collector in .Net - When running manually, instead of running the scheduled task, just run the scan for the specific library Of course you will need to restart Emby Server to establish if these changes make a difference

The "Scan media library" task is scheduled to run every six hours. That was the interval I seem to recall others recommended when I first setup the server may years ago. Usually I'll run it manually as well when new media is added or removed from the library. Not sure if this is worth mentioning, but I've only seen the spike in memory usage when I run the "Scan media library" task manually. So far, I have never seen it happen when the tasks runs automatically according to the schedule.

I've been waiting and waiting for 2FA/MFA in Emby forever. I don't disagree with your statement, but it is a necessary evil. Really, if MFA is a reality someday, your identity manager of choice would likely have Passkeys which makes things almost seemless. I just enabled those with Authentik and its... lovely. I may go with LDAP for Emby, but I feel the work isn't worth it other than my family having SSO across services which is a goal.

yeah but there is nothing in between, the emby server is exposed via its public ip address that is the public ip address of the server it's running on. Here are my network settings in case something would be wrong: you can say that, http and https are activated but I forced the https for remote and there are only remote connections on it. The http port is blocked by firewall.

what is the interval for scheduled task: Scan Media Library

I removed all the plugins in the list Luke provided, including TimeLordTV and TimeLordMovies. Memory usage by Emby hasn't actually changed much from prior to uninstalling the plugins. It started out at around 300MB and over the next five or six hours it climbed to somewhere between 900MB and 1.2GB where it sat for most of yesterday. It's currently sitting at 1.3GB after 24hours. This is pretty much normal behavior. Emby's memory usage suddenly jumping to 2GB+ when a library scan is initiated...that only started occurring in the last month. I'm not sure if what I have is considered a large library by the standards of other Emby users. Usually I only do a server reboot when a new Emby Beta version is released. Although recently that has meant the server is rebooted once a week due to frequent releases, in the past when releases were less frequent I definitely went two or more weeks between restarts without an OOM event occurring. Anyway, thanks for your input!

Plex / emby

HI there, can you please provide a specific example? How to Report a Problem Thanks !