Leaderboard

I just wanted to say thanks. While I do say thanks every time I need help I did want to highlight the fact that one of the main differences between Emby and Plex is support. You guys respond quickly, helpfully, politely even when we might be being dicks and the answer is obvious. You never show frustration client facing and having done accounting software support for 10 years I know first hand what we can be like and sometimes the appreciation is never shown. So thank you for being awesome in your dedication to supporting your users. Happy New Year all and stay safe out there tonight.

Disable all internal scrapers or cut internet connection altogether before initial import (which will significantly increase speed of that initial scan as well).

Those remotes were really sweet!

this is the key issue here. we have one app that almost everyone on a android tv device is using because side loading is a power user user thing ( see what i did there). but there are an increasing number of situations where it doesnt work. you have to imagine that there are lots of people that try the tv app, find it doesnt work, and just move on to plex or jellyfin rather than coming here to complain. so you're potentially losing customers. then on the other hand, you have a universal app. only power users have access to it and by all accounts it still looks and functions like a bag of spanners although it doesnt have the playback issues that the tv app does. despite the occasional spurt when prompted, development has again almost ground to a halt. its just a really dumb situation to leave yourselves and your users in. the logic of having one app is sound but youve left us and yourselves in this no mans land of currently both apps falling short. if you want to continue with the strategy of one app, despite the current crapness of the universal app, you HAVE to get it in the store asap and go all in on bringing it up to the level of the tv app. you cannot continue to ignore the situation, just redirecting those that complain to manually sideload.

Can we have an option to flatten series if there are XX episodes or less. Just provides the ability to eliminate one frustrating click. I wouldn't want it on my 1,000+ episode Looney Tunes series. However, when you only have one or two seasons in a series, it helps drill down easier.

Hi, I'm currently looking for a small group of people who would be interested in helping to translate some text commands. This project has to do with natural speech, so it is also about properly translating the phrasing of a commands, as well as the words. The languages I'm looking to translate are: English => German English => Spanish English => one of the many languages of India probably " hi-IN" to start. Please post below if you are interested, it would be great to hear form you

Title.

Plain Chrome

Am I meant to be excited by something here? Paul

It shows things a little different but easier to make edits. Can't remember if it was a plugin/script or not but does MBZ queries also. But is my primary go to.

@Lukemay have to comment as having multiple Artists fields only reads one. Where Picard shows them together ffprobe only reads one not both artist : Anderson .Paak ARTISTS : Anderson .Paak Fix was retagging Artists with both in one tag in MP3Tag. Or full run through Picard. Same for the additional files Dev will need to comment on multiple Artists fields as FFPROBE does not appear to read all, merging them works. Merged Artists so it looks like Composer Since these are M4A files it could be the something with format itself as each container has different restictions/requirements.

I think it means it added a QSV decode preset (for 11th,12th & 13th Gen iGPU) and then in the other section it says it added a SVT-AV1 s/w encoder (fine, this will work on ANY reasonable cpu - albeit very slowly) and an QSV AV1 encoder (for ARC gpu and Gen 14 when they are released.)

LOl, you seem to be fantasizing a bit - we are far, far away from making use of this. Many things need to happen before and it will take years until AV1 HW encoding will be a common mainstream feature. Hardware Intel AV1 encoding is only supported by Alchemist graphics and these cards won't spread out widely as they aren't competitive enough with Nvidia+AMD. Sales figures will be low. No current Intel CPU supports AV1 encoding. It's included in the Meteor Lake architecture only, and Meteor Lake might not even be released this year. But let's assume that it would get released in 2023. Even two years later, in 2025, Intel will still sell quite an amount of pre-MTL CPUs. Until all those CPUs will become outdated and replaced by newer ones with AV1 encoding support, it will take another 3-5 years, which makes => 5-8 years until AV1 will be at a similar level like H.264 has achieved today Nidia, AMD Similar story regarding market share evolvement Clients It's pointless to let the server encode something when most clients cannot decode it, so in this area, it will take time as well The announcement of a new SoC means nothing. It takes time until the first devices will be available which use the new SoC. drivers will need to be written, support for this will need to be added to the Android (Exo)Player, and this will take years as well. Streaming Protocol At this time, it's totally unclear and unpredictable what will be the most common and most widely support way for streaming. for example, the HLS spec doesn't support AV1 (yet) Summary: There are still years to go until this becomes relevant.

I call BS on this (source is Toms Hardware afterall).. if it is using QSV on non ARC GPU's - then it's feeding it via software, it's not hardware accelerated ? Yes, the article is telling nonsense. The editors have misunderstood the information they got (probably a press release). Just think: This is about hardware acceleration, so how should all the older processor models down to Skylake have "magically" acquired the capability for AV1 encoding/decoding in hardware?

+1 having this issue on Android. Was hoping to move all my vacations pictures/albums to my homeserver since I can always remotely collect to display them. But the image quality is really bad. The images look perfect on the SmartTV LG app though.

It would be nice to add external .sup subtitles support

So as an update, I tried again this morning. Chrome and Edge, still no dropdown. Now Firefox all of a sudden has the dropdown and I was able to get parental controls working perfectly. I have no idea why it all of a sudden started working since I have not made any changes yet. But I got it working at least!

It's a "standard" only in that it is used by the programs of this type that we know of. Of course, if there are other media servers that work with different requirements, you're free to use them instead. After all, it's also arrogant to expect a widely used program to make significant non-trivial changes because you're not prepared to use it in the way it was designed. Paul

I could try to help with English => German

Anime has always been weird for me too. I know Emby does it's best, and generally succeeds with standard movies or TV shows, but anime is a struggle. The suggested from @pwhodges about picking a site and matching their structure is probably the easiest way. I know that's how I managed to tame my anime library. I opted to use TVDB as my provider, and I go to the series page and match my layout to theirs. Scan metadata and everything is fine. It's a bit of effort, but it's not much, and the result is satisfying. I stick to two specific formats for episode naming. I personally use "Show Name - SxEE - Episode Name" (the default format that FileBot uses, which conveniently also pulls it's series data from TVDB, so it kind of avoids a lot of problems). I know FileBot is paid, and maybe there are better free alternatives, but I opted to give it a try and found the purchase worth it. Obviously it's not necessary, it's just a major time save over renaming files manually. The second format is the standard SxxExx. Just making sure the files are laid out so that each season is rooted in the same folder, like the attached picture, and the files named correctly will pretty much eliminate all metadata issues with anime.

@unimatrixjohnny Does all your media how Parental Ratings? Does the browser console show errors when you expand the dropdown? (F12)

I guess a dirty way would be use notepad++ and do a find in files Find: <title>The (Ensuring you have the trailing space) Replace with: <title> Filters: *.nfo Directory: library path But would test on single item or create a test library with a couple item. This is something you have to do whenever adding a new item with "The" in title. Or if a coding guru can provide a script to copy <sorttitle> to <title> (but confict if you have custom sorttitles)

With all media moves Emby nuke items in the database and readds. Grims suggestion is the quickest option. Otherwise you would have to hack the database and manually update mediaitems paths, images columns and possibly other areas and each library options.xml folder path. Ensure you have a backup of db before editing. Similar to this minus obsolete TypedBaseItems table.

I installed 4.8.0.21 beta on another machine the other day, but I haven't had a chance to try it yet. I'll give a try later, and if there's no change, I'll wait for the stable version.

The conflict of trying to support/parse everyone's mystery naming schemes as "S1EP06" is an unknowing naming scheme and parsed "2022" as Season/Episode number. In the end it will come back to already documents supported naming schemes. Episode naming conventions

Kids were chomping at the bit to watch so my ability to diagnose had to wait. Turns out it was a single file in the system.old folder for whatever reason it couldn't delete, but I was able to delete it and kick off the upgrade. Feels silly really, I diagnose better than that when I'm at work. Maybe this will help someone else that gets a similar error.

Sorry fr the late reply, holiday season is a nigghtmare for me. I went though all the meta providers and eventually I got it worrking, anidb seemed to be the cause, but I could be wrrong, however it's worrking as it should now Many thanks for the assistance and happy 2023 when it arrives.

Is this true, now I’m intrigued, not sure why lol. Dang I think I finally threw out my last green button remote controls. Those things were sweet.

Folder structure is : series/season/episodes I have sent you the logs again by PM.

Symfonium have no direct control over what ffmpeg command are passed. It just says hey I can play X,Y and Z and set some preferences in the order. Since Opus is a better codec and it's supported, it's what is requested first. Opus does not support 96000 Hz files so it's probably the issue, Emby should set a proper value and pass it. Maybe there's a way for Symfonium to workaround this by adding some arbitrary limits to the initial request, but it should not be necessary. @Luke probably have the definitive answer here (Fix Emby part to ensure that vorbis target encoding is valid if ffmpeg requires it, and give the profile hack to force a 48khz max bitrate only for vorbis if that's what Emby select in the end.

Hi, we can add that but it will be added to the table views of the web app rather than the reports plugin. Thanks for the feedback.

I thought it may have been an accident.... the fact it was on purpose is more worrying. Personally the themes isn't a huge issue for me because I use black but I really don't like the precedent this sets. The themes worked fine before hand so I can only conclude they were removed to make it easier for you guys. Which is fine I guess but you should really notify users of a change like this when making the update announcement, especially when themes are a selling point to get premier, I don't know about other countries but it would be shaky ground with Australian consumer laws.

The lighter themes will be tough but I think it should be realistic to get the darker ones restored (blue radiance, wmc) on older devices. Thanks.

HI, yes you're right. We can look at adding this to the photos tab. Thanks.

No, it can't be done like this. With the LDAP plugin, Emby gets the user name and password of every user who logs on in clear text and the server attempts to log on with these credentials at the LDAP server. Such procedures are totally forbidden with OAuth/OIDC. It is a core feature of those implementations that you must and may never give your password to any 3rd party. You only sign-in at the site where the account is from that you are using to sign-in. There are multiple authentication "flows". The most typical one is browser redirection, which means that a client app needs to redirect you to the web site that has issued your account. Once you have logged in there, you get returned to the app, while in the background of this procedure, tokens are exchanged between the 3 parties: The app with the issuer website, then the app with Emby Server and eventually Emby Server itself with the issuer website. There's also a "flow" for devices which cannot redirect (because they aren't browser-based): With the "device flow", the client tells the user a website to open (separately, e.g. via mobile device), the user logs on to the website and gets a numeric code, which it then enters into the client app. The rest is the same like above. Assuming Emby Server (and all clients!) would support this, there are additional caveats: The Emby Server needs to have a DNS registration of your own domain (no dynamic dns) and must be continuously and reliably available As an owner of an Emby server who wants to set this up, you need to go quite a way to get this working: You need to open a developer account with the sign-in provider through which you want to allow users to sign on to your server And you need to do this for every sign-in provider you want to suppport. For example: you want to allow users to log in with their Google accounts, Facebook accounts, GitHub accounts and Microsoft accounts With all of them, you will need to open a developer account and then, you need to register your "app/service" (=Emby Server) for OAuth/OIDC authentication The procedures are quite different with all of them and the data you get and will need to set up Emby server accordingly looks differently, and it's quite a process to get it all figured out Finally, there's another complication: when you want to allow users to log in with their Google accounts (for example), that doesn't mean that you want to allow everybody with a Google account to log into your server, which means in turn that you need a mechanism for selection. Possible methods are By invite link you actively send invites to users you want to allow Approval Queue Users who authenticate the first time are put into an approval queue where you regularly need to grant or deny access Probably the most simple one is to only allow existing users (who already have a normal account on your Emby server) to also set up a 3rd party login for their account. I have done all this for a (yet unreleased) project, and what I can say is that it's nice when it's working, but it takes a little effort - and I'm talking just about the setup that users need to do.

While most power outages of a few hours are surprises, I would guess that those that last for days would be weather related. Does that sound like a valid assumption? If it does, could there be a validate button available so that one could check-in to Emby's servers when the weather is predicted to be bad enough to possibly cause a power loss? What would be the challenges to implement that?

I actually quit using plex and came to emby for this reason (since then i know how to make plex work when logged in should internet die). In winter it is not uncommon to loose power for days at a time. Yes i have backup power but internet is dead. There has to be a way for emby to verify a lifetime license with the average type user in such a way as to be secure on a more permanent basis so that the server will not go down at the worst time possible.

Bumping this rather than starting a new thread. My expectation when I saw that Emby supported multiple folders for special features was that each supported folder name would have its own strip under the movie in the client app. If you just did the main 'extras' folder, that's all you'd see, but if you took the time to break your special features down by type and put them in a corresponding folder, you'd see the results of that effort in the client app. After I didn't see what I expected, I looked into it more, and it seems like the alternative folder names are just there to accommodate content generators with their own established folder structures. But..I'd really like to see special features get that grouped presentation I originally envisioned. And maybe someday, their own dedicated tab where you can watch special features by type across movies and other fancy playback options.

Handbrake HA AV1 on Intel only. HandBrake 1.6.0 Debuts AV1 Transcoding Support for the Masses