Leaderboard

now that is a cat-astrophe

@samuelqwe Holy $#!7 Sam she workin' The code needs refactoring, it's dirty because the finger prints was split up from the encoding. I need to put it all together.

Be able to create playlist based on a certain criteria, like genre and or year, in order to create a dynamic playlist that it refreshes automatically when new content is added. This way you can for example, create a tv comedy playlist from the 90's, or a new sci-fi Movies playlist. Some other criteria for rules could be the rating, watched/unwantched, score, tags, language, audio codec, etc The possibilities could be endless

Hi, I would love to have tautulli or equivalent for emby. Especially for people coming from plex, we would love to see something like tautulli. I know there are a few Statistic plugins but i think we all know there is nothing like tautulli out there. I love the way i see people currently watching movies on my server and the details of what is transcoding etc. i know emby also shows ppl watching movies but it isn't the same. I don't get a notification or even see a icon if someone starts to play while i have the emby page open. There is no icon that shows me someone is watching a movie. Tautulli is also open source so if someone has the skills in python to make it work for emby, this would be amazing. For me this is actually really the only reason I hesitate to switch completely. maybe someone can make this happen

Now for the embarrassing part - I'm always falling asleep watching something - then have a complete mind blank what i was watching the next day until the next episode is out and i realise im missing something. Would it be possible to add a 'recently watched' section where you can see all items you've recently viewed in order? Probably more applicable to TV I guess,

As I mention in a related post, I love the additional subfolders for Movie Extras (eg, Shorts, Scenes, Interviews, etc.)! It would be awesome to extend this functionality to TV Series as well. Specifically to add support for many/all of the same folders supported for Movie Extras, eg, extras specials shorts scenes featurettes behind the scenes deleted scenes interviews trailers As well as any additional folders that get added in the future (eg, hopefully Galleries). Support Placement of "Extras" Folders Within Each Season Folder, Plus A Naming Scheme to Link A Particular Extras Folder with a Specific Episode (eg, "\Season 1\E1 - Deleted Scenes\" for episode 1 deleted scenes): I want to clarify that it would be great if these various "extras" folder types could reside within each Season folder. So for example, within a Season 1 folder we could then have an "Extras" folder, a "Deleted Scenes" folder, a "Featurettes" folder, etc. And furthermore, that we could designate a particular folder to refer to a specific episode (eg, "\Season 1\E1 - Deleted Scenes\" for episode 1 deleted scenes). See more below, particularly why I think this would be so useful: https://emby.media/community/index.php?/topic/55915-emby-server-theater-additional-extrasspecial-folder-types-for-tv-series-similar-to-movies/&do=findComment&comment=587195 Thanks for your consideration! PS - If this is something you might like to see implemented, be sure to "Like" this top/first post (as well as any subsequent posts in this thread that highlight particular aspects of what you are interested in) -- "Liking" the top/first post helps the Devs to know how much interest there is in a given Feature Request.

Recently matroska and mkvtoolnix added support for additional subtitle flags including "Hearing impaired" for subtitles for the deaf and hard of hearing (SDH). Request: Emby add some or all of the additional subtitle flags to media info and also as a choice for playback under user user settings. add support for external SDH subtitle naming (ex. moviename.SDH.eng.srt) Reason: my wife and are are getting older and it seems more and more I'm hearing "What did they say" a lot. If I could set certain Emby users to always play the "Hearing impaired" subtitles if available then I wouldn't have to back up and restart playback with SDH subtitles enabled. Other flags like "Commentary" would be nice also as I have several films with those Having this flag would also make it easier to run a script to list which movies have and don't have "Hearing impaired" / SDH subtitles so that I can go out and get the missing ones.

Emby Theater takes 30 seconds to update - and there's absolutely no indication that anything is happening during those 30 seconds. Please display some kind of splash screen image during the update process.

Maybe there could be an option to show only unwatched media in the "Because you watched..." and "Because you liked..." sections of the Suggestions Tab? Or is there already? Anyway, I'm using the web client via Firefox on a Windows 7 Ultimate machine...

I suggested in a totally different thread a bit ago about possibly adding Discogs as a meta fetcher... https://emby.media/community/index.php?/topic/79280-duplicate-music-artists-entries-how-to-get-rid-of-them/ That thread has had a few +1 reply posts. As such i figured adding it to the feature requests was the proper way to gauge interest. If you have used MP3tag you should be familiar with Discogs. Its a GREAT alternative to Musicbrainz.

hey what I'm really missing is support for audiobooks. Simply saving the resume point for those mp3s would be absolutely enough, no need to fetch metadata etc.

Is it possible to add a bitrate for users that are direct(whatever) something? It's good info, and readily available. Thanks

I recently installed the Emby Android Mobile app on a 10 years old and 12 years old phones and a shared tablet. While trying to teach them how to use the app several issues came up that I thought I would share here. The first image here of the home screen highlights the sections where issues where identified. Section 2 did not come from the kids but is a minor squick of mine that seemed to fit in with my suggestions later. The first issue deals with items in sections 3 and 4, Shortly after I had given them a short tutorial and then left them to explore the app they came back and told me there must be something wrong with the setup because they kept getting sent to the settings screen and they figured that meant something wasn't right. After having them show me exactly what they meant I realized there was nothing wrong but their expectations and some confusing navigation indicators. They thought that the three dots after 'My Media' indicated that there was more content available. The same was true of the 'More' item in the bottom navigation bar. I explained that these were just different ways of getting to settings and the 10 yo commented that this must need lots of setup because they sure want you to do that a lot, I would like to see the three dots removed and the 'More' item renamed to 'Settings', They also had several questions about navigation. The first was how come there was only 'Movies' in the bottom bar and if they were in the movies how did they switch to tv shows. I would prefer that library navigation was not part of that bottom bar. From the 'Movies' library screen I was showing them how to navigate through the libraries using the library name at the top of the screen. When one asked how come the 'Home' item in the bottom bar was green instead of the 'Movies' icon. Told them it was a bug and don't worry about it. Navigating through the libraries was fine on all except for 'Live TV' which did not allow you to pick a different library to navigate to. The second section from the home screen image with the 'Home' and 'Favorites' links has always kind bugged me. So much screen real-estate to let me know I'm on the home screen and a link I seldom use. I would like to see that removed and the 'Favorites' put in the bottom bar, With the various things I mentioned above the bottom bar would look like this: and the changed home screen something like this: The final thing I want to mention deals with item 1 on the original screen image and it isn't specifically an Android item. When we setup the android tablet they were not really thrilled with the user switching process. I've never found it particularly difficult but they seemed to feel that they should be able to just tap the picture, tap the other user and be done. In other words - they want to skip the sign out stuff and just show the user selection screen.

Thank you very much, works perfectly fine here. I totally overlooked that multiple properties are possible in good old AND fashion. LOL No idea why.

Alright, I'll wait to see how it goes now and upload the log when it happens again.

Your icons look fantastic. Thanks again for your support.

GEANIAL @roaku for your support. Now it looks like I expected GREAT ADDON !!! I recommend it to everyone who has several versions of their movies. The icon disc is for the UHDRemux, now I would need to put one for the Dobly Vision, but I can't find an appropriate icon ... Regards

Have you tried identifying it using IMDB instead? (tt0439404). That works for me

No, because i just gave you a use case where that would be needed a couple responses ago. For now, the advice I've given is your best/only option. In the upcoming Emby Server 4.6 release, if you disable a user's permission to remote control other devices, then they won't be able to send downloads to them. So once that is released, that will be your best bet.

I'll PM the build to you with instructions once I have it ready.

Ya, my perception is that this went from a hobby project to an essential part of a bunch of other (paid) software and services too/very quickly and that's catching up to TVDB and everyone that's been able to benefit from/exploit that lack of a business model up until now.

Getting income to pay the bills, you mean? Yes - it's a common way to proceed. Paul

Again, we'd like to see specifics of your issue but, if you do metadata and image customizations, then I hope you have selected the options to save both metadata and images with your media because that is really the only way to guarantee these customizations will persist across a number of different events.

@CondordancerIf you have a hard time to delete a picture, its not like text; you need to look for a small garbage can icon

Yes, having those chapter points would likely be the ideal way to detect credits. A database should always be a last resort IMO, as that’s usually very hard to maintain, but is technically doable. I think currently the focus is intros, but once that is further refined I think it would definitely be interesting to experiment with different ways of detecting credits.

"Hot Wheels Hummer" That's funny stuff!

space time continuum disruption

Thanks FrostByte! Seems your Google skills are superior to mine!

Well the IMDB id is queryable via TMDB and OMDB. You can actually see the queries in your log, but yes. Correct as they want a fortune for their data. Like $150,000 a year. AWS Marketplace: IMDb Movie/TV/OTT Data (amazon.com) Pretty sure it comes from TVDB metadata. Not entirely sure where the Trakt id/link comes from. We had one before but the 3rd party dev abandon it. There are topics out there. As a Community site, just means more users need to do their part for Free data. But I can see TMDB getting hammered as services move away from TVDB. Trakt already has. Only so much one dev can do, but we can hope. None that any 3rd party devs had made available. But at the same time Emby will honor all sites TOS, so any plugin that does not honor that will not be in the Emby Catalog.

The local variant being "You can't please everyone and your mom"

Mount those shares in your OS and then add THAT as path in your Library. Edit: Additionally, you can optionally add those share paths in respective fields.

This is simply asking for better micro-services architecture really, emby's monolithic approach is not always the best strategy for everyone and scaling, for example many people like me dont see things like Raspberry Pi's as viable right now, I would crush one of those with my needs, those only seem suitable for very light users yet Emby targets em.. but if I could scale them out horizontally as demands grow instead of building a huge mega server you know what that would be a really viable option given its got good hardware support. Would really complement alot of features emby already provides, like being one of tho only ones to support bespoke transcoding hardware on lil arm boards.. Three lil Pi's with 2-4gig of ram and a NAS doing netboot, running the database server on flash, and feeding em media would do rather well for most power users I suspect, and then you can scale out to 5 nodes, then 7 and etc if demands grow.. also makes using cheap lil hardware like that in a production a bit more comfortable knowing a hardware failure will have a minimal impact.. For the price of video cards now days we could get a Pi Cluster up and going for a fraction of that.. $350 for a Nvidia P2000 right now, I paid $280 for mine almost 4 years ago wtf.. I could buy 3x oDroid H2+ which have modern QuickSync, sata, nvme and 2.5GigE nic's for that and end up with whole high performance transcoding cluster for not much more than the cost of a basic video card. Scaling out lets people start off cheap and grow if needed, instead of overbuilding and then hoping to grow into it now.. this reduces costs for people wanting to get into Emby. Emby's Docker container that writes to a sqlite db through a bind mount is not really adopting the stateless container philosophy at all, its a poor shoe horn like most other container based services out there.. despite having all inputs and outputs going over the network its not portable if I've got to transport local bind mounts that could also be a standard network transport. One of the features I want most, the HEVC output requires pretty good hardware backing it.. some of the excuses to implementing it have been few have access to the hardware given the cost.. well if we can scale on cheap little arm/x86 boards w/hevc encoders that can handle only 1 job then there's a great solution.. <$50 in hardware per 4k output stream is a heck of a deal compared to discrete ~$400+ cards that can do mebe a half dozen of em. You can look all over github and find distributed transcoding projects for all the major players in this field, emby included, that people try to shoe horn in, the demand has always existed if people are willing to put that much effort into trying to make it happen. However all these implementations are not robust and still have a single point of failure, the main emby database so the extra complexity just makes it more fragile and less scalable IMO. Decoupling the database from a single instance to a multi instance would really, really be a great leap in capabilities that is going to make Emby even more attractive, we're not asking for Emby to support k8's today with s3 storage backends and an emby operator and all that.. hopefully one day, but lets not drag our feet on this thinking containers are a fad, I assure you they are not. I'm not even asking for a particular backend, support em all or just pick one you think is best for the job.. as long as I can fire up multiple containers against it we can start to really scale horizontally and setup HA.

Hi. Sorry, where was that said? That was not what was intended from where ever you saw that. What I stated was that there was no trial period for the plug-in which means that it does require Premiere. We are updating the text in the server. Thanks.

Thank you GrimReaper, I had his account linked to the same EmbyConnect name...I unlinked it and it is now working as it should.

What you described is how the system is supposed to work (and how it does work for majority of users, I guess), Watched status is tracked for each User independently. There's obviously some synchronization going on somewhere. Did you maybr associate same EmbyConnect name on both Users? Do you have some sync plugin, like Trakt?

ah sorry. I should have checked this sooner. As its been a while, i'll post all the logs next time it happens. Ive not had any issues for a while now

Ah I see ok sorry I was being stupid thank you ill do that instead Thank you very much for the prompt replies wow you guys are awesome!

That is a completely inaccurate statement. Your argument based on amount of digital releases is flawed. From what I can find current stats show Discogs out in front. Discogs: 1,581,884 current file releases MB: 534,820 releases without physical packaging MB only has 2.7 million releases and Discogs has over 13 million I admit I am biased because I was in bed with Discogs long before I heard of MB so never really used it much. They both have their flaws and advantages as most choices in life do. My experience with consistent data in MB using Beets has not been good, I use Discogs almost exclusively.

For me not even one of the "points" matter at all. I only use the interface to select media to watch or I use the web interface only to maintain my library and "pretty" matters very little but functionality matters a lot and Emby is very functional. I "watch" my media I do not "watch" the interface. In fact as long as the interface is easy to use, as it is, the appearance of the interface is virtually meaningless to me. I think Emby should not waste development time and resources making Emby "prettier" they should spend their resources improving and enhancing the functionality.

I mean stats alone prove that emby.media is, by far, more popular than other sites out there. Site A has no real traffic stats, its not all that popular. Site B gets lots of traffic. Site A is an ok design for what it does, but its not a media site. Site B has a respectable following, and actually outranks the next most popular media server, I forget its name.... hex? something like that... point is there are A LOT of emby users and the product seems to be keeping them happy, plus the emby team listens to the votes of the majority. SITE A SITE B:

All in all you're fairly new here and you still haven't shown us anything of substance... if this is how you got your projects for your award winning websites or whatever, then I wonder how... I would definitely not hire you on what I've seen here

So you are a fake then?

what it looks like to me is that you have shared some opinions - with little to no backup that things are off trend how about some facts on why you think x should be changed to y - examples would be good - you may get people to agree with you You think your design ideas are good and "correct" - but so far most people have disagreed with you - and they have not lashed out but given their opinions why they disagree Anybody can claim experience in x field - how about you link to your award winning website - if its so on trend it should be obvious - should it not?

I'd suggest you catch more flies with honey but honestly, who wants flies?!? You win more converts with compelling arguments. That's better. 'You all suck, I know, I'm an internet expert' isn't a compelling argument. If you have good design ideas the team will listen. You might want to back them up with some before & after screens showing the improvement. Your screenshot showing your own personal tweaks hasn't been well received but that could be an attitude thing...

All back to personal preferences, I personally don't really see any improvement in your css fix, but that is just me. As mentioned in dozens of topics, there is zero chance of pleasing everyone.

Why do you feel they should be so different? I mean, form factors and input methods have to be taken into account and we do do that - with different layouts for big screens vs. small ones and designing things for linear navigation in TV apps vs. point and click/tap in mobile ones. However, from our perspective, our "web app" is just another app that is, very often, used on a mobile device of some sort (tablet or phone). So other than the above, I'm not sure why the overall design or look of it should be all that different... Now, if we were talking about a web site (which is a marketing or support vehicle) then maybe I'd see more difference but we're talking about an app used to display and play your media.

Just goes to show you can't please everyone.. that's why the CSS function is there... I thought jellyfin was a bad attempt at forking emby that really didn't get any improvements visually or functionally. You love what you have done with your emby.. but I think it looks abnormally plain and a little old-school, and eeewww on the solid green play button talking about outdated web design.. I think emby is right up there with the top commercial media sites and following suit with their webdesign and looks across all of their interfaces, the look is why I wouldn't use anything else! But to each their own glad the css option was included!

I agree. Some people still have Betamax and Laser Disc machines.

I don't disagree with the comment about the same team still contributing. That wasn't the point of what I said. As others pointed out in the thread, the level of transparency has changed, just as the openness of the code. It's not as open as it once was. The very "transparency" that drew people to Emby in the first place. It's not just about Emby code but also the code of others that Emby itself uses like ffmpeg for example. Same with many of the codec and other property assets owned by others. Sure, that's one way to look at it. But when you have open source and encourage people to fork your code, the people changing things you did is part of it. The bad comes with the good. That is the nature of open source itself. Heck just look at ffmpeg and the turmoil it has went through and that's just one small part of Emby itself. I pointed out early to just close source the Premiere features themselves so they couldn't be monkeyed with while leaving all non-premiere code open. That would have been the best of all worlds and would have avoided JellyFin and the "hacking" that took place to un-premiere features. No bad blood this way as the core would stay open, while additions and plugins could bring enhanced or new functionality and of course be charged for. Emby started out as community software. Many users spent hundreds/thousands of hours doing testing, writing feedback, making suggestions doing PR, telling friends, doing support, etc. The current state of Emby is in part owed to these very same people, not just current devs. That is something that often times seems forgotten. Exactly, so if JellyFin and Plex aren't really "competition" then who is Emby worried about running with ideas if Emby was more transparent? I personally don't have an issue with Emby going closed source but would have done it differently (only premiere parts). But it's hard for some users to except the changing nature of Emby holding back what it's working on or going to work on when it used to do this and as already mentioned, probably contributed to it's success. Communication is also one of the biggest gripes Plex users have as well so it's not unique here. BTW, I don't think people want fine grained knowledge of things like exactly what part of code is being worked on. I think it's much more high level stuff people are asking about. For example DVR enhancements and groups/categories for TV Channels have been requested by tons of people and a typical response is that it's planned for the future. We all know that but what does "future" mean? It was needed 3 years ago as much as it is needed today. What I think people want to know with a "road map" is a rough overview of what is planned for the next major release and maybe the release after that. Is the next major release going to have DVR enhancements or will it be the release or 3 after this one? <-- That type of thing. Personally I'd think this type of things would actually benefit Emby. If someone was evaluating both Emby and Plex for family OTA/Cable DVR replacement to lower monthly expenses they may very well choose the package (all else equal) that has announced new improvements in the works. Regardless of any change in "transparency", I just want the team to keep knocking things out of the ballpark with each release! But with that said, I totally understand how knowing what will be in the works can help to plan things for admins.

The same people commiting code when it was open source still are in closed source. Take for example the Roku. The Emby Team is compromised of those same individuals for the most part. Nothing has changed. People get the same exact they did open source as they did closed source for most everything. The only thing missing is now the issue tracker isn't filled with nonsense and now it focused strictly on development, our roadmap, and our plans for the future and how to get there together. It isn't about taking the source away. It is about protecting it. It was being abused. People were not using it the way they should have. Forks were made to damage the Emby brand and take away monetization. There were efforts made to disparage Emby as this greedy big mean monster who just wants to take code others wrote and make a trillion dollars on the efforts of open source. Please.. There were issues in migrate to the new closed source model. And most things are still open that can be. The Roku SG app was never open source. Never pretended to be. The Android TV app I believe is the same way. Same with Apple TV if I believe right. These apps never had public code and if they did the same people commit code to them as open source still are as closed source. I don't get the argument that now people can't fix issues and solve feature requests now that they cannot see the code. They weren't doing that to begin with. Only a few were. Those few are now within Emby Team. The future is together. As far as competition. Emby has really none. Plex is some BORG spaceship out to assimilate all media. It isn't just your media your way with plex. It is their agenda your media their way. They aren't really Emby competition. They serve a different customer. Emby is for the power user who wants more. More control. The customer who wants their media they way. Kodi is the closest competition to Emby. It also has a plugin to allow Emby to exist with it. Together. Together is the future. Kodi is more a partner than a competitor. It takes all kinds of fruit to make a fruit salad.