Apologies for the cross post but Nobody seemed to recognise this error in the MC Mac Forum:

I'm not on mac but I'll just share my experience. I've done several transfers from standalone projects to unity and back. To get a standalone project on unity I do the following.

I create a new workspace. I let an avid workstation create a media folder and subfolders in that workspace. I copy in windows all media files in that workstations (avid 1,2,3...10) folder. I open the particular avid and see if all my material is present. Never had any problem.

Now the trick is that editors do not use other workspaces. If they do, and you need to go back to the stand alone edit station, try to consolidate everything into one workspace when finished. Or use a tool called MDV to see where all your media files are. When during editing users have used different workspaces and different edits/workstation on the unity, and sometimes even local storage, your media files are all over the place and you are dealing with several databases.

In practice I found out that it depends a lot on how well you keep you Unity organized. But if things get corrupt then I never found any solution other then the rebuilding the database.

i'm having this problem right now. i rebuilt the database files but i still cannot export anything. any solutions?

In the original poster's screenshot, it shows that the A1 audio from REEL 022 is missing. 

What does your's show?

Our workaround involved putting all the instances of media that "might" be this media file... if not all files in the same folders into one users media folder on the unity then scanning. Prefereable on all machines that owned databases on that drive.

OR

Make one machine the owner of all the media folders and put all the media clips into one big folder and scan.

The problem tended to arise if one user had imported/digitised a clip then sent the sequence and the media to another off site machine... then that machne had sent it back with the original media but another user had loaded up the media.  We then had a situation where older sequences would referrence the first instance of the mediafile whereas newer sequences coming back from offsite would reference the newer instance.  If you then opened bins with both sequences referencing 2 versions of the same media file in 2 or more locations that's when this situation seemed to happen.

We were keeping out offsite machine in sync with media by sending off folders of media by changing the number after the Machine name (for instance an AVID logged in as Z1 had a folder of media called Z1.1 so we'd change it to Z1.090629 and send it off).  BUT this caused us to have many small folders of media and the chances of doubling up on media that we already had when the offsite machine sent stuff back got more likely.

We were mixing OMF WAV audio and MXF DNxHD picture media.  We found that the OMF databases did not get updated or scanned if you were in HD mode.  So all of this had to be done whilst we were in SD mode.

Hope this helps anyone else who encounters this.

RalphFoster:

We found that the OMF databases did not get updated or scanned if you were in HD mode.  So all of this had to be done whilst we were in SD mode.

Hope this helps anyone else who encounters this.

I've found this to be the case as well.  Try changing the format of your project to either SD or HD and then back again to see if they need to scan both types of media.  I don't believe you need to change the "Media Creation" setting, but if you're still having problems, I'd check that as well.

~Hammer