Can anyone please tell me where the Cineform Presets are supposed to be?

They are located as follows:

c:\Program Files\Adobe\AdobeCS4\Settings\Cineform

Whenever I open CS4, there are no CF presets. Should there be another file somewhere that may be missing?

Thanks,

Marty

Martin,

Presets are used when the playback engine in part of CS4, that is not here yet, therefore no presets.

Martin,

Presets are used when the playback engine in part of CS4, that is not here yet, therefore no presets.

Thanks David.
I have PHD 4.01, opened an AVCHD preset in CS4, imported 3 clips from my Sony HDR XR520V camera and exported them as a CF Avi using AME. The export worked perfectly.

As I said previously I have an XP Pro 32 bit system with a QX9650 Processor and Nvidia 8800 GT card. I hope this helps.

Marty

Martin what preset did you use?

Regarding Presets, I select one the is close to the frame rate and size, doesn't matter which, then switch the editing mode to "desktop". You can save that as a preset if you wish.

Martin what preset did you use?

HDV-AVCHD 1080i/1080 i30(60i)

I am on test build of the following setups, same computer HP XW8600 8gb of ram, Nvidia Quardo fx 3700

:::BUILD 1:::
Vista 64bit
Adobe cs3 with all updates
Nvidia Quadro fx 3700 Driver 182.46
Firstlight, I can make adjustments to the color Matrix fine
Prospect HD: 4.0.1.210

I try and open a previous Cineform Prospect HD project from v3 I get this error when I am trying to load the project as Premeire pro cs3 crashes.

Problem signature:
Problem Event Name: BEX
Application Name: Adobe Premiere Pro.exe
Application Version: 3.2.0.0
Application Timestamp: 47fd3df6
Fault Module Name: Mezzanine.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 47fd3a75
Exception Offset: 06144850
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.0.6001.2.1.0.256.6
Locale ID: 2057

Read our privacy statement:
Microsoft Online Crash Analysis (http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409)

I then un-install and put Prospect HD v3.49 Build 193, the project now opens fine.

:::BUILD 2:::
Vista 64bit
Adobe cs4 with all updates
Nvidia Quadro fx 3700 Driver 182.46
Prospect HD: 4.0.1.210

Firstlight, as soon as I try and make any adjustments to the color Matrix I get a crash.

Description:
Stopped working

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: firstlight.exe
Problem Signature 02: 0.0.0.0
Problem Signature 03: 49fb78fc
Problem Signature 04: PresentationFramework
Problem Signature 05: 3.0.0.0
Problem Signature 06: 48fef62a
Problem Signature 07: 625a
Problem Signature 08: e1
Problem Signature 09: System.Windows.Markup.XamlParse
OS Version: 6.0.6001.2.1.0.256.6
Locale ID: 2057

Read our privacy statement:
Microsoft Online Crash Analysis (http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409)

Premiere pro cs4, I try to encode to a h264 quicktime, youtube perset from a cineform master file that I rendered out to a AVI in Adobe Media Encoder 4.0.1

I get near the end of completing the render, "Un-known error", or it finishes the render but then the h264 file has no audio.

Photoshop CS4, extended
I can bring a 1280x720 Cineform video file into Photoshop to choose the frame for stills. If I then bring in a 1080 Cineform file, it is blank just a chequer board.

Dave or anyone.

I have completed a 50 min project. CF 1440x1080 60i when I export to CF.avi 720x480 NTSC wide 16x9

The compressor is making it 4x3 squeezed.. Even when I bring it into Encore I am seeing a 4:3 squeezed video.

If I bring it back into PPcs3 it is squeezed 4x3. I just want to make sure it was just not media player when I went to preview the output.

Bruce,

That is not likely a v4 issue. Just use intepret footage to set the pixel aspect correctly so your Encore encodes will be fine.

Leo,

PC 1 -- that is likely an Adobe bug, as loading projects is primarily a Premiere function. If it fails on multiple PCs, please send the prproj file to support to see if there is something obvious.

PC 2 -- Weird that the same software will not run. Unfortnately the CLR20r3 error report from MS managed code it not very helpful. Is it particular operation that fails, or particular file types? We need to fail generally to find a fix, i.e. what is different about the test you did not that PC (other than CS4 vs CS3, FirstLight doesn't care.)

Bruce,

That is not likely a v4 issue. Just use intepret footage to set the pixel aspect correctly so your Encore encodes will be fine.


Dave that worked but I never had to do that before..Adobe PP CS3 does not even bring the CF.avi back in the project correctly and it alway brought it in 16x9.. What could I have done wrong? I have been testing the compression of CF on 720x480 NTSC/wide That is so improtant to me I have been testing before I bought

Leo,

PC 1 -- that is likely an Adobe bug, as loading projects is primarily a Premiere function. If it fails on multiple PCs, please send the prproj file to support to see if there is something obvious.

PC 2 -- Weird that the same software will not run. Unfortnately the CLR20r3 error report from MS managed code it not very helpful. Is it particular operation that fails, or particular file types? We need to fail generally to find a fix, i.e. what is different about the test you did not that PC (other than CS4 vs CS3, FirstLight doesn't care.)

Hello David,

It is the Colour matrix sliders, such a sred, blue, green etc, as soon as I click on them to make ajustments it just crashes.

Yes both pc build, are the same system just a differentbackup cs3/cs4 build which I restored onto the boot drive in the HP using Acronis Echo Workstation.

Bruce,

I don't believe anything has changes in this area. So it is not likely a new bug, particularly as SD is not a big focus for CineForm. As long as all the pixel data is there, the intepret footage is lossless, so it is a cosmetic bug. Once we solve the CS3 installer issues, and CS4 stuff, than we might find time tweak the SD exports.

Leo,

You can see why that doesn't make sense. Two identical systems one works one doesn't, please test with the same footage, find something that is more logical and send us that data (i.e. a particular file that crashes on both PCs.)

David,

OK, editing has been going just fine. However I can't export anything. If I select File, Export, Media then AME comes right up, but when I hit Start Queue it hangs on Loading project. I tried choosing different export settings (CineForm AVI, MPEG2 Blu-Ray, etc.) but no difference.

If I close PP4 first and start AME from the menu then File, Add Premiere Pro Project, and click on the file it hangs there for about 8 minutes, then errors out.

AME Error log:

5/17/2009 8:18:40 PM : Encoding Failed
-----------------------------------------------------------------------------
Could not read from the source. Please check if it has moved or been deleted.
-----------------------------------------------------------------------------

Here's a directory listing of CFHD files:

C:\>dir cfhd*.* /s
Volume in drive C has no label.
Volume Serial Number is B26A-90B1

Directory of C:\Program Files (x86)\Adobe\Adobe After Effects CS4\Support Files\Plug-ins

05/14/2009 07:24 PM 851,968 CFHDIO.aex
1 File(s) 851,968 bytes

Directory of C:\Program Files (x86)\Adobe\Adobe Premiere Pro CS3\Plug-ins\en_US\CineForm

05/14/2009 07:41 PM 114,688 CFHDVDeviceControl.prm
05/14/2009 07:41 PM 122,880 CFHDVRecordPro.prm
2 File(s) 237,568 bytes

Directory of C:\Program Files (x86)\Adobe\Adobe Premiere Pro CS4\Plug-ins\en_US\CineForm

05/14/2009 07:45 PM 294,912 CFHD_AVI_Importer.prm
05/17/2009 06:56 AM 303,104 CFHD_AVI_Importer.prm.new
05/14/2009 07:46 PM 167,936 CFHD_File_Exporter.prm
05/14/2009 07:46 PM 458,752 CFHD_MOV_Importer.prm
4 File(s) 1,224,704 bytes

Directory of C:\Program Files (x86)\Adobe\Common\Plug-ins\CS4\MediaCore

05/14/2009 07:45 PM 294,912 CFHD_AVI_Importer.prm
05/17/2009 06:55 AM 303,104 CFHD_AVI_Importer.prm.new
05/14/2009 07:46 PM 167,936 CFHD_File_Exporter.prm
05/14/2009 07:46 PM 458,752 CFHD_MOV_Importer.prm
4 File(s) 1,224,704 bytes

Directory of C:\Program Files (x86)\CineForm\Tools

05/17/2009 12:59 PM 753,664 CFHDDecoder.dll
05/14/2009 07:45 PM 757,760 CFHDDecoder.dll.old
2 File(s) 1,511,424 bytes

Directory of C:\Program Files (x86)\Common Files\CineForm

05/14/2009 07:14 PM 98,304 CFHDSDIASIODriver.ax
05/14/2009 07:14 PM 159,744 CFHDSDICapture.ax
05/14/2009 07:15 PM 155,648 CFHDSDIRenderer.ax
3 File(s) 413,696 bytes

Directory of C:\Program Files (x86)\QuickTime\QTComponents

05/15/2009 05:38 PM 1,058,304 CFHDCodec.qtx
1 File(s) 1,058,304 bytes

Directory of C:\Windows\SysWOW64

05/15/2009 05:38 PM 1,077,248 CFHD.DLL
04/30/2009 06:25 PM 1,441 CFHD.INF
2 File(s) 1,078,689 bytes

Glenn

Bruce,

I don't believe anything has changes in this area. So it is not likely a new bug, particularly as SD is not a big focus for CineForm. As long as all the pixel data is there, the intepret footage is lossless, so it is a cosmetic bug. Once we solve the CS3 installer issues, and CS4 stuff, than we might find time tweak the SD exports.

Hi Dave,
Encore crashed when trying to create DVD. Maybe the squashing has something to do with the importprocess server crashes. I did output the file no problem with v3.4.5 in CS3 and the CF.avi did not look squashed after encoding? It almost like the encoder is trying to double encode?

Glenn,

Try completely removing the CFHD_AVI_Importer.prm.new files as I'm not sure Premiere doesn't load them anyway. As you export seemed to go away when you added the new importer, not when you added the cfhddecoder.dll (whih should be unrelated.) Can you confirm please.

David,

I did but no joy.

I forgot to mention, my trial key for ProspectHD expired this weekend so I installed Prospect4K to keep going. Could it be related to that?

Dave,

Encore CS3 crashed on the squashed file as you can see by my post but..Encore CS4 transcoded fine all the ay thru at 4:3 (I fogot to click 16x9) in the transcoder button when I went to transcode 16x9 after I selected interept footage Encore CS4 crahsed too.

could there be something with the wide/ntsc setting and the importprocess error? Dave when I was trying the 3.4.9 version of CF this never occured and even media player saw the CF.avi as a 16x9 output on the exact same computer?

Dave I noticed that even CS3 wants to conform or regenerate the CF files in the project everytime you re-open the project? Is the the importer doing that. I thought once the files were imported they should not have to br re conformed or the peek files should not have to be regenerated?

Dave I noticed that even CS3 wants to conform or regenerate the CF files in the project everytime you re-open the project? Is the the importer doing that. I thought once the files were imported they should not have to br re conformed or the peek files should not have to be regenerated?

Nothing has changed for audio in CS3. If you save the project the audio will not reconform -- confirmed moments ago. There is an old Premeire bug in CS3, that it will sometimes require you to import an old project into new one, to fix weirdness like audio conforms not being preserved, but this is not a Prospect bug.

David,

I did but no joy.

I forgot to mention, my trial key for ProspectHD expired this weekend so I installed Prospect4K to keep going. Could it be related to that?

Glenn,

Your feedback is now confusing, I have no idea what steps you took, therefore no closer to understand your system's issues. Originally you had importer issues, now you are having exporter issues, which suggests you importer issue are resolved. Please clear this up for me. Use email dnewman @ ... as this not nolonger about everyones PC.

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. Very few programs these days, other than NEO Scene, need this codec (including PP CS4), but they are some important pieces of video software, including Vegas (all recent versions), After Effects CS3 (but not AE CS4) and VirtualDub.

After not ever seeing the infamous PP CS4 ImportProcessServer error, I now am either getting that error, a DEP error from Vista or a crash of PP CS4 during the splash screen. I've installed nothing new on this specific computer, since installing build 210 of Prospect HD. It must have taken a couple of days for me to put together the right (wrong?) combination of A/V files and projects to coax the error out of hiding. ;-)

I uninstalled CFHD.DLL with the INF file and moved it to the Vegas 9 folder (w/o installation, so only Vegas sees the VFW codec), so that I could continue to use Vegas 9 (buggy that it is). Then I rebooted and checked all the software on my computer that imports or encodes with Cineform. Guess what? No crashes at all with PP CS4 or anything else for that matter. Maybe it's a coincidence.

Here's another interesting aside. GSpot, the codec appliance (which is not particularly stable under Vista anyway) hasn't worked for me in six months and always crashed on loading. The error message in the Windows event log always mentioned CFHD.DLL. Once I moved CFHD.DLL out of c:\windows\SYSWoW64, GSpot now works fine.

Food for thought, on a very cold day in upstate NY.

I just wanted to add something, because I noticed the other active thread about CFHD.DLL crashing various programs. Here's why VirtualDub probably never crashes with CFHD.DLL:

One video codec to break everything - virtualdub.org (http://www.virtualdub.org/blog/pivot/entry.php?id=139)

Anyone who has ever talked to Avery Lee knows that he's a legend in the video software world. He's very helpful and a while back, he took the time to help me sort out a problem that I was having with the BMD MJPEG codec. No one else could figure out what was going on and he solved it in one email.

My guess is that the error is occurring in the enumeration of all the system video codecs by something that is co-loading with PP CS4 or possibly PP CS4 itself. Maybe PP CS4 version 4.1 will fix this problem.

Hi Jay I think you are on to something here! When I try to Transcode a DVD with Encore CS3 I get a error crash that it can not encode because another progran is using the file? I have no other programs open which lead me to believe that maybe 2 codes are trying to encode the same file?

Wondering if there's any update on getting the ImporterProcessServer crash fixed? I do have several tickets open, but they have not been touched yet. Really need to get this going...

I'll try the CFHD.DLL thing above, and anything else. I have to get a DVD ready for Saturday, and need some way to export the video.

Thanks,
Matt

I've been testing for a couple of days with P4K and the CFHDDecoder.dll David posted (http://www.dvinfo.net/conf/1144271-post45.html). Before I installed the updated CFHDDecoder I had the ImporterProcessServer error all the time. Now I can edit a 2 1/2 hour sequence with 3 HD clips and effects for hours without crashing. I was also able to render out some of this video without a problem.

Try it and see if this addresses your issue!

Regards,
Glenn

OK, editing has been going just fine. However I can't export anything. If I select File, Export, Media then AME comes right up, but when I hit Start Queue it hangs on Loading project. I tried choosing different export settings (CineForm AVI, MPEG2 Blu-Ray, etc.) but no difference.

If I close PP4 first and start AME from the menu then File, Add Premiere Pro Project, and click on the file it hangs there for about 8 minutes, then errors out.

AME Error log:

5/17/2009 8:18:40 PM : Encoding Failed
-----------------------------------------------------------------------------
Could not read from the source. Please check if it has moved or been deleted.
-----------------------------------------------------------------------------

Glenn

I had this same problem when I tried to export out from Premiere CS4. Premiere sends its exports out to Adobe Media Encoder then when you try to start the que, it would just hang at "Loading xx.prpj" and do nothing.

Well it appears this is an Adobe problem and not a Cineform issue. It seems to be unresolved bug when both CS3 and CS4 are installed or if CS3 is uninstalled and some of its files are still there. The 4.0.1 update doesnt fix this problem so we'll see the real solution in their next update.

But here's the fix:

1. Close all Adobe applications.

2. In Windows Explorer, navigate to where you have Premiere installed (i.e. c:\Program Files\Adobe\Adobe Premiere Pro CS4 or c:\program files (x86)\... (under Vista 64). whereever you have Premiere CS4 installed.)

3. Right-click on Adobe Premiere Pro.exe (which might appear without the .exe extension) and choose Create Shortcut.

4. Rename the newly created shortcut to just Premiere. IMPORTANT: The name of the shortcut must be exactly "Premiere" with no other characters (not "Premiere.exe", not "Adobe Premiere.exe" Just "Premiere" with no ".exe".

5. Open a second Windows Explorer window, and navigate to C:\Program Files\Common Files\Adobe\dynamiclink. Under Vista 64 it will be C:\Program Files(x86)\Common Files\Adobe\dynamiclink

6. Move the Premiere shortcut that you created into the dynamiclink folder.

That's it. Now try exporting from CS4 Premiere and after it outputs to Adobe Media Encoder, loading the project settings and rendering output should work.

Here's the link for the original Adobe Solution:

Error: "Encoding Failed. Could not read from the source" (Adobe Media Encoder CS4 on Windows) (http://kb2.adobe.com/cps/407/kb407106.html)

James,
I'm willing to try anything right now, but we're not having issues with the project loading in AME. We're having issues with CFHD files being processed by Adobe products with PHD 4.0.x installed. Timeline scrubbing, encoding, simply having the project open--all these activities cause the ImporterProcessServer to crash. If you remove CFHD from the mix, then there's no crash.

Since Cineform does not seem to be forthcoming with a fix, I think I'm going to have to try converting the project to M2T, which works beautifully without issue in CS4 on Vista64. I'm not sure the timecode will match up correctly, though. :( Surely I'll be able to finagle it through a bit of project importing, matching of up footage and cutting in the right place...

It'd been easier if I hadn't expected the initial release of PHD4 to work--if I knew it was still beta (or alpha, in this case), then I would've started out with M2T like with my just-completed project.

Thanks,
Matt

Matt,

I am aware of the other issues with CS4 and Cineform. Just offering a solution fix for anyone else who might have CS4 export problems (which has been brought up by a few). I havent had the major problems with working within CS4, timeline scrubbing, effects, etc as it seems to be working on my end under Vista 64. So far I havent had any ImporterProcesserServer crashes either since the official update. (Just the install problems for CS3 but fixed it by removing those unnecessary files). But where ProspectHD support for CS4 stands now, I'm still using CS3 for any real work since the RT engine is still absent from CS4.

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

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?

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

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

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.