[Nigel O’neill]

Is this a hardware or software RAID issue? In either case, the data is not lost as it is ‘mirrored’ under RAID1. If you were using RAID0, you could say goodbye to your data.

You should be able to regenerate the array after replacing the faulty disk, or alternatively, use a utility such as Testdisk to access the remain good drive in its orphaned state.

The correct recovery procedure depends on the hardware and operating system you are using. Without this basic information, it is hard to provide any reliable advice beyond the generic.

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]

Rod

What version of Vegas are you using? It could be a codec compatibility issue.

What video file format are you trying to load? Vegas generally does not support DIVX and is a bit touchy with certain versions of Quicktime mp4’s.

One way to tell is highlight the file in Vegas’ Explorer window. If Vages recognises the audio and video stream, it displays information about the file.

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]

That is correct.

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]

@Matt – yes, correct, thanks for pointing that out.

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 agree with Mike. Note that excessive panning and cropping of video can result in some artefacts that make the footage appear to wobble or jitter.

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]

Try disabling automatic scene detection in the capture preferences.

If you end up getting nothing, check as well to see if your disk formatted to NTFS or FAT32. FAT32 has a known file size creation limitation of 4GB.

You can convert disks to NTFS without losing data or having to reformat.

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 would do the multi-cam edits in the source projects and then nest the veg files in a master project. Any changes/tweaks to the source projects should automatically update in the master 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 after changing them to mpeg, try joining them using the binary copy method and see if that works.

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]

Vasst Ultimate S 4.1 has an audio duck feature plus a host of other goodies such as lower thirds, montage and quadcam.

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 had this problem with AVCHD files from a HDD camera and sometime ago someone suggested using DOS’s binary copy to join files e.g.

copy /B file1.mpg+file2.mpg newfile.mpg

It’s been a while I used DOS, you might have to check the syntax!

It might accept wildcards too.

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