Leaderboard

Ok thanks for clarifying and lo and behold I see it now Hmmm that's not great, bust be a bug.

I searched but couldn't find a similar request. If one exists with or without all of the options below then please lock this one and point me in that direction. Now that all users are required to login with username and password at least once on each app/device it would be nice to have the option to use a one time password (OTP) for the initial login on any device but mainly TV apps and streaming devices where it's difficult to enter long strings. It doesn't need to be limited to initial login but should at least allow that. 1. Allow any user who is already logged in to an app or browser to generate a one time 4-6 character OTP for themselves to enter on a new app/device in order to login on said app. This would only log them into their account using the single OTP. 2. Allow an admin account to generate an OTP for any specified user to login. This would be useful for Emby admins to help remote users, particularly those who have difficulty with apps and on screen keyboard-remote combinations. Or to help household users while away from home... 3. The generated OTP would be associated with the corresponding user, either self or assigned by admin. No need to enter or select name on the app login screen, the OTP would suffice. 4. The OTP should be created with a short time to live, either fixed or configurable. I don't know enough about Emby Connect to suggest how it should/could work for those users. EDIT: Evidently Jellyfin has a similar feature called Quick Connect but I don't know if it also has the ability for admins to generate codes.

Just subtitle plugins are the source provider. In the catalog

Sort of an either or when it comes to subtitles or forced subs. As it is a per library setup option.

@Q-Droidit is the downscaling. 21:46:27.801 Stream #0:0 -> #1:1 (copy) <-- I don't understand the multiple mappings here >>>>>> Video Processing Steps for [0:0]: H.265 (HEVC) Step HW-Context Format SW-Format Size Next HEVC >> CUDA cuda nv12 1920x1080 >> scale_cuda scale_cuda >> CUDA cuda nv12 1280x720 >> setsar setsar >> CUDA cuda nv12 1280x720 >> But ffmpeg changed from 5.0 to 5.1 between versions so whatever changed has cause issues like this and may other per other post. But specific conditions are needed to fail as it does not affect all media or servers.

I mostly agree that it was a bad change but it does not impact TV viewing at all. All it effects is the ability to know what is not available. I have found that it is very useable in the form that it is in it just has to be used differently. As far as the feature being where it is hard to find, that is mostly true but there is not a place that would be better for the purpose than what has been chosen. The purpose I allude to is simply knowing what is missing. While browsing is a location that seems to make sense but I do not think it really does for most people. My usage, which is probably very different from yours, does not really need to know what is missing when I am watching but it does when I am trying to perform library maintenance. BTW: I am 95% sure it will not get changed back so I think it is better to learn how to use what we have than complaining about it.

You can use subtitle edit. It will convert between different formats (over 300) with no problem (image based subs like PGS will need you to confirm what letter is what). It can also use AI to create subtitles from the audio.

@Gilgamesh_48Like this

+1 for specific part 1, for users logging in on devices with a OTP. As said jellyfin also uses such a feature which works so much better then logging in with your credentials.

For clarification: In my case, even if an episode description exists in English, it's still displayed in the TV show's original language. (Sorry about the broken screenshot; HDR issues.)

The want lots of money for the precious data. AWS Marketplace: IMDb Essential Metadata for Movies/TV/OTT (API) (amazon.com)

@mickle026I have replicated the problem you are having with multiple tabs and it's all my fault. The fix may be very simple. I plan to test it tomorrow. Vic

Emby doesn´t do HDR and Dolby Vision on the Apple TV. Plex does. Infuse does. So, until Emby for the ATV supports HDR/DV, it can never win.

Yes, it should.

@Zoomer88Could you give the latest beta docker image a try? I added a `IGNORE_VAAPI_ENABLED_FLAG` env variable, setting it to the string `true` should pass the associated flag to emby.

Forced subs works in 4.8 - you select it in the library subtitle options.

hI, yes, it is in the library settings where you enable automatic subtitle downloading.

Thank you to everyone who took the time to ask the Emby team questions across all of the different platforms including here on the forums. There were a lot of great questions that were thrown our way and we've been excited to get the answers out to you. While some of the questions we were not able to answer, we did our best to give you the most accurate and clear answers possible. Now without further ado, here is the first series of questions and answers for you to look over! Please keep in mind more questions and answers will be coming in additional blog posts in the coming days, so not all questions are being answered today. Who owns Emby? Emby LLC owns the Emby product and is a private entity. The owners are undisclosed but note that the development team has full control over the direction of the product. We are not beholden to or under the influence of any investor or investment group. What is the history of Emby? Emby grew out of an open source project called MediaBrowser. Emby's origin in concept came out of that project but there is actually none of that code base still within it. Emby ended up being completely built from the ground up to be a server-based ecosystem as opposed to just a single app as the old MediaBrowser was. Around 2011 what is now the core development team for Emby were contributors to MediaBrowser. We saw the opportunity to build something more flexible than the WMC environment would allow and embarked on creating what we then called MB 3. The core developers spent over a year furiously writing code before anything was released to the public. It was then probably another two years of dedicated development before anything was truly usable as a system. In 2015 it was decided that we had moved so far away from what MB originally was that we needed a new name. A few of the devs got together and came up with "Emby". There are a few reasons behind that name but one of the main ones was that you needed something that wasn't already trademarked and domained. Emby fit that bill and has the benefit of sounding like "MB" when you say it. With the new name, we needed a new logo and we actually held a contest in the forum taking contributions from users and that finally landed us on the logo you see now. Since 2015 we have expanded the team and worked diligently to try and continue to craft the best truly personal media server system we can. We still have a long way to go but have also come a long way to where we are. What are the most popular Emby clients? We do not have exact data on this, due to sideloading and the such, but through the app store platforms we can gain general ideas. Android is the most popular amongst our userbase (both mobile and TV) with iOS in second place as the most downloaded app. What Emby clients do the development team use most for personal use? Our development team uses a wide variety of apps just as our user base does. We have people on the team using Android on mobile and TV, iOS, Apple TV, Roku and Xbox as well. As you can see our dev team really is as diverse as our user base when it comes to how we use the server. These were just a few of the questions about Emby as a product and who we are. In the next blog post we will be covering a few different things such as some of the future goals of Emby as well as release schedules and more! View the full article

Hi, yes we'll look at improving this. Thanks for the feedback.

As someone who uses a password manager and 32 character passwords, this would be a godsend.

Honestly, emby should take this off the marketing site. It shouldn’t be advertised in the current state. I also purchased a premier license and this was a motivating factor, but these trailers are not watchable. If there is no solution, it shouldn’t be a feature. If manual trailer videos is the only solution, it should be clearly stated in the marketing info about the feature. I.e. “Trailers like the movies! (Downloading trailer content required)” Great server streaming platform with a ton of great features, this is a small blemish, but one all the same.

Apple TV only uses Atmos EAC3, used in streaming services. Most Atmos content is TrueHD, and that is not supported by Apple TV. If you need Atmos TrueHD you should use another device.

I did not say but i thought it was rather obvious that my question was pertaining to browser operation. I use my Rokus for watching content but i use my browser for virtually all library maintenance. I wanted to be able to see the favorite indicator on all movies and not just the one my mouse was hovering over. That is I want the favorite indicator to be on all the time IN BROWSERS. My Rokus are very good for watching but they are unsuited for library maintenance. Again I thought it was obvious from my question that I was asking about browser interaction particularly the fact that I mentioned the grid and the mouse hover, which does not exist on the Rokus. I sometimes think Emby people are chosen for their ability to misunderstand simple questions.