Jump to content

Search the Community

Showing results for tags 'Community'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 3 results

  1. I'd love to figure out a way to solve a problem with scraping in Emby. I am finding that Emby never scrapes all of the actor images for movies that I import. And I'm not talking about indie movies, I'm talking about AAA movies with big name actors. It will always find some, but never a complete list. So part of my work-flow for importing a movie is to go back through and manually search for actor images and cards and fill them out myself. I'm a completionist, and having gray cards for actors is a no-go for me. Hopefully I'm not alone in this though. I think that the issue is that the current databases that Emby can scrape are limited. We can't scrape IMDB, so we're left with databases that are incomplete. How about we create our own Emby database and leverage the work that people like me are already doing? What I'm envisioning would be an opt-in sort of thing. I realize that not everyone would necessarily want to share their custom images and/or metadata. But for those of us that would be comfortable doing that, we could create a new Db to potentially fill in the gaps. Over time it could become much more complete than what's currently offered. I'm not talking about replacing the TheMovieDb or Open Movie Db. This would be something to compliment those and to fill in what they lack. It could even be something like this: You upload an Actor Picture and you're presented with a checkbox to add it to the Community Database. You check it and that image is uploaded and connected to the profile in the database for that actor. The same could apply to any Metadata that is currently scraped in Emby. Anytime someone creates something, they get a checkbox to add it to the Community database. By default the Community Database could be the last option for scraping data for content. So if it's not found in the official databases, then the Community database is scraped. I hope this makes sense, and I'm hopeful that I'm not the only one that would be interested in contributing to something like this.
  2. Is it possible to get some clarification on the openess of the code and continuation? First of all: I was not able to find some kind of trial for the premium version. I suppose it is possible to set up some kind of 2/3 day trial so one can test the DVR features etc over a weekend. I prefer that then to get one of the hacked versions.... (and I never paid for a trial). I read quite some confusion on the openness of the code. Is it possible that Emby specifies which parts are open (and to which version) and which are closed? (in accordance with GITHUB's policies etc). Personally I would love to have something open even if I pay for it initially to get into the community. Maybe you can make it 'community open source'. I saw concerns about the restrains of the lifetime license; if it was community sourced that issue would disappear. Emby could also promise that once a new version comes available for where an upgrade of the license is required that the existing code will be available for the lifetime users. (this would of course limit the active involvement of the community during the normal lifetime). In both situations you could specify that all code that was proposed by users can be used in the next version without the version being open (of course the code itself would be usable in the initial product where the code would be available for existing users). I think that would benefit both Emby as the user community. One of Emby's advantages is that it is/was at least partly open and I think that there is quite a group of people that prefer to pay for/support that instead of a totally closed source variant. The restriction of the number of devices can also be an issue for personal use. If you have a family of 5 and when each has a phone, tablet and pc you are already at the max and cannot have the general TV etc connected. Maybe an idea to make it unlimited for personal usage or at least extend the number of devices for personal usage?
  3. I just want to say thanks to Luke and all the other developers out there that are hammering away day in and day out on updates, squashing bugs, responding to the community, and just being all-around great guys. Your time, talent, and effort means so much to me and the community. This includes those who help out on the forums with support issues, and all the other stuff behind the scenes. I have to say... you guys impress me all the time with your expertise, care and concern, and even how patient you are.
×
×
  • Create New...