Just read about the other issues reported with 5.2, I have opened a ticket for troubleshooting but wonder if there is something in common with our systems where we experience the same problems with 5.2. It does not seem widely reported some perhaps some hardware issue?

Here is my system specs -

Mobo - Asus P58X68 Premium
Intel i7 960
Windows 7 64-bit
12 GB - DDR3 RAM
Video card - nVidia FX4800

2 x RAID 0 volumes for O/S and cache (4 x Intel SSD drives)
RAID 5 e-sata volume for video

How would you use the proxies with Vegas?

Rich -

Here are my system specs:

Motherboard - ASUS P6X58D-E
Processor - Intel i7 980X
Memory - 12 GB DDR3
Video - nVidia GeForce GTX 480
Operating System - Microsoft Windows 7 Professional Edition 64-bit

1 x 1.5TB Drive for Operating System, Projects, Previews
4 x 1TB Drives RAID 0 for Video

- Rick

5.2.1 was released last night, that should help with several issues.

Same as all NLEs. With the project closed, move the source video into a sub directory, then reopen the project. Vegas (like Premiere and FCP, etc) will ask where the media is, you can then point to either the masters or proxies as you need.

I installed build 279 and playback in CS5 is much better although it's still glitchy and hangs quite often especially in the source monitor. I also had 2 blue screen system crashes in several hours which I have not had before. I could not play back cineform AVI's in either VLC or classic media player either due to errors, have reinstalled build 268 for now.

While it sound like we still have some improvement for the source monitor, are can't be responsible for any blue screens as that is due to software running at a lower system level than we provide. Likely you need device driver update for something, update you graphics card drivers, RAID drivers etc. Blue screens should always point to a hardware layer failure or the drivers that connect to hardware. In the user mode software we develop, we couldn't cause a BSOD even if we tried.

We work in media player without issue, classic or the version now shipped, I use these all the time. So you may not have had a correct install. VLC doesn't support DirestShow, VideoForWindows or any third party codecs -- it is a open source distribution codec player only (H.264, MPEG base etc.)

Hmmm...
My experience as well- including BSOD (first time this has ever happened on my Win7 64 system).
I do have the latest fx 3800 GPU drivers & can't think of what else (hardware wise) would impact this.
Since I am in the middle of a big (1,000+ clips) project, I think I will stick with build 268 for now.
Everything works perfectly- hard to beat that...

It's good to know it's not just me me, Perhaps we have similar system specs. I ghosted my O/S back to build 271 and have had no issues in 5 + hours of editing. I just updated nVidia FX4800 drivers (the previous release were July 2010) Raid drivers are all up to date. I have not tried any 5.2 builds since upgrading FX4800 drivers as I have too much work to get done but the old vcard drivers were only 3 months old. Raid drivers and mobo are all up to date. Mabey a MOBO Bios update would help?

Anyway - Cineform folks are doing a great job at providing these releases, it's appreciated and I know of no other company that consistently works with their customers at this level and provides such awesome tools!

Hadn't thought about a BIOS update- I'll look into that.
CF guys are indeed really great!!
This glitch is nothing like what we went through FOREVER with CS4/CF.
Build 268 works great, so it's not a critical issue