Forum Replies Created

Page 1 of 2
  • Yeah. I’ve seen it before hidden way down in the system.
    Here:
    (Mac OS) /Users/USERNAME/Library/Preferences/Adobe/After Effects/10.0 (or 11.0 for CS6)

    but I remember that it wasn’t an .ars file there. Plus I think the problem we had is that it wasn’t ‘moveable’ from down in there. (Todd K. would know that).

    When you save it out from the Render Settings dialog box, you know that you have the right file and you know where you put that file.

    -dl

  • they are .ars files.

    If you want to save a render-settings template for use on another system, you can click the Save All button in the Render Settings Templates dialog box before you close it (or, reopen the dialog box later by choosing Edit > Templates > Render Settings). Save the file in an appropriate location on your hard disk, such as in the After Effects application folder. All the currently loaded render settings are saved in a file with the .ars extension. Then, copy this file to the disk of the other system. When you start After Effects on that system, choose Edit > Templates > Render Settings, click the Load button, and select the new .ars file to load the settings you saved.

    output modules are .aom files.

    -dl

  • Dustin Lawhorn

    August 8, 2013 at 8:58 pm in reply to: Convert to Editable Text Problem

    I also thought that it looks like a Faux Bold being added. But since fonts drive me a little batty, I ran the fonts through What the font DOT com and this is what I got.

    “Your WhatTheFont results:
    There are 5 matches for the image you uploaded.

    Neue Haas Grotesk Std Text 75 Bold
    from Linotype Neue Haas Grotesk

    Neue Haas Grotesk Pro Text 75 Bold
    from Linotype Neue Haas Grotesk

    Europa Gro SB-Dem Bol
    from Scangraphic Digital Type Collection Europa Grotesk SB

    Nimbus Sans Novus D Bold
    from URW++ Nimbus Sans Novus

    Nimbus Sans Novus Bold
    from URW++ Nimbus Sans Novus

    Unfortunately, I didn’t really learn much from that. I’ve seen that Haas Grotesk showing up as matching one of the Helvetica variations on my main graphics system.

    I’d like to know what you figure out though. Sorry, that I wasn’t much help.

    -dl

  • Dustin Lawhorn

    August 8, 2013 at 5:08 pm in reply to: Convert to Editable Text Problem

    I would guess that the stroke width is on when it should be off (set to 0). as for the E and A spacing you may just have to change the tracking between those letters.

    -dl

  • Dustin Lawhorn

    August 8, 2013 at 4:33 pm in reply to: keyframe problem

    Hmmm. It could be jutter? check out the thread here: https://forums.creativecow.net/thread/2/963872

    -dl

  • Dustin Lawhorn

    August 8, 2013 at 2:01 pm in reply to: keyframe problem

    Stig,

    Just for clarification, are you seeing this problem on the Rendered file (final file) or during the RAM Preview or just in the Comp viewer?

    -dl

  • Ivan,
    Sorry for the late reply. I missed your reply somehow. But, here goes:

    (Keep in mind that this workflow assumes that I’ve gone into the original “render settings” and changed the Time Span to “Work area only.”)

    I usually “duplicate with file name” in the Render Queue*. Then, go into the comp and see if I can remedy the problem. Then, I try to render out the bad frame by making that one frame the “work area.’ That will force the new render to have the same name with a 001 or 01 addition to it. Check that frame out after it renders. Now, just lose the extra digits and add to the folder.

    If the problem is more than one frame (and it WILL be), I’ve just taken the first steps in the problem-solving sequence that I usually follow. However, getting that one frame to render out correctly just saved me minutes (and sometimes hours) of figuring out what is going on with the others that are dropping. Besides, it’s always quicker rendering out 1 frame than rendering out 120 of them.

    [* = I know it’s a little weird that I “duplicate” before problem solving; however, AE renders don’t really look at the comp until I hit the render button.]

    As for the DPX part of your question, I tend to stick with the legacy formats for Image Sequence workflows right now: PNG, TIFF, JPEG (for previews and rough edits only), and PSDs. I really don’t have a reason for that-I just know that older machines will be more likely to “understand” those older formats?

    -dl

  • [Dave LaRonde] “There just isn’t any convenient, automated way to do 40-some-odd clips.”

    Now, THAT should be a feature request!

    -dl

  • [Jeff Rouric] “I’ll try the image sequence thing, see how that affects the time. Once they’re images, how do you make them into a movie? Won’t it have to render them all back into a movie anyway?

    Thank god this has no sound.”

    It should not change the time of your timeline. Basically, each frame becomes an image file with an automatic incremental number. The image files all occupy a folder with whatever name you gave it in the Render Queue. i.e. “GroovySloMoVideo_0001.png”, “GroovySloMoVideo_0002.png” and so on…

    Yes, you would eventually be rendering all of those back into a video file. But it’s still faster and safer to use Image Sequences when dealing with these really serious keying projects. Although this isn’t the best explanation of this topic it’s a quick enough read to give you a sense of why it’s better: https://www.captaingraphics.net/blog/item/33-image-sequence-vs-movie-what-should-i-render
    I’m not associated with that site or anything.

    I’ve had many a render fail when going out to a video file directly that wasted hours of rendering time. When you go out to image files for each frame, you can see exactly which frame stopped the render. That makes problem-solving your project so much easier!

    Another upside of dealing with Image Sequences is they are Render Farm friendly and you never know when you can get another computer to render stuff while you’re working on another part of the video… From experience I can tell you that setting up render farms with Adobe is not as painful as setting up render farms for Blender.

    -dl

  • it’s the quicktime h.264 part of the conversion that is taking all of that time. Export as an image sequence. It will be lot faster and then take those image sequences later and put them into a quicktime h.264. Another advantage to going out to image sequences is that when you get a bad frame you only lose the bad frame. If you’re going out to a video file, you’ll get a failed render and no video for all of that rendering time.

    -dl

Page 1 of 2

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