Ushere,

Thanks for the reply. Unfortunately I don't have another project to open in Vegas Pro 10 as I just got it recently and started using it. The thing is, SOMETIMES my project will open just fine but that usually takes about 5 tries of closing and reopening Vegas to get it to work.

Also if I may ask Ushere, why is it that when I try to import a lot of footage, say about 900 clips, into a brand new project Vegas states that some files couldn't be imported and then when I drag a clip on the timeline it turns into a plain red screen with audio, but no video. Do you think I am just overloading Vegas at once by trying to import all the footage at once? The reason being is because I plan to re-edit the whole project again, starting fresh, if I can't get this MSVCR90.dll error fixed. The media I edit with is HD .MXF files.

Sorry about not posting my system specs, but here they are:

Windows 7 64-bit
12GB of RAM
AMD Phenom II X6 1090T Processor, 3.2 GHz
Nvidia GeForce GTX 460 graphics card
1TB hard drive

Let me know if there is anything else I can provide to help solve this issue. Thank you very much.

sorry, i should have written 'start' a new project in vegas. try starting a new project and dropping some files in it and see if you have any problems.

can't really help re .mxf (from camera - btw. which camera?) though i often use it as an intermediary.

are you importing 900 clips in one hit? what happens if you add in smaller batches?

ONLY ONE HD!?

I agree with ushere.
900 clips at once, especially with a single hard drive, is just begging for trouble.

Mike

You could have hit the GDI limit in Windows.

Once any single process hits 10,000 GDI Objects, it’s terminated. This is the default limit defined by Windows that a single process can reach.
Each image consumes one GDI Object, every window, icon and graphic element on the desktop consumes a GDI Object. Every toolbar item, button and status bar item consumes a GDI Object. Firefox on my system is using over 2,000 GDI Objects right now. Importing hundreds of images could easily hit this limit.

There’s a registry tweak that can change this in windows 7:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\GDIProcessHandleQuota

Right click on the registry key GDIProcessHandleQuota, click on modify, set the BASE to DECIMAL. The value should default to 10000. You can change this to the upper limit of 16,384 (4000 HEX).

** WARNING! - I recommend only making this change if you are very comfortable editing the Windows Registry. Accidental changes to the registry can render your system inoperable, so exercise extreme caution when making any registry edits. I strongly recommend creating a Windows Restore Point prior to performing any registry edits.

Here’s a site that explains and shows the process of creating a Restore Point in Windows Vista and 7 if you’re not familiar with this tool - http://www.howtogeek.com/howto/windows-vista/create-a-restore-point-for-windows-vistas-system-restore/

Steve Mann

Ushere,

The camera I am using is a Sony PMW-EX1r and I use the clip browser software that came with the camera to convert the footage into .mxf files and import them into my computer.

When I tried to import all 900 clips in one go in Vegas Pro 10 32-bit, I get an error stating that "vegas was unable to import some clips, one or more files might be corrupt." I don't believe its corrupt because the footage is on my timeline, even though its not all 900 clips of it. I just 900 clips but really I am only using about 100-300 of them because the rest are screw up shots, but I just import them just to see what I am working with. However, sometimes when I import large amounts of clips, Vegas imports them but there is no thumbnail image, and when I drag a clip onto the timeline I get a red frame for video but the audio is still in tact.

What I am thinking of doing is probably to edit a little bit of the project first, then render it out of Vegas as a single clip, then bring it back into vegas as the single clip. I will render the edited clip out as as a SONY MXF (.MXF) I am thinking about doing this for the whole project, breaking the project into about 4-5 single rendered clips and just bring it back into Vegas and putting it all together and then rendering it out again as a single movie. Maybe Vegas just can't handle everything that I put the timeline that is why it crashes?

I have an external hard drive, 300GB, but I read around that editing through an external hard drive could cause crashes and slow down, etc. Is it better to edit through an external or internal hard drive? Thank you so much.

ok, from my pov;

use the browser to simply cull the clips down to a manageable size BEFORE bringing them in to vegas.

use vegas 64bit (will make use of your 12gb ram!!!) - opps, sorry you are....

dump clips to external HD - i've never encountered a problem using ex hd's - you really are asking for trouble using the same drive as your system.

i often work long form doco with many hours of material in vegas (not necessarily on the tl though!).

When I tried to import all 900 clips in one go in Vegas Pro 10 32-bit, I get an error stating that "vegas was unable to import some clips, one or more files might be corrupt." I don't believe its corrupt because the footage is on my timeline, even though its not all 900 clips of it. I just 900 clips but really I am only using about 100-300 of them because the rest are screw up shots, but I just import them just to see what I am working with.

It doesn't matter if they are on the timeline or not, if you have a bad media file in your "project media" window, then Vegas expects it to be usable.

Put another way, if you have a bad media file that Vegas is trying to load into the project, then it may crash.

If you suspect your media, try loading a new project and import a few clips at a time to find the bad one.

Steve Mann

Trying to find one (maybe more) bad clip out of 900 can seem overwhelming so here's a method to use.
Load them in 50 clips at a time so you don't overload Vegas.
If the first batch is ok, proceed to the next 50 and so on until you're done.
Make notes of which group of 50 cause Vegas to crash.
Split the bad group in half and try it again.
Keep cutting in half until you find the bad clip(s) and either delete it permanently or re-convert it.

BTW, did you use the latest version of XDCAM EX ClipBrowser to do the conversion to MXF?
I was originally using version 2.0 and found that it would periodically corrupt some of my clips with either distorted audio or blocks of green in the converted video or both.
I installed version 2.60 and my problems disappeared.
Go to http://support.sonybiz.ca/esupport/eSupportHome.asp and scroll down the list to find it.

Mike