Adobe Community : All Content - All Communities

A lot of issues with Premiere Pro CC

forums_noreply@adobe.com — Mon, 24 Jun 2013 16:48:44 GMT

Just like with CS 6 it was expected that there would be a lot of problems out of the gate, but why so many? If I create a new sequence the playback is fine, when I switch back to a previous sequence with all the footage linked, it bugs out and there is no playback. I have to restart the program every time I want to edit in a different timeline. I would adobe would fix some of these issues before launching a new product and using us as their guinea pigs.

I remember when CS 6 wouldn't save a project. Talk about a show stopper.

Does anyone else feel like this?

Import Pro Tools AAF into Premiere?

forums_noreply@adobe.com — Fri, 01 Feb 2013 18:32:18 GMT

Great, it is east to export OMF's or AAF's from Premiere for Pro Tools, fantastic, and there is tons of information on the web about it, but there is zero relivant information about exporting an AAF from Pro Tools for Premiere. Sometimes it works, sometimes it doesnt, premiere will recoignize half of the content and then place diagonal grey lines through the clips. The original clips will be import, but not synced. The Premiere to AVID and vice versa workflow is not what it seems. I miss when automatic duck actually worked before it became integrated into premiere and stopped working.

Ultimate question? What settings to export from ProTools so that Premiere can import an AAF?

Premiere Pro CC 7.2.1 Crashing and Corrupting on Mac

forums_noreply@adobe.com — Sun, 19 Jan 2014 20:04:31 GMT

This started shortly after updating from 7.1, to 7.2, to 7.2.1 almost back to back. I cleaned out everything and re-installed, updated all CUDA drivers, and crashed through the forum without finding a specific cure for my problem. I use Digital Rebellion Crash Analyzer to tell me what is happening and this is what it said for the past 3 crashes.

1st Time.

User Interface Crash

Relevant Line = 1 com.adobe.UIFramework.framework 0x00000001048184ef UIF::TimeBarControlImpl::Enable(bool) + 79

2nd Time.

Relevant Line = 0 com.adobe.HandlerTimeline.framework 0x000000010bdd60f6 HandlerTimeline::TrackViewArea::SetVisibleBaseTime(dvamediatypes::TickTime const&, double const&, bool) + 54

3rd Time.

Relevant Line = 1 com.adobe.UIFramework.framework 0x00000001048184ef UIF::TimeBarControlImpl::Enable(bool) + 79

I'm hoping someone with a Mac / Premiere background will be able to link these 3 crashes to one cause, but they would only solve half of my problem.

I believe Auto Save was corrupting my project Save files for the past 5 days. I had Autosave set to 20 minute intervals before and after Saving and closing my project I was unable to open it again. Even after cleaning out the media cache and resetting Premiere (re-installing) back to defaults the projects themselves would not open without freezing during loading of media. I was forced to create a new project and reimport the previous one to advance in my editing process. After disabling auto-save, I can now save a project and re-open it safely (most of the time), but it doesn't help when the program itself crashes.

Any and all help would be appreciated.

Thanks,

Corn

Computer Specs: 2012 MacBook Pro (non-retina). Processor 2.7 GHz Intel Core i7 . Memory 16 GB 1600 MHz DDR3 . Graphics NVIDIA GeForce GT 650M 1024 MB . Software OS X 10.8.5 (12F45). CUDA Driver Version 5.5.28 (Updated 10 hours ago).

Red Frames in Premiere 7.2.1 Mac

forums_noreply@adobe.com — Fri, 03 Jan 2014 21:54:46 GMT

I updated to 7.1 and took a look at a project from last week and one of the sequences was riddled with RED video throughout the Quicktime Pro Res HQ video that was in the sequence. I then read this post about 7.2.1 fixing this issue related to quicktime files, but I am having the same problem with 7.2.1 (http://forums.adobe.com/message/5918797) <-- OLD THREAD.

I tried disabling/ enabling, OpenCL, CUDA, Software Only, Rendering with Media Encode, cleaning cache, deleting render files, re-installing, etc. The video plays fine when I preview it outside of Premiere Pro CC. Clearly this issue is still there and I wish I wouldn't have updated to 7.1 in the first place.

Anyone have any solutions?

Model Name:	MacBook Pro
Model Identifier:	MacBookPro9,1
Processor Name:	Intel Core i7
Processor Speed:	2.7 GHz
Number of Processors:	1
Total Number of Cores:	4
L2 Cache (per Core):	256 KB
L3 Cache:	8 MB
Memory:	16 GB

Chipset Model:	NVIDIA GeForce GT 650M
Type:	GPU
Bus:	PCIe
PCIe Lane Width:	x8
VRAM (Total):	1024 MB
Vendor:	NVIDIA (0x10de)
Device ID:	0x0fd5
Revision ID:	0x00a2
ROM Revision:	3682
gMux Version:	1.9.23

OSX 10.8.5

Adobe Lightroom to Speedgrade CC

forums_noreply@adobe.com — Tue, 29 Oct 2013 18:03:40 GMT

Hmm.

How can I take a still that was already adjusted in lightroom and match it in Speedgrade? Since lightroom can now handle video I know a colorist who uses lightroom for his mock ups. How can I take his adjustments and make them mine? If I have to do it manually, then I'd rather go with Davinci .

Thanks

Premiere Pro CS6 for Broadcast ProRes HQ Frame rate issues

forums_noreply@adobe.com — Fri, 28 Dec 2012 23:34:03 GMT

I switched from Avid to work on a quick project with DSLR footage shot on the 5D Mark III at 29.97 psf which is not to be confused with 29.97i, a standard frame rate necessary for broadcast. So the commercial spot was cut together, I punched in the proper settings (the very same settings that work with Avid 6.0+ and Final Cut Pro 7), and hit export. When exporting either a Quicktime Animation or Pro Res file from Premiere Pro CS6, premiere creates a file with a faulty framerate, it comes out as 28.4 instead of 29.97. I thought I was going crazy, but no, there are tons of documented experiences with 23.94 being 20-something, and on an on. It seems as if Adobe did not do a good enough job with integrating the Pro Res codec into their software. The only way I could get around it was to export to something else (Blu-ray H.264 at 29.97), and then re-encode that file to Pro Res HQ with either compressor or adobe media encoder. The problem lies in exporting progressive footage as interlaced, it just completely screws up the frame rate. The worst bit is that, I need Pro Res HQ for the distribution house for the commercial spots, they require the ProRes HQ MOV at 29.97i and if anything is off, I get charged for it.

Does anyone else have problems with Adobe Premiere lacking on the professional end? Or similar experience with this problem?

Just do a search for pro res frame rate issue premiere and you will see a lot of other users with the same issue.

Thanks,

System Config:

Mac OSX 10.8.2

2.7GHz Intel Core i7 MacBook Pro 15" Mid 2012

NVIDIA GeForce GT 650M 1024MB

16GB 1600 MHZ DDR3

256GB SSD + 750GB SATA (no CD/DVD)

Premiere Pro CS6 (latest)

Premiere CS6 What to do with the Match Sequence Settings MPEG?

forums_noreply@adobe.com — Wed, 12 Dec 2012 18:33:02 GMT

Premiere does not seem to handle long exports, meaning, videos that are over an hour. The only way I can get an export with a decent turnaround is to export using the Match Sequence Settings tab. After the export I can preview the file, but I cannot convert it. How do I convert this 22GB file for youtube? H.264, etc, I have tried and failed. Even Adobe Media Composer exports it with audio but no video. What gives?