Hack your iMac!

Kanen Flowers found a way to beat Adobe to the punch by "hacking" Premiere Pro's OpenCL approved card list and adding the GPUs found in the latest (at least until June) iMacs.  So far Adobe has only allowed two GPUs found in the Macbook Pros to enjoy the wonders of hardware acceleration, but Flowers discovered simply adding the GPU model names of the ones found in the iMac to the list turned on hardware acceleration for iMac users.

I've actually tried the hack and found some glitches, especially with audio playback which caused crashes. While scrubbing the timeline, the audio would suddenly turn "cylony" and then the system would lock up and a kernel panic would ensue.  Since I reinstalled CS6 and never reengaged the hack, I haven't had those specific audio issues reoccur. Was it the hack or maybe just a funky install?  Who knows, but if you feel adventurous, give it a try.

Head over to Scruffy Thinking to find out more.

Bug Fixes for Premiere Pro CS6

Adobe has just updated Premiere Pro (along with After Effects) with a number of bug fixes and some added features.  I'm most interested in the OpenCL improvements they promise for the Macbook Pros (Thunderbolt models).  Adobe has yet to add the GPUs found in the latest iMacs to the OpenCL Mercury Playback Engine, but hopefully soon.

[Link]

No Underlining in After Effects?

Where's the Underline Button?

I'm late to the party on this one, but apparently you cannot underline text created in After Effects.  It's funny, but it's little things like this that really irritate me more than crashing apps.  Adobe has listed some workarounds but there not nearly as simple as a FREAKING UNDERLINE button!

You can find other ways to underline here.

CS6 Blues Part 3 - Missing Audio Filters

The filter you are wanting to use has exited the building.

So far my experience with Premiere Pro CS6 has been less than stellar with frequent crashes, including the absolutely worse kind - the dreaded kernel panic. One of the crashes I have experienced is dealing with audio.  I have a project that has some noticeable room tone present in the interview bites. My producer wanted me to remove the noise if possible, so I wanted to give Audition a try at it. When I attempted to send to Audition using the command from within the NLE, Premiere Pro crashed.  It did it on the two occasions I tried it, and I didn't feel like trying a third time.

As an alternative, I found the DeNoiser audio filter within Premiere Pro and gave it a try. The results were great.  But some time later, while scrubbing the timeline, Premiere Pro caused a kernel panic.  It was as if Adobe was hellbent on preventing me from removing noise from my audio!  Upon restarting the project, I received an error message that the filter was missing!  I never realized a plugin could just go offline without willfully deleting it. The filter is still present and available to use, but once I apply it to clips in this project, the error occurs.  Deleting the filter from the clips allows me to continue editing.

Searching the Adobe forums revealed my issue and the circumstances that can lead to such an error.  It turns out that if you imported from a Final Cut Pro XML file, which I did, this problem can occur.  Apparently if you recreate the project from scratch within Premiere Pro, the error will not occur.   So there appears to be an issue with the way Premiere Pro is interpreting the audio from within the Final Cut Pro XML file.

Ultimately this is going to be a problem for me because two of my main editing clients are producers who do their own rough cuts in Final Cut Pro.  So if I want to edit these projects in Premiere, I have to go the XML route.  Being able to send to Audition, or use the what-seems-to-be wonderful Denoiser filter, are features of Premiere Pro I'd like to have at my disposal.   I'll be keeping an eye on this forum thread to see if Adobe can offer a remedy.

For a workaround, I exported the audio I needed to be cleaned as an AIFF file and opened up in Audition.  I ran the noise remover, saved and imported the AIFF back in to the project and synced it to my timeline. I would prefer to send it to Audition and "round trip it" back in to Premiere Pro, but I can at least do it this way for the time being.

The thread to keep an eye on his here.

Where's My Stuff? - CS6 Blues Part 2

I'm knocking out the simplest, less frustrating issues first.  And this one has been fixed! When you download your apps from Creative Cloud, you will notice that the extra content, stuff I rarely use but stuff I want to be there because I'm paying for it, is missing from Encore and Premiere Pro.  A week after Creative Cloud was released, Adobe has finally provided links to download this material.

You can get yo grabby hands on it here.

CS6 Blues - Part 1

Okay, so nothing's been happening here for a while but I'm finally motivated to post again.  I have been trying out Adobe's CS6 suite of software and running in to a number of problems.  I'm going to try and document these issues over the next week or so.

Here's my first issue - Adobe Creative Cloud offers 20 gigs of cloud storage.  I've uploaded a file I edited that contains Dewolfe Music.  My client has a subscription to this service.  It's completely legit for us to use it.  But for whatever reason, Creative Cloud flags the file as containing copyrighted material.  But, unlike YouTube which usually allows your video to continue to be used with the usual link provided to purchase copyrighted music, Creative Cloud instead simply allows you to do NOTHING with your file.  You cannot play it back nor share it.  As it stands I cannot share my video work I've created with Adobe's software!

But searching through Adobe's forums reveas a very sweet thing when you're having issues - others who have the exact same problem!  Unfortunately no remedy as of yet and perhaps its as simple as Adobe not flipping the switch to turn on video sharing.  People have run in to this problem with absolutely no music used in their pieces, so I'm hoping we'll see this feature turned on in a few days.  However, the first post was from days ago with no response from Adobe, so that's slightly disconcerting.

Here's the link: Adobe Creative Cloud Forum