by onyxwave » Sun Oct 31, 2021 10:53 am
Peke wrote: ↑Sun Oct 31, 2021 8:15 am
Hi,
It is already in development, I have created native core MM code for importing NFO files. It is still in testing.
There is extensive research I have done some time ago regarding TV Series, Kodi, Sonarr, SickRage, ....
Let me know if we missed anything and if you want I can help you with whatever you would like to do.
I read through the linked tickets (link for ticket 15246 did not work for me - it gave me an "Access Denied" result) and I like where things appear to be headed based on the ticket comments.
I was happy to see this ticket, as I was going to suggest moving away from TVDB. I've moved away from using TVDB over the past 9 to 12 months, and now use TMDB as my main metadata source for both movies and series. I only use TVDB as a rare second option now. So I'm hoping this ticket means that the development team has moved away from TVDB in favor of TMDB. I also utilize both Fanart.tv and TPDB (The Poster DB) for posters and fanart secondary options if I don't like the posters and fanart provided by TMDB. Not saying referencing those content resources is neccessary yet it might be a nice enhancement once the main functionality is worked out.
Though, as long as the function to import the data from the NFO files, I would be really happy with that, as my NFO files are always a little more informative than the having just the data that comes from the site sources like TMDB. For example, I store a lot of my own custom poster/fanart in Imgur and add the links to them in the NFO file (though as a backup I also store images locally in case Imgur ever goes down or their usage policy changes in the future like PhotoBucket changed. So this functionality you're adding is great for me if it reads the NFO files into all respective MediaMonkey fields, and it would be nice if the function would also us to map XML tags in the NFO file to custom MediaMonkey fields if they don't have an associated standard field in MediaMonkey. Also great if there's an option to pull the artwork from the locally stored artwork files first, and then artwork links second so in case links to the artwork in the NFO files no longer exist or the site is unavailable. Any additional functionality after that is just icing on the cake.

[quote=Peke post_id=489538 time=1635686146 user_id=213]
Hi,
It is already in development, I have created native core MM code for importing NFO files. It is still in testing.
There is extensive research I have done some time ago regarding TV Series, Kodi, Sonarr, SickRage, ....
Let me know if we missed anything and if you want I can help you with whatever you would like to do.
[/quote]
I read through the linked tickets (link for ticket 15246 did not work for me - it gave me an "Access Denied" result) and I like where things appear to be headed based on the ticket comments.
[quote=Peke post_id=489538 time=1635686146 user_id=213]
https://www.ventismedia.com/mantis/view.php?id=16332
[/quote]
I was happy to see this ticket, as I was going to suggest moving away from TVDB. I've moved away from using TVDB over the past 9 to 12 months, and now use TMDB as my main metadata source for both movies and series. I only use TVDB as a rare second option now. So I'm hoping this ticket means that the development team has moved away from TVDB in favor of TMDB. I also utilize both Fanart.tv and TPDB (The Poster DB) for posters and fanart secondary options if I don't like the posters and fanart provided by TMDB. Not saying referencing those content resources is neccessary yet it might be a nice enhancement once the main functionality is worked out.
Though, as long as the function to import the data from the NFO files, I would be really happy with that, as my NFO files are always a little more informative than the having just the data that comes from the site sources like TMDB. For example, I store a lot of my own custom poster/fanart in Imgur and add the links to them in the NFO file (though as a backup I also store images locally in case Imgur ever goes down or their usage policy changes in the future like PhotoBucket changed. So this functionality you're adding is great for me if it reads the NFO files into all respective MediaMonkey fields, and it would be nice if the function would also us to map XML tags in the NFO file to custom MediaMonkey fields if they don't have an associated standard field in MediaMonkey. Also great if there's an option to pull the artwork from the locally stored artwork files first, and then artwork links second so in case links to the artwork in the NFO files no longer exist or the site is unavailable. Any additional functionality after that is just icing on the cake. :D