FYI, the latest beta works well for me, including Firstlight, until I try to encode. I consistently get crashes with the following:

Problem signature:
Problem Event Name: APPCRASH
Application Name: ImporterProcessServer.exe
Application Version: 0.0.0.0
Application Timestamp: 491896d7
Fault Module Name: CFHDDecoder.dll
Fault Module Version: 2.5.0.30
Fault Module Timestamp: 49ffb07d
Exception Code: c0000005
Exception Offset: 0000d7bc
OS Version: 6.1.7100.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

CS4 on Windows 7
Dell XPS420 quadcore w 8GB RAM

Regards,
Glenn

Hi Glen when you go to export to what format

Just pushing these new links onto the next page.

Cheers David - Is there any versions that has the presets for PP CS4? I'm keen to see if thats my problem with jerky video? With a older PC and Aspect HD it was fine with editing HD videos and that was with PP 1.5

Moved to CS4 and its dog slow and jerky with the same source video.

Bruce, I tried Cineform AVI and also the Adobe MPEG Blu-Ray presets. Same results either way, it started then Import Process Server crashed.

Leaving Cineform out of the equation, it important to know that Adobe is famous for each version getting slower at the same things the previous version did easily. So when I moved from 1.5 to 2.0 I noticed a performance hit doing the same exact things. CS3 was an even bigger dog than PPRO2 and CS4 has outdone all of them.

Seriously, unlike Vegas (which I don't regularly use but I admit seems to get faster and faster with each version) Adobe seems to show little to no interest in optimizing their code for performance. They seem to only focus on new features with each version, the price of using it with any kind of responsiveness equal to the previous version is a serious hardware upgrade. I have to come to terms that simple HDV projects are going to take much longer to render in CS4 than CS3, even when I am not using any new feature or filters. Same simple HD clips in timeline with same exact effects take sooo much longer in CS4 and playback is not nearly as responsive.....yet.

I love Adobe products but if I have a project that does not require features of the newer versions, I can edit them so much faster in older versions.

In short, (too late...I know) I don't know that it is realistic to expect the same performance from CS4 that you see from PPRO 1.5 on the same hardware. Maybe Cineform will neutralize this a little....but PPRO CS4 requires much more processing in general.

Cheers David - Is there any versions that has the presets for PP CS4? I'm keen to see if thats my problem with jerky video? With an older PC and Aspect HD it was fine with editing HD videos and that was with PP 1.5

Moved to CS4 and its dog slow and jerky with the same source video.

Leaving Cineform out of the equation, it important to know that Adobe is famous for each version getting slower at the same things the previous version did easily. So when I moved from 1.5 to 2.0 I noticed a performance hit doing the same exact things. CS3 was an even bigger dog than PPRO2 and CS4 has outdone all of them.

Seriously, unlike Vegas (which I don't regularly use but I admit seems to get faster and faster with each version) Adobe seems to show little to no interest in optimizing their code for performance. They seem to only focus on new features with each version, the price of using it with any kind of responsiveness equal to the previous version is a serious hardware upgrade. I have to come to terms that simple HDV projects are going to take much longer to render in CS4 than CS3, even when I am not using any new feature or filters. Same simple HD clips in timeline with same exact effects take sooo much longer in CS4 and playback is not nearly as responsive.....yet.

I love Adobe products but if I have a project that does not require features of the newer versions, I can edit them so much faster in older versions.

In short, (too late...I know) I don't know that it is realistic to expect the same performance from CS4 that you see from PPRO 1.5 on the same hardware. Maybe Cineform will neutralize this a little....but PPRO CS4 requires much more processing in general.

haha Cheers Marty,

My hardware has increased but I guess not enough. I went from a 32bit Windows Xp with 3GB of DDR memory with a dual core XP 4800 2.4GHZ with PP 1.5 to

amd opteron quad core 2.1GHZ with 4GB of ECC memory (another 4GB on order) and 64bit W7 (tried Vista) but same jerky play back.

146GB Sata 1500rpm OS drive
800GB Raid 0 media
750GB scratch

Leaving Cineform out of the equation, it important to know that Adobe is famous for each version getting slower at the same things the previous version did easily. So when I moved from 1.5 to 2.0 I noticed a performance hit doing the same exact things. CS3 was an even bigger dog than PPRO2 and CS4 has outdone all of them.

Seriously, unlike Vegas (which I don't regularly use but I admit seems to get faster and faster with each version) Adobe seems to show little to no interest in optimizing their code for performance. They seem to only focus on new features with each version, the price of using it with any kind of responsiveness equal to the previous version is a serious hardware upgrade. I have to come to terms that simple HDV projects are going to take much longer to render in CS4 than CS3, even when I am not using any new feature or filters. Same simple HD clips in timeline with same exact effects take sooo much longer in CS4 and playback is not nearly as responsive.....yet.

I love Adobe products but if I have a project that does not require features of the newer versions, I can edit them so much faster in older versions.

In short, (too late...I know) I don't know that it is realistic to expect the same performance from CS4 that you see from PPRO 1.5 on the same hardware. Maybe Cineform will neutralize this a little....but PPRO CS4 requires much more processing in general.

Also thinking of geting a proper GPU for CS4 but not sure (costs etc)

Quadro FX 580 (http://www.nvidia.com/object/product_quadro_fx_580_us.html)

or

Quadro FX 1800 (http://www.nvidia.com/object/product_quadro_fx_1800_us.html)

prefer the 1800 but cost is a issue

Well I got a importer process server crash again on export from PPCS4. I was a 45min timeline that said it would take 5 hours to export crash happened 45min into export.

Its almost like CS4 can't handle the CF file..

Did anyone else have any luck?

David,

FWIW, I just upgraded my Dell XPS420 quadcore. I went from Vista 32-bit to Windows 7 64-bit and increased the RAM from 4GB to 8GB. It made a HUGE difference. Rendering on the old setup had the 4 CPU cores running between 50-75% and memory was maxed out. I couldn't run anything else. Now I see all 4 cores at 100%, memory in the 5-7GB range, renders are noticeably faster, there's no paging, and I can actually run other apps at the same time!

The additional RAM under Window 7 64-bit may help you a lot.

Regards,
Glenn

David,

FWIW, I just upgraded my Dell XPS420 quadcore. I went from Vista 32-bit to Windows 7 64-bit and increased the RAM from 4GB to 8GB. It made a HUGE difference. Rendering on the old setup had the 4 CPU cores running between 50-75% and memory was maxed out. I couldn't run anything else. Now I see all 4 cores at 100%, memory in the 5-7GB range, renders are noticeably faster, there's no paging, and I can actually run other apps at the same time!

The additional RAM under Window 7 64-bit may help you a lot.

Regards,
Glenn

Cheers I'm so close to going back to Windows Xp32bit and 1.5 as I need to get projects paid off. I've spent so much time trying to get CS4 to work it's started to bug me now.

Only problem is I've editing the project in CS4 and I don't think I can put it back into 1.5 :(

HELP..

I stayed in 2.0 for a long time until CS3 seemed more stable. In fact, I have really only been using cs3 fulltime for the last 6 months. I rebuilt my system and I didn't re-install CS2 so that is when you know you are committed to the latest build! :)

I can foresee myself still using CS3 for some time to come. It is stable, it is fast (first version of Premiere to take advantage of 4 cores finally pushed it ahead of PPRO 2.0). There are a few cool features of CS4 I would really love to use but even when it is working right, it is just so much slower....even in Vista 64 with 8 Gigs RAM.


Cheers I'm so close to going back to Windows Xp32bit and 1.5 as I need to get projects paid off. I've spent so much time trying to get CS4 to work it's started to bug me now.

Only problem is I've editing the project in CS4 and I don't think I can put it back into 1.5 :(

HELP..

Adobe has stated publicly that CS4 is really designed for 64 bit OS with 16 GB RAM to get the full performance.
I've just switched from Quad Core, XP 32, 4 GB, CS3 to Intel i7, Vista 64, 12 GB, CS4 and, so far, it seems like a huge improvement in performance. I am having none of the chronic memory management problems that plagued me on the CS3 system.
My big remaining issue is the fact that Premiere CS4 seems not to be a completely finished product yet. Hopefully the 4.1 update will do the trick.
The other bummer is the difficulty that CF is having with conforming PHD 4 to Premiere 4.
I am hoping that once Adobe gets Premiere cleaned up a bit, and CF gets PHD 4 out the door, running as smoothly as PHD 3 had been, it will be a done deal and I can get back to editing.

Hi guys I think we are getting a little side tracked. We need to stay focused on solving the beta testing and keep providing Dave and support with information!

Sorry am I wrong for saying that?

Good point, this thread has wandered a bit! :-)

While I appreciate the advantages of First Light it will probably not be a much used product in my studio. In the current project, which is an idie, the raw HDV footage is so visually stunning I very rarely adjust it and certainly never for a look.

With 4 if I understand correctly I will have to capture using HDLink where I can only set a base name to my captured footage. It will therefore be quicker to review and log it after it has been captured. I will miss the ability to review log and rough edit straight to cineform. With another 20 hours of tapes to view I will probably continue to do that in CS3.
Are there any other improvements in 4 to get me reaching for my credit card other than the, at presant, somewhat dubiouse advantage of being able to use CS4?

For those of you still having First Light problems using Vista... is User Account Control (UAC) on or off? Also make sure you have the latest QuickTime installed.
Without QT installed, it *should* give you a corresponding message prompt and quit the player whenever you attempt to load a clip (AVI or MOV).

I have found that with UAC ON, any adjustments I make are disregarded. That's because with UAC on, Windows is prohibiting us from writing the necessary information to the metadata database, thus practically defeating the purpose of First Light!

Turning UAC off fixed this problem on our fresh test machine (2.13GHz Lynnfield, 2GB RAM, Vista 32-bit, nVidia GTX260).
For those of you concerned about Vista 64 compatibility, we ran First Light at NAB on Vista 64 machines from Lenovo without incident (Core i7, nVidia Quadro FX1800, 6GB RAM).

We will try to work around this limitation (although I can't imagine ever running a Vista system with UAC on -- I think I'd be institutionalized within 48 hours), but this is the workaround for the meantime.

If you are seeing just a gray window where your video should be, let me know your video card make, model, and driver version so we can figure out where the problems are.

Continue to send feedback directly to me at tbucklin@cineform.com and let me know of any First Light troubles you have. Any CS4-related problems should still be directed towards David Newman or our support department (support@cineform.com)

@Tim,

LOL, Does anyone run Vista with UAC on?

But back to beta testing.

1) First Light now displays the CFHD AVI videos nicely (Vista x64, 4GB, nVidia 9800GT, GeForce 182.50 ), except at 1/4 resolution, where it looks like a scrambled cable TV signal. As you go back and forth between half and full resolution, sometimes, the aspect ratio changes, but I can't see a pattern. I have to check both 1920x1080 files and 1440x1080 files further, in order to see what the heck the pattern of the distortion is, but it appears that 1920 x1080 files display fine in all 3 resolutions and it's the 1440x1080 (PAR=1.333) that are goofy. See what other folks have to say about this.This issue may related to my video card or driver.

2) 1920x1080 CFHD MOV files also work great in FL. I don't have any 1440x1080 CFHD MOV files to play around with, but I can make one to see what happens.

3) The old 30.00 fps files that were converted by previous versions of NEO from Canon 5d2 30.00 fps MOV files, display the frame rate in FL as 23.976 fps (Wouldn't that be nice if it was true!!!).

4) Else, the various FL settings for the active metadata work fine and they stick with the files in PP, AE, various media players (QT Pro, Media Player Classic), VirtualDub and Vegas. Very nice!

5) AE CS4 works fine with CFHD files.

6) If both the CS4 and CS3 suites are installed under Vista x64, you won't get any CS3 files installed (still) and you have to copy them manually to the various CS3 folders. You really need a dialog box that asks the user as to which version you want installed (or both maybe, until people wean themselves off of CS3). This might just be a problem with my computer, but I'd like to hear if anybody else got a good install on a machine with both PP CS3 and CS4 installed.


More later. Gotta do some real work. ;-)

Great feedback, Jay. Glad to see it's working (mostly) for you.

The quarter-res decode is really meant for 4K-res files to be decoded at 1k. Though, it is supposed to still work with 1080p content (and does on our nVidia Quadro-based test machines here.)

ATI cards are still not doing either the half- or quarter-res decodes correctly, but we are experimenting with different output pixel formats to see what the different cards like the best.

As for 30.00fps coming up as 23.976, I'll look into that.

Thanks again for the thorough response.

@Tim

I just checked everything out (Prospect HD V4 Build 208) on one of my XP (x86) computers that just has CS3 installed. Everything works perfectly, including FL. There are no problems at all, with either the menu items being grayed out or aspect ratios being wrong in the FL Player with 1440x1080 files. The 23.976 fps frame rate display in FL appears to be related to 60i and 30p CFHD MOV files of any type (not just those converted from the odd 30.00 fps Canon 5d2 files) and is duplicated on the XP computer. However, I did notice that the two CFHD "importer" prm (AVI & MOV) files were installed in the PP plug-ins folder. I thought that these were only for CS4.

I've run out of anything to test, but that's a good thing. This build is pretty solid for me.

JB

@Tim

I just checked everything out (Prospect HD V4 Build 208) on one of my XP (x86) computers that just has CS3 installed. Everything works perfectly, including FL. There are no problems at all, with either the menu items being grayed out or aspect ratios being wrong in the FL Player with 1440x1080 files. The 23.976 fps frame rate display in FL appears to be related to 60i and 30p CFHD MOV files of any type (not just those converted from the odd 30.00 fps Canon 5d2 files) and is duplicated on the XP computer. However, I did notice that the two CFHD "importer" prm (AVI & MOV) files were installed in the PP plug-ins folder. I thought that these were only for CS4.

I've run out of anything to test, but that's a good thing. This build is pretty solid for me.

JB


Jay do you have cs4? Does cs4 run on XP/64?

Ok I think there is an aspect problem when you use CF.avi and change the resoultion like 720x480 wide NTSC. it is falling short in width it does not fill the render box. And when I open the short clip after converting, Even media player it plays 4:3 squeesed so even media player is seeing it as if it was not wide screen, Look closly at the render box and notice the black bars at the side. I think it is an aspect problem.

Dave can you comment on the possibilities..

Jay do you have cs4? Does cs4 run on XP/64?

I have the CS4 suite, but it's only on one computer running Vista x64 Ultimate with 4GB RAM. It runs fine. The only thing that I noticed was that AE CS4 sometimes doesn't recognize the Open GL card properly, but I never use OGL anyway. I used to have one computer with XP64 in a double boot with 32 bit XP. but I deleted the XP 64 OS partition, so unfortunately, I can't help you there. You could get bold and download the CS4 demo from the Adobe website and see how it runs. The demo is missing a few codecs, but it should give you some idea of why Adobe doesn't support CS4 on XP 64 bit.

If you Google "CS4 XP 64" you will find a lot of items, mostly discouraging. At this point, if you want to go with CS4, you probably should either wait for Windows 7 or upgrade to Vista x64. And my advice is pack the computer with as much RAM as it will hold.

I'm using CS3, Vista 64-bit. I've had problems with importing CF avi files or opening CF projects in Premiere.

I'm uninstalled and reinstalled a number of times, this last time because I thought I was overlooking some cineform files somewhere that were messing up the new install. While I was at it, I thought I would re-download the Prospect HD file (just in case). But it doesn't seem to be downloading. I've only managed to download ~3.5 MB's worth of the zip file. Neo HD downloaded fine.

Also, regarding the screen grabs from earlier showing the importer and exporter files in the MediaCore folder: does that just apply to CS4? What should the MediaCore folder look like in CS3? I know I only had one file (im-CFHD_File_Import.prm) in there after installing Prospect HD.

Other system specs: Quad Core (Q6600), 6GB RAM, Nvidia Quadro FX 1700

But it doesn't seem to be downloading.

OK, it seems to be downloading now. We'll see how the install goes.

First Light looks like it is working, though all I have tried is loading a file and tweaking the settings.

I'm still running into the same problems with Premiere CS3: I can't open old CF projects, and while I can create new CF projects, I cannot import CF files.

First Light is working. However, it would be great to have a manual. I really do not know what I am doing. I have been able to make color corrections and then see the resluts in P-Pro CS4.

Ok, giving build 208 a try.

Machine specs:
i7 920 (stock)
12GB RAM
nVidia 9600GT 2GB,
RAID0 for converted video.
Samsung 2343BX Monitor (2048x1152)
Vista 64

First Light opens (yay!).
The video display area seems to be proportionally constrained. If I maximize, the scrub controls disappear off the bottom of the screen, and the video window overlays other parts of the application (looks like it's floating in front of the app).

Keyframes sure would be nice!!! Either that or a lighting tech that won't change lighting in the middle of a dance...

It seems like a very useful tool. I don't generally need to color correct a whole lot, and this seems like it'll give me the option to do minor tweaks to the overall levels and color, and save me a bunch of time or rear-end rendering. Hopefully.

There's no audio (should there be?).

Again, keyframes would be nice, but I usually don't have footage like what I'm running through right now.

The timecode display does not update as I'm scrubbing or playing.

I don't think I'm seeing all the nifty things that were on David Newman's interview video from NAB. Is there a difference between PHD and P4K versions of First Light? It would be nice to see an actual curves graph that I could manipulate.

I'm not seeing a way inside of Premiere Pro to enable/disable the First Light database. Do I just rename the database and/or project file where the video clip is?

That's about it for now. Have to work on my travesty of a Web site, but initial impressions on this build are pretty good.

Thanks,
Matt

The video display area seems to be proportionally constrained. If I maximize, the scrub controls disappear off the bottom of the screen, and the video window overlays other parts of the application (looks like it's floating in front of the app).

Yep, this happens to me also.

There's no audio (should there be?).

I think that David Newman posted previously that this build has no audio.

The timecode display does not update as I'm scrubbing or playing.

I haven't seen that yet.

I don't think I'm seeing all the nifty things that were on David Newman's interview video from NAB.

Here's a shorter version of a few that are online, but it covers what FL does succinctly.

NAB09 Cineform reveals real time color corrector! | Filmmaking Central - The Process of Filmmaking (http://filmmakingcentral.com/fmc2/2009/04/20/blogs/nab09-cineform-reveals-real-time-color-corrector/)

There is more info re: First Light, on the Cineform website:

Cineform Tech Blog Blog Archive Active Metadata - Technolgy Overview (http://techblog.cineform.com/?p=256)

Ok I recaptured 1440x1080 60i footage but when capturing converted to 1920x1080 first light worked only at full resoultion setting crashed when trying to set to half or quater.

Video was slow motion.. I am using a ati radeon 3400 series HD card I had good picture but like I said it was like watching slow motion.

I can not get a CF file thru PPcs4 compressed to DVD (SD) or blu-ray.. Another note when encoding with media encoder CPU runs 100% maxed out.

Dave did you say the accelerator in not in the beta version?

Hello,

Not sure if I should do a support ticket or just mention the error here.

I installed the latest beta for Prospect HD yesterday.

My setup is:
Vista Business 64-bit
12GB
2 Xeon Quad Cores
Nvidia Quadro NVS 295
Premiere Pro CS4
After Effects CS4

I am getting the importerprocessserver.exe error via Adobe Media Encoder.

Using the settings 720p for window media player.

Any ideas?

The previous beta version worked fine with exporting. The latest has given me the error attached.

I uninstalled the latest version of Prospect HD and reinstalled the previous beta version but that does not work anymore either. I am getting the same error when I export.

Any way to remove all files of cineform and reinstall the beta version that worked for me?

Simon

I've been testing quite a bit, and have successfully converted a number of files to CineForm, adjusted them in FirstLight, and put them into a PPro CS4 project. However, I am seeing the following issues:

- Import Process Server crashes. Happens in PPro, AME, etc.
- Cannot open a project that contains After Effects linked clips, causes AE crash. AE does open standalone.

Here's a crash report from Import Process Server:

Problem signature:
Problem Event Name: APPCRASH
Application Name: ImporterProcessServer.exe
Application Version: 0.0.0.0
Application Timestamp: 491896d7
Fault Module Name: CFHDDecoder.dll
Fault Module Version: 2.5.0.30
Fault Module Timestamp: 49ffb07d
Exception Code: c0000005
Exception Offset: 0000d7ca
OS Version: 6.1.7100.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789


I'm not seeing the FL bugs mentioned above (video scaling, timeline scrubbing, etc.).

On question: should Snapshots contain all of the settings (e.g., white balance, color matrix, etc.)? When I save a Snapshot then try to apply it to another file, these settings aren't changing.

Regards,
Glenn

Ok, giving build 208 a try.

Keyframes sure would be nice!!! Either that or a lighting tech that won't change lighting in the middle of a dance...

Thanks,
Matt

I think you're missing the philosophy behind color grading in the metadata space. Keyframes are not pragmatic for this application. CCing in the metadata space is for overall "look", not tweaking individual scenes.

It seems to me that cs4 is choking on cf files. The main thing I see is we can not use the cineform presets because there are not present? And I am back to the acceleator is that not present either?
Does anyone have an thought a out this? Dave

Did I miss something?

.net framework 3.5 should be installed?

I need to check if I have the latest.

Thanks,

Simon

I am getting the exact same error. I also get it after a few scrubs on the timeline.

XP SP3
Nvidia 8800 GTS
Quad Core CPU 2.83GHz
3.50 GB ram
Intel Matrix Raid 0

Seems there a lot of Import Process Server crashes, including my system. Does anyone have any further info on a possible cause?

I have been asking the same question and no response? I am installing an drivers side airbag my face in beginning to hurt

I noticed your post Bruce. I had a go at Adobe support yesterday but got a 'It's not us, it's you' response and then silence which didn't help me of course. I'm waiting for David to chime in with a possible update.

One tip which may help others in this forum with jittery playback in CS4 off an Nvidia card, is that the current beta driver 185.81 seems to have corrected this for me. I have an 8800GTS and the beta driver fixed playback on reboot. Curiously, it also repaired issues with the Nvidia PhysX config not being recognised in CS4.

Off topic, but thought I'd mention it for the good of all.

HDlink.exe following the PHD 4.0 beta release states version 4.0.1. (1428 kb ). Can someone confirm that this is correct ?

Hello all,

Thought I would jump in with a two questions. I have a laptop running regular vista. I have both CS3 and CS4 production priemuim suite installed. I also have Prospect HD 3.4 installed. I am really trying to only use Premiere Pro CS4 as much as possible. Right now I am able to import my old cineform HDV files that I originally captured with Premiere pro CS3 and Prospect HD 3.4 and import them into Premiere Pro CS4. I have not installed the new beta of Prospect HD 4.0 yet.

My questions are:

When is the non-beta version of Prospect 4.0 going to be available?
When it becomes available and I install it on my laptop will it install correctly on both CS3 and CS4, or will it by default only install to either CS3 or CS4? If so will I be able to manually find the importer files and drop them into CS4 or CS3 so it works in both?

Thanks,

Mark

It seems to me that cs4 is choking on cf files. The main thing I see is we can not use the cineform presets because there are not present? And I am back to the acceleator is that not present either?
Does anyone have an thought a out this? Dave
I think that the answer to your question is either earlier in this thread or in some other recent thread. CS4 only has the CFHD import and export functions. It has no acceleration yet, nor does it come with the Cineform presets. Cineform is working on those features, but they are presently not included in the beta build (208) that is being publicly tested. Prospect HD/4K V4 does have all the functions implemented for Premiere Pro CS3.

I'm taking a wild guess here that when Adobe releases the PP CS4 4.1 update, later this month, Cineform will release the full blown version of Prospect for CS4.

Curiously, it also repaired issues with the Nvidia PhysX config not being recognised in CS4.

I hope that you meant the CS4 Open GL bug, because PhysX (3D particle physics) might be a little crazy for video work. :-)

I think that the answer to your question is either earlier in this thread or in some other recent thread. CS4 only has the CFHD import and export functions. It has no acceleration yet, nor does it come with the Cineform presets. Cineform is working on those features, but they are presently not included in the beta build (208) that is being publicly tested. Prospect HD/4K V4 does have all the functions implemented for Premiere Pro CS3.

I'm taking a wild guess here that when Adobe releases the PP CS4 4.1 update, later this month, Cineform will release the full blown version of Prospect for CS4.

thanks Jay,
I guess at this point the only thing that can be tested is first light? Because I suspect CS4 can't handle the Cineform files without the acceleration! Importert server keeps crashing. And CPU runs solid 100 percent!

Jay not get off topic where did you read about adobe 4.1 release this month? I getting ready to send it back to refund?

Right from the horse's, uhh ... mouth:

Adobe - Adobe Press Room: For immediate release (http://www.adobe.com/aboutadobe/pressroom/pressreleases/200904/042009AdobeNABUmbrella.html)

As to beta testing in Premiere Pro CS4, I would think that Cineform still needs everyone's input on how well importing and rendering CFHD files is working for them. I've only encountered one Import Process Server crash and that was on the previous beta build. Rendering to CFHD works fine for me in CS4.

I hope that you meant the CS4 Open GL bug, because PhysX (3D particle physics) might be a little crazy for video work. :-)

Indeed, you're right Jay, I mean't OpenGL. :o)

You're referring to a performance hit when engaging PhysX I take it?

As to beta testing in Premiere Pro CS4, I would think that Cineform still needs everyone's input on how well importing and rendering CFHD files is working for them. I've only encountered one Import Process Server crash and that was on the previous beta build. Rendering to CFHD works fine for me in CS4.
Jay,
I've had problems with PHD 4 for both import and rendering in CS4
1) Import of HDLink converted EX1 footage: Video previews O.K., but audio track will not import properly
2) Rendering: If I render a CFHD clip from the timeline, the resulting preview image is distorted and squeezed down to the lower third of the frame in the Program monitor.
Raw mp4 and avchd play and render normally in CS4, only a CF issue, and only with EX1 sourced CFHD footage.
I don't know if it's a problem with CS4, PHD4, or if they are just not getting along with each other.

I also get squashing of the preview in CS4 but using HDV footage.

Ok I think I am on to something. I posted earlier the we you go to export/media and the encoder opens and you set your settings to Cineform.avi 720x480 NTSC wide the output preivew does not fit the width and it should 480 is divisiable by 9 evenly.

So I did the following:
selected Cineform.avi
unlock pixel res. set to 720x490!!!!!!! it fit the output preivew!
set NTCS/wide
set quality to medium
set lowerthirds..

NO CRASHES!!!! File outputs fine and CPU runs about 50 to 70% not maxed out!! Can someone else try this to see if it works for them?? It did not matter if I was using old CF files or new ones!!!
No getting it thru Encore is a different story because when you bring it in to there it wants to screw the width up again and show that the video does not want to fit the width again.

Ok I think I am on to something. I posted earlier the we you go to export/media and the encoder opens and you set your settings to Cineform.avi 720x480 NTSC wide the output preivew does not fit the width and it should 480 is divisiable by 9 evenly.

So I did the following:
selected Cineform.avi
unlock pixel res. set to 720x490!!!!!!! it fit the output preivew!
set NTCS/wide
set quality to medium
set lowerthirds..

NO CRASHES!!!! File outputs fine and CPU runs about 50 to 70% not maxed out!! Can someone else try this to see if it works for them?? It did not matter if I was using old CF files or new ones!!!
No getting it thru Encore is a different story because when you bring it in to there it wants
to screw the width up again and show that the video does not want to fit the width again.

Sorry 490 not divisable by 9 trying 495