Leaderboard

A more reliable way to ensure proper matching is to include the TVDB ID in the folder name: /Duck Tales [TVDBID=75931]/<season folders>/ I switched to using these with all media and now have 100% success identifying media first time.

I’ve seen this on multiple Rokus with multiple users. No matter what I set in the webUI from my phone or PC, in Roku it will default to the Suggestions section within each library every time

Hello if possible to make a cut out tool to choose were to view the spotlight for example, here is a background image: i want the spotlight to be more in her face (up) but here is the result just to image it tt The red line is the cut out in my pc / android devices the blue is on my tv (emby for android) as you can see in the first image , only her nose is showing if possible, to choose to move it up or down and if possible, to preview in deferent devices other than automatically cut out the middle part in my tv is showing like this the border is only showing:

Thank you all for your help and assistance . At my age I decided there was just to much to learn and do. So I have returned to windows 11. And Emby Installed on that as easy as , no fus.

I agree. Everybody should be able to find their best compromise. Sometimes you feel it landed a bit one sided. Like your side got nothing, and the other side got their way. That is why I choose to avoid making decisions that way and find a way to code in something that pleases both sides. Having it card style spotlight diminishes the spotlight. Its just a card. Having the spotlight as fullscreen removes that card. Then you see the full image as expected. The bottom portion might be shaded a bit. But otherwise you should get a cleaner look without having other stuff in the view. With card style other cards to the left and right are there. Small slices of those other cards. The fullscreen style that isn't happening. It just provides a very clean way to show the spotlight. Allowing the image of the card style spotlight to also get changed to a different style would also be interesting. Because then the style of the card would dictate more the size of the card. You would need several sizes of the larger hero card to fit each different type of image. Since you wouldn't want that placeholder to show. Even then you couldn't predict some oddball images which would produce the placeholder effect. The zoom eliminates the oddball images and placeholder effect. That is why it was done. Because it was easier? Sure. Because it was the best way to do it? Sure. Because it isn't finished yet? Sure.. You can say that too. That is likely what happened. It just isn't finished yet and we are blaming it for things that haven't had time to be incorporated yet? Maybe? Probably? I am guessing so. I know lots of stuff has to get worked on at once and at the end of the day you only can do so much. So only so much time can be spent on certain things without other stuff falling behind. Lots of moving parts and you have to move with them. Eventually the spotlight will get something better and even I am unsure of what that may be. The future will tell us what that is. User demand will too. Your posts will help decide too. Thank you for the input.

The alternative to scaling with zoom, is scaling to fit. Scaling to fit leaves those black bars on the sides. The placeholder is visible. The row items all have placeholders behind them to separate their container from the others. So the images if they do not fit the exact dimensions of the container it will show portions of that placeholder. To prevent that it is using scaling to zoom. The spotlight could allow different image types to be used, but that over-complicates what should be a simple feature. I think having it allow a full-screen backdrop too would do just that. Adding the setting to select the different image would be used by a slim minority of users. Most wouldn't even be using the spotlight because it has to included by the user running the server. Even getting the spotlight added is just for a slim minority of users. They do not even know it is there. It would need to be enabled by default with a row or something to get them to know it exists. That might be needed to get them up to speed. How many enable the spotlight and know how to do it? How many after doing that would prefer a full-screen backdrop spotlight style over the standard hero row card style? How many wish they could change the style? How many wish they could change what type of image is used? It is a good idea. But this would have to get done on the server (web app) side either way. It has to start with change somewhere. IMO... Having the server (web app) go directly to having a full-screen spotlight style option would be more beneficial than just changing what image shows up on the hero row spotlight style. After that I can see perhaps extend the spotlight to allow more imagetypes to appear in the hero row spotlight style. But the full-screen should always be using the backdrop since its designed for that purpose. Just my opinions, not the entire Emby team or anything. My opinion doesn't carry more weight than any other. We code for whichever way the ball falls. If it lands one way that is what is done. We will code it however the team wants it done.

Oh okay. And i've always thought the problem is the video stream does not play at all, but only the audio stream. But it's just hidden by some UI stuff?!

This is all more or less by design, because with "Native (Live)" the videos are really treated like a live tv stream by Emby - with all positive or negative side affects.

I admit. That does look good. The glowing ball to indicate the index position you are in the row. The balls indicate total items in the row. It does give a good look at much more of the backdrop this way. All the apps should have this. It is that good. I agree.

This is from the Android TV Beta and it looks so much better that the android and web version I have seen.

Would it be difficult to implement a feature to allow transcribing a video podcast to audio-only, for listening on my phone? If a podcast has both audio-only and video formats, I typically choose the video version for archival purposes. When downloading these to my phone, it would be nice if I could choose 'audio only' under the transcribing quality, so I could continue listening with my screen off. I'm sure this would not be a widely used feature, but if it would be trivial to add it would be cool to have.

user data is based on external ids, so yes, if they are not grouped as multi-version then this could result in duplicates in continue watching.

I want to add a second sort order for music on the Emby web APP, just like iTunes. The first sort order would be by album artist name, and the second sort order would be by year. When the album artists are the same, it should sort by year. How should I modify the Emby Server configuration file? The above inquiry was translated by AI. Please excuse any errors.

I went with Emby for my media server because it was open source, the devs were really responsive, and there were lots of good community plugin developers. None of that is true anymore.

I've been saying this exact thing for so long as well. I'm actually surprised more people haven't pointed this out because it is so goddamn annoying to keep getting these vague, uninterested and generic responses from Luke. Too many people are treating this like a Jellyfin forum, thinking that the devs at Emby are "doing us a favor" by providing this service. When in fact the opposite of this is true. Simply put, this is still a business at the end of the day. We paid for a product and expect said product to work, or at least have these problems resolved when they are reported. If not for lack of options I am certain that most of us would abandon Emby in a heartbeat, myself included. These people get away with treating their customers like crap only because of lack of competition, but all things come to an end one day.

well that’s what i get for reading posts on my phone in the bathroom can’t believe i missed that one. that worked a treat. thanks

Is there any chance this will fixed soon? Thank you!

I am in active development of an MCP server that could be used with any local or remote LLM, local works almost with all lmstudio llms, mostly testet with gemma4:E4b. At the moment it allows to run all of the scheduled tasks, and search for any file. I also wrote my own voice assistant and since lmstudio also connects the mcp, voice control also works. I will attach the github repo as soon as I think it's ready.

Playback history is recorded by provider ID (IMDB, TVDB, TMDB, etc). If you remove a movie for example, then re-add that same movie by either re-adding the original file in a new location or adding a whole new file that matches the same movie; it'll still be marked as watched. In short: you can move your library and re-scan the new location without worry. It'll keep the watch history.

Neither do I with the latest version. Web app still shows it, though. Maybe @Lukecan offer some insight.

The css over here will do the trick.

@quickmicSync, looks good thanks, still struggling with the layout and downloading, but I'll check your FAQs and Guides and see if there's anything of help there, if not I'll start a new topic. Thanks, Bob

So in your extended and detailed reply , we can expect that if "external" app does transcoding or watching live tv, that device is not counted in premiere limit ?

But here's the thing. There is no requirement for an Emby user to be linked to an email address. The email link that does exist is for Connect and there is an email password reset for that already. So, not only would this require a proper authorized email smtp setup, but also another email link to the local Emby user. This also presents a new attack vector.

How should that work: Release date equal or newer than 2026 but older than 1900?

They are a strategic partner, meaning there is likely revenue sharing involved. That was one of the key topics back when they had the form to become partner. So no, it is not that simple that because app X is on the platform then anyone else can just build and app and get published.