Premiere Pro CC 2014 multicam glitch 8.2.0(65) Build

I've looked and haven't seen anything posted like this, so if there is, I'm sorry! But I've just updated to the Premiere CC 2014 8.2.0 (65) Build and noticed that the multi-cam function is glitching out. I'm editing four, ProRes 422, 1920x1080 camera files and as long as I'm switching cameras in real-time, it's good, but if I move the CTI back on the timeline and try to start editing again, the program begins switching rapidly from one camera to the next. The only way to make it stop is to use the razor tool and make a cut on the footage, then proceed to edit in real-time. You can imagine how annoying this is during a 40min segment on a timeline! I've also noticed that my computer fan is more active than it was previously when using premiere. Anyone else experience this or have a fix?
Computer: MBP, 2.7GHz i7, 16gb 1600 MHz DDR3
Graphics: NVIDIA GeForce GT 650M 1024 MB
OS: Yosemite v. 10.10.1

Having the same issue, Premiere CC 2014 8.2.0 (65)
Multi cam gliche, need to turn Multi-cam off and on a few times for it to stop.
I also get red screen in my program window. and the software freezes for a few seconds.
Please fix this.
working with video
Type: MXF
Image Size: 1920 x 1080
Frame Rate: 29.97
Source Audio Format: 48000 Hz - 24 bit - 8 channels
Project Audio Format: 48000 Hz - 32 bit floating point - 8 channels
Total Duration: 00;00;02;12
Pixel Aspect Ratio: 1.0
MXF File details:
Wrapper type: MXF OP1a (type: SingleItem SinglePackage MultiTrack Stream Internal)
File generated by: Sony, Mem (1.00)
MPEG-2 422 Long-GOP
and
Type: MPEG Movie
File Size: 53.5 MB
Image Size: 1920 x 1080
Frame Rate: 29.97
Source Audio Format: 48000 Hz - 16 bit - Stereo
Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
Total Duration: 00;00;13;26
Pixel Aspect Ratio: 1.0
Computer
Processor 3.5 GHz 6-Core Intel Xeon E5
Graphics AMD FirePro D700 6144 MB
Memory 32 GB 1867 MHz DDR3 ECC
Software OS X 10.9.5 (13F34)

Similar Messages

Adobe Premiere Pro CC not opening an xml file created in Adobe Premiere Pro CC 2014

Hello,
I had created a project using Adobe Premiere CC 2014 which had some minor changes, which were going to be done by my boss, who uses Premiere Pro CC. However the project file of Adobe Premiere CC 2014 was not getting opened in Premiere Pro CC giving a message of type that as this file was created in a newer version of Premiere, it cannot be opened. After searching on this forum I found that we have to convert the Premiere Pro CC 2014 project file to XML file which can be then imported onto Premiere CC. So I created a XML file by selecting File-> Export -> Final Cut Pro XML and sent it to my boss. However even the xml file is not getting opened after being imported onto Premiere Pro CC giving an error of sorts, Cannot open the file since there is a problem with the codecs.
Have I done something wrong? Please guide me since I am a beginner to the Adobe environment and would very much appreciate any help.
Thank you.

Indeed..... but are they fully documented, includuing Adobe's implementation of Multicam?
Collapsing them should really be no more than a day or two of work for an Adobe engineer and a day of beta testing. Seriously. Lots of people want this - it only takes a few minutes with google to find people struggling with this exact problem. Premiere Pro Multicam --> Resolve.
Since we do a lot of multicam work it's something that's important to us.
Lots of other people never go near multicam, so I guess for them it's something they really don't care about.
I currently have > 22 hours of multicam sequences that need primary colour correction and follow on grading..... resolve would be the best choice by far.

Premiere pro cc 2014 crashing my system

I have a new Mac book pro (2014) 16 gbs ram.. everything is upgraded to max. downloaded the new premiere pro CC 2014. and it's crashing my system every time.
it takes about 4 mins. with the spinning ball. Then all the processes and plugins load in. Then it says "premiere pro couldn't find any capable video play modules. Please update your video display drivers
and start again" WHICH IS FREAKING IMPOSSIBLE SINCE I AM ON A MAC BOOK PRO. So sick and tired of companies not working out glitches in this crap. Could someone please help. I am so
angry and frustrated here.
Sean

Somewhat figured it out and extremely frustrated.
I created another new user with administrative privileges. When i did this i got AE CC 2014 and Premiere Pro CC 2014 working. However, they will not work in my regular main account which has
administrative priviledges. On the phone with ADOBE they told me that it was a permissions issue and that it was Apple's Problem. Which I CALL B.S.!!!
I tried to repair permissions in disk utility knowing full well that it wouldn't fix the issue. How on earth would apple know what the permissions errors in folders or files are for Adobe products!!
I was very angry and upset with the Adobe technical support for this issue.
On the new mac pro i am using i was able to create the new administrator account and erase the old administrator account since i have 0 documents or old data that i have on it other than programs.
However, on my mac pro. I have well over 15 years of data on it including 100 GB of music, etc... that i simply can't just erase away. Not too interested in working on 2 different accounts either.
Not sure what to do now and i am extremely frustrated.

Adobe Premiere Pro CC 2014.2 (8.2) freezes up constantly on Mac OS X Yosemite

After the latest update (no idea which one but the latest update) Premiere Pro cc just keeps freezing up constantly. There's no indication what brings it up but after different periods of time I just get the apple wheel and the entire program freezes up. I force quit and get the "sorry, a serious problem has occured", blabla. Sometimes it's in the middle of cutting a clip, sometimes it's while trimming. There isn't a single indication what causes it. At first I thought it was only because of using a multicam clip, but that's not the case anymore. I tried reducing memory to other apps, deleting preview files, deleting autosaves, turning off autosave altogether, deleting Adobe Premiere 8.0 preference file, changing permissions, basically everything in this post: Re: Adobe Premiere Pro CC keeps crashing... (Which now also seems totally neglected by Adobe).
Believe me, there's hardly a thing I haven't tried.
It's getting REALLY frustrating now and it's time something is done about this. Yes I know, "don't just say it's frustrating, explain the problem", but that fase has passed now. I'm paying for this product and it needs to work like it should.
Also I know I'm not the only one who's having these problems.
My specs are:
OS X Yosemite 10.10.1
MacBook Pro (Retina, Mid 2012)
2,3 GHz Intel Core i7
16 GB 1600 MHz DDR3
NVIDIA GeForce GT 650M 1024 MB

Hi JJ,
JJ Millen wrote:
It is not about the past times you may or may not have participated, but about the latest message from rob654 and my last messages in that thread (which are clearly not about Windows).
One great reason to get a Mac only version of the post. It is never a good idea to post on a Windows post with Mac problems. And when threads get so long and unruly, the team can't focus on the actual issue so it doesn't get the attention it needs.
Now that we have that sorted out...
JJ Millen wrote:
I checked that and it says 8.2.0. (65) build.
Thanks for the verification. You are running Premiere Pro CC 2014.2 (8.2). It helps to have that absolutely clear.
JJ Millen wrote:
Here are all the checkpoints mentioned in that thread, applicable to my project:
- Version 8.2.0;
- My Creative Cloud says Premiere Pro is up-to-date;
- Operating system is OS X Yosemite version 10.10.1 (14B25);
Very well, did things operate any differently on Mac OS X 10.9.x? Or did you have the same problem?
JJ Millen wrote:
Type: MPEG Movie
File Size: 4,0 GB
Image Size: 1920 x 1080
Frame Rate: 25,00
Source Audio Format: 48000 Hz - 16 bit - Stereo
Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
Total Duration: 00:12:35:16
Pixel Aspect Ratio: 1,0;
So is this H.264? What is the camera that you are working with? DSLR?
JJ Millen wrote:
- I do not get any error messages, except for the "Sorry, a serious problem has occurred"-message after I have to force quit my Premiere because of the freeze;
What kind of drives are the media files stored on?
Are the permissions set correctly (as Read/Write) for the Mac HD and your media drives?
Are the permissions set correctly for all the Adobe folders as I outlined in my blog?
JJ Millen wrote:
- The problem mostly occurs when cutting a clip with the razor tool, regardless of the kind of clip;
When you import clips, are you using File > Import, or are you importing via the Media Browser?
JJ Millen wrote:
- Yes this has worked before, the problems started either after creating a submix (which I've deleted, without result) and/or after updating to a newer version of Premiere CC;
Definitely do not update Premiere Pro or OS X when in the middle of a project. Wait until it's complete. If you did either or both of these things, you can cause your project to become corrupt. After your current project is wrapped, test with a brand new project.
JJ Millen wrote:
- The only software I run actively besides Premiere is Apple's Mail program, Safari and/or Chrome, sometimes Wire, sometimes Spotify;
- I currently have no third-part effects or codecs installed in Premiere;
- I installed the latest CUDA Mac Driver, version 6.5.37 (release date 01/14/2015);
- The problem just happens while working in my sequence, not in any final output. I don't know what is meant by "previews", but I have the yellow bar indicator in my sequence, if that's info you need.
I have heard of others having issues with OS X 10.10 and NVIDIA GPUs. My advice is to consider downgrading your OS if you continue to have issues. I believe I have avoided a lot of trouble by sticking to OS X 10.8.5.
Previews AKA the Media Cache are your "render files." They can become corrupt, so it's a good idea to trash them when troubleshooting. You can locate them via your Preferences > Media. Click the Browse button.
JJ Millen wrote:
Okay I went through that menu (which I'm not eager to do, I prefer direct contact) and came across the CUDA setting inside the project settings. I've now enabled the "Mercury Playback Engine GPU Acceleration (CUDA)", which might help.
So were you set to "Mercury Playback Engine Software Only" or "Mercury Playback Engine GPU Acceleration (OpenCL)" prior to changing it to "Mercury Playback Engine GPU Acceleration (CUDA)?
JJ Millen wrote:
Testing with a brand new project is not an option. I have a deadline for my current project and it's impossible to start from scratch. What I did try is start a new project and importing the existing one, which didn't help so far.
I was just wondering if you experienced the same issues in a new project. Any project you update to a new version is suspect, in my opinion. In the future, try to avoid doing that. If your current project is corrupt, I could see why you are having certain issues.
For what it's worth, we had another user that exhibited similar issues until they started with a brand new Premiere Pro CC 2014.2 (8.2) file.
Since importing your 8.1 file to a new 8.2 project isn't working, make sure to triple check permissions on all the Adobe folders I laid out in my blog post: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)
It's the #1 reason Mac users experience freezing and crashing. The other one I'd look at is that NVIDIA drivers are not working well with Yosemite. Finally, if you update a project across versions, it can become corrupt. Not much you can do about that except start a new project ASAP.
Thanks,
Kevin

Flickering footage in Premiere Pro CC 2014 but not in Premiere Pro CC 2013

Hi guys,
I've been having repeated issues with Premiere Pro CC 2014 on Windows. Basically my footage has a weird strobe/flicker when in the suite and when rendered off even although the footage looks fine, unaltered out of the camera. I rendered off the same footage in the 2013 edition of the software and there is no flicker/strobing going on. I've included one of the worst effected shots in CC 2014 and CC 2013 for comparison.I also experience graphical glitches occasionally when rendering. Please watch below:
Premiere Pro CC 2014 - strobing (300% speed, cropped 15%, RGB curve adjustment, software rendered)
YouTube
Premiere Pro CC 2013 - strobing (300% speed, cropped 15%, RGB curve adjustment, software rendered)
Premiere Pro CC 2013 - no flickering - YouTube
The footage was shot on a Nikon D3200 at 1080p 25fps, aperture 3.5, shutter 1/50, ISO 400.
Editing on a
Dell Optiplex 9020
Intel i5-4570 3.2 Ghz
4 gb Ram
Intel HD Graphics 4600
Windows 7
Has anyone else experienced this issue? My suspicion is an issue with either my graphics card or insufficient RAM.

Thanks for posting that info. This mirrors the issues I'm seeing with DSLR footage.
It's so hit or miss if it's going to flicker. I'll delete renders and re-render and certain clips will be fine, others are now flickering. I tried to make a test project that demonstrated this issue, but couldn't reproduce the effect. RGB Curves and Three Way CC are in my list of effects, as well, where I see the issue.
Just curious, is anyone else working on projects started in other versions/computers? I've seen it on project started in PPro CC and finished in CC'14. Saw it again on a project started on Mac in FCP7, converted to CC'14 Win7. Quite honestly, I haven't been starting projects myself in CC'14 because of the flicker issues.
As a workaround, I was hoping to import the CC'14 project back into CC or Media Encoder CC, but no luck there.
Another issue I've had with CC'14 includes converting a CC project to CC'14, giving it to a CC'14 Mac user and the A/V sync is lost. We abandoned that collaboration all together because of the issues. CC'14 has been incredibly unproductive to my workflow, despite the great interface update and various other features added. I haven't had mystery issues like this since CS4. I'm keeping our post team in CC as much as possible until the issues are resolved.
-JB

New (8/14) Macbook Pro Retina - Premiere Pro CC 2014 spinning beach ball

Help! Seems my shiny new wiz-bang 4-core Macbook Pro with 16 GB of Ram and a 512 solid state drive works just fine with Adobe Premiere Pro CC 2014 until my project reaches a certain size, then it won't open the project and immediately gives me the deadly spinning beach ball. The only way to exit is to force quit whereupon I get the "Sorry, a serious error has occurred...". Aggravating beyond words.
Saw one forum comment where it was recommended to update to the 6.0 CUDA driver, but not even sure I have a CUDA driver. Plenty of space left on hard drive. In Premiere Pro preferences under the "Memory Tab" it doesn't seem to matter if it's set to "Optimize rendering for.... Memory or Performance." I've reinstalled the Premiere Pro App twice. Doesn't help.
Some specs:
Processor 2.5 GHz Intel Core i7
Memory 16 GB 1600 MHz DDR3
Graphics Intel Iris Pro
NVIDIA GeForce GT 750M GPU PCie
Intel Iris Pro GPU Built-in
8 GB DDR# 1600 MHz (x2) = 16 GB RAM
350 GB of 499 GB left on drive
Of the 16 GB of RAM I have 11 available for Premiere Pro and the other 5 GB allocated for other apps.
Any suggestions would be greatly appreciated.

>NVIDIA GeForce GT 750M GPU PCie
>Intel Iris Pro GPU Built-in
Dual graphics adapters are a bane on civilization!!!
-http://helpx.adobe.com/premiere-pro/kb/error---preludevideo-play-modules.html
-http://forums.adobe.com/thread/1001579
-Use BIOS http://forums.adobe.com/thread/1019004?tstart=0
-link to why http://forums.adobe.com/message/4685328
-http://www.anandtech.com/show/4839/mobile-gpu-faceoff-amd-dynamic-switchable-graphics-vs-n vidia-optimus-technology/2
-Mac Utility for dual adapters http://forums.adobe.com/thread/1017891?tstart=0

Adobe Premiere Pro CC 2014 Crashing very often! Please Help!

Hello,
I am currently editing my first feature on Adobe Premiere Pro CC 2014 and it is currently up to date.
I am editing on a iMac 27in, late 2013 brand new computer.
Processor: 3.5 GHz Intel Core i7
Memory 32GB 1600 MHz DDR3
Graphics: NVIDIA GeForce GTX 780M 4096MB
System: OSX Yosemite V 10.10.1
The project is located on a 8TB G Drive
7200 RPM
High Performance ThunderBolt drive.
Details of the project:
I am currently working on a fine cut of 5K Red Footage that is being cut in the RAW.
I work at 1/2 quality settings and have no lag.
The timeline includes limited stacked video files and various mp3 audio files.
The Problem:
Lately, the program will randomly quit or freeze up 4-5 times during an 5-6 hour edit session.
Many times it is random, however, it seems to happen often if I accidentally click on the end of a clip on the timeline and it goes to switch into trimming mode.
Also, it will randomly go into the "pinwheel of death" out of nowhere followed by "Adobe CC is not responding."
My project file is just about 15MB now.
What is causing this reoccurring problem?
How can I make it happen less? I have scoured the forums and found similar articles but no helpful solutions.
I have recently turned auto save on to save every 2 minutes because there have been more than one occasion where I lost A LOT of work because of this issue.
I am about two weeks out from picture lock delivery and this issue is driving me crazy and loosing me a ton of time.
Please help or let me know if any more additional information can help solve the issue.
I have sent in well over 25 error reports already.
Thanks,
Thomas.

I think I may have found the solution...
I completely removed the Premiere Pro folder under User > Documents > Adobe and so far it seems to have solved the problem.
I of course backed up my projects and than deleted this folder. So far it seems it worked.
I'll know for sure in a day or two, but after constantly crashing, Premiere hasn't crashed for the last 4-5 hours of work.
Goran

What is the problem with Adobe Creative Cloud Premiere Pro CC 2014, why it freezes often?

I Purchased the Adobe Creative Productive Premium Suite CS5 in early 2010 and I was very satisfied with it all this time, I can say that I never had a problem while using any of the Production Premium applications. Few weeks ago, I asked Mr. Philip Bloom about a technical issue regarding the best method to use a 50 FPS clip with a 23.976 FPS project, and I got his kind help but he recommended me too that I should upgrade to the latest Adobe Cloud CC 2014 which has many new features added to the different programs. I took his kind advice and downloaded a trial version of all the Adobe Cloud CC programs which I use for my filmmaking business.
Today is the 20th day of my trial period and I have 10 days left to take the decision of continuing with CC 2014 or not. The past 20 trial days were not very pleasant. I want you to share with me the following details which I'll list them as bullet points and I would appreciate diagnosing the problem if you can and suggest a solution for it to re-try the Adobe Cloud CC 2014 for the 10 remaining days with no further problems.
I used to have the Gigabyte graphics card GTX 470 for about 4 years and it malfunctioned last year and I replaced it with a humble Geoforce GT 610 card, but it worked fine with the Adobe Suite CS5 programs.
My system configuration is Intel Core I7 950@ 3.07GHz , installed memory 12 GB. , Windows 7 Ultimate, 64 bit Service pack 1, 3 hard drives 1TB. each (one of them is dedicated for Adobe asset files and the editing work)
For the first 2 or 3 days I used mainly the Premiere Pro CC 2014 establishing short projects for a max. of 5 minutes each and it was working normal. But, later, as soon as I started to build a project which reached about 24 minutes of length and I began to edit those before I add more clips to the timeline, unfortunately, the PrPro CC 2014 started to freeze on any of the frames every time I try to edit normally as I used to do with the CS5, so, I had to wait for 2 or 3 minutes every time it freezes, then it works for seconds then freezes again!! and during the 20 days mentioned above it crashed once.
The movie files of my project are the Nikon's .Mov files and the editing work which I performed included effects such as Color correction (levels) color correction (fast) color correction (Auto) sharpen effect, and stabilizing effect.
I installed the Magic Bullets Suite trial version, and the Neat Video trial version, aiming to purchase either the DeNoiser or the Neat Video (but I tried their effects without saving them to the project).
I used to export parts/ or whole project before finalizing the editing process to be able to monitor on a TV screen (mp4 file format) some of the changes I made in PrPro before being freezed.
Based on my previous 5 years experience using the CS5 Suite I have a strong trust in Adobe, I never thought the problem was in the PrPro application, but rationally I thought it was the graphic card (GT610), and accordingly I purchased yesterday a new Zotac Geoforce GTX 770 (listed by Adobe as an approved card) and I installed it and checked that it is running fine and I checked the processor temperature which was within the normal level.
Only today, I began to think that it might be something wrong with the Adobe Cloud CC 2014 ( a bug or something) and as a result of searching on the internet I could see lot of users since 2014 who were having freezes and crashes with the CC and the CC 2014 versions. That was a shock for me, could it be that until Feb. 2015 the same severe problem still occurs???
Sorry for any inconvenience, looking forward to seeing a solution for that serious problem.

Hello Ashraf,
Sorry you didn't get any help on this post. In the future, please contact Adobe Support for 1-1 assistance on issues like this: Contact Customer Care
Thanks,
Kevin

Multi Cam Flicker Issue - Premiere Pro CC 2014

Multi Cam Flicker Issue - Premiere Pro CC 2014 can any one help me pls

Hi,
This might help :
Go to File > Project Settings > General and change the Video Renderer to Mercury Playback Engine software only. Click OK and select Delete Previews.
Thanks,
Rameez

How to work on the same project on two machines at the same time and also exchange progress seamlessly using Adobe Premiere Pro CC 2014?

We are working on a film project on Adobe Premiere Pro CC 2014. Two editors are working on the same film project (same pproj file ) on two machines. As a result the bin structure and the file structure is exactly the same. We even bought two licenses for the respective machines to make matters simple (at least we thought it would).
Now when we share a sequence between the two machines, every time we have to import and re-link media. Also each sequence import comes with its own set of files, which are actually already present in the project. Basically the new sequences are looking to re-link the media to the original/ source files only and are completely ignoring the file structure present in the project.
In all editing softwares, timeline/ sequence sharing is a very common practise when working on multiple machines. Why is it so tedious in CC 2014? Every time we share a sequence between the two machines the media gets doubled and tripled in the project. As a result the project file size is increasing perpetually. Already Premiere CC 2014 is extremely laggy and slow, and this stupid bug is making it more difficult for us to finish our work on time.
Has anybody ever faced this issue? How do we solve it? We are willing to try out any workflow that you can suggest.

Concurrently working on the same project it requires a specific implementation in all editing programs like Avid's Unity/ ISIS shared storage. That's what you are simply not considering. none of your issues would be any problem if your projects resided on a commonly accessed server or something like that. Check respective hardware solutions.
Mylenium

Flicker footage in Premiere Pro CC 2014.2. Tested on different computers. When waiting for fixes this bug?

Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different. Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
It can occur even in the parts without filters !!! But no all time.
ver 2014.2 - win 7 - intel i7-4770 - gtx 770 - flicker!
ver 2014.2 - win 7 - intel i7-4770 - Intel HD Graphics 4600 - flicker!
ver 2014.2 - win 7 - intel i7-2700K - quadro 2000 - flicker!
MERCURY PLAYBACK ENGINE work fine! But still flickering in preview and render.
When waiting for fixes this bug?

Hi Aleksey,
Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different.
Have you tried with the Mercury Playback Engine set to "Software Only?" More info please: FAQ: What information should I provide when asking a question on this forum?
Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
Is this a brand new project or one you updated from an earlier version? What kind of footage are you exporting? Which preset are you using?
When waiting for fixes this bug?
If I can repeat the case here with the same hardware, GPU, and drivers, that would be easier to fix the bug. Currently, I cannot recreate the bug. If you or anyone else can provide me with steps to recreate the bug, that would help immensely. It sounds like this will be the difficult thing.
Thanks,
Kevin

Premiere Pro CC 2014 crashes when loading project file

Hi guys, any help on this is much appreciated as I have a job due in 18 hours and I'm in big trouble if I can't fix this.
I've been editing a project in Adobe Premiere Pro CC 2014 (updated to the latest version) and when I tried to access the same file today it is giving me the error message:
'Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project.'
I had saved other version files and they all seem to be working properly so I know it's not my HD that is corrupt. In fact my suspicion is that it has something to do with a blur effect i'm using. The only problem is, I can't even access the file to delete the effect as the project file won't open.
Information about my computer:
I am using a Macbook Pro
OS X version 10.9.4
2.6 Ghz Intel Core i5
Memory 16 GB, 1600 MHz DDR3
Any suggestions/comments would be appreciated.

Guys I solved my own problem - thought I'd share with you how in case anyone else is having this problem -
I came across this thread
Premiere Pro CC error message and crash
which had the suggestion -
"Do tou have after effects installed? If yes, please try to import the main sequence into it and then export it as premier pro project from file/export ootion and then try to open that in premiere pro."
This didn't work for me too but I did try and import my existing project into a new project and copy all the files over. Works fine now.
I don't know if I will have the same issue again tomorrow so I'm going to render out a super high res video before I close premiere just in case

Why does Premiere Pro CC 2014 renders incredibly slow?

Dear Premiere Pro experts
I created a movie with Adobe Premiere Pro CC 2014 and I have serious performance issues when it comes to export the movie.
The first 10% renders pretty fast and takes 1 hour. Then it takes for every additional 1% about 4 hours! (never rendered it to finish so far, 14% max so far)
Here are some facts that might help to isolate the problem:
Project:
Length: 24 minutes in total, splitted into several sequences (up to 4 minutes) and arranged on a "main-sequence"
Input: Cineform AVI files, 1080p, 59fps (I converted GoPro 3+ footage (3D!) using GoPro Studio to the Cineform format for further processing)
Desired Output: Same as input, preserving 3D (Render 3D Intermediate)
Effects used: Warp-Stabilizer (default settings) and Auto-Color (smoothing 1-2 sec) on almost every clip.
Hardware / Software:
i7-3770K @3.5 GHZ (Quadcore)
16 GB RAM
NVIDIA Geforce GTX 970 (also tried with a ATI Radeon R9 290X)
Windows 8.1
SSD for OS and programs, RAID 0 for media files and project, separate drive for rendering output.
Then I tried to render using AME using the same settings. The whole video rendered in about 14 hours what is acceptable in my case. There problem here is that the 3D gets lost, even if I selected "Render 3D Intermediate". The picture for the left eye is the same as the one for the right eye. This is not happening when I do a direct export. But the direct export get almost stuck at around 10%.
There is almost no difference in choosing Software-Rendering and GPU. Also, the GPU has almost no load. Premiere Pro uses the CPU for about 45% (total usage 65%) and takes up 5-9 GB of memory (total usage 65%). Disk usage at around 14b/s.
I think there are two problems. One is that AME renders differently (no 3D) and the other is that the direct export takes way too long.
Can someone help me with any of these problems?
Thank you,
Martin

I did some additional research and found out, that the slow rendering happens with this combination:
- Auto-Color using Temporal Smoothing
- Render 3D Intermediate
Without rendering the 3D intermediate, Temporal Smoothing is not a problem. And without temporal smoothing, Rendering 3D Intermediate is not a problem.
Might this be a problem in the codec or in Premiere?

After upgrading to Premiere Pro CC 2014, I can't change the render preview location

Ever since I downloaded Premiere Pro CC 2014, I cannot re-route my render preview files. I have two internal hard drives and I need the files to go to my secondary one. With CC, it did this just fine, but since I've upgraded to 2014, it will not do it. I've set it the same way I did before in Preferences/Media, then set the Media Cache Files and Media Cache Database to the new hard drive. It's eating all my hard drive space and I cannot render or export a large sequence. Is there a trick to this I'm missing that has changed?

Thanks Neil! I'm actually wondering how to change where the preview files go. I've attached two screen grabs. Right now my media cache is going to my SATA drive (my smaller of my two internal hard drives and the drive where Premiere Pro is located.) I want to re-route my render files to go to my Macintosh HD drive which is much larger and gives me more breathing room. I could do that before but since I've upgraded to 2014, even though I have it set in preferences, it STILL goes to my SATA drive. So annoying! I'm wondering if I'm doing something wrong or if it's a bug. I'm still running Mountain Lion (getting ready to finally upgrade, I've just been needing to backup my computer), could this be the reason? Any ideas? Thanks so much for the help!

ICanon C100 playback issue premiere pro cc 2014

I am having playback issues in Premiere Pro CC 2014 with footage shot on my Canon C100 (29.97 fps). It was happening after doing a straight import and creating a sequence using "new item". Then, after reading some other threads here and elsewhere, I interpreted the footage so premiere would see it as progressive (no fields) rather than interlaced, but that doe not seem to help. It is even doing it when I play at 1/4 resolution. The only solution seems to be to quit and restart and reopen the project. Then it works temporarily for a little while but not long enough to actually edit. I have done projects in Premiere with C100 footage in the past and have not experience this level of difficulty.
My Media Cache is not going to the startup diskc(it is gong to the right place)
I am on a Mac 2.66 Ghz Quad-Core Intel Xeon
OS X 10.8.5
10GB 1066 MHz DDR3
NVIDIA GeForce GT 120 512 MB
Please help - very frustrated. If the solution is to transcode, it sort of kills the value of premiere in many ways.

Hi,
This might help :
Go to File > Project Settings > General and change the Video Renderer to Mercury Playback Engine software only. Click OK and select Delete Previews.
Thanks,
Rameez

Premiere Pro CC 2014 multicam glitch 8.2.0(65) Build

Similar Messages

Maybe you are looking for