Connect HD 3.2 now in public beta

Back to post

Comments

David Newman wrote on 9/14/2006, 11:22 AM
Conversion error isn't happening here. Please verify that this file exists

C:\Program Files\Common Files\CineForm\CFVideoChange.ax

If it does try registering it :

regsvr32 "C:\Program Files\Common Files\CineForm\CFVideoChange.ax"


Jayster wrote on 9/14/2006, 11:29 AM
epirb - you mentioned that the file you captured with Vegas barfed when you try to convert it with HD Connect. Perhaps that won't happen if you capture it with HD Connect instead of Vegas.

Vegas said in their 7.0a release notes that they added timecode reading to their HDV capture. Maybe something they are doing is incompatible with HD Connect's conversion software.
epirb wrote on 9/14/2006, 11:39 AM
David,
i am working with Jake in support I am also sending this to him.
I went thru again and made sure all .ax files were registered.
This time howvere the file you mentioned when i try I get the following message:
LoadLibray("C\Program Files\Common Files\Cineform\CFVideoChange.ax") failed- the specific module could not be found.
David Newman wrote on 9/14/2006, 12:28 PM
We will have worked it out. For new beta has every more thread code than we reported, this required a DLL that wasn;t in the installer. We will put this in the next beta. Good find. It is what beta testing does well.

David Newman
CTO, CineForm



epirb wrote on 9/14/2006, 12:48 PM
David,
the .ax file Jake sent me fixed the issue! thanks so much for the fast attention and your teams effort to solve this issue.
A great product with great support ALWAYS!!!

Now its off to focus on why V7 crashes on all CFDI 's playback for me.
Even the newly converted file after our fix here.
Laurence wrote on 9/14/2006, 1:47 PM
I just installed then, then had to uninstall the multi-threaded version of the 3.2 beta. It worked just fine in Vegas 6 but would imediately crash Vegas 7. The original single threaded 3.2 beta works fine. I'm using a 3.06 P4 with two gig of RAM.
David Newman wrote on 9/14/2006, 1:52 PM
We have a new build going up that addresses the conversion issue. Looking into the Vegas 7 issues now.
epirb wrote on 9/14/2006, 2:00 PM
David,
FYI I have submitted my Vegas error reports RE the crash issue to Sony. Per your previous post said they (the reports)would not help you guys!
Again thanks for your hard work!
David Newman wrote on 9/14/2006, 8:28 PM
We can now see why Vegas 6.0 and 7.0 are "behaving" differently -- we only got Vegas 7.0 yesterday (someone forgot to put us in the beta list.) Hope to solve it soon.

David Newman
CTO, CineForm
DCV wrote on 9/15/2006, 7:27 AM
Holy cow,

Somebody really dropped the ball on this one. To think that all the time wasted here on this issue could have been easily avoided...

John
Jayster wrote on 9/15/2006, 7:56 AM
A forum user was repeatedly complaining that companies shouldn't be getting betas before we do. He said it was unethical and gave unfair advantages.

This is a case in point of why I don't agree with him.
p@mast3rs wrote on 9/15/2006, 8:01 AM
Heres my take on the beta thing. I dont think its unfair to give betas to companies/book writers/etc... as long as they are fair and equal about it. Like if I wanted to write a book on Vegas 7, I would expect to be given access to the program in order to be able to compete fairly with other Vegas book writers. If I werent given access, then I can see bitching about it. In this case, Cineform should have definitely got the beta as well.
David Newman wrote on 9/15/2006, 4:09 PM
The beta thing turned out to be a SNAFU over an expired email address. Not too much harm done.

Here is a new beta that at least addresses crashing on the systems I have tried. Connect HD 3.2 Beta

We will look into why Vegas7 is slower than it should be in a future release, but this should help get Vegas 7 working with CineForm again.

David Newman
CTO, CineForm
kcrosley wrote on 9/15/2006, 6:20 PM
Hey David,

At least for me, this version fixes the problem of Vegas crashing when rendering with my 1080 24p Cineform files. Thank you!!!!

Looking forward to additional Cineform enhancements wrt Vegas 7. You guys are great!

BTW, for anyone who is shooting in HDV -- especially if you like to do the "filmlike" 24P thing (deinterlaced, pulled-down to 24 fps) -- Connect HD (the "full" version of Cineform) is the bomb. Well worth the price.

(ASIDE: But seriously, Sony/Madison, what is the deal with with Vegas 7 not having been tested against full version Cineform? My very first impression of Vegas 7 was *crash city* because of these problems. The reason I licensed Connect HD in the first place is because it was so obviously promoted in Version 6. Same goes for Pixelan SpiceMaster, by the way... Bought PRO based on the great experience with the lite version included with Movie Studio 6, but the plug-ins have strange behavior with plug-in selector in Vegas 7. Seriously... WTF?)

Best Regards,
Keith

Best Regards,
Keith
David Newman wrote on 9/16/2006, 8:10 AM
Thanks Keith,

Looks like we will get this version out of beta soon so Vegas 7 users can get some stability back.

Anyone else please offer feedback on this new beta. Need to know if we truely have a fix.

David Newman
CTO, CineForm
LJA wrote on 9/16/2006, 9:31 AM
Version 2.7 of the CF codec (contained in Connect HD 3.2 beta build 28) appears to have solved the playback crashing problem I have noted in other threads. Thanks to CineForm. As soon as they knew about the problem, they fixed it. Too bad Sony hadn't followed up with CineForm to make sure that they had tested against V7 before V7 was released. CineForm intermediates are very important to us HDV users and therefore to Sony too.

Playback performance is still slow however, slower than m2ts under V7 and slower than CF HDIs under V6. Hope this can be fixed. Thanks again.
riredale wrote on 9/16/2006, 9:48 AM

"The beta thing turned out to be a SNAFU over an expired email address..."

Was it a couple of years ago that HotMail was brought to its knees because someone at Microsoft forgot to renew the URL "passport.com" license for $35? Stuff happens.
David Newman wrote on 9/16/2006, 12:54 PM
Very minor update that addresses epirb VideoChange error. This was an installer fix so the build number is still 28. New 1pm Sept 16th PST : Connect HD 3.2 Beta The resizing is now threaded for faster HD to SD or SD to HD conversions on dual core or dual proc system (it is N-way threaded for as many cores as you have -- tested up to 8.)

David Newman
CTO, CineForm
Laurence wrote on 9/16/2006, 8:19 PM
Well, it no longer crashes Vegas 7 on my system. Also, the page-file size seems to hold constant on 1080 video so I'm not getting the stuttering audio. I still see the pagefile size increasing on 1280x720 video though.
David Newman wrote on 9/16/2006, 10:18 PM
I found the page size is usage is much larger on V7 vs V6. I was concerned at first until I noticed M2T files doing the same thing. Seems frame caching is different but it is otherwise not an issue.

David Newman
CTO, CineForm
DCV wrote on 9/17/2006, 9:04 AM
I'm very happy to report that the latest beta (build 28) of Cineform ConnectHD and its codec has fixed the problems I was having with Vegas 7 crashing during timeline playback. The pagefile usage is still much greater than V6, but it's working now. Thank you David and your team for all your hard work! Now I can seriously look at purchasing V7+DVD :)

John

PS - I'm sure Sony and Cineform developers learned an important lesson here, please beta the next release of Vegas BEFORE it comes out!
epirb wrote on 9/17/2006, 9:31 AM
PS - I'm sure Sony and Cineform developers learned an important lesson here, please beta the next release of Vegas BEFORE it comes out!

While I agree that it should be beta tested It may be possible that Cineform may have been unaware of the release of V7(or at least the interanl changes that were being made) and that their release of 3.2 just happened to arrive at the same time.
I credit Cineform for the quick attention to "Both" issues.

The one I brought up was not so much a vegas issue as it was an installer issue(i think). both David (monitoring these furums after his post of the new beta , as well as his tesh support team jumped on both issues. resolving one completely and quickly, and the other with major headway in a solution that works now and are trying to improve even more.obviously that one will require them to work with V7 in their lab.

While I know Sony's team probably has a lot larger volume of tech support issues coming into to them. (i have submitted 2, no response yet , but ony submitted on thurs) And thier submission process is a PIA ,BTW. I too wish there was at least a little bit more response from them here on the forums. Granted we should be submitting tickets to them for the problems so that the have the information they need to start working on them .
But if we and them could somehow organize our posts(keeping them on topic) so that they could get a better handle on what issues seem to be more prevelant. That too could reduce the amount of inflow of tickets to them.

Bottom line is we know they are working on many issue for the .b release. but some small acknowlegement of some of these things would be nice here from the Forum admin.
Personaly , I think the .b release should be and hopefully is simply fixes for issues that have arrisen from the mass distribution of the new verson. Not adding new things or features as others have suggested .Every new version has its bugs and quirks thats why most of us still use V6 for critical projects until we
a) get more familiar with 7's features and changes.
b)discover and what bugs still exist and need to be resolved.
At least thats what I do..

BTW the new version is working great in both converting files and playing back on the t/l.
Jayster wrote on 9/17/2006, 10:48 AM
epirb:
For my own part, the issues with CFDIs are quite a dissappointment. I do my work primarily with CFDIs. Playback on the Vegas t/l was slow enough in Vegas 6, and is now significantly slower in Vegas 7. And the crashes.. Yikes! How was that not caught prior to release? As much as CF was pushed by Sony in the earlier releases, you'd think it wouldn't be overlooked for this release. I can't imagine that .m2t is intended as a full substituted for using CFDIs, because it just doesn't cut it for complicated compositing, etc.

The DVI info.net forum is also very active with Vegas users posting about the same issues that we are reporting. This other forum draws more time and attention to Cineform (quite understandably) because that forum represents all their customers (PPro and other NLEs). In fact, Vegas users are a minority of Cineform's customers. And our HD Connect product, at $200, is also a minority of their revenue (compared to $500 for Aspect HD and $1500 for Prospect HD, with lots more users on the Adobe-NLE side). The HD Link utility we use in HD Connect is common to the other packages, thus we are fortunate in that we benefit by the innovations that our competing NLE users are getting.

I also commend Cineform's quick response to these issues, but I feel that both Cineform (who has lots of other more important $$ customers, but doesn't want to forget us) and Sony (who should know better) could have been quite a lot more proactive in testing Vegas 7 with CFDIs and actively coordinating with Cineform (by phone or in person, not just with an expired email account on a beta tester list). As important as HD is to the future of the NLE, how could they drop the ball on this? Maybe the answers lie on the business end of things. But anyways, I am very appreciative of the efforts from Cineform (even if they are last minute) and I hope Sony will fully address the problems on their end.

All "complaints" aside, I have faith that these things will be worked out. Hopefully the end result will be that CFDIs perform noticeably better than in Vegas 6.
fldave wrote on 9/17/2006, 12:16 PM
Interestingly, I don't think you can totally blame Vegas for this. I don't have Connect HD, and I haven't had any problems in V7 with Cineform Intermediates that have been made totally within Vegas. It seems that all of the ConnectHD users were the ones having the problems. Since Vegas and Cineform are not from the same company, some post-live tweaks by each company are kind of expected in my mind.