Avid Error of the Day: File ‘creating6′ can not be deleted because it is busy.
As with all of these Avid errors, just skip ahead to other less-technical blog content. I post these when I want solutions to turn up better in searches for other Avid users (and myself).
I've seen this as "creating2" "creating3" "creating4" "creating5" "creating6" etc. Had a crash while importing an image -- images longer than around 10000 pixels in one dimension will cause Avid to hang. Also, TIFF in 16bit RGB instead of 8bit RGB.
No problem, right? Force quit Avid and restart. Problem is, it doesn't see the drive I was importing to anymore, so it gives this file error. (Some speculation on Avid boards talks about permissions and stuff.)
Anyway, the fix is easy if annoying. Full system reboot. Hopefully you've fixed whatever in the image caused the crash in the first place. Once I was rebooted it saw the drive again and I was able to proceed.
Avid Error of the Day: ECH: CBDataNotAvailable
As with all of these Avid errors, just skip ahead to other less-technical blog content. I post these when I want solutions to turn up better in searches for other Avid users (and myself).
Couldn't find anything on this playback error. I'm working with 1080i HDV (so GOP) footage in a 1080p project, with the motion effect promoted and the 3:2 pulldown / detect frames. Only some clips, all longer than a few minutes, seem to have this problem. I suspect this is related to the fact that the footage was captured without timecode because the camera man left so many timecode breaks.
No solution, but after a crash, I rebooted Avid Media Composer and was able to go to the first frames of each of these clips, matchframe and cut back in the clip pre-promotion. Once I have the clips cut down short, I'll try detecting the frame cadence again to remove the flicker-motion.
No idea what module ECH refers to, but the fact that the error shows up in the same place as FlameThrower stream errors (aka FireWire), makes me think it is something to do with how the Avid interprets the frames of the footage for playback.
Avid Error of the Day: Unsupported Resolution
As with all of these Avid errors, just skip ahead to other less-technical blog content. I post these when I want solutions to turn up better in searches for other Avid users (and myself).
After accidentally attempting to consolidate some of Avid's internal media, like the "Media Offline" card, I stated getting an "Exception: Unsupported Resolution" error.
It seems from this thread that there are a number of things that can cause this. But this advice is what worked for me:
Found a fix for this (for me anyway) on a Mac. I had the same problem "Exception: Unsupported Resolution". Tried all the things the forums suggested, including a complete re-install of the MC software... STILL had the problem. Eventually distilled it down to this: apparently the Avid did not think that's it "internally generated" media files were supported. By "interally generated" I mean, basically, Avid internal BLACK signal media, etc. Turns out the Avid software ships with an "Avid Media Files" folder in the Application folder than contains media and media databases. Trash those 2 databases (just like you would on any regular media directory) and, upon relaunch, Avid rebuilds them and... poof... no more "Exception: Unsupported Resolution". Here is the directory path to delete the database files:/Applications/Avid Media Composer/SupportingFiles/Avid_MediaFiles/ ---> delete "msmMMOB.mdb" and "msmFMID.pmr"
So definitely try this before reinstalling Media Composer.
Avid Error of the Day: MVL_INSUFFICIENT_SPACE
Putting this out there so I can find it again, and to help others, hopefully. If you're a casual reader of the blog, skip on to the next post.
Got a strange little error MVL_INSUFFICIENT_SPACE in Avid Media Composer on the Mac when trying to export an AAF to the desktop. I knew there was plenty of space on the desktop, but I tried other drives, including a Unity one. No luck. The internet boards were recommending turning off drive filtering in Media Creation settings. That didn't work either.
Turns out the Unity drive that had that media I was trying to export was 99.5% full. A quick trip into the Administration tool to add a few hundred gigs sorted that out.
By the way, this didn't cause Avid to crash or slow in any way. So it's nice to know you can bump up against space limits without that happening. (Would be nicer if the error just said what the problem was, and if it didn't create empty .aaf files and make the .exported version of the sequence, but now I'm just dreaming out loud.)
Call Sheet
In the Can
- Movie Review: A Separation
- FilmCraft Book Reviews: Editing and Cinematography
- Your Wednesday Links: Oscar Reax
- Movie Review: Coriolanus
- Movie Reviews: Carnage and Rampart
- Avid Error of the Day: File ‘creating6′ can not be deleted because it is busy.
- Your Wednesday Links: Hey, Have You Heard of SOPA/PIPA?
- Movie Review: Haywire
- Your Wednesday Links: Infiltrating the Rose Parade
- DVD Review: The Inbetweeners Movie (Region 2)
Word of Mouth
Favorites Re-Released
Back Catalogue
Balance Sheet
See other ways to support.
Help us go ad-free. Our pledge:
when donations beat ad money, we'll remove the ads.
