Jump to content

Search the Community

Showing results for tags 'lockedfields'.

  • 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
    • Android TV / Fire TV
    • Windows & Xbox
    • Apple iOS / macOS
    • Apple TV
    • Kodi
    • LG Smart TV
    • Linux & Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • 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
  • Testing Area
    • WMC UI (Beta)
  • Other
    • Non-Emby General Discussion
    • Developer API
    • Hardware
    • Media Clubs

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 2 results

  1. for some not yet decophered reason folder 'louis theroux' although identified correctly on tvdb is given original title 'louis theroux: miami mega jails'. this mistake infects the trakt link, so i cleared original title field in my emby. but it (incorrect original title) came back on refresh locking the name (title?) field (unticking) does not protect original title field as still blank original title is reverted on refresh. can this work if only i knew better (1st time lock metadata user).
  2. When one has Emby configured to store data in NFO files adjacent to their associated videos, and you then designate certain metadata fields to be "Locked" a XML field of <lockedfields> is added to the NFO file, containing a "|" delimited list of the metadata fields to be locked from editing. In my prior experiments I found that if I added this field to an existing NFO file (ie, one that Emby has already added data to) then Emby would read the NFO and lock the corresponding fields. I mistakenly thought then that I could add this XML field to my externally generated NFO files as part of my migration from a different media management system (my custom-built one). My hope was that Emby would take in the data from my NFO, and then subsequently lock the appropriate fields from further editing. However, <lockedfields> is being completely ignored on import, resulting in no fields being locked (though the other data, such as Tags, is correctly imported). The following is an example of the NFO file data that I'm generating: <movie><sorttitle>Voice Behind the Mouse</sorttitle><plot>Leonard Maltin interviews Wayne Allwine and Russi Taylor, the voice of Mickey and Minnie Mouse. They talk about the characteristics of Mickey and Minnie that they see in themselves. They compare how Mickey's voice changed over the years, even within Walt Disney's run of doing the voice. Allwine and Taylor consider how Walt would probably embrace new technologies of today. Allwine does most of the talking, sharing anecdotes and touching on a wide array of other subjects related to Disney animation. Taylor, his real life wife, recalls how she prepared for her Minnie audition. The feature includes some clips of "Runaway Brain", older shorts, "House of Mouse", and even the costumed Mickey Mouse at Disney's parks, as well. It's a great supplement - both very informative and entertaining.</plot><lockedfields>Overview|Tags</lockedfields><tag>Shorts</tag><tag>Disney</tag><tag>Mickey Mouse</tag><tag/></movie> http://www.imdb.com/title/tt0408316/ Please pardon the formatting -- it seemed best to present it exactly as I'm generating it from my other program. Thanks! 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.
×
×
  • Create New...