When animating Illustrator layers in a 4K comp, they sometimes get cut off in weird ways - as if there's a mask there that shouldn't be - and this bug is reflected in the full render as well as the preview. Setting the resolution to half (1080P) or lower displays and renders the image properly. Purging memory/cache, switching GPUs, restarting, working locally only, and trying other machines has not worked. This bug is also present when rendering at full resolution through Media Encoder. My main system is running Windows 10 Pro with a GTX 780 as my display card and 2 1080tis, an i7 5820K, 16 GB of ram, a 500 GB SSD as my system drive, on a Gigabyte GA-X99P-SLI board and the latest version of After Effects (15.1.0); my graphics drivers are up to date, and I've tried rolling back 2 updates with no luck. Converting to shape layers is not an option because rigging has already been done, and some of the layers would cause After Effects to slow down greatly because of their complexity.

I'm not a huge fan of using the timeline in such intensive way as it is right now as it can get so cluttered with all the twirled open settings. I would rather prefer having dedicated panels for all the individual tasks.

So that we would have a transform panel(much like the transform effect) for altering so settings, a panel for adjusting and animating shape layers/masks, a text panel to add and adjust all those text effects, .....
As soon as those settings are altered the parameter becomes exposed in the timeline and there you could just adjust the timing and interpolation turning the timeline into a dopesheet.
This way the timeline would become cleaner and more easy to navigate. Cinema4d and all the other (node based) compositors use this approach and I much prever working in their timelines.

AFX would make a step towards being more user friendly in my eyes closing the gap to the Node based Compositors ;-)

We just updated two of our Mac Pros to the latest AE 15.1 and it is having problems importing some of our media. These are 1080p pro-res 422 .mov files.

Error is: Source file has no importable streams. Please check that it is a valid video/audio file. (86 :: 1)

If we go back one version of AE the files open fine again, so there is something changing with this update that breaks support for our QT Pro-Res footage, as it is the only variable changing on the system. This issue also occurred when we tested it on an older (2008) mac pro

Downgrading to 15.0.1 allows us to continue working with the media.

This is also occurring in Premiere so it seems to be an issue across the Adobe suite updates.

This is a bug report (although this web site makes it infuriatingly unclear if this is where bug reports go).

I am seeing behavior in the new version in which projects that contain PNG sequences seem to lose those sequences, giving a cant open dialog for every g..d... piece of media. I can cause the error by simply tabbing to another app and then back into AE. Note that projects open fine with all media and if you dismiss these multiple warning dialogs, everything works fine (of course for some projects, that can be hundreds of dialogs).The error seems to disappear if you turn off Auto Footage Reload (hey, who needs features anyway?).

Windows 10 Fall Creators Up to date 256GB Ram All SSD or m.2 Nvida 2 Titan X Pascals 2 1080's.

The user interface times out in Windows and offers up a "Not Responding" very quickly. The timeout seems to have shortened considerably in CC2018.

There should be a way to run the message queue both from script and from plugins so that clicking on the AE windows doesn't immediately make them stop responding and so that progress can accurately be reported to the user.

I have written this script which highlights the problem. Playing around with various values for 'totalTime' and 'numIterations' really shows off the problem and I have something that seems to work ok as long as updates are less than five seconds apart and the user doesn't click on any AE windows. It's a total hack though to call window.update() once per number of elapsed seconds though...

script "Demo: Progress Bar"

strict on

(function() { try
{
var resource =
"palette {" +
"alignChildren: 'fill'," +
"panel: Panel {" +
"orientation: 'column'," +
"alignment: ['fill', 'fill']," +
"label: StaticText { text: 'Some text.', alignment: ['fill', 'center'], characters: 20, }," +
"progress: Progressbar { value: 0, alignment: ['fill', 'center'], }," +
"}," +
"}";
var win = new Window(resource);
var panel = win.panel;
var label = panel.label;
var progress = panel.progress;
win.layout.resize();
win.show();

var totalTime = 25.1; // in seconds
var numIterations = 6;
var sleepTime = (totalTime * 1000) / numIterations; // sleep in milliseconds
win.text = numIterations + " iterations at " + (sleepTime/1000).toFixed(0) + "s each.";

var then = Date.now();

for (var i = 0; i < numIterations + 1; ++i) {
    if (i < numIterations)
        label.text = "Iteration " + (i + 1);
    else
        label.text = "Done!";
    progress.value = (100 * i) / numIterations;

    var now = Date.now();
    var elapsedTime = (now - then) / 1000;
    var numUpdates = elapsedTime + 2;
    //$.writeln(numUpdates + " updates.");
    for (var t = 0; t < numUpdates; ++t) {
        win.update();
    }
    then = now;

    $.sleep(sleepTime);
}

$.writeln("done.");
$.sleep(250);
win.close();
win = null;

}

catch (error)
{
var str = error.message + "\n\n"
+ "Exception: " + error.name + "\n"
+ "File Name: " + File(error.fileName).fsName + "\n"
+ "Line: " + error.line + "\n";
alert(str);
}
})();