[Glenn Sakatch]

If you have not changed the in/out points on a clip since it was used to create the motion effect clip, alt matchframe will call up the clip without affecting its in/outpoints. Without alt you will simply get a new inpoint at your matched frame. Then the trick of using locators would be a good work around.

Glenn

[Glenn Sakatch]

We have tried this in the past with our Fibre Jet System. If you don’t have a proper Avid sharing program or system, the problem is that the database is alway rebuilding on you.

As your top post says, one system is editing on a project, and the other system is only ingesting material. Unfortunately the system doing the editing gets a database rebuild everytime a new clip is added. We tried having two different projects as well, one for editing, one for ingesting, but you end up with the same problem. The software Michael is pointing to looks very interesting. In our experience, you definately need some other piece of the puzzle to run interference on the database rebuilding. Perhaps that is what this new software is doing.

Glenn

[Glenn Sakatch]

One of the reasons AMA works, but works best as an intermediate creator.

Glenn

[Glenn Sakatch]

Plugin 64 should be the one you want. 64 bit for Avid Media Composer 6.5 (I assume you are running Mac lion or mountain lion?) file is xpmm 2-0-2-6-9l

Did you download the Avid MXF AMA plug in as well?

Within Avid you can check which plugins you have installed. This should tell you if it has installed correctly
go to your console (tools>console) and type AMA_ListPlugins

This will tell you the version and type you have installed

When you are doing your volume link, you aren’t going into the contents folder correct? You are in a structure that shows you there is a contents folder…don’t go any deeper.

Glenn

[Glenn Sakatch]

To link to the volume, instead of the individual files, you should be in a folder situation where you are inside an area where you are now looking at the contents folder. sourcescard1contents….something like that.

If this doesn’t work, uninstall and then reninstall new versions of the plugins. Both the mxf plugin from Avid and the C300 plugin from Canon. 305 is the same as 300, and should be all you need. I’m not sure what the 100 one is for, but it sure won’t hurt to install it as well.

Be sure you are installing the version for Media Composer 6.5. There are two different versions on the site.

I find most times people can’t use the link to volume is because their plugin is bad/out of date.
or they have altered the folder structure. There is no need to not copy across the entire folder structure off of a card. Don’t start drilling into the card and decide what to take…take it all.

Glenn

[Glenn Sakatch]

Does your avid fail to launch after this error?

No, deleting a database will not delete the media. Avid will simply rebuild it upon the next reboot.

I would actually suggest doing a search for any mdb files on the computer. I had a corrupt one that was put onto my C drive at one point. It gave me a similar error on bootup, and then crashed the program.

If you delete all mdbs on your system, Avid will rebuild the ones in needs (the ones in the mxf/1 etc folders.

Glenn

[Glenn Sakatch]

I just tried both methods and had success each way, although i was doing a very simple test:

C300 source clips on my shared storage.

made a brand new sequence
manually drove into the folder structure and selected 1 C300 mxf file and imported it at dnx36

did a basic edit with this one file. took sections out for a total of 3 edits.

decomposed the sequence to take it offline.

In a seperate bin i have all my c300 ama links for this entire project.
I select all those clips (command A) then select my sequence in the other bin. Right click to relink. Select the second option down of selecting items in all open bins.
select “allow relinking of ama linked clips to source file”

might have to play with a couple of other settings depending on the version of Avid you are on

I usually turn off create new sequence

everything relinked to the full res ama linked clips.

Then i cut another sequence with the imported dnx36 shot…did the same kind of edit.
selected my sequence right clicked and said batch import.
told it to import everything (not just offline clips)

It came up with a screen asking me where the footage was, since i didn’t move it, i simply set the resoluction to full res and said go.

clip imported just fine, this time at high res.

Not sure why you are having issues. If you have been moving source files around, perhaps your directory structure has been damaged. C300 would be one
of those items that you want to maintain the original structure if possible…although at least you can do a manual import on a per file basis if that is necessary.

[Glenn Sakatch]

Just be careful when you download the plugins from Avid. There are different versions, depending on what version of Avid you are running. As Shane said, not sure if 5.0 is on the list….i know 5.53 (think thats the build) is on the list.

Glenn

[Glenn Sakatch]

I usually do the ama and transcode to dnx 36, then relink up to 175 process, but before ama,- and before C300- we would import and digitize at low res, cut, delete and reimport to highres.

Now i typically would do the uprez on a DS box, so i don’t need to bring in all the raw footage, it will allow me to import parts of files. MC will want to reimport all your raw clips, but if you have space, you should be able to batch import all your 115 clips up to 175.

How much footage are we talking about?

As for the 23.98…make sure you are timing your show out at 59.94 drop frame while you edit in 23.98

From there, can you not drop your 23.98 sequence into a 59.94 project for the conversion? (assuming you don’t have access to proper Avid DX hardware.
(again, i don’t usually do this step in MC, but in DS, so i’m guessing on that one)

Glenn

[Glenn Sakatch]

I have had this happen on two different systems. (one mac and one Windows)
It is a database issue, but it is not connected to one of your actual storage drive databases.

On windows i found the culprit in my users/avid area. On Mac i was having trouble finding it. (i think it ended up being in the applications/mediacomposer/(show package contents) area.

Either way, just do a search for MDB files and delete any that aren’t on an actual storage drive. Or better yet, just delete them all. Avid will rebuild the ones it needs, and ignore the rest.

Glenn