Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects End Credits text crawl

  • End Credits text crawl

    Posted by Christian Neil on January 10, 2008 at 3:55 pm

    I’m positively stumped about a problem that I’m having with a 3 minute end credit sequence I’ve created in AE 7.0. Specifically, when I burn the DVD (using Nerovision Express), the credits roll fine for the first 30 seconds, and then the video starts to jump (similar to when Media player has playback problems when the computer’s out of RAM). The music plays fine, but the text has this problem no matter what I do.

    I figured that perhaps the problem was that AE was having to do too much math when figuring the vectoring for the text, and tried creating the credits as a bitmap in photoshop and animating the bitmap instead of having the credits run as vector objects, but I’m having the same problem. I even tried doing the same animation directly in Premiere Pro 2.0, and it had the same problem.

    I am positively stumped on this, and must resolve this in less than a week to send to SXSW.

    Anyone else have a problem with this? Any wisdom that can be offered would be most appreciated.

    Steve Roberts replied 18 years, 4 months ago 2 Members · 7 Replies
  • 7 Replies
  • Steve Roberts

    January 10, 2008 at 4:10 pm

    I don’t think the problem is the vector-calculation you described.

    We have to isolate causes and apps here. Do the credits play fine when you play them as a rendered Quicktime movie straight out of AE? Have you tried rendering them as a low-data rate movie out of AE for testing?

  • Christian Neil

    January 10, 2008 at 5:19 pm

    The fact that I have the same problem with animating a PSD object of the same material leads me to concur that it’s not a vector calculation issue.

    I’m rendering as an uncompressed avi file, and haven’t tried rendering anything at a lower resolution. I might try that this evening and see if it makes a difference.

    Is there an advantage to rendering as a Quicktime file? I work mostly on PCs (by circumstances, not choice), and usually work with avi files. I’ve done similar credits before, albeit in shorter format, and have never had this problem before.

  • Steve Roberts

    January 10, 2008 at 5:30 pm

    It’s a good idea to render uncompressed before compressing to MPEG-2 for DVD. However, we won’t be able to test the playback of that uncompressed movie, since it’s too big to play back smoothly. That’s normal — uncompressed movies are meant to be sent between apps, not played back.

    So. To make sure that the movie is fine before going to the DVD app (or MPEG-2 compressor), I recommend you take the uncompressed AVI and make a WMV or something out of it. Just to check playback. It’s not perfect, but it’ll do.

    Naah, uncompressed AVIs are great for passing movies between apps. I just work on Mac, so I use Quicktime.

    Anyway, make sure the movie is fine before MPEG-2 compression, and if it is, the problem lies in the apps following it in the workflow. Let us know.

  • Christian Neil

    January 10, 2008 at 5:51 pm

    I haven’t been compressing down before burning the disk…I’ve just been burning the uncompressed avi file, and that might be the problem. Nerovision Express is a very low-end product, and that could be the problem also, particularly with a large file. So far, everything I’ve burned with Nero works fine, but nothing feature length.

    I will try what you suggest and report on the results.

    Thanks for the help!

    Chris

  • Steve Roberts

    January 10, 2008 at 6:05 pm

    Well, sometimes DVD authoring apps compress the file as part of the authoring process, so in and of itself, going straight from uncompressed movie to DVD authoring app shouldn’t be a problem. The MPEG-2 compression had to have taken place at some point in the process, or the DVD wouldn’t have played at all.

    We (here) just compress as a separate step to allow more control over the process.

    Anyway, keep us apprised.

  • Christian Neil

    January 15, 2008 at 5:38 pm

    We finally managed to solve the problem. One of my editors encoded in Canopis and used Encore for the authoring (both programs that I have yet to learn), and that seemed to solve the problem.

    I just wanted to report back in and say the problem is solved, and I greatly appreciate the help.

    Now on to deal with the next problem, which I’m sure is scheduled immediately. 🙂

  • Steve Roberts

    January 15, 2008 at 5:41 pm

    Thanks for getting back to us. It always helps to hear solutions.

    Good luck on the next one, coming in 5 … 4… 3 … 🙂

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