We are now opening the 64-bit VfW codec for public testing. This requires a 64-bit OS and a 64-bit Vegas 9 install. It is also recommended that you update one Vegas component to help with smooth playback at sub-resolutions (see the knowledgebase.)
1) Open HDlink and confirm that you have a license, either within the trial or a purchased license.
2) Using VirtualDub (64-bit) open the Video -> Compression menu, and confirm you have "CineForm x64 ..." codec in the list. If you do you have decoder access.
3) Select CineForm compression in VirtualDub and press "Configure".
4) If you can change the compression quality you have a license, and every should also work in Vegas.
OK now it is working. Maybe deactivating and reactivating is the key. Maybe it was the new build. Whatever it was, now I am up and running at in both the 32 and 64 bit versions of Vegas.
The VirtuaL Dub thing worked just as you stated with the exception of the name---mine says Cineform 5.1.1, not x64. The Cineform codec installs showed up in the Control Panel Windows files together with Cineform and Cineform Player. Is everybody happy? Me is.
JJK
Cliff, that system has problem not related to CineForm. You say you get errors even downloading a third party tool (VirtualDub.) It makes me not trust anything else it does. Several who it wasn't working for now say it is, so we have moved in the right direction -- I gather a second PC of yours is also working.
So just you and Ed you the only one remaining, and Ed hasn't tried the new stuff yet.
Dan - I did an Acronis restore of a known fresh install of Vista 64 Ultimate. The error messages from Sourceforge for downloading Virtualdub were web page errors.
My Desktop install works fine. I can see the latest Neo Scene in 32bit VP8, but 64bit VP9 shows nothing.
Any other 64 bit codecs I installed (K-lite Codec pack, etc) shows up in the render as option dialog for video in VP9.
I copied the libmmd.dll file to system32 folder.
I'm trying to determine what else could it be given that the install went perfect as far as I could tell after the restore of the Acronis Vista 64 Ultimate install image.
Cliff Etzel
Videographer : Producer : Web Designer bluprojekt
Well I followed this procedure, Cineform is nowhere to be found as an option - please - this is the one thing I need to get up and running as I'm beginning to need to edit on location with my laptop.
Cliff Etzel
Videographer : Producer : Web Designer bluprojekt
Nothing to go on at the moment. Doesn't the 32-bit component work -- V9 32-bit and/or VirtualDub 32-bit? This is a clear a particular PC issue not a general error.
It seems odd that nothing works on the 64bit end of things. My desktop was a piece of cake for getting Neo Scene up and running with VP9 64 bit compared to my laptop. Virgin install of Vista 64 Ultimate. VP8.0c 32 bit shows the Cineform Codec option no problem, but nothing in 64bit VP9 or VirtualDub 64.
Cliff Etzel
Videographer : Producer : Web Designer bluprojekt
NeoScene-1.3.3.118-Setup.exe still works for me. This is importing and rendering from VP9-64. I did have to right-click, select properties and say unblock before I could get it to install.
I am observing the exact same thing (as Cliff) on my machine (Q6600, nvidia nforce 650i chipset, 4GB). I've tested the latest neo scene installer (1.3.3.118) on Win 7 Ultimate 64-bit (build 7100) and Vista Home Premium 64-bit (SP2), both with absolutely fresh installs and get the same results (which is no 64-bit VFW codec). 32-bit CF HD shows up in 32-bit versions of virtualdub and vegas 9 but not the 64-bit versions.
Strangely, I find I can render to Cineform avi in both the 32bit and 64bit versions of Vegas 9, but I get a licensing error when I try to render to Cineform in Vegas 8.
Vista Ultimate 64, Q9650 and I see Video for windows Cineform x64 in Vegas 9.0 64 and Cineform 5.1.1 in Vegas 9.0 32. Configure works ok. I have to create a preset and save and select so that the codec stays in place after selection or the Sony codec (default) will pop back .
JJK
Who's "Dan"? Yeah I know it's confusing with those initials sounding like a name, but the least we can do after all the effort he's put into us is to get his name right. :-)
New file works well for me. In order to leave UAC on, I do the following:
Change the security properties of the installation file to give all users full rights.
I then add the installation file to the DEP exception list.
I have no installation errors when doing the above and rendering/importing is working great.