All Activity

I think the issue is that we have a large number of tabs in TV libraries as it is. Maybe it should wait until the tabs are configurable.

I have to be honest, I'm not 100% sure either. Most of the time, most of what I do with the server is "muscle memory", and for some reason, I feel as though I used to just go to my TV library and select a playlist. I also have playlists on my home screen, so I might be confused how I got to them. If it wasn't always there, it would be nice to have...

HI, please try Emby for Android 3.5.37: Thanks.

HI, please try Emby for Android 3.5.37: Thanks.

HI, please try Emby for Android 3.5.37: Thanks.

Hi, did you try our suggested Docker options? https://hub.docker.com/r/emby/embyserver

Can you please try it again and get us this information? We are hoping to release 4.10 to stable soon. Thanks.

Hi, I'm not sure that we've ever had this under TV show libraries.

Did you enable TV display mode in the app settings? If you're controlling with a remote then I would recommend this.

Ok thanks will give that a go when I get chance. At the moment trying to see if I can force to download AC3 as I'm not bothered by Dolby in the bedroom

The TV I was testing on is TCL 6 . I also I have a TCL Q7 . Went to my buddy house and he has a LG C6 . Had the issue on all 3 tvs. On my Shield it works fine . So the TV isnt the issue. Also Plex works. Jellyfin works but has DV problems with some files and Emby stream DV to HDR. I am assuming its just a fire tv issue

Hi, we have identified one source of a crash that is resolved for the next app update. Thanks.

Hi, what version of windows are you on?

The url you're trying to access sent back a 403 forbidden error: 2026-06-22 06:23:10.799 Info HttpClient: GET https://opop.pro/x_path1_x 2026-06-22 06:23:11.159 Info HttpClient: Http response 403 from https://opop.pro/x_path1_x after 359ms 2026-06-22 06:23:11.187 Error LiveTvService-0HNMG90ID2TND:0000001D: Error processing request *** Error Report *** Version: 4.9.5.0 Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3 Operating system: Linux version 6.18.33-Unraid (root@Develop) (gcc (GCC) 15.2.0, GNU ld version 2.46-slack151) #1 SMP PREEMPT_DYNAMIC Mon May 25 10:59:51 PDT 2026 OS/Process: x64/x64 Framework: .NET 8.0.25 Runtime: system/System.Private.CoreLib.dll Processor count: 12 Data path: /config Application path: /system MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: Forbidden You may have to disguise the user agent and/or referrer fields in order to get around that.

That is likely because the Roku is set to "Auto" in the Roku Audio settings. When using Auto the Roku will determine via HDMI which codecs are supported or not from the connected hardware along the HDMI chain. Sometimes it gets this wrong. Sometimes it isn't aware your TV does support EAC3, which is Dolby Digital+, rather than just Dolby Digital. You can set your Roku to Dolby instead of Auto for the Preferred streaming codec. Then for Digital output format choose Custom. Then inside the custom settings, enable Dolby Digital and Dolby Digital Plus. If you know your TV that Roku is connected to also supports DTS enable that too. Then restart/reboot the Roku. Change audio settings requires you reboot the Roku to reset the HDMI chain. Then test it with the Emby Roku app. Try to play something with EAC3. Do you hear sound? Or is it just silence? If you do not hear sound and you just hear silence you may need to disable the Dolby Digital Plus in the Preferred streaming codec. But if it does have sound it proves the Roku couldn't properly detect EAC3 support on your TV using the HDMI chain. The Roku cannot detect EAC3 properly on the Samsung TV I have even though it works perfectly. The Emby Roku app reads the audio capabilities directly from your Roku. As you make changes to the Roku system audio settings it does affect how Emby will play. Fixing this on the Roku audio settings will fix the Emby Roku app.

@thekingswolf?

Good to know. If it works fine on PC and phone but stutters on Fire Stick, then the channel/API part is probably working and this is more likely a Fire Stick playback issue. The plugin does not download or re-encode the YouTube video. It gives Emby the YouTube item, and then the Emby client has to play it. Fire Stick can use a different playback path than PC or phone, so it may behave differently.

Hi there, how are your files named and organized?

Hi, try using the image editor to delete the existing image. Then run a library scan and that should create a new one.

What TV are you using?

HI, yes, this is something we need to look at incorporating. Thanks.

I’ll gonna try, seems to run fine on pc/phone but on fire stick i got a lot of shuttering

HI, try refreshing the metadata on it and then try playing using the Emby web app or Emby app rather than Infuse.

Hi, please attach the ffmpeg log as well. Thanks.

Thanks for following up.