All Activity

FYI, Emby for Android on Sony TVs has grey letterboxes during playback. Emby for Android TV has proper black letterboxes. Emby for Android has some nice UI features like viewing actors while a show is playing, but the for ATV version will pause playback when you try to view actors. There are some other UI differences as well. I'd prefer to use the standard Android version, but since I have Sony TVs and don't want grey letterboxes, I'll be using the for ATV version.

Hi I have tried both TVDB and MovieDB as Episode Metadata Downloaders and neither pulling in genre info. Have confirmed that they both have genre info related to TV episodes. As a test, I deleted a genre in one of my old episodes, that already had complete genre information, and asked Emmy to refresh the metadata for that episode, hoping it will pull in the genre I deleted. Once refresh was completed, I checked out the episode and it never pulled in the genre I deleted. System stopped pulling in genres for Dutton Ranch, Marshals, Your Friends and Neighbours, For All Mankind, Legend of Vox Machina, to name a few.

I’ve added a “Music” directory which plays my extensive mp3 classical music files through my great speaker setup. Sweet!

That behavior is possible. “Alexa, stop/pause/resume” are Alexa-level media commands, not necessarily Ear Wax skill commands. Alexa decides which active speaker or media session those commands apply to, and in multi-Echo setups it may control a different Echo than expected. For clean Ear Wax testing, please use the full skill form: Alexa, ask Ear Wax to pause Alexa, ask Ear Wax to resume Alexa, ask Ear Wax to stop Bare commands may still work, especially “next,” but they are routed by Alexa’s media-control layer before Ear Wax gets involved. If playback behaves strangely after a bare command, retest the same action using the full “ask Ear Wax” command so we know the skill handled it directly.

Nice to hear it's working, enjoy!

I followed this topic because I have the same issue. Since this is going a while I had shortly the oportunity to use my phone in an car with Android Auto (Connected via USB). When I start the FLAC Albums from the car head unit it will play the album completely fine, if I start the same album direct from my phone 2 songs and thats it. I don`t know if this helps for the case but like to share the knowledge.

I am looking to display an image inline on a plugin config page. Currently targeting 4.9.1.90 and the GenericEditFrameWork as shown off in the SDK demo Ideally i would like to place an image (a movie poster image to be exact) in the the nested list with buttons (perhaps instead of the stock icon?), but failing that i can settle for just any method of displaying a poster anywhere. Is this possible without reverting to http/js config pages? (please bear in mind i dont fully understand the terminology i am using so i might be making mistakes, hopefully you get my drift) Thank you

Ik heb weer een bestand dat niet afspeeld in Emby app op de lg tv, tot 2x geprobeerd heel vervelend want op de Android app speelt het wel meteen af. Het gebeurt de laatste tijd steeds vaker

Looks like it works like a charm ! I've tested Posters only as I don't use overlays on thumbs and banners. Cheers @yocker

Thank you so much @yocker, you are the best !! And please enjoy your summer break, have a nice cold one for me

For Apple TV specifically, though, the mpv route has a few trade-offs that a native HLS + fMP4 (stream-copy) path avoids: It's a third-party engine. Bundling and maintaining mpv instead of the platform's own AVFoundation is a long-term cost, and it tends to lag behind OS changes. It breaks some native integrations. The clearest one for me is audio: routing sound to an AirPlay 2 device such as a HomePod doesn't behave the same as with the system player — with the native pipeline that just works (multichannel included); with a custom renderer it's often limited or lost. It tone-maps rather than passes through. This is the big one. As far as I can tell, the mpv path does its own tone-mapping and then outputs an HDR signal, which makes the TV switch into HDR. It's better than re-encoding on the server, but it's still a tone-map: the TV never receives the original Dolby Vision bitstream, so its own DV engine (with the dynamic, per-scene metadata) never gets to do its job. To my eyes it simply doesn't look identical to native DV passthrough. That last point is why fMP4 remux matters. With HLS in an fMP4 container, the original HEVC/Dolby Vision stream can be stream-copied (no re-encode, no tone-map) and handed straight to AVPlayer, so tvOS does true native HDR/Dolby Vision + Match Content. I've got exactly this running on an Apple TV 4K now — DV Profile 8.1 remuxed losslessly, the TV switching into native Dolby Vision — so it's not theoretical. None of this is mpv-vs-fMP4; ideally both exist. But for Apple TV users chasing reference-quality HDR, native remux is the one that looks right. +1 to finally adding it.

And Thorium to rule them all.

I’ve identified a persistent race condition in the tuner handshake process. In environments where tuners require a specific negotiation window, Emby’s current aggressive, automated retry logic creates contention, often resulting in avoidable handshake failures. I am proposing that the tuner retry logic be made configurable—specifically, allowing users to toggle these retries on/off or adjust the interval. This change would significantly improve stability for those of us using specific hardware or custom proxy setups without impacting the default behavior for the rest of the community. Is this something the development team would consider implementing? I have logs available to demonstrate the handshake conflict if needed.

Edge is the superior choice for watching any video as it supports all the formats and therefor doesn't require any transcoding. Firefox is slowly catching up. Chrome does support a good amount of formats but not as many as Edge. Pure browsing is a whole other discussion.

Auto doesn't work anyway and defaults to a very low quality (can't remember the actual quality). Auto should really be called default and not auto.

Holey Moses it is fixed! I have been waiting all this time as a test. All Hail Inter-Dev Cooperation!

I gave up and switched to the Emby portable install, which is a bit more stable.

The two (now three) Roku's that won't work are all remote, and are attempting to use secure connections. (The four working Rokus are all local and using an insecure connection) Using android emby app, or via web, both work remote over the secure connection. But maybe that's part of the problem? The emby server does still mention trying to get something from https from emby.tmsimg.com, but then says it receives a http reply. Could emby server be doing something that the strict roku system doesn't allow in a https connection? Other then that, the emby server logs sometime talk about some activity that completes after the remote connection is closed. So it does appear that the Emby Roku app is closing the connection. EDIT: Nevermind on the response from emby.tmsimg.com in the log. It says http response, but from https://. However, the question of if emby is possibly trying to do something not allowed in strict https:// that causes the emby Roku app to disconnect still remains. (?)

Related? http://videoprocessor.org/lldv https://professionalsupport.dolby.com/s/article/HTML5-Browser-Support?language=en_US

I would like to help bump this up the list. I recently discovered embycredits, and run only Roku's, so I would like to see all the work adding credit chapters pay off.

People use edge? Your globe icons are called "Favicons" typically with a .ico file extension. People use edge?

Buenísimo compa hoy llegando a mi casa llego aprobarlo se agradece mi compa aguante los strm

THANK YOU THANK YOU THANK YOU my Emby installation is shining tanks to your help. Go Emby!

Hey Luke, Just to clarify, the attached file was from the Emby server log, just not all thousand rows but the ones relating to the error. But I've attached the full file here from that crash. Hope it helps and sorry for not attaching the full thing from the start. I might as well have done so embyserver.txt

Whenever I switch the MacOS Emby client to "TV mode" (I can't quite recall what it's called in the menu because I can no longer get back to it), the application becomes unusable. There seems to be some sort of layering malfunction. Attached are some screenshots, it's really hard to showcase because nothing really works--I can't play a video or navigate the menu at all. Please note: This is a Mac Mini M4, but it also does the same thing on an M1 Mac Studio. Emby server: Version 4.9.5.0 MacOS version: 15.3.1