Depends on your system. i-class CPU highly suggested.

Works just like files from anywhere else, on my Nikon D300S.

geoff

My biggest issue right now is one that there is still some debate about (even though I know that I'm right), and that is that on some DSLR video clips in MOV format, Vegas stretches the color range out from sRGB to cRGB. It isn't really Vegas's fault directly. It's the VFW pipeline that Vegas uses. Anyway, mov clips from my Nikon D5100 slide onto a Vegas timeline in cRGB range, but onto an Adobe timeline in sRGB range. Same thing with the higher bitrate mov format from my Panasonic GH3 (AVCHD is fine). GoPro range is also stretched. Yes, you can put a cRGB to sRGB correction filter on the video to put the range back where it should be, but at 8 bit conversion it looks kind of banded and with 32 bits renders take forever.

Nobody else seems to be bothered by this and I don't even think many here will believe me, but this issue is driving me a little nuts, and yes, I am absolutely 100% certain about this.

No problems with Panasonic GH2 standard or with the various available hacks but I am not using MOV format

Thanks everyone I appreciate your answers. My cameras are still HDDV and most of my work comes from those cameras. I do not remember anyone giving DSLR footage. I have done AVCHD and the likes. I have an I7 machine so I should not have any troubles. I remember when Vegas was struggling with the AVCHD format for a little while that is why I asked, and the customer was curious as well. Thanks again you guys are great. this is a great forum

Edited a project shot with Canon 5D, and Vegas Pro 12 worked like a champ.
No issues whatsoever.
Think the footage was .mov.
Sound right.
Vegas was her usual agnostic self!
I have one of those i7 thingys.

"I have one of those i7 thingys."

I laughed out loud. Thanks.

Hey, I still remember when a 4mhz Z-80 with 64K of memory was the fastest thing on the planet !! (in fact, it is still in a box down stairs come to think of it ... )

mikey