Due to Media Bins - Sony Vegas 12 not responding

MRiver wrote on 11/18/2014, 9:30 AM

Hello everyone,

I'm having for the second time trouble with a project when creating media bins.
When Sony Vegas crashes (which is happening so often) and I want to open the project again, the program is not responding for a longer period of time.
The first time it was on a wedding project where I created about 30 different bins. Opening time for sony vegas about 48minutes.
This project was done on my laptop, DELL 8GB RAM/ Core i7

Now I have a new project, video from Miss Luxembourg 2015 where I have created about 20bins, my timeline is almost empty.. and vegas did crash just by stretching a clip. Now after about 1 h of waiting sony vegas was still not able to open the project.
I have a complete new desktop pc. 32GB RAM/ Intel Core i7-5820K Extreme, Geforce GTX970, Asus X99-A X00 RG SA. This PC has so much resources and power !! but Sony Vegas is having problem to open a project where my timeline is almost empty ...
What's wrong with those stupid BINS and HOW can I solve this problem !!!

First I thought it was due to my laptop .. but now is happening again with a brand new powerful pc which is 4K capable ..
all my files are local, I don't use any external drive.

I start to believe that sony vegas is nothing for professional use but for small amateur projects ..

Sony Vegas Amateur ... deficiently not Sony Vegas Pro.

Sorry, yes I'm really pist off... need to deliver the project in 2 days ... this is so frustrated

And I'm really

Comments

OldSmoke wrote on 11/18/2014, 9:41 AM

@MRiver

What are those files in your bins? Do they require Quicktime? With which codec are the encoded?

Edit: Please be so kind fill in your full system specs.

MRiver wrote on 11/18/2014, 10:13 AM

@ OldSmoke,

I'm using Canon 6D cameras, so the files are straight from the camera, .mov quicktime.

System: Intel(R) Core(TM) i7-5820 CPU @ 3.30GHz 3.30GHz
RAM 32GB
64 bit System

Windows7Pro

OldSmoke wrote on 11/18/2014, 10:32 AM

Quicktime is a pain and even more so on the PC platform. Vegas is 64bit and Quicktime for PC is only 32bit; there have been plenty of posts in this forum regarding Quicktime issues. If you can, transcode to something else. For a quick test, save the project under a new name, use a batch transcoding tool and replace media (Vegasaur does a good job). You can use a fast encoder and low resolution since this is only for testing.

vtxrocketeer wrote on 11/18/2014, 10:48 AM

Out of curiosity, how MANY mov clips do you have in all of your media bins? Vegas tends to not do well, even crash, when a project contains more than 50 of these; memory is the problem. Transcoding to an intermediate, like a Cineform avi, makes for a much smoother editing experience.

(And for the forum to fully assist you, I think we'll need to examine some of those Miss Luxembourg clips ;) )

MRiver wrote on 11/18/2014, 10:57 AM

I'm not sure what you mean OldSmoke, should I transcode all my original footage to another videoformat ?

Just for your info, I did spend 2days just to watch the hole footage from the event and did cut everything usable for my video and all this usable sequences are in those bins ready to be placed on the timeline. So I need to have access to those bins, can I transcode those clips located in the bins ?

MRiver wrote on 11/18/2014, 11:15 AM

@ vtxrocketeer,

It's more than 50mov clips... can't tell you exactly how many they are as I'm waiting since 2hours that sony vegas is responding back. But I guess around 200-300 mov clips.

here is the video from the repetition's, 2weeks ago ;-) https://vimeo.com/109937199
thank you for all kind of support ... in 2 days I need to deliver the official video clip ...

vtxrocketeer wrote on 11/18/2014, 12:09 PM

I think you probably have too many Quicktime clips in your project. As mentioned above, these aren't really PC-friendly and Vegas chokes on more than about 50 in a single project. As you wait for your project to open, what is happening to your PC's memory? I think a process called "I/O surrogate" will show a very large consumption of memory as you try to open the project.

Do what OldSmoke recommended: batch transcode your clips and replace them into a copy of your project. Obviously, you have to use a transcoding tool OTHER than Vegas because you can't load more than 50 of your source Quicktime clips at a time into Vegas. I use and recommend Cineform avi. The free UTvideo and Lagarith codecs (avi) also would work very well.

Post back and let us know how you get on.

OldSmoke wrote on 11/18/2014, 12:34 PM

I have used many times Vegasaur for situations like this. You can open an empty project and use Vegasaur within Vegas to transcode external media to any codec that is installed on your system and has a render template in Vegas. There are other tools like Gearshift but I am only familiar Vegasaur. There is a 30day free trial which is fully functional too.

MRiver wrote on 11/18/2014, 12:49 PM

Ok thank you guys for the tips, I go with vegasaur and make a trial.

@OldSmoke,

Can you just explain me how the workflow exactly is ?? I open an empty project and then ??

I just didn't get it yet if I'm transcoding my original footage to avi ... means I will have to review all the footage again and cut the sequences I want to use in small clips.

Or can I transcode with vegasaur my current project where I already have done all this work ?? means vegasaur will transcode all my mov clips located in the bins to avi ??

OldSmoke wrote on 11/18/2014, 12:56 PM

@MRiver

If you can open the project with all the bins, then yes, Vegasaur can transcode the media in the bins. How did you make in/out points on the individual clips? Did you save them with the clip?

Once you have Vegasaur installed, open the "Transcoder". It is very easy to learn. In VP12 Vegasaur is under Extensions. I think you need Vegasaur 1.98 for VP12, 2.0 is for VP13.

There is a small triangle next to the green plus button that will open the required dropdown menu.

MRiver wrote on 11/18/2014, 1:00 PM

ok, that would be perfect ...

I'm still waiting that sony vegas gets back into the project ... since 3h now :-/

farss wrote on 11/18/2014, 2:27 PM

Your best chance is to use a tool to transcode your original media to a different codec. I would suggest the Sony MXF @ 50Mbps. It's 4:2:2 so better than your camera original and very easy to decode.

How you do this with the least pain is to transcode to a different folder.
Then rename the folder that holds your camera original footage.
Then restart your project that's taking so long.
Vegas will not be able to find the source media for the project and will open a dialog box that'll let you specify where it is. Here you tell Vegas where the transcoded files are. Vegas should be able to workout that all the media for the project that's missing is in the new folder location.

Bob.