It's not necessary to put SysWOW64 in the path, since all activity by 32 bit software is redirected from system32 to SysWOW64 automatically.

For everybody who is getting audio and video playback, do you have a full Prospect or other version installed and then swapped the dll and prm files? Since I did a fresh install of XP and CS4 on my computer, I didn't install Prospect - just the importer files. Could that be a reason I get audio only?

Realtime Cs4 playback
 

Hi,
any news on progress of the Cine Form realtime playback engine for Premirer Cs4?
Regards

Nice! Very similar to what I'm running. If you can I would look at upgrading to a Quadro card instead of the GeForce series. While some may say there is little difference, I've seen folks with the GeForce cards run into strange problems, which were resolved by changing the video card. I'm running the nVidia Quadro FX3700 card and have not had any playback issues with Premiere Pro.

In a couple words? Better performance with any program that utilizes the graphics card. Just like getting a Quadro would be the ultimate graphics card for video, not everyone has that kind of money. However in terms of performance, the 275 is going to be a lot faster than the 9600. Not to mention that the 9 series is 2 generations old.

Compare both.
9600 - Click on the Specs Tab
NVIDIA GeForce 9600 GT

275 - Click on the Specs Tab
GeForce GTX 275

If only CS4 supported some other CUDA-enabled card besides Quadro. That's a little more than I can spend right now. The 275 looks intriguing, though, as does the 285.

Wonder if we could get Cineform's RT playback to be CUDA-enabled...any CUDA, and not just Quadro (although, if somebody gives me a couple grand, I'd buy one!). I'll have to start a different thread, if I want more info on Quadro though, and try to keep this one focused on the RT engine's timeline for CS4...

Thanks,
Matt

When I had CFHDDecoder.dll under SysWOW64, the video in the Program Monitor in CS4 was all white with occasional flash to black. Audio worked nicely. When I put CFHDDecoder.dll in system32, the video played as expected, and looked pretty good. Is the 32-bit redirection from system32 to SysWOW64 something that needs to be configured?

I should note my sequence of events: Installed PPro 1.5 + updates (that's my current version). Installed Prospect. Installed CS4 Production Premium, + updates. Put DLL in SysWOW64. Imported a CF AVI in CS4. Got the white (no) video in the program monitor. Save project. Move CFHDDecoder.dll to system32. Reopened project in CS4. Video now plays as expected.

*shrug* I can't say how Vista 64 treats system32 or SysWOW64, because so far I know next to nothing about Vista* beyond the TV commercials and Internet vitriole. But the above steps are what made it work for me. I imagine Cineform will need to ensure that all these items are captured as test scenarios.

One further thing--Premiere CS4 installed under Program Files (x86), and I put the PRM files in that directory tree as Dave indicated. Would that make any difference on the system32 vs SysWOW64?

Thanks,
Matt

Quote: However in terms of performance, the 275 is going to be a lot faster than the 9600.

Can anyone provide some simple benchmark results to demonstrate a meaningful performance benefit of a 275 (or similar) over a 9600 (or similar) for Premiere Pro and Cineform? Until then color me skeptical ... a 9600 is a third the price, works great with Premiere and CF, and can be bought in a silent, fanless configuration.

No. Unless a piece of software is written to explicitly refer to one or the other of the system folders, you don't need to configure anything. For example, if I had a piece of 32-bit code that said to run file "c:\windows\system32\xx.exe", there would be no redirecting to SysWOW64. That's generally bad programming to do that, though, since there are built-in environmental variables that you can use to refer to Vista x64's system folders.

I suspect there is something else going on with your setup. As long as you can make it work, using system32, there's no reason to worry about it.

I haven't tried the CS4 Beta yet, just the standard Neo Scene installation. However, I see white frames (thumbnails) in Bridge CS4 and Mocca for AE for Cineform AVI files. This is on Vista 64 HP SP1.

PP CS4 Does Not Play Back CF Express MOV
 

Hi, this is my first post on this board.

We bought CS4 and CF Prospect4K as an online finishing solution, collaborating with Iridas SpeedGrade. Most editing ist done with FCP, due to a much wider freelancing editor base and the ability to sync sound files via TC. We were happy when the second build came out supporting MOV - another step to make a meaningful workflow happen.

We started a project in PP CS4 and imported 2 Express CF MOVs 1024 x 512 which we previously encoded with ReMaster on the Mac. They worked as expected. We tried to import more files. But they were not able to be played back in the canvas window; pulling them into the timeline caused Premiere Pro to freeze.

After restarting PP the files worked. The work-around now is: Importing a file, quiting Premier Pro and restarting Premiere Pro. This is pretty tedious.

Of course this was not a payed job. We gave up and work in FCP for now. There are too many other bugs in CS4 to call it prime time ready. Hopefully in the summer Prospect is fully working in CS4 plus all the other shortcomings are ironded out. The intended workflow in CS4 is great - just not working currently.

Kind Regards,

Hans

Audio problem fixed
 

For anyone else who is getting audio only avis, install one of Cineform's products. You need the decoder with the importer. My video imports correctly now, but is jerky on playback.

That means you are not using the importer, instead you are using the VFW codec (which is slower.) When setup correctly (default excution paths can be an issue), the importer works without any other CineForm install.

How can I be sure the CFHDDecoder.dll is being used to decode the CFHD AVIs I import into CS4? Is there some tell-tale sign? Right-clicking on the resource in CS4 doesn't seem to provide any clue.

David, that was what support told me when I submitted a ticket on it. I have the dll in the suggested execution path. I assume it is the correct one since I did a fresh install of CS4 using all defalt settins.

In the properties pop-up you will only see metadata if you are using the new importer. Time and Date info and Fingerprint, etc.

I may be doing this all wrong, or something. Here's my setup:

1. Premiere Pro 1.5.1, Prospect HD 3.4.6
2. Premiere Pro CS4 (Production Premium)
3. Vista Ultimate 64 (xp 32 died)

Things I've tried, plus results, with this beta decoder. I think I may have confused results, and it took me a while to sort things out. Getting old, I guess...

1. Place CFHDDecoder.dll in Windows\system32. CFHD AVI plays fine in CS4. Not sure which codec it's using.
2. Place CFHDDecoder.dll in Windows\SysWOW63. CFHD AVI won't play--preview screen is white, mostly, some black. PPro CS4 locks up for extended periods.
3. Remove CFHDDecoder.dll completely. Reboot. CFHD AVI plays fine in CS4--even in multi-camera.

I'm not sure, but I'm suspecting that the CFHDDecoder.dll really doesn't play on my system, or just doesn't work. Plus, CFHD AVIs won't play in Windows Media Player 11 at all, due to a decoder error. I figured maybe my Prospect needs updating, but since I have both CS4 and PPro 1.5, that upgrading Prospect is pretty much a useless venture--the Prospect installer would consider CS4 to be the current PPro in install for that.

My system is i7, Asus P6T, 12GB RAM, video on a SiL 4726 RAID0. Installed OS, PPro 1.5.1 + Prospect HD, and the Production Premium. Using default settings to install. I'm thinking that CFHD was playing as VFW, when it played nicely, and my new system is just fast enough to handle it. I'm thinking the CFHDDecoder.dll really doesn't work correctly. I really didn't (don't, yet) know enough about Vista 64, so thought putting the DLL in system32 resulted in the dll being used, but after seeing the behavior of putting the dll in SysWOW64, and then removing it again, I have to say the DLL doesn't work.

Just my observations, with some miniscule interpretation. Maybe the PHD 3.4.6 is providing some decoding? I don't see how it could, though....

Thanks,
Matt