Thanks for your reply! Right now I still got many issues getting this to work for me. There are many files with names 'hhd800.com@' at the front and the program cannot search from the actual DVD ID. I have to manually edit the names but it will be too time consuming. There are few hundreds of these. I hope I can retain the original file names so that I can continue to seed. 
And can these work for Plex? I tried loading with Plex but many metadata was not displayed correctly.
Hi,
Ah, your getting this becuse "hhd800" looks like a video ID, so Jav-It is trying to parse it first rather than continue to look within the filename for additional patterns. Since your file name format is rather interesting, It was never really considered. I think I have an idea on how to deal with this edge case, so I'll see if I can get a fix prepared for you.
As for original filenames, there is an option to leave them as originally found (and not change them), but that only effects the filename and not the foldernames. Is that enough for you? Preserving torrent names with Symbolic Links is pretty easy on Linux/MacOS, but I'm not sure if Windows has something similar. Perhaps If I know more about what your torrent requirements are, I can try to find a solution.
As for Plex, I'm not sure because I don't have it (Since Plex is not free). The NFO file format follows KODI specifications, which is also compatable with other open source projects like JellyFin (A FOSS Plex alternative). I assume if you have an importer or program that can read KODI formatted files then you would be fine.
Hi the fix works for me now. Thank u so much! It does picks up the right ID for those files. As for the leaving the original filenames I have tried using the code --alt-naming-method="original" it does effect on both filenames and foldernames so there is no problem now.
As for Plex there is a free version if u no need the extra features. I did use an importer called XBMCnfoMoviesImporter to load the KODI formatted nfo and it does load most of the items except for the actor image. Since it doesn't load can just have the option to disable downloading of actor image? Another reason is because there will be too many duplicate actor images under different folders as each actor can have many DVDs. To serve different users requirement u can fix to allow display of actors image for Plex and also disable downloading altogether? There is no need to have a tag genre for 'JAV' since the entire folder is JAV, hope I can disable it. Also same goes to the .tbn file which is essentially the folder.jpg in different format only use for KODI. In essence I only require the poster, fanart, thriller, nfo and everything else can remain as original. As for the title it will be good to add the DVD ID on the front so the I can search via DVD ID. Something like MIDE-123 Title...
Lastly if can rollback on the items that was done that will be good. ^^
Thanks for the feedback, as I’m glad it works for you now!
In regards to actor images, adding an option to ignore them is totally possible. It just needs to be prioritized and added to the backlog. The reason why images are mirrored for each folder is due to technical limitations. Actor images must be found locally or be specified by a fully qualified path. Since there is no way to guarantee the location where people choose to store such information, locally is the best option. In addition, since actor images are limited to head shots, the disk space requirement for them is quite low.
As for the “JAV” genre tag, this is important for other edge-cases. For example, many users have collections that include JAV, but are not exclusively all JAV. So when adding a small amount of JAV content to their libraries, having accurate genre tags is desirable for searching.
In regards to thumbnail files, indeed some of the metadata included is exclusive to KODI standards. While this information might take up a marginal amount of disk space, since KODI has been the most dominant and popular open source media center project for a while it makes sense to align compatibility with it. This is especially true, since other projects tend to use subsets from the KODI specification, meaning general compatibility can be maintained.
I hope this clarifies things a bit! (^_^);
