View Full Version : New beta builds for 64-bit and installer issues


Pages : [1] 2

David Newman
June 26th, 2009, 07:09 PM
Prospect 4K -- http://www.cineform.com/downloads/Prospect4Kv405b214d-090626.zip
Prospect HD -- http://www.cineform.com/downloads/ProspectHDv405b214d-090626.zip
Neo 4K -- http://www.cineform.com/downloads/Neo4Kv405b214d-090626.zip
Neo HD -- http://www.cineform.com/downloads/NeoHDv405b214d-090626.zip
Neo Scene -- http://www.cineform.com/downloads/NeoSceneV132b117g-090626.zip

Again these betas use the same code base as the release build, yet the installer is changed to help fix system with alternation install locations for Adobe CS2/3/4. These are all the first installer to include the 64-bit VFW Codec for Vegas 9 and the 64-bit version VirtualDub (and other tools.)

Looking for feedback on installer issues and whether your 64-bit tools can now using the CineForm codec.

Stephen Armour
June 27th, 2009, 04:28 AM
Are the links broken for Prospect4K and HD? Having trouble with the downloads...

Carlos Bustamante
June 27th, 2009, 04:51 AM
It is not only the links. The cineform server seems to be down.

Charles Sommer
June 27th, 2009, 11:39 AM
finally!!!! a build that doesn't crash everything in sight. grobotto loads, no com surrogate errors, and so far no tmpeg or premiere elements crashes. the installer, though, still does not install the cineform importer plugin into premiere elements.....in fact, the install log states that it had searched for premiere pro, cs2, and cs3. but, it makes no mention of searching for cs4 or premiere elements.

David Newman
June 27th, 2009, 03:34 PM
Charles,

We need your install.log, it is located in Program fIles/CineForm/[product name]

Charles Sommer
June 27th, 2009, 10:15 PM
be glad to....
should i post it here or to whom or where ought i send it?

Thorsten Meyer
June 27th, 2009, 11:22 PM
When I run the new Prospect HD I get after finishing the install the error "This program might not have installed correctly" with the option to "Reinstall..." or "This program installed..."

I send you my C:\Program Files (x86)\CineForm\ProspectHD\Install.log

Eric Larson
June 28th, 2009, 06:37 AM
with new versions coming out regularly I was wondering are we suppose to uninstall and then install the new version, or just install over the old version?

David Newman
June 28th, 2009, 09:30 AM
Always uninstall before and new install. While installing over the top does work, there is a small chance an older component will remain.

Charles,

email it to me (via DVinfo.net.) while it should go through support, sadly I'm the one looking at installer issues these days.

David Newman
June 28th, 2009, 10:28 AM
When I run the new Prospect HD I get after finishing the install the error "This program might not have installed correctly" with the option to "Reinstall..." or "This program installed..."

I send you my C:\Program Files (x86)\CineForm\ProspectHD\Install.log

I didn;t see any issue in the install.log. Is there any problem with the installed software?

Charles Sommer
June 28th, 2009, 01:26 PM
ok david,

i sent the install.log file to you

David Newman
June 28th, 2009, 05:27 PM
A fixed for Neo Scene and Elements, and for 64-bit codec registering.

Try this:
http://www.cineform.com/downloads/NeoSceneV132b117i-090628.zip

P.S. 4:50pm PST -- Bumped yersion to 117i -- including licensing to match that of Neo HD/4K which always seemed to work. Just in case.

Charles Sommer
June 28th, 2009, 05:35 PM
thanks for all your help!
this latest installer now works for me with neoscene and premiere elements. the importer plugin installs into a cineform folder in my plug-ins\en-us directory.

Keith Paisley
June 29th, 2009, 08:43 AM
I have tried installing the latest (117i) version of Neo Scene on my Windows 7 64-bit machine and it doesn't seem to work with either Vegas 9 64-bit or VirtualDub 64-bit. There are no errors during installation. I have looked and I currently have 2 versions of cfhd.dll in my \windows folder tree.

one is in C:\Windows\SysWOW64 - it is shown as 880kbytes and has a timestamp of 6/28/09 5:24 PM. I checked the file properties and the file version of this one is 5.1.1.369, Product Name/Version Neo Scene 1,3,2,117


the other one is in C:\Windows\System32 - it's 968kbytes and has a timestamp of 6/26/09 12:55 PM. the file version of this one is also 5.1.1.369, , Product Name/Version Prospect/NEO 4K 4,0,5,214

any ideas on how to get this working?

On vegas 9 if I select a Cineform encoded clip in the explorer, the properties show up as Video: Stream attributes cannot be determined, CFHD
Audio: 44,100 Hz, 16 Bit, Stereo, 00:01:00;00, Uncompressed

On vdub64, the error message states that it cannot locate a decompressor for format 'CFHD' (unknown) and then goes on to explain that VirtualDub requires a VFW compatible coded to decompress video.

UPDATE: based on something I saw in another thread I tried reinstalling NeoScene as an administrator and now (strangely) the CFHD.dll file in /Windows/System32 has a slightly earlier timestamp, but everything else in the properties is the same as it was. The new timestamp is 6/25/09 7:57PM.

Keith Paisley
June 29th, 2009, 10:39 AM
Here's another update. I downloaded dependency walker and analyzed CFHD.dll (in /System32) and according to DW, the system is missing MSVCR80.DLL and IESHIMS.DLL

also the following appeared in DW's log window
Error: The Side-by-Side configuration information for "c:\windows\system32\CFHD.DLL" contains errors. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail (14001).
Error: At least one required implicit or forwarded dependency was not found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.

David Newman
June 29th, 2009, 01:09 PM
Neo Scene : http://www.cineform.com/downloads/NeoSceneV132b117j-090629.zip

The above version has been testing to work, in Admin or User modes, with UAC on or off, XP 32/64 and Vista 32/64 (no Windows 7 support yet.) Please confirm on your system. I also includes the 64-bit version MSVCR80.DLL, for those that didn't have that.

Encoding licensing has been testing for trial and activated system. If you are now only having encoder license issue, when you request to CineForm codec control panel for the first time (in Vegas or VirtualDub) how many seconds does it take to open?

Keith Paisley
June 29th, 2009, 02:12 PM
I understand that Win 7 isn't currently supported since it's only in RC stage at the moment, but unless I'm mistaken I see that others have gotten it working with Vegas 9 64-bit and cineform hd 64-bit codec, at least partially. I am curious to know what could be going on with my setup. My install is very clean - so far I've only installed vegas pro 9 64-bit, vegas 8.0c (though I deinstalled it), sony acid pro and neo scene.

I have Vista 64-bit but i wiped out the installation a few months ago because the performance was too much of a disappointment. I am not interested in reinstalling it since I will be installing the released version of win 7 in a few months. So if anybody else out there has managed to get it working with Win 7 64-bit, I'd like to compare notes.

Keith Paisley
June 29th, 2009, 02:33 PM
sorry, I forgot to mention that the latest (117j) version did not rectify the situation.

David Newman
June 29th, 2009, 03:03 PM
sorry, I forgot to mention that the latest (117j) version did not rectify the situation.

What situation? you have said a lot, what doesn't get fixed.

Are you still missing MSVCR80.DLL?

David

Keith Paisley
June 29th, 2009, 03:24 PM
What situation? you have said a lot, what doesn't get fixed.

Are you still missing MSVCR80.DLL?

David

No, I got MSVCR80.DLL and IESHIMS.DLL and confirmed they are both x64 versions via Dependency Walker. I am still unable to open cineform AVIs using either Virtualdub64 or Sony Vegas 9 64-bit.

Dependency walker doesn't mention any missing dlls now, but I am still getting this error message in the DW log window though.


Error: The Side-by-Side configuration information for "c:\windows\system32\CFHD.DLL" contains errors. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail (14001).
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.

There are two dlls listed with slightly different icons next to them. see below

http://i43.tinypic.com/j8ipe0.png

David Newman
June 29th, 2009, 03:49 PM
No idea what "Side-by-Side configuration information" is. The Depends output is otherwise fine. In you do to c:\windows\system32 And Right Click on CFHD.inf and select install what happens?

David

Keith Paisley
June 29th, 2009, 03:58 PM
yes, I've tried the "install" on the cfhd.inf file to no avail.

if it matters, everything seems to work on 32-bit virtualdub.

David Newman
June 29th, 2009, 04:21 PM
yes, I've tried the "install" on the cfhd.inf file to no avail.

if it matters, everything seems to work on 32-bit virtualdub.

If that right click install doesn't work, your PC has other issues not related to the beta. All other reports have said the direct install has worked (admin level required.) The issues we have been working on are installer and encoder licensing related, the 64-bit VFW Decoder has been working for a couple of weeks, mostly without issue.

Charles Sommer
June 29th, 2009, 06:37 PM
curious few lines in my install.log file now with the j build. seems it finds then doesn't find premiere elements:

Look for PremierePro.exe
Read HKLM\SOFTWARE\Adobe\Premiere Elements\7.0 Got C:\multimedia\Adobe\Adobe Premiere Elements 7.0\Plug-ins\en_US
Premiere Elements Found
Create folder: C:\multimedia\Adobe\Adobe Premiere Elements 7.0\Plug-ins\en_US\CineForm
Output folder: C:\multimedia\Adobe\Adobe Premiere Elements 7.0\Plug-ins\en_US\CineForm
Extract: im-CFHD_File_Import.prm... 100%
No Premiere Elements Found

Jay Bloomfield
June 29th, 2009, 08:02 PM
No idea what "Side-by-Side configuration information" is. The Depends output is otherwise fine. In you do to c:\windows\system32 And Right Click on CFHD.inf and select install what happens?

David

That's how Vista keeps track of multiple versions of DLLs, etc., used by different programs:

Side-by-side Assemblies (Windows) (http://msdn.microsoft.com/en-us/library/aa376307(VS.85).aspx)

David Newman
June 29th, 2009, 09:45 PM
The only error is the log message, it says that where it installs or not. It is working fine.

Keith Paisley
June 30th, 2009, 07:15 AM
That's how Vista keeps track of multiple versions of DLLs, etc., used by different programs:

Side-by-side Assemblies (Windows) (http://msdn.microsoft.com/en-us/library/aa376307(VS.85).aspx)

Interesting. So this definitely seems to be the source of the problem I'm seeing with the 64-bit CFHD VFW decode (i haven't tried a 64-bit encode) on Windows 7. If I'm correctly understanding the information in that MSDN link, my guess would be that Windows 7 probably has slightly different default libraries that aren't accounted for in this version of CFHD.dll.

Bill Ravens
June 30th, 2009, 07:20 AM
Keith..
I have the 64-bit Cineform codec working in Win7. I had to manually install the 64-bit build. Do this by copying the two files into the system32 folder. Register the files by right clicking on the .inf file and selecting INSTALL. Reboot. I believe there are issues with the Win7 RC1 UAC module.

Keith Paisley
June 30th, 2009, 07:41 AM
Keith..
I have the 64-bit Cineform codec working in Win7. I had to manually install the 64-bit build. Do this by copying the two files into the system32 folder. Register the files by right clicking on the .inf file and selecting INSTALL. Reboot. I believe there are issues with the Win7 RC1 UAC module.


I have tried installing CFHD by right-clicking CFHD.inf and selecting "install" but it didn't work, even after a reboot. By "two files" i assume you mean CFHD.dll and CFHD.inf, correct?

Also, can you tell me which version of the files you have installed? I'm also curious to know if you have you viewing the CFHD.dll file in dependency walker.

thanks

Bill Ravens
June 30th, 2009, 08:06 AM
Keith...
yes, those are the 2 files I copied over. cfhd64.dll gets copied over with a name change to cfhd.dll
Have not looked at the execution with Dependency Walker.
I'm using the 214d version with NeoHD. Decoder version 5.1.1
Sorry about the incorrect reference to install procedure. I had to mess around for a while and forgot which method worked. I think I, finally, got it to install by opening the COMMAND WINDOW and manually typing in the install string used by the Cineform install.bat file.

Keith Paisley
June 30th, 2009, 08:23 AM
Keith...
yes, those are the 2 files I copied over. cfhd64.dll gets copied over with a name change to cfhd.dll
Have not looked at the execution with Dependency Walker.
I'm using the 214d version with NeoHD. Decoder version 5.1.1
Sorry about the incorrect reference to install procedure. I had to mess around for a while and forgot which method worked. I think I, finally, got it to install by opening the COMMAND WINDOW and manually typing in the install string used by the Cineform install.bat file.

Hi Bill, I will try installing NeoHD beta to see if it makes any difference. I've been installing NeoScene. In the mean time, would you mind satisfying my curiosity by checking the versions of the following dlls?
/Windows/System32/IEFRAME.DLL
and
/Windows/System32/SHLWAPI.DLL

those two files seem to trigger some sort of warning in dependency walker for me. (see http://i43.tinypic.com/j8ipe0.png)

Bill Ravens
June 30th, 2009, 08:30 AM
Keith...

ieframe v 8.0.7100
shlwapi v 6.1.7100

David Newman
June 30th, 2009, 08:45 AM
I've seen similar warnings with no issues, we don't directly use anything from those DLLs.

Keith Paisley
June 30th, 2009, 09:03 AM
Keith...

ieframe v 8.0.7100
shlwapi v 6.1.7100

thanks, those are the same versions that I have, so I guess they're not the issue.

Keith Paisley
June 30th, 2009, 09:06 AM
I've seen similar warnings with no issues, we don't directly use anything from those DLLs.


Hi David, you've seen those "side by side" warnings, including the "The application has failed to start" part? To me that error message sounds like windows will not start that DLL at all due to the side by side issues.

and to Bill, can I ask which apps you are using to decode with the CFHD VFW 64-bit codec?

thanks.

I did a system rollback to the point where it basically had no apps installed and then tried all of this again, to no avail.

Bill Ravens
June 30th, 2009, 09:09 AM
Vegas 9-64, MediaplayerClassic, Virtualdub, Avid, any vfw application will read CF DI's.

Keith Paisley
June 30th, 2009, 11:50 AM
Vegas 9-64, MediaplayerClassic, Virtualdub, Avid, any vfw application will read CF DI's.


ugh, i just installed a fresh copy of win 7 RC (Ultimate) on a spare drive and still no love. On the clean install i just tried installing the last NeoHD beta (since that's what you said you were using) and virtualdub AMD64 and I can't get the 64-bit VFW codec to show up. I'm really, really trying to avoid installing vista64 again.

Bill Ravens
June 30th, 2009, 12:42 PM
I would give Cineform some time to get to Win7. I know they're very swamped.

Graham Hickling
June 30th, 2009, 09:06 PM
Similar experience as Keith installing these versions (ProspectHD and Neoscene - tried both) with Premiere CS3 on Windows 7RC Build 7100.

- both installed to the correct directories
- encodes and exports of CFHD avis from Premiere are OK
- scrubbing is OK
- playback in Premiere's program windows is red and upside down (could be a graphics card issue?)
- had the 32 bit version of MSVCR80.dll with PHD installed, but Neoscene updated it to the 64bit version
- VirtualDub 32 finds the CFHD vfw codec
- Virtualdub 64 does NOT, even with a manual right-click and 'install' applied to the inf file

I don't have a CFHD64.dll file (just two versions of CFHD.dll) nor a Cineform install.bat file, so those bits of the thread above were mysterious to me ...

Walker dependency just shows the two files David says not to worry about.

David Newman
June 30th, 2009, 09:11 PM
We made some headway with Windows 7 also, more to come.

Keith Paisley
June 30th, 2009, 10:00 PM
We made some headway with Windows 7 also, more to come.

oh this is very good news. Please keep us updated.

Keith Paisley
June 30th, 2009, 10:11 PM
double ugh. I went through the pain of installing vista 64 home premium (SP1) on a spare drive, updated it to SP2, then installed the latest NeoScene beta (1.3.3.118) and virtualdub 64-bit (1.8.8-AMD64) and I'm still not having any luck. Besides some other standard "Windows Updates" i've done nothing else to this machine. Am I missing something obvious?

Jay Bloomfield
July 1st, 2009, 08:48 PM
There's still no 10 bit DirectShow import for After Effects CS4 and Prospect HD. AE only uses the VFW codec for AVI files and ignores the CFHDIO.aex plug-in. If you temporarily rename CFHD.DLL, then you get no Cineform video track in AE at all, only audio.

Cineform MOV files are properly imported into AE as 10 bit though.

David Newman
July 1st, 2009, 08:50 PM
This NeoScene version should install on 64-bit Windows 7.

http://www.cineform.com/downloads/NeoSceneV133b118-090701.zip

Other builds to follow

Keith Paisley
July 1st, 2009, 10:49 PM
This NeoScene version should install on 64-bit Windows 7.

http://www.cineform.com/downloads/NeoSceneV133b118-090701.zip

Other builds to follow

Oh yeah!!! I'm not ready to proclaim this as "the answer" but I can tell you right now that with this installer everything's good from a CFHD x64 standpoint on my "fresh" Vista64 install, whereas none of the other builds worked. So now I will switch my system back to the Win7 boot drive and try it out, and hopefully tomorrow I will be back in business.

thank you very much!

Keith Paisley
July 3rd, 2009, 07:46 AM
I was unable to work on this yesterday but I got my system drive switched back over to my original Windows 7 install and I am happy to say that with the latest build I am now able to decode video using the x64 VFW CFHD codec. The only problem I'm seeing now is that for some reason I do not get any audio track decode, which is the opposite of what I had before. Anybody else observe this?

UPDATE: Nevermind, there's no longer an audio problem on my end - apparently somewhere in all the system restore cycling (while trying to get the earlier 64-bit builds to work), the ac3filter ended up being not installed on this machine (though the cineform installer indicated that it was). I just reinstalled ac3filter 1.61b and it seems to have rectified the situation.

thank you cineform for getting this working properly on windows 7! I've a large backlog of footage that I can finally start editing again.

William Urschel
July 4th, 2009, 05:00 AM
Earlier, in another post here, I said, " I give up on Adobe CS4" (or as David might say, " I given up oon Adobee C s4" (!) After several more days of futile effort, I guess I am really mistaken in making any more investment for the foreseeable future in time or money in a further Cineform/Adobe combination.

I have just done a totally clean install of the OS and ALL other programs (including the latest Cineform Prospect 4k). Cineform, as always, proves to be an invaluable tool in all respects for CS3. But with Premiere CS4, it doesn't even show up as an option yet for the basic set up, after the $500 investment 6 months ago in Adobe and more recently another $200 for the latest Prospect 4K build. Am I missing something? Or, because of Adobe's obdurate attitude and behavior, is that just the way it is?

Soeren Mueller
July 6th, 2009, 03:31 PM
I'm currently using NeoScene 1.3.3 b118 (from 1.7.09) on Win7 RC 64bit and everything works fine besides one problem I'm having:

In After Effects CS4 I get duplicated/skipped frames!

Here's what I'm doing:
1. Converting Canon 5D MkII h264 MOV clips via HDLink/NeoScene to Cineform AVI
2. Loading Cineform AVI into After Effects CS4
3. Loading original Canon MOV into AFX as well
4. Compare them frame by frame - in the Cineform AVI sometimes a frame is duplicated and the next frame skipped (so instead of the next correct frame the image data of the previous frame is duplicated)

After removing CFHD_AVI_Importer.prm from the Adobe Common MediaCore directory both the original MOV and the Cineform version look exactly the same - no frames are skipped/duplicated!

Seems to be an isolated issue with the Adobe Cineform AVI Importer/Reader Plugin...
So for now I'm just using the default AVI/DirectShow Importer.. (I guess the quality for 5D converted clips should be the same)

Cheers
-Sören

David Newman
July 6th, 2009, 06:14 PM
I'm currently using NeoScene 1.3.3 b118 (from 1.7.09) on Win7 RC 64bit and everything works fine besides one problem I'm having:

In After Effects CS4 I get duplicated/skipped frames!

Here's what I'm doing:
1. Converting Canon 5D MkII h264 MOV clips via HDLink/NeoScene to Cineform AVI
2. Loading Cineform AVI into After Effects CS4
3. Loading original Canon MOV into AFX as well
4. Compare them frame by frame - in the Cineform AVI sometimes a frame is duplicated and the next frame skipped (so instead of the next correct frame the image data of the previous frame is duplicated)

After removing CFHD_AVI_Importer.prm from the Adobe Common MediaCore directory both the original MOV and the Cineform version look exactly the same - no frames are skipped/duplicated!

Seems to be an isolated issue with the Adobe Cineform AVI Importer/Reader Plugin...
So for now I'm just using the default AVI/DirectShow Importer.. (I guess the quality for 5D converted clips should be the same)

Cheers
-Sören

Are you sure you are aren't mixing 29.97 and 30.0p in the one composite. Neo Scene converts to 29.97, so you need a 29.97 composite. I'm not seeing duplicate frames, nor are others when the project is setup correctly.

Soeren Mueller
July 7th, 2009, 01:04 AM
Are you sure you are aren't mixing 29.97 and 30.0p in the one composite. Neo Scene converts to 29.97, so you need a 29.97 composite. I'm not seeing duplicate frames, nor are others when the project is setup correctly.

Hi David!

Of course that's the first thing I thought of as well.. but that couldn't be the cause as I switched the composition to 25fps and in the "interpret footage" dialog box I told AFX to reinterpret the footage as 25fps as well. To be sure I switched that back to the original setting (29.97) and changed the composition too - with the same results: strange randomly (at least it seems to me) duplicated/skipped frames!

I saved the project and now I can always reproduce it - when I delete/move the CFHD_AVI_Importer.prm everything is fine (but of course not using the Cineform Importer), when it is there I get the strange frame skipping. (always exactly the same project and footage)
I tried several AVIs from the same conversion process and they all show the same effect.

Would it help if I upload a short Cineform AVI that shows the problem somewhere? Or do I have to open a support ticket?