Reply to thread

Message

<blockquote data-quote="VdR" data-source="post: 807416" data-attributes="member: 25818">Moving Pictures is THE plug-in for MP! Great work. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />I know it has been discussed in many threads, I still dare to bring it up again. It is too complicated to keep the movie databases on multiple clients synchronized. I understand the difficulty of running from one database and that we have to wait for MP2 to see that realized.And there are a number of workarounds. I make sure the movies are in the database as I want it on one client, then use MP Artwork and Info Copier and then the other clients synchronize automatically (unless the other client beat me to it updating it's database). But that it is cumbersome to do for every movie added and every change made. So I have a request.Would it be possible to have the importer run in one of three modes;stand-alone (functionality as now)master (functionality as now, and with every update writes an .nfo and data files to the movie folder)slave (only uses available .nfo and data files, checks for updates on those)That way the workaround is automatic by just selecting master on one and slave on the other clients. There is a copy of the database on every client, that makes access fast and disk space is cheap. Can't go wrong, except that if you would set two clients as master results are unpredictable. And if you have a slave but no master the slave's database would remain empty.What about that?VdR</blockquote>

[QUOTE="VdR, post: 807416, member: 25818"] Moving Pictures is THE plug-in for MP! Great work. :D I know it has been discussed in many threads, I still dare to bring it up again. It is too complicated to keep the movie databases on multiple clients synchronized. I understand the difficulty of running from one database and that we have to wait for MP2 to see that realized. And there are a number of workarounds. I make sure the movies are in the database as I want it on one client, then use MP Artwork and Info Copier and then the other clients synchronize automatically (unless the other client beat me to it updating it's database). But that it is cumbersome to do for every movie added and every change made. So I have a request. Would it be possible to have the importer run in one of three modes; stand-alone (functionality as now) master (functionality as now, and with every update writes an .nfo and data files to the movie folder) slave (only uses available .nfo and data files, checks for updates on those) That way the workaround is automatic by just selecting master on one and slave on the other clients. There is a copy of the database on every client, that makes access fast and disk space is cheap. Can't go wrong, except that if you would set two clients as master results are unpredictable. And if you have a slave but no master the slave's database would remain empty. What about that? VdR [/QUOTE]

Verification