[Nigel O’neill]

The only time I experienced that was when one of my templates was accidentally set to ‘none’ instead of blend for the interlace setting, but you have already tried that.

I use jpeg’s, though, typically between 240 and 300 dpi, and varying in size from 1.5 MB to 5 MB each. Are you able to try it with jpeg’s to see if the judderring effect remains?

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]

I have found that dirty tape heads can sometimes cause enough dropouts and force the creation of a new file. It happens on my HC3, and after a head clean, I am able to get clean, uninterrupted captures.

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]

Nest your separate projects (veg files) together under a new project.

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]

… and you right-clicked on the image and selected ‘reduce interlace flicker’?

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]

If you still have the original projects, you could nest them in a new project and then use the bit rate calculator and do a 2 pass variable bit render to a DVDA template. That does mean re-rendering, but on a fairly powerful i7 system, that should only take a couple of hours. This would give you the best quality output as you are starting from good source footage. You can then bring that into DVDA and create a DVD without menus (single movie).

If not, you can assemble the WMV output files in a new project and then use the bit rate calculator and do a 2 pass variable bit render. Quality will be an issue as you are essentially re-rendering already higly compressed files.

I use Mark’s bit rate calculator. If you search this forum you can find references and links to it.

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]

We need an FAQ section….

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]

Benjamin

You might want to check your DVDA template audio settings. If it defaults to PCM, it will want to rerender the audio and create DVD files that exceed the disk size. I set my DVDA audio to AC3.

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]

Sam

Enable auto-ripple editing (CTRL+L) and then click on the first clip, and whilst holding down the SHIFT key, select the last clip. Everything after the selection moves down the timeline as as well.

Instead of the SHIFT key, you can also hold down the CTRL key instead whilst selecting clips in any order you want. You can them move them. Have a try.

It’s a good idea to switch off aAuto-Ripple s it can have undesrable results, especially if you add a titles track and forget to move it as well.

I am aware that you are a ‘n00b’, but can I suggest you search the forum first or read the manual?

https://www.sonycreativesoftware.com/download/manuals

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]

In theory you should be able to remove the (f)ailing disk from the array, replace it with one that is identical or larger in size and then regenerate the mirror. Just how to do this depends on the WD RAID utility. RTFM… .

I had a bad run with WD disks, but it turned out to be my RAID controller on the motherboard was at fault. I ended up using Windows RAID instead (in software) and not only did the problems go away, but my system performance increased significantly.

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]

Sony Vegas will not encode QuickTime h.264 files.

You use the Sony AVC “render as” preset and select the highest resolution with the = in front (this means that the preset matches your project parameters). Then use Apple Quick Time Pro (it’s not free, but reasonably cheap) to make the QT file.

You might also want to search this forum for Quicktime and read the threads.

https://forums.creativecow.net/thread/24/927210#927217

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