(Page 1 of 1 pages for this article )

Filed under: GentryMedia Sister Sites •ProVideo Coalition •

Kicking the tires of After Effects CS 5.5 p.1

With the upcoming release of After Effects CS5.5, I thought we would take a look at the big updates, the the minor updates and everything in between.  In this one, I’m going to start out basic…...really basic!

O.K.  When I said minor, we’re really going to start small, but it’s normally the small things that make you want to put your foot through your monitor.  I just installed CS5.5 yesterday morning and, of course, like an excited kid at Christmas, I immediately launched it and sat in awe athow how it really didn’t look any different than CS5.  I’m joking about that, obviously, as the first thing I wanted to do when I launched After Effects was find a clip on my desktop to import to start tinkering with the new features.  Now, one of my BIGGEST annoyances with AE CS5 (on Mac) is that I have to press CMD+CTL+H to hide After Effects.  WHY DOES ADOBE HAVE TO MAKE THINGS DIFFERENT THAN EVERY OTHER MAC APPLICATION ON THE PLANET BY ADDING “CTL” TO THE MIX?  As you can tell, it’s just generally annoying, as CMD+H as become muscle memory for just about every Mac user on the planet.  Well, Adobe has changed this, thank God!  Now, to hide After Effects, simply press CMD+H, just like on (most) every other Mac application.

Well, the only problem now is that I must unlearn what I have learned, and remove “CTL” from my memory banks!  Like I said, we’re starting small, but it’s the small tweaks that add the seconds and minutes back to your day.

Kevin P McAuliffe is a Senior Editor at MIJO, in Toronto, Canada.  As always, you can send him an .(JavaScript must be enabled to view this email address) or follow him on Twitter @ http://www.twitter.com/kpmcauliffe .

FTC Disclosure: I have not been offered any consideration or compensation from Adobe for the review/editorial of this product(s).

(Page 1 of 1 pages for this article )

                   

 

The Best of Stunning Good Looks Art Adams | 08/30 A directory of my best articles, sorted by topic. This entry is a guide to my best articles, sorted by topic. Enjoy!

10 Final Cut Pro things FCP editors might be missing in Adobe Premiere Pro CS6 Scott Simmons | 05/11 These are a few of the things that I found myself searching for as I’ve been moving over to Premiere Pro CS6 as a FCP 7 replacement Adobe is making a big play for Final Cut Pro users with their CS6 release of Premiere Pro. It’s vastly improved over the Premiere Pro of old and is a lot like Final…

After Effects Apprentice Free Video: Working with Nested 3D Compositions Chris and Trish Meyer | 05/07 How you can be two places at once inside After Effects As we mentioned awhile back, we’ve been busy the past year and a half creating an extensive, multi-course video training…

---

You must be registered to comment. This is an effort to reduce spam. Please REGISTER HERE.

I still get confused about com+H when switching between Mac and PC—Com+H hides text selections, etc in the Comp window.

On the Mac I moved away from Hiding so much and often used option-click when switching to another app, or used Expose to peak, or Com+drag on a background window titlebar to see underneath it.

Posted by .(JavaScript must be enabled to view this email address)  on  04/28  at  09:39 AM

---

I also was able to do some early testing of CS 5.5.

I was really impressed with the warp stabilizer.  Its incredible in certain instances what it can do.

I was also ecstatic for the addition of timecode support.  That is, until I tested it.
Timecode came in great, and worked well through After Effects, and even in Premiere.  Its when you try to take a 23.976 render outside of adobe’s world that the problems arise.

When you take your render to Final Cut, Quicktime, or even the AJA Utilities the timecode is totally wrong, and is a 30 base timecode.  There are still 24 frames in the second, but the timecode goes up to 29 and skips frames, making it totally inaccurate.  This is a problem with CS5 as well, but I was hoping it would have been fixed.  Lets make sure Adobe knows about this problem!

Posted by .(JavaScript must be enabled to view this email address)  on  04/28  at  11:02 AM

---

Name:

Email:

Location:

URL:

Smileys

Remember my personal information

Notify me of follow-up comments?

Submit the word you see below: