Thanks Bill.

I did notice with NEO no scope problems! It may be psychological but I thought the Cineform avi images retained more detail in the highlights than the .mxf files did.

I did a great deal of comparisons A/B tests. CFHD does give more detail, but, I thought it was so slight as to not really be noticeable. You're eyes are better than mine.

Bill:
The old rename CFHD didn't do it for this one.

I have deleted all the converted files and reconverted from the SxS card to a new directory and still certain files when added to the time-line kill Vegas. They are not the same files as killed it before so it seems Cineform is corrupting the files during conversion. I know I need set up a ticket with them but maybe someone here understands sooner.

Yeah, I'm seeing the same thing. Not sure why.

I'm not finding a problem, other than Vegas having to be told the file properties. I did have problems trying to insert an mxf file into a project with 1440x1080 50i properties, but that was before all the trouble I had with the "sorry" notice. Was OK when I rendered the mxf files to matching properties.

To check before speaking, I've just opened a new project, imported an mxf file, rendered it to a new track (which made it 1140 x 1080 50i), then "rendered as" the mxf to 1920 x 1080 25fps progressive and imported that to the TL (Vegas says properties 1920 x 1080 50i), and finally used HDLink to convert the mxf file to 1920 x 1080 25p and imported that to the TL (again Vegas says 50i). I changed properties to progressive. All play on same TL.

So, have you got the most recent NEO HD? NEOHDv3.24b155? Have you removed AJACaptureFilter?

Be nice if Vegas had the 1920 x 1080P 25 template installed, but I suppose it doesn't actually matter whether it's 25P or 50i when it gets displayed.

The problem has all the appearances of being RANDOM. Despite the fact that you haven't experienced it, the fact that Michael and I both have makes it real. I do have the most recent version of Neo HD, altho' I'm sure the version is not related to this problem.

Bill, did I say it wasn't real? What is it with some of you? All I was reporting was the test I ran in an effort to respond to a question. Guess one shouldn't bother. Sometimes it's nice to know whether the problem is intractable or not, and here it appears not. Maybe I'll have trouble in future.

feeling a wee bit defensive, are we, serena? exactly what is YOUR issue with my posts? you always have some negative response. get off your pedestal.

Ah, not defensive at all. Annoyed, yes. But glad that you've stated your problem.

annoyed? at what? that I don't buy into your reality as mine? c'mon, don't be shy
let's have it out on the table...I dare you...lol
my only problem is that you consistently argue with me. I don't have a problem with what you say...you're, apparently, a very smart person...yet you have a bit of arrogance..

Well I can see how you might perceive "arrogance" because I always try to speak from knowledge rather than with opinion, and hence your "pedestal". However that is a severe mis-reading. Checking back a bit through your posts I can find only one case of my responding to you, and I supported your statement. I see other instances where people had responded negatively to you. So I think you actually object to the tone of my posts in general, rather than any interaction with you specifically. The odd thing is that I had you on my "list" of people with expertise but, unlike the impression you have, I can be mistaken.

Fight, fight, fight... I still think HD DVD is going to win .... oops wrong thread...

;-)

Cineform tell me an new version of NEO-HD will be out tommorow which "might" address this issue.

Mike, did they say it is a recognised problem, or just hopefully that another version will fix it? There were several updates beyond build 148 where on running HDLink I got the error message: "error while unpacking program, error code E2, please inform author". I couldn't get a working version beyond build 148 until build 155 was released. And b148 gave me trouble on the timeline. Cineform said this seemed to be a random error, possibly related to virus checkers. Which wasn't my problem (isolated machine without protection).

I have no virus checker on my edit machine because I don't connect it to internet. Here is what Cineform said:

Please provide us with more information
Comment(s): We have a new build of NEO HD that will be uploaded by tomorrow. It may fix this issue. Give it a try and let me know if it works or not.

Ticket Information:
Ticket #: 611-5792334
Date Created: 2/29/2008 12:39 PM PDT
To update or check the status of this Ticket:
- Go to: http://supportcenteronline.com/ics/support/default.asp?deptID=614&ticketID=5792334

- Log in, and you will be automatically taken to the Ticket page.

Very similar to the response I got! But hey! Eventually they were right. It worked.

EDIT: clarification: I wasn't suggesting that a virus checker was a cause of the problem you are experiencing -- different problem.

Incidentally, checking the Cineform site, I see NEO HD build 154 posted for download. I'm running b155.

For me it is build 155 that is problematic. I think they are regressing to 154 to fix a bug as 154 was posted as the "new" version today????

Interesting --- I didn't see the 155 official posting, only got it in response to a ticket. I don't get advice of updates, despite having asked for them.

Attn: Bill / Serena (good friends now I hope):

David Taylor (Cineform) has directed me to the build 157 beta. Here is a link. The current full version is the build 155 that I was running with problems.

http://www.cineform.com/downloads/NEOHDv325b157-080229.zip.

Mike

Well, build 157 has same problem for me. Bill, you said you have seen this so how do you deal with it? Must I open files one by one to what is bad and then reconvert them?

These sort of problems are most annoying, where we throw stuff at them in the hope that they'll go away. Some time ago (back 2 or 3 years) Cineform had a temporary problem with AMD processors. I have AMD, and I see you have Intel. Most likely of no relevance.
Incidentally, the "sorry" notice has re-appeared in V8, but I'm ignoring it.