Search the Community

I am new to Emby (since Synology is dropping support for Video Station). I setup Emby SERVER, and gave permissions to the appropriate shared folders in my video library on my NAS. It is finding my new content/additions OK. However, there is an instance where I have both the original film (1987) AND the remake (2009). However, Emby has identified both films as the 2009 version, even though the actual file names are different (Movie name & Movie name 2009). I went to the EDIT metadata screen. I found the section with the external database references (IMDB, etc). Clicking on the icon on the right brought me to the IMDB website with the (incorrect) movie showing. I did an IMDB search for the proper movie & copied the title reference, then put it in the IMBD field. I deleted the other external database reference numbers & saved my changes. However, all the other metadata remained unchanged. In Video Station, there was an option to do a manual search, which produced a list of possibilities. When I selected one of those movie titles, the metadata would repopulate with information appropriate to my selection (title, actors/directors/writers, description & thumbnail images, etc). Is there a way to do that in EMBY, so I don't have to manually edit every metadata field for movies it incorrectly identifies during automatic indexing?

I'm running into an issue getting metadata and images for content being added to my library. The short-short is that it works fine when I first start emby but at some point, the indexer (such as Fanart.tv, TMDB, etc.) starts blocking ("connection refused") the requests. Most of the time, powering off the box for a couple minutes and then bringing it back up clears the problem for a time. Sometimes connections are still refused and the restart process has to be repeated. The frequency in which this happens ranges from hours to days and I'm struggling to catch a correlation between the incidents and library change volume. This seems like a threshold issue in that my configuration is generating too many requests, but I'm not seeing it. Libraries are configured for real time monitoring with advance pulls. Looking at scheduled tasks status' I see they are only firing when content is added. In reviewing my configuration it also raised a question or two. So, here I am, asking for advice from those who love and know emby on what I'm missing and how to correct this. For the questions, the 2 biggest are; 1) How does emby generate/maintain API keys for the various indexers? In looking at several generations of the server logs I see that the key is consistent for each indexer. Is the key unique to each emby installation or shared by all installations? The latter could be significant in my configuration as I route most all of my internet traffic, emby and otherwise, through a commercial VPN. My ISP knows enough about me and my family. They don't need to know more. 2) Is it possible to use my own api keys for the indexers? If so, how? NOTE: I'd really rather not have to go this route. SERVER INFO: NOTE: All external requests do go through a VPN Thanks in advance for any assistance you all can offer.

Hi everyone, first post here so I hope this is in the right area. I just wanted to share a bit of an idea to gauge interest and opinions from the Emby community. Myself and a few friends are all loyal Emby Server users but have always had the problem of having to manually manage metadata for content we like to have available on our media centers, but is not indexed on The TVDB. This is content along the lines of: Sport (WWE, NBA, UFC) Adult films Training and course videos (CBT Nuggets, Linda, Khan Academy) Youtube videos / channels Music Videos Unfortunately with the TVDB's policy on some of the above, we have had to manually produce the metadata and generate our NFO files. To remedy this, I had thrown together a database / API and developed a quick and nasty scraper that would retrieve the data from our DB and generate the NFOs for us. This has been working quite well for us but unfortunately the metadata still had to be added and maintained in the database by the handful of us using it, which has now lead to the idea of making a more public database/site/api that everyone can use and everyone can contribute to. The idea, outside of what we use ourselves currently, is definitely in its infancy but it would essentially be a DB for everything else. So with that said, I thought I would just put this out there and see if there was any interest in the Emby community for an additional indexer/database.