All Activity

Doesn't seem to be working atm. if it is indeed what is wanted and not a communication misunderstanding.

There doesn't appear to be any way to drag Playlist items to rearrange them on the mobile app.

Hey @Luke I need to vent my frustration about the extremely sluggish update cycles of core components. I have been waiting for over 6 months now for an update to the ffmpeg base! It is unacceptable that paying customers have to beg indefinitely for up-to-date detection and rendering of HDR10+. If you look over at the open-source twin Jellyfin, you see how it should be done: their in-house jellyfin-ffmpeg handles the latest HDR standards perfectly, thanks to weekly unstable builds and fast stable releases. On top of that, there are visual and functional flaws that are becoming increasingly annoying: Ugly Audio Display: It bothers me immensely that the top display strictly insists on showing "EAC-3" instead of cleanly and beautifully translating it to "Dolby Digital Plus 5.1 / 7.1" etc. It just looks unfinished. Messed Up Metadata: The metadata at the bottom regularly displays completely erratic information that doesn't match the actual media files at all. Dead Plugins: Official extensions like CoverArt feel completely abandoned and are just gathering dust. Meanwhile, the Jellyfin community offers modern, dynamic solutions like JellyTag, which automatically renders crisp HDR10+ badges onto covers on the server side. To be completely honest: What did I actually pay so much money for Emby Premiere for? It is deeply frustrating to see that the free open-source alternative gives you everything for free, significantly faster, and technically much better executed. If this lazy update policy for playback engines and outdated plugins doesn't change drastically and very soon, Premiere loses all its value to me. Are there any actual plans from the developers to catch up with current standards, or is this project permanently being left behind by open-source?

Server version 4.9.5.0 Theatre version 2.310.2.0

After reading some of the issues/problems posted here I took the plunge and updated from 4.9.3.0 to 4.9.5.0 anyway. I want to report that everything works with no issues. My libraries did not rescan and no modifications to "date added" occurred. I also did a "Scheduled Tasks -> Scan media library" with no issues, took about 30 seconds on a very large library. Using the Docker container deployment. I also saw the client side update for ET legacy (4.9.5.0) on 6/16/2026 with no issues either. All good

Good points. I have had trouble getting a top of the line Sony TV from working with Emby. But I only tried it once with Sony back in 2020. What about trying a test demo h.264 10 bit video. Perhaps the conversion creates some time line or metadata errors that are tought to spot. I also suspect that transcoding with options set very high can create rather large files and the Sony TV player might just reject the video for that reason. Using test vids can prove that it's not the video. Just an idea.

Is there any way to do that without having "Recordings" in Live TV show all my downloaded shows, too? That's what happened last time I changed the Live TV setting to have series recordings go to the larger TV library.

Hi. What was the solution?

Does this mean there has been a recent change to language handling? I reported Mayan not being supported a while back, has that changed?

That's just as obstructive, though. The problem is having to scroll past two screens' worth of suggestions/recents before getting anything that matches the search term I just entered.

I've now restored the backup and copied my stream links. I was able to reproduce the problem every time. After the update of the plugin, and after restart of the emby-server-service, the entire configuration in the backend was deleted. Unfortunately, the plugin's log only contains these 3 lines: 2026-06-17 22:55:27.997 Info App: Loading Emby.WebStreams.Plugin, Version=4.9.1.39, Culture=neutral, PublicKeyToken=null from /var/lib/emby/plugins/Emby.WebStreams.Plugin.dll 2026-06-17 22:55:29.571 Info App: Starting entry point Emby.WebStreams.Plugin.WebStreamsPlugin 2026-06-17 22:55:29.613 Info App: Entry point completed: Emby.WebStreams.Plugin.WebStreamsPlugin. Duration: 0.0413947 seconds Anyway, as soon as I add the first link again, the entire configuration in the front end is deleted- or rather, it’s repopulated. I’ll test this functionality in the field tomorrow .

yes it makes me think that it related to the subject the op is asking about. Whether it has a part to play in the code they are writing i dont know. I was drawing attention to it as potentially relevant.

Luke will probably have another new one in about a week also as the latest will soon expire. Just check that link he posted for all updates.

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

Yes, this is sufficient, however the timer is just internal behavior and currently cannot be avoided.

I do believe the AndroidTV app does have such a message, but it only comes up once or on new installs so as not to nag people.

OK. Haven't seen that before but we'll take a look at it. Thanks.

So @Luke there is a new version available I can download and sideload? Remembering I live in New Zealand and there seems to always be a huge delay with the Samsung store. Please confirm?

OK we'll take a look at that. You can also change quality directly in the video player.

I understand, but thank you very much for considering it anyway.

@RealLinuxGamer@LukeI have not retested yet on the new server version with Emby for AppleTV 2.0.6 (3), but there has still been no issues on the Nvidia ShieldTV Shield Experience Upgrade 9.2.4 (33.2.0.400) Emby Server: 4.9.5.0 Emby for AndroidTV 2.1.43g and 2.1.46g (subtitles work on both versions, directplay and transcode)

I think it is an issue in that version of the app. we have already submitted an update to Samsung. You can sideload if you need immediate relief.

Anyway I don't see this issue on the iOS 26.6 beta so maybe the best solution is just to wait and let Apple resolve it.