Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects HELP PLEASE AE6.5 ERROR !! After Effects error: an unspecified AVI or DirectShow error occurred.

  • HELP PLEASE AE6.5 ERROR !! After Effects error: an unspecified AVI or DirectShow error occurred.

    Posted by Kevin Merker on December 7, 2005 at 2:57 am

    After Effects error: an unspecified AVI or DirectShow error occurred. (1) (53 :: 33)

    Machine 1 : p4 3.06 , 4 GB DDR2 ram (3 gig enabled), WD120 8mb cache (main), Win XP PRO sp1 (NO UPDATES), direct X 9.0b, QT 6.3

    Machine 2 : p4 3.2 , 4 GB DDR2 Ram (3 gig enabled), WD 160 8mb cache (main), Win XP PRO sp2 (up to date), direct X 9.0c, QT 6.5

    Nothing but basics installed (all required drivers & software to export from AE6.5 & Avid Xpress Pro Codecs)

    I have also tried to render without changing windows boot.ini (to enable 3 gb ram).
    I have done some research and i could only find that it has something to do with codecs. (possibly). Tried to render with and without OPEN GL on.
    I have also tried to render with (QT) Animation, None and Microcosm & Video for windows to no avail. I have also redone my OS on my machines to make sure that it isnt a prob with the OS etc. It worked before, perhaps im missing a step somewhere .. PLEASE HELP.

    In my project i have mov files (AVID codec), JPEGS, and some MP3’s , all files play fine inside of AE (ram preview etc), on both machines,

    After Effects error: an unspecified AVI or DirectShow error occurred. (1)
    (53 :: 33)

    Any help would be appriciated thanks

    Kevin Merker replied 20 years, 5 months ago 5 Members · 8 Replies
  • 8 Replies
  • Kevin Merker

    December 7, 2005 at 3:02 am

    Also another note, It does not crash on the same frame , nor have problems with ram usage, Hard drives are also NEW Fresh drives (swapped out after we got the error the first time). Source footage is put on board on one machine (seperate drive (IDE) and on external HDD (FW/USB2.0) , both 16 mb cache drives.

  • Sean Cusson

    December 7, 2005 at 4:33 am

    Sometimes lowering your memory cache in After Effects can help. When I get that same error I lower my cache to 45% before rendering. It usually helps. Also, sometimes I’ll simply render out to a targa sequence, then if I get the crash, I can start AE again and continue the same render (making sure that Overwrite Files is turned off) from where the crash happened. At least then I don’t lose the time I spent rendering before the crash. Once the whole sequence is rendered, I bring it back into AE and then render to an AVI. These aren’t permanent fixes, just work arounds.

    Sean Cusson
    Q media design
    sean@qmediadesign.ca

  • Phil Biggs

    December 7, 2005 at 11:02 am

    I had this error when trying to render a sequence with MP3s. I converted them to WAVs using QT Pro and it seemed to work. Couldn’t tell you the science behind that and it was probably more a coincidence than methodical – but it might be worth a try seeing as though you’ve tried everything else.
    Phil

  • Kevin Merker

    December 7, 2005 at 1:25 pm

    Yea, I tried with wav’s and with removing audio all together, and i still recieve the same error, i cant believe that noone at adobe have emailed me back yet about this problem.

    Thanks for your help, up to this point its still not working.

  • Steve Roberts

    December 7, 2005 at 1:55 pm

    Have you entered the secret prefs by holding down the shift key when accessing the prefs? Hold it down until the dialog box appears. Try setting it to purge every 5 frames during Make Movie.

    Or … have you downloaded the latest DirectX drivers? (a guess)

    Or … if you’re on the latest Quicktime, have you tried downgrading to QT 6.5 or whatever?

    Steve

  • Kevin Merker

    December 7, 2005 at 2:20 pm

    i havent tried the secret prefs thing, ill give that a shot shortly, as far as direct x i have dx 9.0c and 9.0b .. also qt .. i gave qt7 a shot .. simply wouldnt work , so now i got 6.5. soemthing and 6.3.. hope this works thanks for the help guys

  • Matt Stalker

    December 7, 2005 at 3:22 pm

    Hi,

    I get this error sooner or later on almost every job I do that has audio. I don’t think it’s that uncommon since all the guys in my shop seem to get it. We get it during RAM previews and sometimes during renders. During RAM previews, flushing the cache seems to temporarily fix the problem. For rendering, we do as the above poster suggested: lower the number in the “Purge Every (x) frames” in the secret preferences.

    We don’t get this problem if there is no audio in the project. It seems like the audio is filling up the RAM and not being purged for some reason. Is that why a manual purge fixes the RAM preview and the purge every (x) frames fixes it for the renders? A question for the tech guys I guess…It is annoying and I’d love to see it fixed!

    Matt

    Matt Stalker
    Center City Film & Video
    mstalker@ccfv.com

  • Kevin Merker

    December 8, 2005 at 1:31 am

    Thanks Guys , it seemingly worked, i appriciate you guys inpute and time, THANKS again , the cow rox

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