Yes, I am using the Cineform intermediate template that came with Vegas Pro 8 to reencode the mts file.
I am using 2.8 version.
Thanks for the link. I will try it out.
If it is within the budget of the project I will also consider just buying the Cineform codec since my clients have saddled me with this media, I have a lot of it and I will have to use it.

thanks for you help

david

I've had the Cineform codec produce artifacts like that when I tried rendering to unstandard frame sizes. Cineform seems to work fine for 1440x1080, 1280x720, 720x480 and 720x576. It seems to get kind of strange if you select unstandard sizes though, whereas the Pegasys MJPEG codec for instance can do whatever size you want it to.

Laurence:"I've had the Cineform codec produce artifacts like that when I tried rendering to unstandard frame sizes."
That's interesting. I kept running trials with a 5 minute sample, each time getting more conservative until I rendered out at stock setting 1440x1080. Still no joy. Thanks for the pegasys tip.

I dug a little further - even though the template says Cineform 2.8 when I look at the properties of the resulting file:

General
Name: MJ6_cineform hdv native.avi
Folder: K:\Aud4Int\Filter\Power Shell\Monday
Type: Video for Windows
Size: 2.31 GB (2,362,434,048 bytes)
Created: Friday, May 16, 2008, 09:32:51
Modified: Friday, May 16, 2008, 09:41:46
Accessed: Friday, May 16, 2008, 13:20:36
Attributes: Archive

Streams
Video: 00:03:45.592, 29.970 fps, 1440x1080x32, CineForm HD Codec V3.3.0
Audio: 00:03:45.592, 48,000 Hz, 16 Bit, Stereo, Uncompressed

CineForm HD Codec V3.3.0. Now that is interesting.

I downloaded the free CineForm NEO Player and still no joy. Maybe I need to reboot to get the codec to be noticed? I tried Media Player and I get the same artifacts.
http://cid-cd0e17091a1e1d24.spaces.live.com/photos/cns!CD0E17091A1E1D24!124/

While I haven't purchased Cineform directly I may still ask a question on their site.

I'll let you know what it takes to get rid of this.

ddt

Maybe you have encoded with a newer verion and decoding with an old. There is a bug in Vegas8 that sometimes it loads the wrong decoder. To prevent this error, rename the cfhd.dll component in program files/Vegas Pro 8 directory. If this doesn't fix things, send a short clip to support by filing a troublt ticket with www.cineform.com/support.

David Newman
CTO, CineForm

No, you don't need to reboot. There is something unsatisfactory in your workflow. 40 hours of HDV is a lot of data, but presumably the final length will be less. Assuming that you don't have the capacity or time to convert it all to DI, I would do a rough cut with m2t and render that to avi using cineform (maintaining full frame). You can finish the cut and reframe. I guess you could complete the cut in m2t before generating the DI. Maybe "reframe" isn't the right reading? If you want that frame size for output, do that in rendering.

You are right, 40 hours of HDV is a lot. Ultimately the output of this project will be 40 5-25 minute videos. There were two HDV cameras with for 4.5 days. If I have my way we will end up using less than 15% of the HDV since most of the useful moving pictures are Camtasia captured screen.
Still to figure out what I need, I still need to see them sync'd with audio.
The good news is that the second camera rarely has anything useful enough to bother with so I am going to start with intermediates only for camera A.

So, I downloaded the 15 day trial of CineForm Neo HDV and voila, clean intermediates. I don't have time to fight a war over why the Sony version of the CineForm codec codes as caca. Even after I had the HDV codec loaded the Sony Cineform coded files were unusable.

So the answer is, spend $250, advance to GO.

I spend $200 bucks to add a 1.2 terrabye RAID 0 array to hold the intermediate so now it will just be rendering time. It should only take 60 hours to create intermediates for 20 hours, by next week I can be editing.

ddt