strm files: why don't you use metadata info from nfo file?

[horstepipe 422]

Hey @@Luke

could you please elaborate why you made the decision not using stored metadata info in .nfo files for strm files?

So when you playback a strm file the first time, it is being probed by Emby/ffmpeg and the metadata info is being created and stored in the nfo file. But when you rebuild your database the info is gone, so the information from the .nfo file is not being used, why? :-)

 

Best regards

[Luke 42083]

Because people will customize that for display purposes, it will cause transcoding failures, and then we'll have to troubleshoot that.

[horstepipe 422]

Because people will customize that for display purposes, it will cause transcoding failures, and then we'll have to troubleshoot that.

Understood, thanks.

Any chance to add a hidden option for that?

Edited August 23, 2018 by horstepipe

[Luke 42083]

We already have the via saving in emby database.

[horstepipe 422]

We already have the via saving in emby database.

Yeah but I‘d love to keep those information when updating to the upcoming beta, for which (afaik) you‘ll get most performance benefits when you rebuild the db from scratch

[ebr 16187]

 the upcoming beta, for which (afaik) you‘ll get most performance benefits when you rebuild the db from scratch

 

I'm not sure where you got that information but that should not be the case.

[PenkethBoy 2068]

Yeah but I‘d love to keep those information when updating to the upcoming beta, for which (afaik) you‘ll get most performance benefits when you rebuild the db from scratch

have been testing the new server with upgrades and new build library.db files

 

No speed difference

 

only obvious difference is that a new db is smaller

[horstepipe 422]

have been testing the new server with upgrades and new build library.db files

 

No speed difference

 

only obvious difference is that a new db is smaller

 

Nice to hear, thank you!