Some quick likes and dislikes of editing a recent project with Premiere Pro CS6

Over the last 2 days I cut a short film on Premiere Pro CS6. It was shot on a Canon 5D and I had no time to convert the footage, so I figured Premiere Pro was the way to go because I wouldn't need to re-compress the footage.I used Plural Eyes to sync the footage to the external microphone, and it worked, though took some finessing, and some manual syncing and I would say it got about 75% of it.Then I started cutting and had all the crash issues from my earlier post on the NVIDIA GTX 285, but was able to switch to my NVIDIA QUADRO FX 48000 and mostly cleared up the issues. No more serious Error messages, and no more screen going black. Still some random crashes, but nothing too bad, that a quick restart wouldn't get running again.I was running the footage out of premiere pro through my DV deck to an external NTSC monitor, and it looked great.Now I edit in Apple Final Cut Pro 7 and AVID Media Composer, but have always preferred some things of Final Cut Pro. And there are some things about Premiere Pro that I like and some I don't.I don't like how you can only set a duration for your default transition in Premiere Pro, and you can't set up a favorites bin of effects either per project or within the system. I would always make a bin of favorites in Final Cut Pro with various lengths, and was quickly able to apply any transition I wanted.I also don't like how on a clip in the timeline that is not butted up to another clip, all transitions start at it's cut and can't be put center on the cut or ending at the cut. You have to extend the clip to make the transition go further than the cut. Now it is pretty easy if you select the cut first as you can just hit E to extend the clip to the playhead, even if a transition is already on it. And I have set command-D to apply the default transition, so I can easily extend clips and apply the default transition with one hand (awesome), but I still want a bin of my favorite effects, and if not in the effects browser, let me do them in the project like I can do with AVID.The integration with Adobe After Effects is a thing of beauty. Just being able to make changes so quickly is totally awesome. Once you have either imported a After Effects Sequence or sent files to one from Premiere, you just save changes in AE and they show up in Premiere, and you render in Premiere. AWESOME! This makes Premiere the best program for graphics intensive stuff bar none. I think Premiere Pro should become the premiere program for Direct Response because of this alone!When Snapping is turned on, why does the cut tool not snap to the playhead. Now it seems to still cut…

Premiere Pro CS6 having some serious issues with NVIDIA GTX 285

I started on a job today shot on a 5D and didn't have time to convert to ProRES, so I decided to cut it in Premiere Pro CS6 to save conversion time, plus since I have a compatible PluralEyes to sync off camera audio. It took a bit of time to do the sync, but after I watched my footage and then began cutting, but Premiere Pro could not have been more unstable. I crashed over and over, and was losing time and work. So much that I tried exporting to quicktime, but it was just going to take too long to render the timeline so I could edit.I found this thread on the Adobe Forums, and found my exact problem. I'm on a MacPro 4,1, Lion 10.7.4, CS6.0.1, 32GB RAM, GTX 285 with the latest nVidia and CUDA drivers.  I am seeing 2 primary issues: Lots of Serious Error crashes.  This happens without any noticeable pattern - sometimes with the title tool, trim monitor, or simply just scrubbing the timeline.  It seems to happen more frequently with Dynamic Links in the timeline.  Also, I believe it is happening more often (or maybe exclusively)  with the MPE GPU option enabled.  I think in Software Only mode, it may not be present, although further testing required. Also, I am having an issue where Pr will display black only in the source and program monitors, unless I click around the timeline and will get flashes of images.  This is remedied by changing over to Software Only for the MPE.  It seems to be worse if Safari is running.I was having the same issues exactly, and have the same system setup, but with only 24 GB of RAM, and am running Mountain Lion 10.8.0. I kept having to trash my prefs which worked for about 5 minutes before I crashed again.So I decided to remove the GTC285 and put in my QUADRO FX 4800. It is old and slow, but still pretty decent. I installed it about 2 hours ago, and Premiere Pro has been rock solid afterwards.This shows it is either an NVIDIA driver or CUDA issue, or something in the Premiere Code with the GTX 285, as with the QUADRO FX 4800 it is running like a dream.Adobe and NVIDIA need to fix this fast, because this is a major issue. If it was not for me having a spare video card I would have been SOL, as I have to finish this project and fast!UPDATE: Had one crash after 3 and a half hours, but I have been saving now, back to the old paranoid saving all the time. Still unbelievable the difference with the different video card!UPDATE AGAIN: And crashed again! OK, so not rock solid, but still much better than it was with the GTX 285.

Biscardi Creative FCP to CS6 Part 3

Biscardi Creative has posted part 3 of it's switch to CS6 from Final Cut Pro 7. A good read with interesting points.•Because of Native editing, they their render time is basically down to realtime render, so a 30 minute show has around a 30 minute render! That is a huge change!•It requires more setup before hand, and it is smart to organize everything before import.•Still using FCP 7 for videotape ingest!•Use Davinci Resolve for grading, though it does not support all the files that Premiere Pro does, so a flattened ProRes Quicktime file is created from final timeline and use resolve's scene detect tool!There is of course more, and this is a must read for switchers!

Larry Jordan on Adobe Prelude

Larry Jordan has an excellent article on the new Adobe Prelude CS6 for ingesting and logging footage.I knew it was for logging and even cutting a rough assembly, but didn't realize it could export to either Premiere Pro or Final Cut Pro 7. Very cool.And it sounds like the biggest issue is the lack of ProRES presets for Media Encorder, which I always found odd, but not hard to create for oneself.Larry also offers a complete 2 hour tutorial on how to use Prelude at his site.

Trouble opening a current Premiere Pro CS5.5 sequence in Premiere Pro CS6

I have posted the following to the Adobe Forums and hope to get a response soon:I am trying to open my current Premiere Pro CS 5.5 project within Premiere Pro CS6, but am getting the following error message:The preset used by one or more sequences requires third party components that could not be located.This was a project that was imported from Final Cut Pro 7 originally, but the only 3rd party stuff used in it are Magic Bullet Suite plug ins and I have already installed them all.I can't even see if this project has CUDA acceleration anymore, as it is set to Custom Sequence and greyed out.Any ideas what I can do?