All Activity

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

Hi @MarvinB sure my english wasn't very clear. TLDR the issues were not possible to reproduce 100% leave it with me i need to do more testing. What i do know for sure is that If you issue [or have interpreted through little fault of your own] "Alexa, stop|pause|resume" commands as opposed to "Alexa ask ear wax stop|pause|resume" commands you can find yourself in a situation where Echo A is controlling Echo B. I think i need to troublehsoot harder trying to be sure (although there is no 100% way) that the skill version of stop|pause|resume is being invoked. (And i assume the same could be the case for Emby Alexa). Any clarity that can be shed on the architecture might help but accept appetite might be limited for that until an issue is shown/reproduced.

I have been moving my numerous local drives over to a NAS raid box. I took my custom TV series "Dallas Cowboy Games" where I have all their wins from the 70s til now each in their own season folder from inside J:\TV1\NFL\ to \\NAS\Media\TV\NFL Because I have not removed the old J:\TV1\ path from my library Emby still sees it with all the custom work I did (images, dates. descriptions, etc) and it sees the \\NAS\Media\TV\NFL as "Inside the NFL" Is there anyway I can "Identify" the new location as my custom series without having to go through all that work again?

Seems to be a basic function that has long been overlooked.

Yo respondo yo probada la versión no beta y funcionando sin problema

Unfortunately, after enabling logging and debug logs, there is no option to send the logs from the Home screen or in the settings. I sent the logs to sa2000 and I will upload them here. These logs are for Google TV: Emby for Android 3.5.36 > EmbyServer 4.10.0.14 beta for my public facing EmbyServer. No longer plays movies with Error: Object reference not set to an instance of an object Emby for Android TV 4.9.5.0 > EmbyServer 4.10.0.14 bets for public EmbyServer Plays everything fine, but does not have the subtitle options: adjust placement or adjust timing. LOG: Emby.Server.Private.Home belongs to my private home use server. Previous.Logs.0.4.10.0.14 beta.txt embyserver.4.10.0.14 beta.txt Emby.Server.Private.Home.txt

I was responding to ebr's comment about Emby's 'normal use' about built-in OS integration. Maybe I misunderstood ebr?

Yes I'm aware of that setting and it's nice to have but it's also applied across all devices. I don't want my users burning through their mobile data when watching on their phones because I set Auto to 20 Mbps.

The lower x applies the execute/search permission bit to all the directories and files specified in the command. The upper X applies it to directories (needed) but only to files which already have it set for other users/levels. In other words lower x makes all files executable and upper X only does it for files which already were and ignores others, like media and metadata files. It's a cleaner and safer approach.

Admins can in newer versions of Emby force auto to be what they want it to be. With it set, you can by the power of deduction know if it is a manual setting.