I think jweis is spot on. Standalone read in or re-sync is the only way here. Just to clarify some of your comments though- Avid consumes MXF OP1-Atom natively. This means it does not have to 'import' it, it just needs to read it into a database to play/link etc. The database in this instance is either your interplay system or the stand alone

Hi Rob, thanks for the reply, you are right I think I was overcomplicating it for myself - we are going to go down this route, will update how we get on...

we are using XT2, XT Access and IPD to push material in and out via TM so far pretty successfully. What questions do you have?

Hi, thanks for that - just an update from our side - since posting this we went with the 2.0.3 update on Avids advice on the indexer and it appears to have made a lot of difference to the responsiveness of the indexer, and also the scanning issues have settled down someehat after this...not sure how relevent this is but fwiw thanks

Hi everyone, got an odd situation... Interplay 1.6 on ISIS 2.01 using MC 3.5.4.3 Editor checked a bunch of bins into interplay after re-naming the bins. project got re-replicated using back up background software, and original (un-renamed bins got checked in too) - dont ask me how I wasn't there at the time ;-) Net result is though, that there are

Our Interplay v1.6 64 bit indexer is doing this too, snag is we have only got one. Can I reboot this machine at an opportune time then? Most of my workspaces seem to be rescanning, even though some of them have not been updated for a week. Page file appears correct on our system... any input welcome thanks Graham