Jump to content


Photo

.NFO not generated on actualize or rescan or identify

NFO

  • Please log in to reply
15 replies to this topic

#1 dkurok OFFLINE  

dkurok

    Newbie

  • Members
  • 8 posts
  • Local time: 02:30 PM

Posted 13 July 2017 - 08:33 AM

I've got a video (The LEGO Movie from 2014) in my Emby-library. For this video the emby-server did not generate an .nfo-file when I added the movie to the library and also not on rescan or actualize (metadata-manager) or on identify. It downloads the pictures for the movie (banner.jpg, poster.jpg and so on) and stores it in the folder where the movie stays.

For other movies in the same library there is always an additional nfo-file.

The metadata-manager does show the information of the movie (plot and so on) which are normally stored in the nfo! So somewhere (database?) it is persisted.

But why is there no nfo-file in this special case?

 

Reagrds

 



#2 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 135879 posts
  • Local time: 08:30 AM

Posted 13 July 2017 - 12:57 PM

Hi there @dkurok, in order for us to help answer that, please provide the information requested in how to report a problem.

 

You may also want to verify that you've actually enabled saving metadata to media folders in Emby library setup.

 

thanks !



#3 dkurok OFFLINE  

dkurok

    Newbie

  • Members
  • 8 posts
  • Local time: 02:30 PM

Posted 13 July 2017 - 05:40 PM

Hi Luke,

 

attached you'll find the server-log.

Search for "Lego" to see the different behaviour of two different "Lego"-films. The "The LEGO movie (2014)" reports an error after fetching the pictures (See line 13121 ff for example). The other LEGO movie (Batman) does not produce this error.

I've verified again: Actually the saving of the metadata to media folders is activated (and works for other movies like the Batman-movie).

 

Thanks!

Attached Files



#4 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 135879 posts
  • Local time: 08:30 AM

Posted 13 July 2017 - 10:45 PM

Can you open the detail screen in the web app for this title, scroll down to the bottom and copy and paste the media info here so that i can see it? thanks.



#5 dkurok OFFLINE  

dkurok

    Newbie

  • Members
  • 8 posts
  • Local time: 02:30 PM

Posted 14 July 2017 - 03:42 AM

Here are the infos:

Medieninformation
Video CodecH264
AVCYes
ProfilHigh
Level30
Auflösung720x576
Seitenverhältnis5:4
AnamorphNo
InterlacedNo
Framerate25
Bitrate1953 kbps
Bit-Tiefe8 bit
Pixelformatyuv420p
Ref Frames1
NAL4
Audio Sprachedeu
CodecAC3
Darstellungstereo
Kanäle2 ch
Bitrate128 kbps
Sample-Rate48000 Hz
VoreinstellungYes
TitleDeu Dolby Digital stereo Default
Audio Sprachedeu
CodecAC3
Darstellungstereo
Kanäle2 ch
Bitrate384 kbps
Sample-Rate48000 Hz
VoreinstellungYes
TitleDeu Dolby Digital stereo Default
Containermkv
Pfad\\DELLSERV2012\Filme\The LEGO Movie (2014)\The LEGO Movie (2014).mkv

looks somehow strange in the title of the Audio...

should spell something like Deutsch (I'm from Germany)  at the beginning...

Do you need additional info?



#6 dkurok OFFLINE  

dkurok

    Newbie

  • Members
  • 8 posts
  • Local time: 02:30 PM

Posted 14 July 2017 - 03:53 AM

this is how it looks in the browser (in the post above you cannot see the strange characters, because the html-editor of the post throws it away). You can see the strange chars at Sprache and Title of the two Audio-entries596877fabe87d_Capture.jpg

 



#7 dkurok OFFLINE  

dkurok

    Newbie

  • Members
  • 8 posts
  • Local time: 02:30 PM

Posted 18 July 2017 - 03:04 AM

Hi Luke,

did you find some cause for the error in the log-file?

Many thanks



#8 BigGoose62 OFFLINE  

BigGoose62

    Advanced Member

  • Members
  • 92 posts
  • Local time: 07:30 AM
  • LocationNC

Posted 18 July 2017 - 08:13 PM

I'd like to piggyback on this thread. OP mentioned the server still displayed the movie's information, so the data is most likely saved somewhere. Any ideas on where to look for that saved data? In other words, if not saving metadata to media folders, where does Emby save the metadata? I have several movies that also don't generate an .nfo file for some reason.



#9 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 135879 posts
  • Local time: 08:30 AM

Posted 18 July 2017 - 11:21 PM

I'd like to piggyback on this thread. OP mentioned the server still displayed the movie's information, so the data is most likely saved somewhere. Any ideas on where to look for that saved data? In other words, if not saving metadata to media folders, where does Emby save the metadata? I have several movies that also don't generate an .nfo file for some reason.

 

If you don't enable saving to media folders then it is in the database only. 



#10 dkurok OFFLINE  

dkurok

    Newbie

  • Members
  • 8 posts
  • Local time: 02:30 PM

Posted 19 July 2017 - 02:20 AM

As mentioned at the very beginning:
- meta-data saving to media-folder is enabled
- for most of the movies it works
- special case receives pictures, but no .nfo is generated
- error on .nfo-generation is clearly logged
- meta-data are stored somewhere / in DB

So question in this post is:
What is the reason for the error during the generation of the .nfo-file?

#11 rhodges OFFLINE  

rhodges

    Advanced Member

  • Members
  • 189 posts
  • Local time: 07:30 AM

Posted 19 July 2017 - 08:59 AM

I am going to guess that it is because of a bad character that is it is trying to write as XML (nfo file). It probably happens in the process after it is written to the database.

 

You might try remuxing the mkv and see if that fixes the issue. I have used the XmlWriter in C# before, and I thought the main purpose of it was so that it handles encoding special characters for you. I haven't however, come across that character before, so I'm not sure what the expectations are, from a C# XmlWriter perspective.

 

Edit: Xml 1.0 does have a limited range of special characters and that is definately not a valid character in the range. Remuxing might fix the issue, assuming it doesn't put the invalid character in again. The long term fix would probably be to sanitize the text before it is passed to WriteElementString.

 

https://www.w3.org/TR/REC-xml/#NT-Char

	System.ArgumentException: '', hexadecimal value 0x01, is an invalid character.
	   at System.Xml.XmlUtf8RawTextWriter.InvalidXmlChar(Int32 ch, Byte* pDst, Boolean entitize)
	   at System.Xml.XmlUtf8RawTextWriter.WriteElementTextBlock(Char* pSrc, Char* pSrcEnd)
	   at System.Xml.XmlUtf8RawTextWriter.WriteString(String text)
	   at System.Xml.XmlWellFormedWriter.WriteString(String text)
	   at System.Xml.XmlWriter.WriteElementString(String localName, String ns, String value)
	   at MediaBrowser.XbmcMetadata.Savers.BaseNfoSaver.AddMediaInfo[T](T item, XmlWriter writer)
	   at MediaBrowser.XbmcMetadata.Savers.BaseNfoSaver.Save(IHasMetadata item, Stream stream, String xmlPath)
	   at MediaBrowser.XbmcMetadata.Savers.BaseNfoSaver.Save(IHasMetadata item, CancellationToken cancellationToken)
	   at MediaBrowser.Providers.Manager.ProviderManager.SaveMetadata(IHasMetadata item, ItemUpdateType updateType, IEnumerable`1 savers)

Edited by rhodges, 19 July 2017 - 09:03 AM.


#12 dkurok OFFLINE  

dkurok

    Newbie

  • Members
  • 8 posts
  • Local time: 02:30 PM

Posted 19 July 2017 - 10:28 AM

Hello rhodges,

 

I always thought that emby is getting the metadata from the metadataproviders as defined in the settings (metadata) for the library. If so, remuxing the mkv wouldn't change anything, because in this stage the movie-file itself is not scanned for metadata.

You're right with the special char 0x01 (which is SOH = start of header in ASCII). But I think this comes from the metadata-provider (The Open Movie Database and TheMovieDb in my case) or somehow during the interpretation of the metadataprovider's answer.

Am I completly wrong?



#13 rhodges OFFLINE  

rhodges

    Advanced Member

  • Members
  • 189 posts
  • Local time: 07:30 AM

Posted 19 July 2017 - 02:18 PM

My guess is that it is coming from audio track information, based on the screen capture you provided. I'm pretty sure that information is also written to the nfo file. My thinking was, that somehow it is bad in the mkv. Then again, it could be an issue with ffprobe or ffmpeg or whatever they are using to pull the file metadata.

 

I would take a peek at it with mediainfo and see if it looks funny there. Then remux it with a newer version of mkvtoolnix if you do see weirdness there. Or, maybe you need to update ffmpeg.exe and ffprob.exe. I don't know if it is supported or not, but I occasionally go and download the latest stable versions from time to time and replace them in my Emby ffmpeg folder.



#14 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 135879 posts
  • Local time: 08:30 AM

Posted 19 July 2017 - 02:40 PM

Please try again with the next release of Emby Server. Thanks !



#15 dkurok OFFLINE  

dkurok

    Newbie

  • Members
  • 8 posts
  • Local time: 02:30 PM

Posted 25 July 2017 - 04:37 AM

Updated to version 3.2.26.0 yessterday and now it generates the .nfo-file correctly for the movie.

Thank you Luke!



#16 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 135879 posts
  • Local time: 08:30 AM

Posted 25 July 2017 - 09:57 AM

Thanks for the feedback.





Also tagged with one or more of these keywords: NFO

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users