Glenn Sakatch
46
Avid Coins
85
COW Coins
36
DaVinci Coins
4
Premiere Pro Coins
2
Solve Coins
Forum Replies Created
-
Do a search on your computer for the MDB files. The database files. I do recall a situation that was killing the launch of the program a few months ago, and it was related to the creation of a database file (and avid mediafiles folder) in a location where they had no business being. If memory serves it was somewhere on the launch drive, perhaps in with the actual program itself. I had the problem on two systems, both times the easiest way to find it was to search for the database’s.
(just found an old post i made on this type of lockup… here is an excerpt)
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
-
As an alternative answer.
We’ve had problems in the past with C300 and spanning clips, where the problem turned out to be corrupt files coming off the original shoot card. Footage was copied from the card to a hard drive. We were transcoding from that hard drive, or a copy of that hard drive. Was finding some of the longer clips were crashing. If i put those same clips through Resolve, they didn’t crash. Upon closer inspection I found black frames in the clips coming from resolve. In the end we kinda decided there was a problem with the original shoot files. Avid would crash out, while Resolve would just ignore the bad frame and move on.
Try a file in Resolve and see what you get.
Glenn
-
is it hung up on that screen, or just taking an extremely long time? This has been a problem in Avid for a while. Try disconnecting your network connection and relaunch.
On my system, it seems to hang, but if i sit and wait for a few (2 or 3) mins, it makes its way through. Seems to be something about scanning media on the network.
Avid reported they fixed this problem awhile ago, but it has never been “fixed” for me. If i’m in a hurry, i diconnect the network, launch, and then reconnect the network.
PITA, but it works.
Glenn
-
Vimeo does have a link to Drop box for uploads, and promotes that it can do automatic uploads from your dropbox folder.
One note on squeeze. I just had it doing a watch folder scenario. Going from After effects to my watch folder…through squeeze to a “to Vimeo” folder. Squeeze was going through the watch folder doing the newest movies first. This meant as after effects started an output to the watch folder, squeeze starting doing its thing to the same movie (before after effects was done) I loaded up 5 movies in the watch folder before i started squeeze, and before i got AE going. As soon as squeeze was done with the first movie, it started working on one of the files AE was working on. This results in an “incomplete output” error on those movies. I could not find any setting to tell squeeze to change its order of operation. If anyone knows where it is, i’d love to hear. For now i can’t move the files into the watch folder untill after effects is done creating them.
Glenn
-
i thought the error message it gave out listed the name of the missing font.
Has that changed, or am i thinking of a different program?
Glenn
-
+1…sort by date.
(the gobbledigoop does make sense if you are coming off tape, and does match source file names if coming off files, but agreed, they are not always easy to read)
This is the perfect situation to keep you mxf folder organized as you ingest new material.
Everything new goes into the 1 folder. After an ingest or import session, change that 1 folder to something to identify it. For many of my projects my folder structure starts looking like this
Avid MediaFiles/mxf/Aug13 RED Cam
Avid MediaFiles/mxf/Aug 13 C300
Avid can read these folders as long as the database has already been built inside it, which it should have done before you renamed it from ‘1’ to “Aug13 Red Cam”
the “1” then becomes a working files folder for renders and title creation. Now when its time to archive or back up, you can selectively move camera media around. If you know a file from a shoot date is corrupt, its easier to find it in your media pool. Your bins can be set up to show you the file location, incase you can’t remember when the media was shot.Also if a client comes back and wants a shot from an old project, (and you back up your media) its much easier to find.
Seems like a bit more work at the start of a project, but for large projects i always organize this way…as i have a lot of returning clients, always wanting to combine old footage with new footage.
This is an easy way to archive an entire project, but only bring in certain shoot dates later on when a couple of shots are needed.Glenn
-
Some preliminary trouble shooting might save you some money as well. As you have already spent money on 1 drive that didn’t fix the problem, before you spend more money you should confirm the media is good. (My guess is the firewire is the problem- although at DNX36 i would’ve thought playback should work), but i would copy a transcoded video file to your local drive. Put it in the proper folder structure and get that one file into your project. If it plays back fine, then you know your transcodes are good, and the problem probably lies with the throughput. Troubleshooting should always have a logical checklist of what does work, to be able to identify what doesn’t work. Never hurts to check the source media first.
Glenn
-
Windows or Mac? Calibrated Q MXF might be able to import directly on a mac. Windows version is for viewing only i believe.
Pretty sure with C300 you need the structure. I guess another question would be “how can the structure
be rebuilt?”I would also try to load the shots in Resolve. If it sees them, then you could reoutput mxf with an AAF, and he should be able to go from there.
Glenn
-
Based on your earlier post, i’m wondering if there is a conflict with windows? If Windows opens one of those “what should i do with this device” windows, cancel out of it before continuing.
Unfortunately i don’t have a dv camera to try out the workflow myself.
Make sure Avid is launched first.
Plug in and turn on your camera, run the auto config through the capture tool to try and discover the deck.Make sure you have a hard drive selected to capture to.
If all else fails, try creating different projects with different settings. NTSC 30, HD 59.94, HD 23.98. It shouldn’t be that difficult to get it to recognize your camera.
Perhaps someone with a DV camera can chime in with a step by step they do to get it to work.
Sorry, can’t be much more help.
Glenn
Glenn
-
When you plug the external drive in, Avid will read the database that is with the media on the drive, and will repopulate your bins with media. You shouldn’t have to “set up” anything. The Drive letter assigned by your home computer will probably be different than the one assigned by the school…this should be irrelevant to Avid, as long as the database is contained in the MXF/1 folder…which unless you do something manually to alter it, it will be.
If you are AMA linking to footage on the external drive, then a database will not be built, and you may have to point avid to the footage again, doing a re-link to ama operation. But again, if you do a straight import or digitize to create avid media, you should be good. Just be aware of the differences if using MC 7 at school, and and older version at home. Check Avids compatibility specs about this. (you’ll want to make sure you are on the most up to date legacy version possible)
Glenn