[Nigel O’neill]

Patti

That’s a pretty powerful system and should be more than adequate for the job. Do you have more than 1 hard drive in the system? The Dell system also has an ATI video card. You might want to consider replacing that with an NVidis GTX 480 or GTX 570 card as Vegas takes advantage of the CUDA cores on the card during certain renders.

What is your source footage, project settings and render settings? Screen shots will help.

By way of comparison, how long does it take to render unedited footage of a similar duration? Are you able to run a test and post your results?

If you are running anti-virus software, disable it (but don’t forget to re-enable it afterwards).

Intel i7 920, 12GB RAM, ASUS P6T, Vegas Pro 10 (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Vegas should install what VC++ redistributable runtime modules it needs during installation.

Jason, I am a little confused:

I tried to upgrade to 10.00c but it didn’t work so I had to reinstall 10.00a.

Were you able to install 10c?

I am even more confused in that your error message relates to 10a. Do you have an error message relating to 10c?

Intel i7 920, 12GB RAM, ASUS P6T, Vegas Pro 10 (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Carlton

Ugly ex-wives aside :-), one needs to consider the format/CODEC the NLE was designed to edit. FCP is a Mac tool for editing MOV and does it well, but is pretty hopeless in dealing with anything other than MOV/MP4 files. Vegas handles pretty much any format and ingests almost anything. Vegas runs on non-proprietary (inexpensive) hardware and multiple versions of Windows. FCP runs on Mac’s. Period.

I played with earlier versions of Avid and Premiere, but neither of them were stable (at the time). I think it was CS3 at the time.

I also looked at Grassvalley Edius, but could not come to terms with the interface and controls. What Vegas could do easily, Edius made very difficult, but there are some features in Edius I would like to see in Vegas. Edius 4 had an HD Storm card which not only allowed ingesting from a number of inputs, but offloaded the rendering to dedicated hardware. It is very expensive compared to SVP10!

Lastly, I found a great support forum called Creative Cow Sony Vegas ;-). Whilst not a technical reason per se, it was a significant deciding factor for me. I found this especially helpful as there are many experienced contributors who helped me through a number of sticky situations. So much so that I give back to the Creative Cow community whenever I can, drawing on my IT background. As I learned in my career so far, you can have the world’s best product, but without an effective support network, the product will fail.

Intel i7 920, 12GB RAM, ASUS P6T, Vegas Pro 10 (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Tim

Sounds like there is something in your media bin that Vegas is trying to relink upon starting which has been deleted/renamed outside of Vegas. You might want to inspect it and give it a thorough clean out.

If you are accessing your project files on an external USB 2.0 drive, that is also a known cause for sluggishness.

As a last resort you could also try defaulting your Vegas installation as you start it:

Click on the Sony Vegas icon whilst at the same time holding down ‘CTRL’ and ‘SHIFT’.

Intel i7 920, 12GB RAM, ASUS P6T, Vegas Pro 10 (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

The last time I tried mixing PAL HDV (1440) and DV (720), the difference was very noticeable on the DVD when using a 1440 project template. HDV was noticeably much crisper, but there was noticeable tearing on fast pans in the DV footage, plus DV looked muddy. Luckily for me, the client had requested only standard-def DVD (720), so I used that as my project settings.

In my case, the mixing of footage was accidental (one of the OP’s camera’s was set to DV whilst all other camera’s were HDV), and generally should be avoided. Although I have multiple HDV camera’s, 2 of which are pretty close in specs (FX1 and Z1P), getting them to match is not always easy. In a multi-cam shoot it pays to use matched cameras. I even avoid mixing CCD and CMOS camera’s, to try and maintain a consistent look and feel.

Intel i7 920, 12GB RAM, ASUS P6T, Vegas Pro 10 (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Patti

What are your PC system specs in terms of CPU, RAM, operating system and Vegas version? I couldn’t find your system specs in your earlier post as suggested. 23 hours is a long render time. What format are you trying to render from and to?

I regularly edit and render multi-cam HDV shoots, and 1.5 hours of time line footage with colour correction and multiple effects seldom takes longer than 2 hours to render, even with 2 pass variable bit rendering enabled.

The only time I have seen such long renders is in DVDA when I had to create a blu-ray ISO image from HDV renders (that took 23 hours). The resultant ISO contained 4+ hours of HDV video. DVDA is a single threaded app, whereas Vegas is multi-core aware.

Intel i7 920, 12GB RAM, ASUS P6T, Vegas Pro 10 (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Nick

As per Mike’s suggestion, that will mean having to do a re-capture, but it may be worth the upfront effort and spare you some grief. We assume that your source is a tape.

Intel i7 920, 12GB RAM, ASUS P6T, Vegas Pro 10 (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

FYI, MXF is a breeze to edit in Vegas, and maintains image quality. You might want to consider combining the MXF files into one large file. Saves you getting hundreds of smaller MXF files which can be a nightmare to manage. I believe that is done in the clip browser.

Intel i7 920, 12GB RAM, ASUS P6T, Vegas Pro 10 (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Fitting 90 minutes of SD video should be more than possible on a DVD, unless you are not using VBR encoding. I have shot 90 minute wedding receptions in HDV in poor light and then used 2-pass VBR encoding and delivered it on a DVD. Even when played back on a high-def TV, the graininess is not noticeable and looks great. If I use CBR, the grain is noticeable as DVDA does the heavy rendering and does not do so as optimally as Vegas.

Intel i7 920, 12GB RAM, ASUS P6T, Vegas Pro 10 (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Go to File | Render As… and select MainConcept MPEG-2 with the DVD Architect NTSC Widescreen video stream template for 16:9 or the non-widescreen template for 4:3. Then render your audio as Dolby Digital AC-3 Pro using the Stereo DVD template. If you give them the same name just with different extensions, then DVD Architect will know that the files go together. then just author your DVD in DVD Architect.

If you want fit and render, say, 90 minutes onto the same DVD (e.g. the 1st and 2nd half of the game on 1 DVD), you will need to use a bit rate calculator (such as Mark’s Bit Rate Calculator) and select 2 pass variable bit rendering as a Custom setting of the MainConcept MPEG-2 with the DVD Architect NTSC Widescreen template. The quality should be quite acceptable for DVD playback.

To download and use Mark’s Bit Rate Calculator:

https://www.johncline.com/bitcalc110.zip

Intel i7 920, 12GB RAM, ASUS P6T, Vegas Pro 10 (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6