[Jason Lingohr]

Yeah, very backwards.

A few irksome observations having installed the NeoScene demo:

• Matching the intermediate project settings to my CFHD avi, and the preview works great. As long as the preview res matches, it’s fine. As soon as anything changes in the new project settings, including field order, the preview turns choppy.
• If I attempt to render to 30fps (native for the 5D Mk II footage), Vegas just sits there with the clocks running, and no frames written… ie. the classic Vegas hang (and I thought good practice was to match input settings)

I would have thought if I have progressive source media at 30fps, I’d want to stay with that… but as it stands, this seems impossible 🙁

Also, even though I rendered to 1080p, MediaInfo doesn’t even show a field order, and Vegas seems to think it’s still i. Changing the codec from Auto to Progressive made no difference.

So it would seem that I’m stuck with 1080i, when my source is 1080p.

Thoughts?

(Just discovered that there is a Vegas patch that may fix preview issues… https://techblog.cineform.com/?p=1424)

(Also, this is half relevant to the i/p issue: https://techblog.cineform.com/?p=1407 … but, as my source is MOV, my issue still stands. I guess when rendering to CF AVI, the codec has no idea of i/p or isn’t applicable?)

[Jason Lingohr]

Truly bizarre… I just don’t get that codec as an option. Followed your instructions to the letter. From what I can tell, the machine it is installed on is missing the cfhd.dll file.

From the sounds of it, NeoScene is worth the money, and I’ll want full 1080p renders anyhow so will go down that path.

Thanks SO much for your help John!

[Jason Lingohr]

[John Rofrano] “When you pay a lot of money for a camera you expect to be able to use it’s output without a lot of transcoding but unfortunately, the best format for acquiring is not always the best format for editing.”

Yeah, exactly. Having said that, I’m not entirely sad that Canon chose a MOV container… and I’m definately happy they went with something smart like H.264 inside it!

[John Rofrano] “Vegas Pro 9.0 32-bit has the CineForm codec but no templates.”

Right. Thanks for the info; last bugging of you — what is the codec called! I’ve looked under avi and others and don’t see anything that directly names CineForm. I realise I need to goto Custom, but what dropdown do I select for the codec?

The closest I got was using m2t as per what I posted; as far as I can tell it has used CineForm (as wow, finally, I have realtime preview!) but can’t be sure, and would much prefer to be working with an avi container than an MPEG-2 TS.

Thanks SO much for putting up with the noobish questions thus far. I don’t get why any form of intermediate documentation has been both removed from Vegas’ help, and not updated in their knowledgebase…

[Jason Lingohr]

[John Rofrano] “Lots of people with cameras way more expensive than yours (including myself) use it because it produces very high quality output”

Sorry John, I didn’t mean to sound like I was in the highend of the field. I guess I’m used to being considered that in the stills arena.

Excuse the continuing questions, but is Cineform NeoScene included with Vegas 9, or any Cineform codec for that matter, as I don’t see them. I read this from Sony’s site:

2. Go to File > Render As. The Save As Type should be set to “Video For Windows (*.AVI)” and the Template should be set to “HDV 1080-60i Intermediate”. Now click Save. The files will be saved as an AVI that utilizes the Cineform HD V2.5 codec. It retains all the detail from the M2TS file.

If you do not see “Video For Windows (*.AVI)” and the Template “HDV 1080-60i Intermediate” in your drop-down menus, then you can render the file to MPEG-2. Go to File > Render As. The Save As Type should be set to “MainConcept MPEG-2” and the Template should be set to “HDV 1080-60i”. Now click Save.

Does that still hold true for 9, or does one have to purchase this codec seperately?

(Oh and why wouldn’t the avi version show up?)