Vegas 7e and Neo 2K HDV

revupvideo wrote on 5/25/2007, 4:37 AM
Upgraded to Vegas 7e and then bought the upgrade of Connect HD (worked fine) that became NEO HDV (renamed only?). As stand alone NEO works fine but just try and render as an HD Intermediate file and it then tells me I must buy Connect HD (which does not exist) even though the correct codec is there and the original file was created by NEO as an AVI file!!!!!

Has anyone else found this? To me it seems that Cineform and Sony have got their wires crossed and not told each other what they have done. As usual it is us the end uder that gets caught up in things.

Comments

revupvideo wrote on 5/25/2007, 9:46 AM
Thnaks for that. I uninstalled the player but still the same problem. Re-installed NEO, VEGAS and so on spent an hour or two on this and still no resolution. Have emailed CONNECT with a strongly worded email. Awaiting the excuse or solution.
teaktart wrote on 5/25/2007, 10:44 AM
Don't hold your breath for a response.....
You'll die waiting...

Eileen

3 weeks and counting waiting for a reply to my support ticket to CineForm!!!
Laurence wrote on 5/25/2007, 12:44 PM
Eileen:

Cineform does tech support a little different than other people, but it's kind of nice once you figure it out. Sign onto the Cineform site, and they have what amounts to a private forum between just you and them that you can look at. It took me a while to figure it out at first, but now that I have, it makes sense. You can see your online dialog with them at a glance rather than having to sort through your old emails.

Anyway, if you sign onto their site and look for this, you'll likely find that your post was answered shortly after you sent it. They probably sent you an email linking to this that got tagged by your junk mail filter.
David Newman wrote on 5/25/2007, 5:40 PM
The support guys and myself try our best not to leave people hanging. If we missed you please follow up.

For installation issues, Sony, Connect HD, NEO HDV ,NEO player are all fighting over one component: windows/system32/cfhd.dll So delete it then install the tool you have the license for. If you don't own any CineForm components, re-inssall Vegas, otherwise all you need to do install is your old Connect HD or new NEO HDV/HD/2K. Vegas only uses CFHD.dll, nothing else from CineForm, so this is a simple way to control this arbitration. You can even back up CFHD.dll CFHDmine.dll and install NEO Player to get its bonuses, then more CFHDmine.dll back to CFHD.dll. We are working to make the NEO Player more friendly to Vegas users.

David Newman
CTO, CineForm
Serena wrote on 5/25/2007, 6:17 PM
David,

Your website doesn't really lead existing customers through the transition from the old Cineform to the NEO suite. Recently, when I visited checking for any updates to Connect HD I had some trouble finding it. I found it by borrowing down through FAQ. Subsequently I found other paths, but nothing that's obvious on your home page.
It would help if your site provided more thorough guidance for people interested in NEO. The business with NEO Player is obviously one area, and the need for SSE2 enabled CPUs, which I, for one, paused over but didn't understand. So NEO HDV works fine on my AMD 64 2x 4800, but not at all on my supporting AMD XP 2800 machine. Unfortunately I found that out after buying the upgrade for the XP (I presume there is no way to hand it back).
teaktart wrote on 5/25/2007, 8:47 PM
Ticket #611-3712846

With an original posting date of 12/28/06 when I started having these problems with ConnectHD and CineScore and Vegas 7c.

The whole history is on my support ticket ....including my 4/28/07 posting which remains unanswered, no reply, "work in progress"....

Eileen
David Newman wrote on 5/26/2007, 9:03 AM
Eileen, It might be worth starting new ticket with your current issues as the 7c issues are gone with that version -- it did have issues with 7b&c, fortunately both 7d & 7e are much better. In the end we only address our bugs, so do your best to demostrate the issue, as if we can't reproduce it here, there nothing much we can do. It the moment the are no open bugs listed for Vegas support, I'm not saying there aren't any yet to be discovered. Everything reported lately is either an installation issue, which upgrading the cfhd.dll directly can address, or a few with the recent SSE2 requirement.

Serena,

Sorry your got caught up in the SSE2 change, there where too many good reasons to standardize rather than have products targeted to different CPUs. You maybe able to undo your upgrade, but I don't know the policy. In general we would advise trying the software first on each system you intend to use it.

David Newman
CTO,CineForm
Serena wrote on 5/27/2007, 11:47 PM
David,

Understand your reasons for SSE2 and agree I was a bit hasty in buying the upgrade. I've just got used to Cineform stuff working! Actually I did try NEO on the older machine, but in midst of all my difficulties I jumped to the incorrect conclusion that NEO not working was part of a more general problem. So when those got sorted (so that Connect HD worked again on both machines, and NEO worked marvellously on the AMD 64 machine, I went the next step. Anyway I got the XP CPU back working with Connect HD. It would have been nice if your site had been a bit more specific about SSE2 limitations, maybe providing a link to check CPU compatibility (such as the one I subsequently found). The difficulty is that some of us are not all that clever when it comes to the workings of the black boxes (not me, anyway).
David Newman wrote on 5/28/2007, 8:32 AM
Could you recommend that SSE2 test? We could simply link to that.

David
teaktart wrote on 5/28/2007, 10:46 AM
SSE2 enabled CPUs

What does that mean?
How would I know if my computer IS compatible with this?

I would like to avoid the issues that Serena has noted about this on one of her computers
Serena wrote on 5/28/2007, 4:34 PM
David,
Funny how one''s memory distorts things. Turns out that the site I went to did not detail all processors, but it did make the crucial statement:
"The SSE2 (Streaming SIMD Extensions 2) instruction set is included with Intel Pentium 4 and later processors, and with AMD Athlon 64 and Opteron and later processors."

Clearly the AMD XP didn't fit!

EDIT: a useful link might be http://en.wikipedia.org/wiki/SSE2SSE2[/link],
and specific to http://en.wikipedia.org/wiki/SSE2AMD and SSE2[/link].

The difficulty arises because SSE2 was implemented later in AMD processors than in Intel. Your statement of minimum CPU requirements is correct, but previously I think might have been less precise?
Certainly the query I sent to my "computer guy" quoting your webpage information contained "NEO products are for SSE2 CPUs not, older MMX only class systems : Pentium 3 and Alpha XP."
Unfortunately his reply said only that my CPUs were more modern than those!
David Newman wrote on 5/29/2007, 10:29 AM
Eileen,

Did Serena post help. SSE2 just means a computer purchased in the last 5 years for Intel and the last 3 years for AMD. Only AMD's Althon XP still seems to be used for video work, but unfortunately that CPU is not supported by NEO.

David Newman
CTO, CineForm
teaktart wrote on 5/29/2007, 10:36 AM
I actually looked up the same link and its still confusing...

I have an AMD 64 x2 4400+ Dual Core which is 1 1/2 yrs old so I gather that this is current enough and would work with NEO?

Eileen
David Newman wrote on 5/29/2007, 4:32 PM
Yes, and in our minimum system spec we list Athlon 64s, and as yours is a dual core that is well above the minimum.

David
mark-woollard wrote on 5/30/2007, 6:01 AM
David

I'm happy to report that my new E6300 Core 2 Duo system (2Gig RAM, nVidia 7900) makes Neo HDV work like a charm. On my old dual Xeon 2.8 (533FSB), 2Gig RAM, nVidia 6800GS, SATA RAID0, HDV capture (simultaneous conversion to CFI) using HDLink never worked reliably. I usually got a huge number of short clips, audio longer than video, and/or the red clip problem. I had to use Vegas or HDVSplit to capture. That's all gone away.

Mark