Forum Replies Created

  • Paul Morris

    October 24, 2008 at 6:07 am in reply to: Harddrive set-up

    Thanks Steve. Yes, Vegas is very definitely on the ‘C Drive’ internal main drive. My main point is whether it’s healthier for the rendering files to be sent to a drive separate from the ‘D Drive’ which contains project/source files; to stop thrashing. What do you think?

    Vegas on C Drive (internal)

    Project/Source files on D Drive (internal)

    Render to external eSata drive

    Thanks for your help, and I hope this help someone else out too!

    Paul.

  • Paul Morris

    October 21, 2008 at 8:34 am in reply to: Vegas Pro 8.0 Using Lots Of Disk Space When Rendering

    So a better harddrive configuration would look like this…

    C Drive: applications/software, for example Vegas

    D Drive: clips/captured files/clips that you are editing/jpegs/wavs files etc

    E Drive to render your project into (can this be external, if so how fast do write times need to be?)

    Is it okay to render to the same physical drive as your project, in this case the ‘D Drive’?

    Question: In rendering how much data per second is Vegas processing? I know this will vary from computer to computer but could we render to an external drive, what write speeds are needed?

    Thanks.

  • Paul Morris

    September 16, 2008 at 10:06 pm in reply to: Render settings for best quality HD playback

    Two pass rendering?

    Does anyone have any tips for Vegas’ prerender option? What does it achieve?

    Anyone?

  • Paul Morris

    September 5, 2008 at 9:26 pm in reply to: Vegas Pro 8.0: Using All Cores

    Thanks for clarifying that!

  • Paul Morris

    September 4, 2008 at 5:03 pm in reply to: VASST Ultimate S Pro: Still Motion?

    Cool, thanks guys. Editing something now that will pay for Ultimate S Pro!

  • Hi John, that worked. I downloaded the latest ATI drivers. Thanks a lot for the tip.

  • Paul Morris

    August 25, 2008 at 5:01 am in reply to: Vegas 9 to include 64bit

    I bought a new laptop which was meant to be set-up as 64-bit but came with Vista 32-bit so I am sending it back for 64-bit, the supplier has to do it, all in preparation for Vegas Pro in 64-bit.

    I’ll cast my vote for the stability of Vegas, especially vs Premiere.

    People often tool around with their computers thinking they are ‘customising’ or ‘optimising’ them and they often have them so full of junk it’s no wonder they crash.

    I keep my editing computers lean and mean with all sounds, shutdowns/hibernates/screen savers turned off.

    The OS, no bloatware, and minimal software, Microsoft Word, Photoshop CS2, Canon DPP and RAW capture/viewer software, Avast, Spybot and that’s about it. And, the editing comp is never online.

    It’s a temple not a junkyard.

  • O.k., thanks, I’ll try that. Velocity over multiple clips anyone? Cheers.

  • Paul Morris

    August 12, 2008 at 11:21 pm in reply to: Vegas Won’t Recognize my Canon HV20…..Sorta

    Hi, is the out on the HV20 set to DV, HDV or both? Also, Vegas likes to set up a default vidcap on your computer. If you have been using HDV then change the video standard on the HV20, from HDV to DV, and then try to capture, it can confuse that default (HDV) vidcap.

    Say I have filmed something in HDV, and captured it. Vegas will set a default vidcap for HDV out of the HV20. So from then on capturing HDV from the HV20 will be a breeze. If I change the standard on the HV20 to DV, at capture things go haywire.

    That’s what I have observed. So I film everything in HDV with a Vegas’ default vidcap behaving nicely.

    Try the prefs in capture, upper left hand dialogue box, you’ll see it. Tool around there.

    Resetting can be tedious. I found that I had to be pedantic and couldn’t EASILY find a trick to override Vegas. I had to turn everything on and off a million times and then finally it would work. So with a working defualt vidcap I don’t touch the HV20 video standard (HDV)!!!

    Keeps me sane.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy