Plugin: MetaExtractor

[yocker 1247]

@sh0rty
It should work now. I copied the fix i had added to individual items and it works now, so very fast and easy fix.
Problem was that i had it look in parent directories which Emby does not use for collections.

MetaExtractor.dll

[sh0rty 714]

Working well now! Thanks! 

[feerlessleadr 173]

Sorry for what maybe a stupid question, but if I already store my metadata in nfo files (generated by emby) as well as images stored with my media, will this plugin offer something different than that (other than intro skipping backup, which I'm definitely interested in)?

Thanks!

[yocker 1247]

1 hour ago, feerlessleadr said:

Sorry for what maybe a stupid question, but if I already store my metadata in nfo files (generated by emby) as well as images stored with my media, will this plugin offer something different than that (other than intro skipping backup, which I'm definitely interested in)?

Thanks!

Not stupid at all. Will admit i wondered the same thing but it was made from the request and idea from another person so there is a use for it for some and i'm happy to help out.  
You can save the NFO and Artwork in custom folders and collections are supported.
Other than that, not really.

If you have any suggestions that could make it useful for you then you are more than welcome to report them here and i will look into them.

[feerlessleadr 173]

Thanks, am I able to install this just for the intro skip marker backup (specifically since you're working to make that portable, which the current backup doesn't do yet) without using the other metadata stuff?

[yocker 1247]

16 hours ago, feerlessleadr said:

Thanks, am I able to install this just for the intro skip marker backup (specifically since you're working to make that portable, which the current backup doesn't do yet) without using the other metadata stuff?

Enable


And it will be portable.

[Suliamu 36]

Thanks a lot for this.   
Some time ago i requested exactly this functionality for people who run emby with the media-libraries mounted as read-only, but it seems that no one understood why this would be a good feature.  
This is really nearly perfect.   

But i have a bugreport to make: custom file naming is unfortunately not working for me. 
When i enter into "Settings - Custom Artwork Names - Poster Name: cover" he nonetheless exports it as "Example Movie (2025) - 1080p-primary.jpg".
I've tried it multiple times, also with restarting and so on. 
I run 4.9.1.90 on Linux.  

And also couple more feature requests
a) When exporting just one library into a custom folder, it uses the root folder of "Custom Export Folder Path" to put all the item-folders inside. 
This is pretty inconvenient. 
Example:
If i have two libraries called "Movies" and "International "Movies" and i just export "Movies" into the "Custom Export Folder Path" /home/emby, 
then /home/emby looks as follows:
/home/emby/Example Movie 1 (2025)
/home/emby/Example Movie 2 (2025)
It would be good if the plugin would also with single library exports export into a parent folder that goes by its library name. 
In that case:
/home/emby/Movies/Example Movie 1 (2025)
/home/emby/Movies/Example Movie 2 (2025)

b) In "custom file name" it would be great if there would be a checkbox or something so you can choose the option to save images only by their rudimentary typename without the Itemname as prefix. 
Instead of Example Movie (2025) - 1080p-primary.jpg it would be nice if you could save it only as "primary.jpg" (or whatever you have put into Custom Artwork Names).
This would ensure maximum compatibility across most of mediaservers. 

c) Maybe make a naming convention that gives full compatibility between emby/JF as the default. 
For example when i've compared the docs between emby and JF i found that "primary.[ext]" isn't mentioned in the JF-documentation. 
They officialy support cover.ext, poster.ext, folder.ext - just as Emby does.  

Thanks again