Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

How to deal with ImporterProcessServer.exe?!

Rudi Herbert

Well-known member
Joined
Jun 1, 2007
Messages
1,433
Reaction score
0
Points
0
For those CS4 users that are computer literate:

What is the ImporterProcessServer.exe utility that Premiere so heavily relies on? It allocates up to 2GB of memory of it on any given project I'm working on so it has to be important.But this thing is causing freezes and crashes in Premiere and it is responsible for those "media offline" and "file format not supported" messages of death you get all of sudden in a project that was working fine. Any ideas how to deal with this, how to optimize for it, what to do or not do to prevent these crashes? I've been working on a somewhat large project with about 200 XDCAM EX clips organized in several folders and several timelines, nothing this system with 12 GB of RAM and an i-7 processor couldn't take it easily, but it continues crashing on me every 20-30 minutes.

Help will be much appreciated,
 
a tool that is needed to feed premiere RED files. I think it will be going away soon.....but not yet....Everyone knows it's a bitch.
 
We have had some similar problems, but have over 3,000 clips and 16 gig of RAM. It seems that the ImporterProcessServer and the ImporterRedServer programs run out of steam and reload themselves. Eventually, you run out of RAM to start up another copy. I discovered this by looking at the Task Manager and saw that there were about fifteen copies of the program running. When I started shutting down most of them, it cleared up enough RAM to get things going again. I'm sure it's something that Adobe will address. I'm not enough of a tech wizard to really explain what's happening, but I also noticed that if you cut down on the number of sequences that you have open within a project, the performance is better, as well. We have about forty sequences and now work with only about five open at a time. You can open and close the sequences at any time, so there really isn't any reason to keep more than a few open at a time. I'm hoping to talk to Adobe next week about the problem and I'll let you know if we get any good answers.
 
Back
Top