movie.xml

[Steven 158]

Is Emby now using nfo instead of xml? I just added a new movie and noticed it is no longer an option in the metadata settings - unless something borked?

 

[FrostByte 5392]

I believe the default was changed to be more compatible with other systems such as kodi.  There is a plugin called emby xml if you wish to use that

Edited January 6, 2016 by FrostByte

[Steven 158]

The system.xml shows that it's not disabled.

 

<MetadataOptions>

      <ItemType>Movie</ItemType>

      <ImageOptions>

        <ImageOption>

          <Type>Backdrop</Type>

          <Limit>1</Limit>

          <MinWidth>1280</MinWidth>

        </ImageOption>

        <ImageOption>

          <Type>Screenshot</Type>

          <Limit>1</Limit>

          <MinWidth>0</MinWidth>

        </ImageOption>

      </ImageOptions>

      <DisabledMetadataSavers />

      <LocalMetadataReaderOrder>

        <string>Emby Xml</string>

        <string>Nfo</string>

      </LocalMetadataReaderOrder>

      <DisabledMetadataFetchers />

      <MetadataFetcherOrder>

        <string>The Open Movie Database</string>

        <string>TheMovieDb</string>

      </MetadataFetcherOrder>

      <DisabledImageFetchers />

      <ImageFetcherOrder>

        <string>TheMovieDb</string>

        <string>FanArt</string>

        <string>The Open Movie Database</string>

        <string>Screen Grabber</string>

      </ImageFetcherOrder>

    </MetadataOptions>

[Steven 158]

Correct.  I believe the default was changed to be more compatible with other systems such as kodi.  There is a plugin called emby xml if you wish to use that

 

Oh ok. It's not an issue if that's the way Emby is going. I had just rebuilt my system.xml earlier today and wasn't sure if something else had caused it.

[FrostByte 5392]

It will still read your old metadata files, it just won't create them in the old format without the plug-in.  I just went with the flow

[Steven 158]

Yep. I only use Emby/MBT so compatibility isn't an issue for me, so whatevers! Cheers

[Happy2Play 9783]

Not that is should matter, but what versions?

 

I have a system that still using the core xml settings without the any issues.  New installations/Rebuilds have to figure out all these changes on there own.

 

Setting near the bottom of system.xml

<DisableXmlSavers>false</DisableXmlSavers>

Edited January 6, 2016 by Happy2Play

[Steven 158]

Version 3.0.5801.0

 

My DisableXmlSavers was set to true but setting it to false still doesn't enable it. To be honest now that I've noticed nfo's in my TV shows in with the video files I do find it a bit messy compared to xml being stored in a metadata folder.

 

Is there a reason we have to dump xml saving when it's going to be kept for reading?

 

Edit: Emby had just reset the xmlsaver to true. Shutting down the server and changing it resolved it.

Edited January 6, 2016 by Steven

[Happy2Play 9783]

 

Is there a reason we have to dump xml saving when it's going to be kept for reading?

 Probably to stay compatible with other media fetchers like Media Center Master that use xml for primary metadata.

[Steven 158]

So why not leave xml saving alone as an option then? Does nfo offer anything xml doesn't?

[Deathsquirrel 745]

So why not leave xml saving alone as an option then? Does nfo offer anything xml doesn't?

 

NFO files are just XML files with a different extension and, one presumes, a standard internal format.  They changed the default format some time ago just to be more widely compatible.  If I had to guess I'd say the influx of Kodi users with the release of the Kodi plugin/client played a part.