Reply to thread

Message: <blockquote data-quote="RoChess" data-source="post: 594421" data-attributes="member: 18896">The "XBMC NFO" system is NOT the same as the "NFO Scanner" system that is also supported (the little checkbox on "Importer Settings" tab). So to avoid confusion with people reading this; this method explained by kcpent uses the XBMC NFO system. The simple NFO Scanner system only looks for an IMDb-ID, such as for example tt1234567, ignoring any other info, and then uses that IMDB-ID to get all the movie information via the IMDb scraper.Having both the "NFO Scanner" and "XBMC (Local)" Scraper enabled (NOTE: Remember to adjust priority in top position or it is ignored in most cases), might be the reason some people are having problems, or delays.As for your 2nd Step #4, this is pointless, like you said you are redoing the same information. The whole key behind the XBMC NFO system is for the initial import process based on those NFO files being generated already, or after disaster strikes and you want to rebuild your HTPC. Redoing it directly after all the information is already correct is redundant.So you have to look at it more like a backup system for future recovery. This is why you don't have to re-run the XBMC NFO generator everytime you import a new movie, unless you are extremly paranoid on your backups. So once a week/month suffices.All the functionality will eventually be build into MovingPictures itself, based on "Enhancement Issues" submitted to the Google SVN website (see my signature on how to do so). So you don't have to submit again, as these are existing issues. The "MP Folder Organizer v0.3" functionality for example has already been made functional in the MovingPictures v1.1 source code in a better way, including undo option. It didn't make the deadline to get integrated into MovingPictures v1.0, so you have to be patient longer. It would be unfair to keep prosponing a new release from becoming stable, just so another feature can get added. If that was the case it would remain beta forever, as there is always a new thing to add. You are however free to download the v1.1 source code and compile it yourself to get all the new functionality. I run a v1.1 version myself as well, due to <a href="http://code.google.com/p/moving-pictures/source/detail?r=1036" target="_blank">Moving Pictures source code revision 1036</a>. That one didn't make the cut into version 1.0 either (as you can see it shows /trunk/ (reference for future code) and not /branches/ (reference for next stable version code) in the path), but I couldn't wait <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin    :D" loading="lazy" data-shortname=":D" />The only thing added to the v1.0 branch right now is bug fixes, but everything is pretty much fixed to a satisfactory level (it will never be 100% bug free), so expect version 1.0 to be released soon. The small bugs still found will then be fixed in v1.0.xx releases (we are already at v1.0.4 actually), and then later you can expect a new v1.1 beta as the whole development process repeats itself.That's the whole benefit of these small applications, is that they can be written quickly to do one task, but to integrate them in an existing application takes a lot more effort and testing (to make sure nothing else stopped working).A better solution would be for those contributions to be written in C# directly (the language MediaPortal and MovingPictures are written in) and submitted as a patch, but that's just not always an option for the person who has the time to do the contribution to begin with.PS: regarding '&', not sure if you are the same poster, but there is a difference between '&' and '&amp;' at usage level for an application (the '&amp;' is an HTML 4.0 URL encoding entity to represent '&'). Check your database to see what encoding was used to process the '&' char originally.</blockquote>

Verification