Request Bounty

[Jonathan1683 24]

Would you guys consider doing some type of bounty for added features? I see a lot of things that don't seem to get done, but maybe if there was some added funding or some type of incentive to get it done maybe we can get it done sooner? Some things I would like to see get done are 1. User Request Function 2. Missing Episode native support Report 3.Duplicate movie finder if we crowd funded the most popular features would you guys consider it?

 

Thank you

Edited February 10, 2022 by Jonathan1683

[Sammy 735]

It's one thing to throw money at it. It's a whole other thing to have the trusted people to do the coding.

[ebr 14912]

Hi.  We don't feel that working on features one person may be willing to pay the most for is the right approach.  We try to work on the things that will bring the biggest benefit to the largest audience of users.

[ulanov 10]

This is interesting, and it highlights a dilemma for me (though I know there may be no answer to my dilemma).

Here's a use case: I love Emby, use it constantly, and have become a big promoter on other forums, recommended Emby to lots of new users.  I have learned to appreciate decisions made by the developers as I have gotten deeper into it.  (And I've even been part of calling @ebr and @Luke developer Gods on the Plex forums!)

But there is one big thing missing for me.  I have a 4,000 film library from the earliest silent era through the bright heyday of Hollywood in the Thirties, the remarkable refugee-fueled Forties, and on into the great independent films of the Seventies through today.  Emby only collects and displays in its metadata the Director among the crew, and not, in particular, the writer(s).  This makes it difficult to follow a particular writer or at least as important writer-director (who wrote but didn't direct some films) across their career and the evolution of the movie world.  (Examples: Preston Sturges, Billy Wilder, Francis Ford Coppola.)  This has been mentioned by others in Emby forums before, and the general response has been that (at least some think) adding the Writer isn't worth the additional data space or sorting time.  [In prior Emby builds Writer used to be standard captured but was removed as bloaty; my wish is to see it implemented as an optional toggle, rather than impose it on everyone.]

So, I would be perfectly willing to pay a bounty to get optional automatic scraping of movie Writer metadata.  I'd feel I wasn't imposing my wishes on the Emby community or unfairly demanding that a minority wish is catered for.

On the other hand, I get that in a limited developer world, with the need for quality control, that might not be good.

That's my dilemma.

[Jonathan1683 24]

What about having a vote on the next things to implement? I always see talks of adding things later, maybe we can get a list together. Shoot a email out to users and vote on what they would like to see most. I think missing episodes would be a big feature for everyone.

[rbjtech 4260]

On 08/02/2022 at 16:28, ulanov said:

This is interesting, and it highlights a dilemma for me (though I know there may be no answer to my dilemma).

Here's a use case: I love Emby, use it constantly, and have become a big promoter on other forums, recommended Emby to lots of new users.  I have learned to appreciate decisions made by the developers as I have gotten deeper into it.  (And I've even been part of calling @ebr and @Luke developer Gods on the Plex forums!)

But there is one big thing missing for me.  I have a 4,000 film library from the earliest silent era through the bright heyday of Hollywood in the Thirties, the remarkable refugee-fueled Forties, and on into the great independent films of the Seventies through today.  Emby only collects and displays in its metadata the Director among the crew, and not, in particular, the writer(s).  This makes it difficult to follow a particular writer or at least as important writer-director (who wrote but didn't direct some films) across their career and the evolution of the movie world.  (Examples: Preston Sturges, Billy Wilder, Francis Ford Coppola.)  This has been mentioned by others in Emby forums before, and the general response has been that (at least some think) adding the Writer isn't worth the additional data space or sorting time.  [In prior Emby builds Writer used to be standard captured but was removed as bloaty; my wish is to see it implemented as an optional toggle, rather than impose it on everyone.]

So, I would be perfectly willing to pay a bounty to get optional automatic scraping of movie Writer metadata.  I'd feel I wasn't imposing my wishes on the Emby community or unfairly demanding that a minority wish is catered for.

On the other hand, I get that in a limited developer world, with the need for quality control, that might not be good.

That's my dilemma.

So these sort of edge cases are exactly what Plugin's are there for - to fill the gaps - Emby does have Metadata options for Writer (as seen below) - so it just be a case of re-scraping the data from a source that provides it.  Alternatively, 3rd party media tools such as TMM may even be able to do this for you automatically via the NFO file.  I don't use TMM but @GrimReaper will I'm sure advise if this is indeed possible ..

[Junglejim 351]

LOL... What is this Red Dead. 

I'm not sure this will work with a closed code base like this. I could be totally wrong.

Votes are a good idea but the forum already has that feature, you just have to give your support to the request! Maybe they could expand on that.

Third party media tools like TTM and .nfo files belong to a piece of crap called Kodi! This is a wast of time as far as this apps development is concerned.

 

Edited February 10, 2022 by Junglejim

[rbjtech 4260]

5 hours ago, Jonathan1683 said:

What about having a vote on the next things to implement? I always see talks of adding things later, maybe we can get a list together. Shoot a email out to users and vote on what they would like to see most. I think missing episodes would be a big feature for everyone.

Emby do this via the number of likes on the suggestion - the more likes, the more likely it is to be on the implementation list - but I agree, it's clunky and not obvious what existing 'top runners' already are.  It should automatically have the top suggestions listed - this will also cut the number of duplicates...

[rbjtech 4260]

3 minutes ago, Junglejim said:

I'm not sure this will work with a closed code base like this. I could be totally wrong.

For Core integration yes, it's closed source, but there is a LOT that can be done without the need to touch the core - none of the data in Emby is locked - it's open to extract, edit and change by Emby Plugins or other tools, infact emby make it VERY accessible via the open API.

[GrimReaper 3291]

32 minutes ago, rbjtech said:

So these sort of edge cases are exactly what Plugin's are there for - to fill the gaps - Emby does have Metadata options for Writer (as seen below) - so it just be a case of re-scraping the data from a source that provides it.  Alternatively, 3rd party media tools such as TMM may even be able to do this for you automatically via the NFO file.  I don't use TMM but @GrimReaper will I'm sure advise if this is indeed possible ..

It surely is. 

The Godfather (1972).nfo

Edited February 10, 2022 by GrimReaper
NFO

[GrimReaper 3291]

38 minutes ago, Junglejim said:

Third party media tools like TTM and .nfo files belong to a piece of crap called Kodi! This is a wast of time as far as this apps development is concerned.

That is completely misjudged view, NFOs are widely used within Emby ecosystem as a backup/portability solution - as well as they can be used to completely drive one's library, like mine do. Aside from number of other uses (Collections, hopefully at some point Playlists too).

Edited February 10, 2022 by GrimReaper
Typo

[Junglejim 351]

lol.. if you need to use a crap media tool to get shit to look good.. that's not good!

Some people don't like .nfo + image files sitting on there server with there media.

[Happy2Play 8281]

Everyone has their own opinion, but anything happens to a centralized solution you have to start over if something goes wrong.  If saved with media everything is there to be reused.

[GrimReaper 3291]

1 minute ago, Junglejim said:

Some people don't like .nfo + image files sitting on there server with there media.

That is personal preference (how wise it is not to - that's different matter). That doesn't mean it should be frowned upon. 

[Junglejim 351]

Yea your totally right, everyone has there own system. I personally don't subscribe too yours.

My Docker containers are backed up every night, my media is backed up every week. I manually set my meta how I like it with Emby with just the default db.

I don't see any need to use anything else.

Edited February 10, 2022 by Junglejim

[rbjtech 4260]

1 hour ago, rbjtech said:

So these sort of edge cases are exactly what Plugin's are there for - to fill the gaps - Emby does have Metadata options for Writer (as seen below) - so it just be a case of re-scraping the data from a source that provides it.  Alternatively, 3rd party media tools such as TMM may even be able to do this for you automatically via the NFO file.  I don't use TMM but @GrimReaper will I'm sure advise if this is indeed possible ..

@Junglejim 

"Alternatively, 3rd party media tools such as TMM may even be able to do this for you automatically via the NFO file. "

As I originally said, TMM is there as an alternative and you want the specialised data - if there is no demand for 'Writers' then why would emby spend time implementing something very few want ?

28 minutes ago, Junglejim said:

Yea your totally right, everyone has there own system. I personally don't subscribe too yours.

My Docker containers are backed up every night, my media is backed up every week. I manually set my meta how I like it with Emby with just the default db.

I don't see any need to use anything else.

If that works for YOU - great - many of use use our media storage (with metadata) as a hub for MANY systems, not just Emby - so for us, centralised metadata is the obvious solution.

[Junglejim 351]

Yea I get it. That's cool. I just use Emby.

All good!

[ebr 14912]

1 hour ago, Junglejim said:

Yea your totally right, everyone has there own system. I personally don't subscribe too yours.

My Docker containers are backed up every night, my media is backed up every week. I manually set my meta how I like it with Emby with just the default db.

I don't see any need to use anything else.

Just FYI in case you aren't aware.  If you make customizations to your metadata and/or images and ever need to reinstall your system (say you get a new server machine) then you will likely lose all of these customizations unless you save your metadata and images next to your media.

Your choice, your preference, but just something you should be aware of.

[ulanov 10]

Thanks to all, especially @GrimReaperfor how to gather the Writer info via tMM.  It's a powerful tool.  Working through all the forum debates on nfo-or-not, is also an interesting exploration of database and file management.  I'm going to go the tMM route, as the only way to get the metadata I want captured.  That will be a fair amount of additional work for a 4,000 film library, since not all matches are correct, etc., but for now the only way.

1) It would just be a very nice core function of Emby if scraping all metadata fields on the usual metadata sources could be user-selected or turned off in settings (as with tMM, in the example above).  Across the entire Emby community there must be a lot of users who wish they could auto-scrape within Emby one field or another not currently captured by Emby (even if we don't all have the same field in mind).  Emby gets better and better and incorporating this selective field scraping as a core function - or if someone built a plugin to do it - would mean a user didn't have to find options through this kind of forum digging or take the extra time of the community.

2) On the Writer specific point, I think the key thing is that writers are actually as central (sometimes even more) to many movies as directors and cast (and certainly more than minor cast members), which is why the writer listing is a central data point on lots of movie sites and libraries, and I don't really see why Emby dropped the listing as core, but I respect the devs making judgments even if I don't agree! 

Great thanks again

 

[GrimReaper 3291]

2 minutes ago, ulanov said:

1) It would just be a very nice core function of Emby if scraping all metadata fields on the usual metadata sources could be user-selected or turned off in settings (as with tMM, in the example above).  Across the entire Emby community there must be a lot of users who wish they could auto-scrape within Emby one field or another not currently captured by Emby (even if we don't all have the same field in mind).  Emby gets better and better and incorporating this selective field scraping as a core function - or if someone built a plugin to do it - would mean a user didn't have to find options through this kind of forum digging or take the extra time of the community.

Lend your support here: