AVCHD in vegas

x0091935 wrote on 10/4/2009, 2:12 AM
I'm a vegas, premiere and final cut user, and i love vegas. But since i brought a sanyo xacti hd2000 o records in 1920 x 1080 p 60frames i can't render my files...i have 4 gb but a 32bit system...then no more then 3gb used...i still get the red clips when i put my footage in a timeline....please...can anyone help me? using vegas 9 b....still in the same....

Comments

DonM1 wrote on 10/4/2009, 2:55 AM
From your question I can't understand where you are getting stopped, sorry. But a thought came to mind - might you be using FAT32 drives?

-D
ccliffy wrote on 10/4/2009, 7:26 AM
4 GB memory/RAM?

how much free hard drive space? vegas can handle AVCHD
JohnnyRoy wrote on 10/4/2009, 9:00 AM
> But since i brought a sanyo xacti hd2000 o records in 1920 x 1080 p 60frames i can't render my files...

Just to be clear (based on the title of this thread) the Sanyo Xacti VPC-HD2000 does NOT shoot AVCHD! This is your problem. It records in some unique flavor of MPEG-4/H.264 which does not conform to the AVCHD standard which is why Vegas and other NLE's can't deal with it. People should be very careful when buying inexpensive H.264 cameras because they are nothing but trouble if you plan to edit your footage. They are designed to 'Shoot-N-Watch' and for that they are very good. If you want to edit, make sure the camera has the AVCHD logo.

I would start by converting the Sanyo files with an external program to a format that Vegas can edit. Perhaps you can use something like Super(c) to convert them to the Huffyuv or Lagarith codec.

If you are looking for an inexpensive HD camcorder that shoots AVCHD I would recommend you look at the Sony HDR-CX100 for $380 street price it can't be beat. I have the older CX12 and I love it for casual shooting and it edits beautifully in Vegas Pro 9.

~jr
LReavis wrote on 10/4/2009, 10:24 PM
I routinely render files from my HD2000, with rarely a problem - generally rendering to 60p (59+ frames per second, not fields, as with interlaced) using Cineform (after a NeoScene install). So far I only have had problems - crashes - if I try to put too many files on the timeline at once.

After I render the clips, then I use the Cineform version in my project - I don't try to edit directly from the .MP4s. The Cineforms are a bit jerky in preview (for some reason, more so than the native 60p .MP4s on my machine), but otherwise seem to be rock solid.

I think I saw red frames once, but can't remember the details. Q6600 on P5B, WinXP 32-bit, 8 GB RAM (I'm about to go to 64-bit Win7).
hazydave wrote on 10/10/2009, 12:16 AM
There does seen to be a "disagreement" between Sony and Sanyo with at least the 1080/60p video out of the HD2000 and FH1. This really has nothing to do with Sanyo being "cheap" (though the FH1 is relatively cheap, it's a real camcorder, not one of these glorified webcam like those from Flip and Aiptek, etc). Sanyo was making MPEG-4 AVC cameras long before Sony, Panasonic, etc. cooked up the AVCHD spec (which is derived from Blu-Ray)... so they used existing standards. In theory, anyway.

There's really no advantage in Vegas to editing MPEG-2 transport stream files and AC-3 audio, rather than MPEG-4 transport stream files and AAC audio, which is the only difference between Sanyo's output and that from an AVCHD camcorder, other than possibly the peak bitrates in Sanyo's variable AVC, and of course, Sanyo's 1080/60p mode, which none of the AVCHD camcorders support.

I have found that the crash in Vegas (which some people don't see, but many do) seems entirely related to some disagreement in the handling of the MPEG-4 transport wrapper. If I remux the Sanyo MP4 using either mp4creator or (when it doesn't crash) mp4box, the video loads and edits just dandy in Vegas. On a fast computer.

I still much prefer Cineform transcodes for any complex editing of AVC, or even MPEG-2 if there's lots of editing to do.

Cineform gets jerky when your HDD is too slow.. that's at least the usual problem for Cineform on playback. For 1080/60p transcoded video, it's about 28MB/s worth of data (100GB/hour).. you need a good, fast, modern hard drive to keep up with that. Buffering probably helps you there, too.
Rv6tc wrote on 10/10/2009, 11:08 AM
I'm having similar problems as the OP. Trying to edit AVCHD from a Canon HF-S10. I've been shooting at 17mbps versus the 24 to try to eliminate the bandwith problems that Spot talks about in the VASST AVCHD training DVD. But I'm getting random red frames... "out of memory" lockups. And many other assorted random problems. I have an i7-920 CPU, ASUS P6T MB, and 6 GB RAM on Win 7 32-bit. Also, I did Blink's memory tweak, which at least allows me to render... when the editing works.

Seems like there are some people that have made this work. Unfortunately, I don't seem to be one of them.