DV Info Net

DV Info Net (https://www.dvinfo.net/forum/)
-   CineForm Software Showcase (https://www.dvinfo.net/forum/cineform-software-showcase/)
-   -   Prospect/Neo 4 Problem Thread (https://www.dvinfo.net/forum/cineform-software-showcase/235443-prospect-neo-4-problem-thread.html)

Matt Vanecek May 20th, 2009 07:57 PM

James,
Thanks for the clarification.

It's just really frustrating. PPro 1.5 did what I needed until just recently. Doing more multi-camera work, and that's just a pain in something without a multi-camera view. Plus, CF won't support 1.5 anymore. So when I upgraded, to coincide with a new editing system, CS4 was what was available. Only, CF doesn't support CS4.

I don't really miss the RT Engine. First Light is a real coupe, in my opinion, for CF, and really obviates the need for in-NLE color correction (for me, right now, anyhow). My system is fast enough that CF files play real time, because I don't really use a lot off effects. Up until the ImporterProcessServer crash now, anyhow. I just want an importer that won't crash--I'm more than happy to wait on the rest if I can just edit & export.

I haven't retried the CFHDDecoder.dll thing again, yet, though, per Glenn's suggestion. That's next step--and then rebuilding the project as M2T.

Thanks,
Matt

Adam Zell May 20th, 2009 08:22 PM

Hey guys,

I have found this a couple of months ago and it seemed to work for me, was when you have premiere loaded up, if you are working in a windows enviroment, then hold down on your Ctrl, Alt and Delete to bring up your Windows Task Manager. When you have that up, go over to the process tab and search through for the ImporterProcessServer file that is being used. Right click on that and go down to Set Priority, and then select High instead of normal on the list. Most computers don't have the memory allocation and power to do real time, but High should be enough that it will allow you to import the larger files. I have like 3 hours of footage and it allowed me to bring it all onto the timeline. See if that helps out?

Matt Vanecek May 21st, 2009 07:01 AM

Well, the CFHDDecoder.dll thing didn't work. The export just froze. Worth a try, I guess. Setting ImporterProcessServer priority never worked, either, just for the record. ImporterServerProcess would just crash the encoder.

Back to M2T; hopefully I can get the colors right and get it rendered out in time....sure would be nice to be able to take advantage of First Light...

Matt

Glenn Babcock May 21st, 2009 11:29 AM

Matt,

In my case it was two issues and two solutions; the posted ImporterProcessServer and the reinstall. James' solution may be a sub for the reinstall.

The way I knew the ImporterProcessServer fix worked is that I didn't get crashes while editing anymore. Is that much working for you?

Regards,
Glenn

Jay Bloomfield May 26th, 2009 12:50 PM

Quote:

Originally Posted by Jay Bloomfield (Post 1145047)
I have a theory about some of these PP CS4 crashes and that they are being caused by the VFW version of the Cineform codec, CFHD.DLL. ...

I wanted to add something further to this. As many people have noted, in PP, there are two routes to render a CFHD AVI file. The Cineform-authored exporters (plug ins) use the DirectShow version of the codec, but PP also allows producing an AVI file with any compatible video codec installed on your computer and it apparently accesses the VFW version of the CFHD codec. My suggestion would be for everything except NEO Scene, to somehow block PP from using the VFW version of the codec, since its use is redundant and it may be the source of some of the crashes in PP.


All times are GMT -6. The time now is 01:12 PM.

DV Info Net -- Real Names, Real People, Real Info!
1998-2025 The Digital Video Information Network