Can somebody help me find the divide and conquer page? Is it still applicable? Or can someone teach me how to find corrupt media? Please? Thank you. I am having so many errors right now and I just can't isolate the problem.

here are some of the errors that come out:

Exception:invalid argument....

Assertion failed:(*fileHdl)->magic==DISK_MAGIC

STRM_BUF_SMALL,buflen:1024

Badly need your help. Thank you.

Hi,

Mark in and out around the first half of your sequence.  Press Play In to Out (6 key on the top row of the keyboard).

If the sequence plays, there's no corrupt media between the in and out points, so try again by marking in and out around the second half of the sequence.  When you find which half won't play, continue marking in and out around smaller and smaller portions of the sequence until you find the clip or effect that is causing the problem.  Delete the effect or media and rebuild/recapture/reimport it.

good luck,
Carl

Thanks Carl. I did this before already and I already found some of the bad media. My problem now is I think I've got a bunch of corrupted files in the bins. What I'm trying to do now is batch import each bin that I have but a lot of times, it ends up stopping the batch import without me cancelling it. Then I also get the BUS THREAD error at times when I locate a file during batch import. I really don't know what's going on. First I had this problem on the Unity. Now I transferred the project into a local drive and started re-importing it on a local drive(because these are MXF media from SonyEX cameras), then I got a lot more errors. If you need any more info about my problem I'd be glad to talk about them here. I badly need help on this. Thanks.

Hi,

biennarc100907:

What I'm trying to do now is batch import each bin that I have but a lot of times, it ends up stopping the batch import without me cancelling it.

I'd try batch importing smaller selections of clips and see if you are able to identify which clips are causing the batch import to fail, or if it is not consistent and is a problem with the system itself rather than the media.

biennarc100907:

I also get the BUS THREAD error at times when I locate a file during batch import.

Hopefully a Mac person will chime in on this.  I know nothing about Mac error troubleshooting.

biennarc100907:

I really don't know what's going on. First I had this problem on the Unity. Now I transferred the project into a local drive and started re-importing it on a local drive(because these are MXF media from SonyEX cameras), then I got a lot more errors.

Just to make sure, have you tried creating a new user and a new project and deleting the MCState settings?  It may not be a settings problem, but it's best to eliminate them as a possible cause.

good luck,
Carl

Where do I delete the MCstate settings?

Hi,

Not sure on a Mac, but on my machine there's one in C:/Users/hp/Documents/Settings and one in C:/Users/hp/Documents/Avid Users/Carl.

good luck,
Carl

And from the settings folder, the files to delete are "MC State", "Site_Settings", and "Site_Attributes". On relaunch the system will detect the missing files and build new ones. If you have previously dragged any user settings into the site settings window, those will need to be restored after the rebuild.

certainly try all above and, if you can, delete all the pre-computes from your project and see what happens.  For some reason I have found (as has been noted in other threads of this nature) that most of the time corrupt media tends to be an Avid generated effect or title. 

biennarc100907:

Where do I delete the MCstate settings?

Applications>>Avid Media Composer>>Settings

MC State is the the Settings folder.

switthaus:

...delete all the pre-computes from your project...

Keep in mind that this would include any imported matte key clips as well.

which is why I said "if you can..."!

:-)