Vegas 10 was released today. When rendering to Cineform HD from HDV, the "configure" button in the render settings window is greyed out.

Is this a Sony issue or a Cineform issue?

Sony has confirmed that time limitation prevented the quality controls from being implemented in time for the lauch on version 10. I only just found out that it didn't make in. Fingers crossed for a point release.

I have already posted this on Sony Vegas forum, but I'm looking to transition my office as soon as I can get the problem fixed so I apologize for the double post.

I know about the grayed out button, but Vegas Pro 10 is simply reading "cannot find codec". I have NeoScene installed. Is there a conflict since I appear to be the only person who is having this issue?

NeoScene don't have the component Vegas 10 is looking for. We just updated the 5.2 beta to include the needed component.

Dan,
Problem fixed. Thank you.

I also want to add that my quick test of grading native Canon DSLR files vs. the Cineform shows once again that Cineform holds up better and is less likely to produce banding.

Vegas Pro 10a can't find the codec for NEOHD. I presume that b272 doesn't contain a fix?

EDIT: actually my question is a bit premature: I've struck this problem with NEOHD v4.3 b240 on my laptop, and for sure there is no update for that version. On the main machine I have v5.13 and haven't yet tested that with Vegas Pro 10a. Will check that in the morning.

EDIT2: VP10a handles NEOHD 5.13 without problems.

What is the fix for v4.3?

NeoScene don't have the component Vegas 10 is looking for. We just updated the 5.2 beta to include the needed component.


Version 5.2 installed. V10 still > Cineform configure still greyed out.

What is the fix for v4.3?

Upgrading it to 5.x is the solution.

Version 5.2 installed. V10 still > Cineform configure still greyed out.

It will be until Sony adds that control, hopefully in a 10.0b release.

Upgrading it to 5.x is the solution.

An expensive solution! Easier to not use Vegas 10 on the laptop. But probably that is only a temporary fix, as Vegas will continue along the upgrade path. Or not to use NEOHD on the laptop. Mainly used for transferring card data to HDD (so not a huge loss), but does seem a pity to have a NEOHD licence that can't be used.

Vegas is occasionally (at random) muting the video of NEOHD clips. "Cure" is to exit and restart Vegas, which is a nuisance. No errors reported or other indications of fault and affects all occurrences of the affected clip (timeline, project media, media manager). Any thoughts on the likely cause?

Audio is all Vegas, the SDK they use from CineForm is video only.

As NeoHD allows for two activations, why not just put 5.2 on the laptop.

Two activations? I thought it was only one (which is the reason, years ago, I bought 2 licences) -- has that changed over the years?

"Audio is all Vegas, the SDK they use from CineForm is video only."

Which means that Vegas is temporarily losing the address of the SDK for the clip?

We allow for two activations, but it is a single user. It was intended so you can run it on laptop and a desktop -- not for two work stations with two operators. Been that way for long time.

I don't follow you logic for "losing the address", if it is audio then it is question for the Vegas support team.

>>I don't follow you logic for "losing the address", if it is audio then it is question for the Vegas support team.<<<

Very likely my logic isn't logical. However it is the video that is vanishing, not the audio. I understand the misunderstanding: neither would I use the term "muting" in relation to video, but Vegas does.

The licence question: originally the 2nd licence was for another workstation on a local net and I had forgotten how the licence system worked.

We allow for two activations, but it is a single user. It was intended so you can run it on laptop and a desktop -- not for two work stations with two operators. Been that way for long time.



Really? I bought 2 licences for the same reason! Nice update.