Reply to thread

Message

<blockquote data-quote="fforde" data-source="post: 808355" data-attributes="member: 52082">I am sorry I must have misread you above. I was under the impression you had moved movies from one external drive to another. This complicates things... The problem is that Moving Pictures removes the movies from the database before you have a chance to tell it about the new import path. So you need to trick Moving Pictures into thinking that the disk where the files used to be stored is offline. if you could do this then Moving Pictures would not remove the movies from the database. Honestly I am not sure there is a proper solution aside from moving the files back. I am sorry. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" /> In the future in situations like this, if you add the new import path before you move the files you will avoid this problem. At this point though I would recommend just letting things reimport.:sorry:</blockquote>

[QUOTE="fforde, post: 808355, member: 52082"] I am sorry I must have misread you above. I was under the impression you had moved movies from one external drive to another. This complicates things... The problem is that Moving Pictures removes the movies from the database before you have a chance to tell it about the new import path. So you need to trick Moving Pictures into thinking that the disk where the files [i]used to be stored[/i] is offline. if you could do this then Moving Pictures would not remove the movies from the database. Honestly I am not sure there is a proper solution aside from moving the files back. I am sorry. :( In the future in situations like this, if you add the new import path before you move the files you will avoid this problem. At this point though I would recommend just letting things reimport. :sorry: [/QUOTE]

Verification