[steve1977]

Using latest beta and struggling with one thing.

My posters are in the format "poster.jpg" and my fanart in "fanart.jpg", which is the official Gotham naming convention. Unfortunately, EMM does not recognize this - probably because it uses an alternate Frodo/Gotham naming convention?

I have tried to use the "expert/custom" convention, but this does not work at all. When changing to "custom/expert" and saving the configuration, it just automatically switches back to XBMC mode again.

Thanks for your help!

[DanCooper]

We always use the "export DB filenames" for default settings:
<moviename>-poster.jpg
<moviename>-fanart.jpg

But you can also add new filenames in expert settings, like:
poster.jpg
fanart.jpg

If you have added new settings to file settings, you need to reload all movies to recognize the new filenames: Tools -> Relead all movies.

[steve1977]

Thanks. I have tried the expert mode, but there appears to be some bug with it. I change to "use" expert mode and then press apply/ok. When I re-enter the settings, it is back to XBMC.

This may be related to error messages popping up upon startup and also upon leaving settings?

*** Failed to convert 1.81:1 ***
*** Object reference not setup to instance of an object ***

[AnthonyJS02]

Thanks. I have tried the expert mode, but there appears to be some bug with it. I change to "use" expert mode and then press apply/ok. When I re-enter the settings, it is back to XBMC.

This may be related to error messages popping up upon startup and also upon leaving settings?

*** Failed to convert 1.81:1 ***
*** Object reference not setup to instance of an object ***

Make sure you have fetched a language under tv settings. Appears to be the error that pops up when that's not set. That should let you save all other settings.

[DanCooper]

*** Failed to convert 1.81:1 ***

Rescrape all metadata to solve this error.

[steve1977]

Reads like both of the errors are unrelated to selecting "expert use" disappearing upon exiting preferences. Can you validate that you can switch to "expert use" and it "sticks"?

[DanCooper]

Reads like both of the errors are unrelated to selecting "expert use" disappearing upon exiting preferences. Can you validate that you can switch to "expert use" and it "sticks"?

If you have the error "Object reference not setup to instance of an object", no settings and advancedsettings will be saved.

Please read the hints i have wrote in the release thread: Link

[redglory]

EDIT: created another thread here

[steve1977]

*** Failed to convert 1.81:1 ***

Rescrape all metadata to solve this error.

Thanks Dan. I would prefer not to over-scrape them. I am using MBS in parallel and MBS creates the XML/NFO for me (I am using EMM for posters et al). Can you take a look what EMM produces and why this results in this error message for EMM. I can imagine the MBS devs may be willing to fix it of this is wrong how they create the XML/NFO files for XBMC.

<video>
<codec>h264</codec>
<micodec>h264</micodec>
<bitrate>13453496</bitrate>
<width>1920</width>
<height>1040</height>
<aspect>1.85:1</aspect>
<aspectratio>1.85:1</aspectratio>
<framerate>23.97602</framerate>
<language>fre</language>
<scantype>progressive</scantype>
<default>True</default>
<forced>False</forced>
<duration>85</duration>
<durationinseconds>5074</durationinseconds>
</video>

[steve1977]

Any thoughts?

[DanCooper]

*** Failed to convert 1.81:1 ***

Rescrape all metadata to solve this error.

Thanks Dan. I would prefer not to over-scrape them. I am using MBS in parallel and MBS creates the XML/NFO for me (I am using EMM for posters et al). Can you take a look what EMM produces and why this results in this error message for EMM. I can imagine the MBS devs may be willing to fix it of this is wrong how they create the XML/NFO files for XBMC.

<video>
<codec>h264</codec>
<micodec>h264</micodec>
<bitrate>13453496</bitrate>
<width>1920</width>
<height>1040</height>
<aspect>1.85:1</aspect>
<aspectratio>1.85:1</aspectratio>
<framerate>23.97602</framerate>
<language>fre</language>
<scantype>progressive</scantype>
<default>True</default>
<forced>False</forced>
<duration>85</duration>
<durationinseconds>5074</durationinseconds>
</video>

Aspect ratio is now calculated by width divided by height:

1920x1040 = 1.8461...
16:9 = 1.777...8

[steve1977]

Rescrape all metadata to solve this error.

Thanks Dan. I would prefer not to over-scrape them. I am using MBS in parallel and MBS creates the XML/NFO for me (I am using EMM for posters et al). Can you take a look what EMM produces and why this results in this error message for EMM. I can imagine the MBS devs may be willing to fix it of this is wrong how they create the XML/NFO files for XBMC.

<video>
<codec>h264</codec>
<micodec>h264</micodec>
<bitrate>13453496</bitrate>
<width>1920</width>
<height>1040</height>
<aspect>1.85:1</aspect>
<aspectratio>1.85:1</aspectratio>
<framerate>23.97602</framerate>
<language>fre</language>
<scantype>progressive</scantype>
<default>True</default>
<forced>False</forced>
<duration>85</duration>
<durationinseconds>5074</durationinseconds>
</video>

Aspect ratio is now calculated by width divided by height:

1920x1040 = 1.8461...
16:9 = 1.777...8

Thanks. Does this hold true for "aspect" and "aspectratio"? Does EMM divide them or scrape them somewhere it is already divided?

[DanCooper]

Ember recognize only "aspect" and remove "aspectratio" while generating NFO.

We use the MediaInfo.dll plugin to read the file informations. I'm not shure with way the plugin use to recognize the aspect ratio.