WHAT IN TARNATION DOES THIS MEAN!!!! And how does it come about. Just finished placing a gfx an suddenly this came up.

TIA

Biker

Anyone.... Anyone... Bueller?

Just came across this one.  Working in SD with anam. mask and IllusionFX TC gen.  Seq is 28min long and there are two clips... this happens at the begining of second one.  

Before I restarted I was also getting this error:

AMEResourceManager::ReconfigMem()

Error [-16777163] unable to:

LegedVDMInterface->EnsureSufficentBuffering

XW8400; SN 1.8.1

Oh Yes I've seen this one. Several times today actually. (SN 1.7.7 on Isis)

I think it *may* be related to mixing OMF and MXF media in the timeline, but yet to chase that theory down.

It seems to mean that the sequence has a corrupted subclip within it. Once you find the corrupted subclip (which is usually either the shot it stops on or the following shot) then you have to lift it out, restart the app and then reinsert it back into the sequence.

You'll know you got the right shot when the sequence plays across the bad bit.

Corruption of some sort. 

Most of the error messages in Media Composer or Symphony Nitris will not actually tell you what the problem is.  You just have to know what them mean from experience. 

One of THE most annoying errors I have encountered.

It happens randomly (and FAR too regularly), and as Trevor says, it usually takes a reboot of the app to fix it (after you have removed the corrupt effect!).

We are running SN 1.8.1 and MCA 1.7.7 on ISIS 1.4.

Incidently, I had one of these errors this morning on an "Avid Pan and Zoom" effect and found that if you changed the cache parameter (in the fast menu within the effect editor) to "video resolution", it sorted it.

This gives me the impression, it may be to do with memory?....

Hey there, 

Ok, I joined this community just to make this comment as the frustration this problem has caused me and my editor has been headsmashing on desk magnitude. I am not sure of every reason why this message CORE_UNABLE_TO_DO appears, but our run in with this error came with regards to imported Jpegs and applying Pan and Scan effects.

We were making a programme for the BBC, ONLINE edit using a Nitris AVID suite.

Basically in our instance we found that AVID, does not like large JPEG files. I had edited a few in Photoshop such as applying Gausian blur to get rid of lining etc.. so we thought that maybe it was the way the paint programmes saved the JPEG, but as far as I am aware a JPEG is a JPEG right?

Basically as a test we just changed the format of the pictures from a JPEG to a TIFF file, and hey presto we had no further problems.

I hope this helps someone out.

I agree "Avids" do not like large jpg files BUT Avid DS handles them just fine! 

 We have been getting this error since upgrading to 1.8.3 and only when working in SD 30i.  One particular editor has been plauged by this, he will edit with no problem for hours then all of a sudden the error hits and he can do nothing.  Like mentioned earlier in this thread, it is usually when working on an effect like pan and scan, safe color, etc.  So far I have found two ways to deal with this, neither works in every situation, but sometimes we can get past the issue. 

First, This seems to be a corrupt effect problem.  In a few instances we have isolated an effect, that once removed, will make the error go away.  It can be very hard to find the bad effect in a long sequence.

Second,  If I can't isolate any bad media or effects, we once again restart the system. This time I log into windows instead of the editor and a lot of times the error will go away.  Then the editor can log back in and it will be fine for him the rest of the day.  We both have Windows Admin rights, I don't know why this makes a difference.  It is not Avid user settings either, I have imported my setting into his, made new settings, etc. 

Soblick, I am going to try your cache trick next time this problem comes around. 

Good Luck,

Gordon

I occasionally get this error, SN 1.8.3. No imported JPEGs in my sequence anywhere. All MXF media. Unclear when and why it happens.

Have another theory that seems to cause CORE_UNABLE at times... partial render of a timewarp effect. 

(NO JPEGS on my sequences either.)

It is partial renders for me. No matter what they are... reformats, 3D warps etc.