[Nigel O’neill]

Great article. I was going to get a GTX590, but I don’t think the rest of my system will keep. I’ll settle for a GTX580 and save some $$ and avoid a PSU upgrade. Yay!

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (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]

Just used SVP11 for a 3 camera HDV multicam edit with Vasst Ultimate S. Apart from slightly different looking ‘render as’ templates and a few other cosmetic differences, it still works :=)

It is an evolutionary rather than a revolutionary change for what I do. I wish Sony would bring back Cineform… . I miss v8 🙂

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (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]

I am not having such issues capturing from HDV tape into SVP11. I have only experienced such problems with drop outs on the tape, which causes a new clip to be generated each time.

One thing to check is your 1394 firewire driver which you might have to either check for updates for, or downgrade it to a legacy driver. My windows 7 system is using such a legacy driver as it was not recognising my cameras. I have noticed my laptop firewire completely drops out after 30 or so minutes in a live capture environment, but I have not bothered rolling back the driver as I was only experimenting.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (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]

Unfortunately this is a known issue for which Sony has no fix. It has happened to me in a couple wedding video projects as well, and I noticed it only happened when I was nesting veg files. In the projects I have done since without nesting, the problem has not occurred. It’s a real pain in the b*tt when it happens, and I ended up having to render out an m2t file once I completed the edit and before shutting down my PC.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (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]

Are you using 2 pass VBR rendering? I have seen this occur before, and the only ‘cure’ for me was to do a single pass VBR render.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (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]

Depends on the capture rate of the DVD-r camcorder. Typically, they record at mpeg-2 8.5 mbps (compressed), which compared to mini-DV tape of 25 mbps (uncompressed) is a 1/4 less in quality. Many DVD-r camcorders allow you to record more, but at a lower quality setting. A good indicator of quality is the recorded length on your DVD-r. If it is around 30 minutes per disc, you have selected the highest possible bit rate and quality setting. If your discs are 1-2 hours or more in length, you have compromised quality for quantity. There is no software that I no of that can replace the missing bits of data.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (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]

Unfortunately no. Stabilisation works by cropping the video and then compensating for unwanted pan, tilts and motion using the cropped out areas to make the correcting/counteracting adjustments.

You will notice that if you use an event that has a very deep zoom in and out and stabilise that event, the cropping will be quite excessive compared to if you just stabilised a relatively static zoomed out (or in) only portion. You might want to consider splitting up your event and stabilising the sections where there is minimal zooming, and add cutaways when you are zooming in, or cut the zooms out all together.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (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]

David, you cannot ‘reverse engineer’ data that has been removed by a render process. You really need the original source files to get the best possible quality.

There are products on the market that claim to upscale footage, but since I have not used them, I cannot comment on their efficacy. Perhaps someone else has and will respond to your post.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (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]

1) You would use the DVD import feature of Vegas, pop it onto the time line and add your chapter markers, so that when the rendered file is imported into DVDA, it recognises them.

2) Alternatively, you can create the chapter points in DVDA. The thumbnails can be easily generated in DVDA without screen grabs, and you can select any section of video.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (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]

I have taken the upgrade path from v10 to v11, but probably will not install it until 11b or 11c.

I am still on 10c as it does exactly what I need. Sure, it does crash now and again, but it has never failed me on a render since version 8. I cannot say the same for Avid, Premiere and Pinnacle, which I have used in the past and failed to render. I don’t get paid if I can’t produce the goods. I would rather put up with the odd crash than not be able to produce anything at all.

I save regularly and hit Ctrl-S almost out of habit, so I usually do not lose more than a couple of minutes work, sometimes none at all.

To Angelo Mike, I am mystified as to what could be causing your issues, but as your are using your PC for other applications including Internet browsing, one of the following could apply:

• interference from your virus/firewall software
• installation of a CODEC pack <- These are very bad for Vegas
• corruption of Vegas system software from other software installs
• a virus
• Use of an unsupported CODEC eg DIVX in a project
• etc

Keeping your editing system clean is a must, especially if you intend to run a business from it, therefore a second editing workstation is a must.

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