Speed Issue Resolved

Dan Sherman wrote on 11/17/2005, 11:47 AM

Over the past few weeks I've posted notes about the speed of my editing machine.
The slow speed thereof.
Second and third instances of Vegas were taking minutes to load.
I was also having blue screen stuff happening and crashing.
NOT THE FAULT OF VEGAS.
Grazie offered some excellent advice,---as he always does,---in that keeping those processor fan fins clean is essential.
My problem was not related to that issue,---because as your know there is no airborn dust in Canada.
It all stays frozen in place!
Seriously though,---my tech (I am not one), replaced the paste that connects the processor to the sink fan (hope I got that right).
Now all is running, as our friend Grazie may say,---"swimmingly".
If there are others out their with sluggish machines it may be something to consider after trying everything else.
Hope this helps someone.
Well,---I'm off for my hair transplant appointment.
Too late for me.
Cheers.

Comments

Former user wrote on 11/17/2005, 11:56 AM

So it was a heat issue. That paste helps transfer the heat from the processore to the heat sink so the fan can then pull the heat away.

Glad it worked out.

Dave T2

Jeron wrote on 11/17/2005, 12:44 PM

Sherman,

I'm glad you solved your problem!

I know this is off the topic of this thread, so I hope you don't mind me asking...

I'm a new Vegas user (switched from Xpress Pro) and I'm still trying to "dial-in Vegas workflow". I'm curious, what kind of workflow would dictate two and three instances of Vegas running? Is it common for a Vegas editor to run multiple instances?

Thanks,

Jeron

seanfl wrote on 11/17/2005, 1:08 PM

having a couple running at one time allow you to copy sections from one project to another. If I have a bunch of tracks laid out just the way I want them, and I want to combine that section of a project with another in process, I can copy over what's going on with project a into project b.

the other neat feature is nested timelines, where you can insert a whole project that will appear as a single track in your new project. Let's say you have a 30 second commercial that is inserted into your longer 10 minute piece. You can place the commercial's edit file onto your timeline, and if you make any edits to the commercial, it will automatically upadate inside the larger project.

Hope that helps...that's how I use them from time to time.

Sean
------------------------------
broadcast voiceovers

plasmavideo wrote on 11/17/2005, 1:57 PM

QUOTE: I'm a new Vegas user (switched from Xpress Pro) and I'm still trying to "dial-in Vegas workflow". I'm curious, what kind of workflow would dictate two and three instances of Vegas running? Is it common for a Vegas editor to run multiple instances? -

I run 2 instances sometimes so that I can render one project while laying out another.

Chienworks wrote on 11/17/2005, 2:04 PM

That's the single biggest reason i run more than one instance. I'll sometimes have half a dozen renders going on while still working on another project.

The other reason is that i'll use one instance for playing around with ideas to avoid messing up anything in the main project. Then when i have something working i'll copy and paste it into the other instance.

Jeron wrote on 11/18/2005, 7:39 AM

Thanks for the info everyone.

Running multiple renders makes sense. I also like the idea of having a "master project" instance running and a "workspace project" instance running.

I can't believe how well Vegas works, taking up so very few computer resources. I'm used to one instance of Xpress Pro sucking up every single resource on the computer... and then complaining that it wants more :)

Jeron

Grazie wrote on 11/18/2005, 8:27 AM

Woah! - Credit WHERE it is due please . .

The solution came from Johnny Roy - our jr. He was THE one who recognised that the error message I finally did get, and was simoiar to the one he had - we had/have the same ASUS MB - and he immeadiatley asked me if my fans were working? I said yes, I can hear them, but that I would send him a photo of them so he could at leat see them, in action, as it were .. . but ONCE he had SEEN them it was his laughter that I heard above everything else - we SKYPE, yes? - Clean those fans lad! . . .

So one JR plus he knowledge PLUS a vacuum cleaner and a soft artist's CLEAN brush - did the trick.

Grazie

riredale wrote on 11/18/2005, 9:18 AM

As others have mentioned above, you can run multiple instances of Vegas in the background doing rendering at idle priority, while you work in a primary Vegas window in the foreground.

I've also used multiple instances of Vegas when doing surround-sound work. My usual pattern is to first cut the documentary using the default front audio. When the project is nearly done, I go back to the beginning and open a second and third instance of Vegas. The second instance I load up with the original raw video footage. The third instance I load with the raw surround audio, captured from Minidisc.

I can then go though, scene by scene, and locate the corresponding surround audio from instance #3, and then copy-paste from #3 to a new surround track on #1. It's easier to show than it is to describe, and aside from the hassles of syncing up the rear audio to the front audio, it proceeds fairly quickly.

I've recently begun using a little custom-built mic interrupter pushbutton switch that I velcro to the handle of my VX2000. At the end of a take, I hit the button, putting in sync on both the front and rear audio. This makes it a lot easier and faster to sync the audio later.