This content has been marked as final. Show 12 replies
For AVCHD you need a really beefy PC. Yours likely is not beefy enough. It looks like time to invest in better hardware, install the OS from scratch, install CS4 and NEVER install K-Lite again if you are looking for stability.
My guess would be that the MP4s just aren't supported. One of the problems with MPEG files is that there are so many variables within them. Premiere's compatibility does seem to be centered around the standardized subsets of HDV, XDCAM and AVCHD, so it's very possible to get an MPEG2 or MPEG4 file that deviates from those specs and just plain won't work.
Many thanks for the responses.
Harm: Premiere runs at about 30% combined CPU time while a new blank project is open and 200Mb mem. Adding the MP2 .avis worked fine today, as did mp4 generated by Windows Movie Maker, however, while the mp4 .mov (appearently unsupported while called myfile.mov, but suddenly supported if renamed to myfile.avi - calling a seperate codec filter?) imports today, but utilises 100% on playback. Interestingly enough, the 100% continues until about 30 seconds after I hit stop and drops back to 10-15% usage -> it settled down to 10-15% from 30% after I'd loaded a few source files. This is not a hardware limitation, but software somewhere.
Be very careful about advising people to reinstall an OS - this is an utter last resort!
K-lite plays well with Movie Maker and Nero Vision on this machine and supports all these files under those "editing" suites, so I'm reluctant to blame solely that.
Jim: I've read that Premiere struggles with MP4 varients. Can you help me understand how Premiere reads files? It seems to use system codecs, but all the documents seem to point towards internal ones? If its using internal, why does a k-lite reinstall change the error messages, and if its system and everything else appears to be able to use these files via system codecs, where does the problem lie?
Many thanks for your help Jim - and any other responses!
Further to this, the majority of the CPU cycles go to ImporterProcessServer.exe... can anyone explain what this is?
>Can you help me understand how Premiere reads files?
Unfortunately, no. I've no knowledge of the programming under the hood.
Sometimes, ImporterProcessServer.exe will quit, but Pr will continue to run. If you try to import anything into Pr while IPS isn't running, you will get the File Dimensions error. At least that is what happens here.
Shutdown and restart Pr, then try to import again while making sure that IPS is running.
Last week I had problem importing MP4 and found that by making sure my MP4 source was encoded as AVCHD they would indeed import (thanks Jim). Today I found out the hard way that longer clips of the same codec still won't import, producing the height/width error.
Perhaps your "longer clip" attempt happened with IPS not running, as Jeff suggests?
Actually it just says (Not responding) in the little import window. Only after manually crashing the ImporterProcessServer.exe do you get the height/width error message. Any other MPEG-based file you import after that will produce the same error until you restart the app.
Wath is this ImporterProcessServer.exe? And why he takes so many RAM?
Or prompt me, where i can read about this.
Sorry if my english wrong. I`m not speak on english. :(
ImporterProcessServer.exe (I believe) is the actual executable that handles the process of importing file types into Premiere. I can't answer your RAM question excepted to say that parsing most video formats is an intense process.
Thank you. And one more question...
It means, that process must exit, then import ending? Or this process work parallel with Premiere.exe, until Premiere exit?