AFTEREFFECTS

News, Information & Workflows from Users & the Adobe Ae Team

CC 2014.0.1 updates for After Effects, Prelude, and SpeedGrade fixes issue with trial period

We have released updates for the CC 2014 versions of After Effects, Prelude, and SpeedGrade: After Effects CC 2014.0.1 (13.0.1), Prelude CC 2014.0.1 (3.0.1), and SpeedGrade CC 2014.0.1 (8.0.1). These updates contain only one fix for a problem with the trial period in these applications.

When you launch the CC 2014.0.1 version of the applications as a trial, it will reset the trial period if you had used the trial of the previous (CC) version of the applications. This is the only change in these updates.

warning “RAM Preview needs 2 or more frames” after scrubbing audio in After Effects CC 2014 (13.0)

The After Effects team are investigating a bug in After Effects CC 2104 (13.0) where a memory leak occurs while scrubbing audio (holding down the CTRL or Command key while scrubbing). This memory leak can eventually consume all free RAM, which can lead to the warning message “After Effects error: RAM Preview needs 2 or more frames to playback” when you try to initiate a RAM preview.

While we investigate this problem, you can avoid the bug and memory leak by not scrubbing with audio. When the problem occurs you can resolve it by closing and restarting After Effects.

Using the Edit > Purge commands do not affect this problem, as the leaked memory is not tracked by the image cache. Leaked memory is memory that an application consumes but does not return to the operating system as free memory when it is finished with it, preventing re-use of that memory. In Activity Monitor on Mac OS or Task Manager on Windows, you can track the amount of free memory on your system and memory in use by After Effects.

The “RAM Preview needs 2 or more frames” warning means that After Effects can not build a RAM Preview because it can’t build a second frame.This may because your composition or work area is only one frame long, or as in this case it can happen when there is not enough free RAM to build the second frame. High resolution compositions and 16bpc or 32bpc color have higher memory requirements and therefore may experience this warning more frequently.

To discuss this bug, please post in this thread in the After Effects User to User forum.

Adobe Media Encoder CC 2014.0.1 (8.0.1) update: bug fixes, H.264 at 4K, new YouTube presets, and more

Today, the Adobe Media Encoder CC 2014.0.1 (8.0.1) update was released. This version provides important fixes and enhancements and is recommended for all users.

This update addresses several bugs, adds support for 4K in H.264, new and simplified presets for YouTube, and other features. Read the details below in the “what’s new” and “fixed bugs” sections.

Ideally, you should install the updates automatically through the Creative Cloud desktop application or by choosing Help > Updates, but you can also directly download the update packages from the download page for Mac OS or Windows.

For information about updates for other Adobe professional video applications, see this page.

If you want to ask questions about these new and changed features, come on over to the Adobe Media Encoder user-to-user forum. If you’d like to submit feature requests (or bug reports), you can do so here.


what’s new


  • Improved DCP color calibration: Improved color calibration from QuVIS for BT709 workflows. This will result in improvements in source color matching, color saturation, and increased detail in darker areas.
  • Moved user preferences and presets to new location: Preference and preset files are now located in your user profile’s Documents folder, instead of a folder hidden by the operating system. All preferences and presets from Adobe Media Encoder CC 2014 (8.0) will be automatically moved to the new location. Premiere Pro CC 2014 and Prelude CC 2014 will continue to see and make available your encoding presets.
  • 4K support in H.264: A new 5.2 Level choice for H.264 provides full support for 4K frame sizes and frame rates.
  • New YouTube encoding presets: The encoding presets for YouTube have been completely rebuilt and simplified. The changes include:
    • A new preset for 4K resolution (3840 x 2160).
    • All 360p presets have been removed.
    • The Frame Rate and TV Standard settings on all YouTube presets now use Match Source, so only a single preset is required for each frame size.
    • The Target and Max bitrate of the new presets are higher to better align to YouTube’s recommended settings for High Quality uploads.
    • 1-pass instead of 2-pass encoding, which reduces encoding times without a significant loss in quality. Note that YouTube automatically re‐encodes all uploaded videos for optimized streaming, regardless of source codec. YouTube recommends H.264, which offers both high quality bitrates and reduced upload times.
    • The new presets are:
      • YouTube 2160p 4K (40 Mbps)
      • YouTube 1080p HD (16 Mbps)
      • YouTube 720p HD (16 Mbps)
      • YouTube 480p SD Wide (8 Mbps)
      • YouTube 480p SD (8 Mbps)

fixed bugs


  • 25fps XDCAMEX files were 1 frame short when smart rendering was in use. This is fixed.
  • Complex video assets produced blurry image every 1 second when encoded into H.264. This is fixed.
  • XAVC Intra 2K or 4K encoding without including audio failed. “Error Compiling movie. Unknown error.” This is fixed.
  • Media Pending frames did not go away after an MPEG source had been indexed. This is fixed.
  • Error “[..\..\src\Command_FormatChanged.cpp93]” appeared when a preset was deleted. This is fixed.
  • Export failures, assert and error messages occurred when selecting “Match Sequence Settings” for a 120fps GoPro file.  This is fixed.
  • Transcoding DPX files to XAVC at UHD resolution failed.  This is fixed.
  • Exporting a merged clip from Premiere Pro would result in silent audio or a failed encode. This is fixed.
  • Encoding a 4K clip with text or timecode overlay effects using OpenCL Mercury Playback Engine acceleration on Mac OS resulted in bad frames. This is fixed.

workaround for slow performance and poor resolution with RED R3D files in After Effects CC 2014 (13.0)

The After Effects team are investigating a bug in After Effects CC 2104 (13.0) where RED (.R3D) files are very slow and the image resolution is poor, about 1/8 sampling.

The following workaround has been reported to solve the problems in some cases:

1. Save the project.
2. Choose Edit > Purge > All Memory & Disk Cache.

Please post whether or not this workaround helped you on this thread in the After Effects User to User forums.

removal of FLV and F4V export features from Adobe Media Encoder, After Effects, and Premiere Pro

After Effects CC 2014 (13.0), Premiere Pro CC 2014 (8.0), and Adobe Media Encoder CC 2014 (8.0) do not include exporters for creating FLV and F4V files.

You can still import videos in FLV and F4V formats into After Effects and Adobe Media Encoder. You can still import videos in the F4V format into Premiere Pro.

If you want to create a video to play in Flash Player, then you should generally be using H.264 (.mp4), not the obsolete FLV or F4V formats. This has been the recommendation from the Adobe Flash team for quite some time already (as far back as Flash Player 9).

We removed the exporters for FLV and F4V files from the Adobe video applications (Adobe Media Encoder, After Effects, and Premiere Pro) because maintaining these obsolete exporters was a large amount of work, and we could better spend that effort on developing new features and fixing bugs in areas that are used by more people.

We are still committed to creating video files that play well in Flash Player, and that is why we are focusing our efforts on the H.264 (.mp4) exporter, which is what is currently recommended by the Adobe Flash team.

If you do still have a need to create FLV or F4V files for some legacy workflows, then we recommend that you keep the previous versions—Adobe Media Encoder CC (7.2) and After Effects CC (12.2.1)–installed alongside the current versions. Then, whenever you need to transcode or export a file in one of these legacy formats, you can just start the previous version of the application for this specific purpose.