Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro HELP! – ImporterProcessServer.exe has stopped working + width/height too large

  • HELP! – ImporterProcessServer.exe has stopped working + width/height too large

    Posted by Clint Milner on May 8, 2009 at 1:11 pm

    I’m getting this error everytime I try importing a video that I got converted from a BetaCam tape. I have the movie in Microsoft DV Codec and Quicktime DV Codec.

    The first thing that happens is this error pops up with the following details:

    ImporterProcessServer.exe has stopped working
    Problem signature:
    Problem Event Name: BEX
    Application Name: ImporterProcessServer.exe
    Application Version: 0.0.0.0
    Application Timestamp: 491896d7
    Fault Module Name: MSVCR80.dll
    Fault Module Version: 8.0.50727.3053
    Fault Module Timestamp: 4889d619
    Exception Offset: 00008aa0
    Exception Code: c000000d
    Exception Data: 00000000
    OS Version: 6.0.6001.2.1.0.256.1
    Locale ID: 2057
    Additional Information 1: a388
    Additional Information 2: cb1346f285b14b60ce06bcb7640ef607
    Additional Information 3: 7188
    Additional Information 4: c8538bb25c54d271cb1dde4a6dfbc4e0

    Then a dialogue box pops up that says

    File Import Failure

    File video dimensions ( width/height ) too large.

    I have no troubles importing files I’ve used previous to this project.

    I’m using CS4 4.0.1

    Vista Ultimate.

    Many thanks for any help and advice.

    Kind Regards,

    Clint

    Adobe CS4 Master Suite
    Vista Ultimate 64 SP1
    Intel Core i7 920 @ 3.60GHz
    12 GB DDR3 RAM
    NVidia Quadro FX 3700
    Matrox RT.X2 LE Capture Card
    4 TB RAID 5

    Guidon Mendoza replied 16 years, 8 months ago 3 Members · 2 Replies
  • 2 Replies
  • Eddie Lotter

    May 8, 2009 at 3:58 pm

    Use a program like GSpot to interrogate the problem DV AVI file to be certain that it conforms to the DV standard.

    Another thing to try is to open one of the problem clps in Windows Movie Maker and export (publish) it as DV AVI and test that file in PPro.

    Cheers
    Eddie

  • Guidon Mendoza

    September 6, 2009 at 8:49 am

    I hope this would help, but I don’t think so. It seems to be a bug on the suite coding. I have the same and I have checked everything.

    Cheers and good luck

    Guidon

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy