Premiere Pro CC 2014 - warp stabilizer

Within the last couple of days, I have been dragged, kicking and screaming, into the world of Creative Cloud! I have pre-paid for the first year and, so far, am not convinced I have done the right thing. I have been running CS6 with very good results for some time and was looking forward to the new facilities and options in CC 2014.
So, I have read in another discussion, that Premiere Pro is not backwards compatible. Surely this cannot be true?
My first use was to load a (copy) project I had been working on for some time. Source files were AVCHD (.mts as imported) 1920x1080. The performance in timeline playback is sluggish, where CS6 had been very smooth. Then it met a clip which had the CS6 Warp Stabilizer applied. In CS6 it was very effective. In CC 2014 it just showed a black screen with just a small area of picture visible in the top rleft hand corner. It needed rendering and that suggested it was going to take 30-35 minutes to render a single (approx 20sec) shot!
So, if the program is NOT backwards compatible, I create a brand new project. I imported a few clips (AVCHD - .mts extension). I placed one of them on the timeline - having first dragged one of the clips to 'new item' to set up the parameters for the project. I dragged the warp stabilizer on to the clip, leaving the Warp controls in default. It did exactly the same thing, a black screen and just a small portion of the picture in the top left hand corner.
Please, somebody assure me that I have not just spent over £300 on software which is going to slow me down and make life far more difficult than it was before.
PC/Windows 8.1/8Gb RAM/Intel i5

With profoundest apologies, I have found the answer in another discussion concerning Warp Stabilizer.
I was so anxious to get up to speed with CC2014 that I failed to search properly.
Alan S.

Similar Messages

Premiere Pro CC's Warp Stabilizer BUGS...see for yourself. (7.0.1 & 7.1)

I'd love to hear from Adobe Staff on this one. Hopefully they can focus on fixes over features for the next update, especially for one it's most touted effects.
Warp Stabilizer works great at stabilizing clips in Premiere Pro CC...but I'm beginning to learn that it's quite buggy. The two bugs below simply cripple the user experience when you use the effect a lot like we do. Here's a link to a sample project with just 2 clips (around 1 minute in length each) on two separate timelines with each clip stabilized using the Warp Stabilizer effect. It's only a sample/test project meant to show the issue which can be MUCH larger in a longer/bigger project. Relink to any longer media and you'll quickly see what happens when you have multiple warp stabilizers applied to a Premiere Pro CC project and how problematic it can be.
https://dl.dropboxusercontent.com/u/105331144/Warp_Stabilizer_SAMPLE_Project.prproj
See for yourself.
Two VERY Annoying BUGS and One Unfortunate Feature:
BUG #1: (It affects 7.0.1 and the new 7.1 Release/Update)
1) With GPU Acceleration Enabled and both sequences open, once the timeline render bar has turned yellow, hit save.
2) Now toggle to the 2nd sequence and you'll notice a delay/freeze as the render bar switches back to red and then yellow again.
3) Now toggle back to the other sequence and you have the same thing occur. Then, you can toggle back and forth with no delay...until...the project saves (or auto-saves) again...and then the delay/freeze will happen all over again.
4) Side Note: Even when you right-click on the sequence in the Project window, there's a delay. Right-click on a sequence with no Warp Stabilizers and the drop down list pops up immediately.
What's the Big Deal?: When you have tons more warp stabilizer effects applied to multiple sequences, not only does it take a while to save, but when it does, you are forced to wait while Premiere Pro freezes momentarily. This affects AUTO-SAVE too!!! The more warp stabilizers, the longer the wait. Our sequences have delayed up to 30-40 seconds depending on how much we've used warp stabilizer in each sequence. Imagine if you have Auto-Save set to every 30 minutes or less, well that means that every 30 minutes or less you'll be forced to stop while premiere freezes up for 30-40 seconds or so (depending on how much this effect is used). Other effects do NOT have this issue.
BUG #2: (It affects only the new October Release/Update of Premiere 7.1...this issue is NEW and does NOT occur in 7.0.1!!!)
1) Take the above project into Premiere Pro CC 7.1 (again, this does NOT occur in the previous 7.0.1 release) and hit FILE>EXPORT>Media.
2) You'll notice a delay while the EXPORT SETTINGS popup opens.
3) Toggle to different "FORMATS" in the export settings window and there's more delays every time the format is switched.
What's the Big Deal?: Again, this is a small sample project. When you have a much bigger project with lots more Warp Stabilizers applied to many more clips this "delay" can extend up to several minutes!!! Yes, on a recent project over an hour with MANY warp stabilizers applied to lots of clips, it took 7 minutes for the Export Settings window to pop up after hitting EXPORT>Media. And there was about a one minute delay now when switching formats. This occurs whether GPU Accleration is enabled or not. It ONLY occurs on Premiere Pro CC 7.1
UNFORTUNATE FEATURE #1:
We obviously use Warp Stabilizer A LOT. It's a great effect. The above bugs cripple the user experience. This last issue isn't a bug, but rather a default setting on Premiere Pro's warp stabilizer that should be changed. Within the settings of Warp Stabilizer there's a section called "Method". The default setting is "Subspace Warp". That sounds pretty cool. But in practice, and we have had lots of practice (eg. THOUSANDS of clips stabilized in just the last few months alone (no exaggeration)), we've found that switching the default method to "Position, Scale, Rotation" is a MUCH more effective way to stabilize a clip. Most of the time it cuts down on that "wobble" that you might see in complex moving clips...but more importantly, 9 out of 10 times it crops the video either the same or less than when you use the default method. By "crops less" I mean that the "Auto-Scale %" is less. Of those 9 times, I'd guess 7 or 8 of them would crop in on the video less while the other 1 or 2 times there would be no change to the Auto-Scale %. Less scaling = better.
What's the Big Deal?: Well, as cool as Subspace Warp sounds, our numbers don't lie. Again, we use this effect on HUNDREDS of clips every week. When you have to go into hundreds and hundreds of clips every week and keep switching the setting so the effect will work better, it gets old real fast. We end up wasting so much time doing this but it's worth it because the results are undeniable. Why not create a CUSTOM PRESET???! Well, that'd be nice if it worked...but it doesn't. The problem with a custom preset like that is that when you drop it on a clip, it doesn't activate/analyze the clip automatically so you have to manually go into the settings and hit analyze which negates any time saved. It's be great if the default "method" was simply changed to Position, Scale, and Rotation. Or at the very least, it'd be great if one could create a custom preset that would automatically activate/analyze the clip it's dropped on (just like the original effect does).
(BONUS FEATURE: It'd also be nice to have the ability to set a "max scaling %" too so you never crop in more than a preselected amount...but first things first...fixes over features.)
NOTE: I'm on a 2011 suped up iMac running OSX 10.8.5

[r]Evolution wrote:
Would it help to Render these Warp Stabaliized clips instead of leaving them in the sequence w/ the Effect applied?
Any way to "Batch" Warp Stabalize your media before editing so the effect is not needed during the edit?
Sounds like you guys could benefit from having your shooters use a "Stabalizer".
Thanks for the rendering tip rEvolution. Rendering the clips does help with BUG#1, however, I'm not sure if it would truly save us any time because of the constant need to render and rerender tons of very short clips with this effect as we make adjustments to the edit. Warp Stabilizer is GPU Accelerated so playback is really smooth which is great but why does saving a project have any effect on this and cause it to freeze up? And then it works great...until the next time the project is saved. Using any other effect, there is no issue (that I've found) when a project is saved or auto-saved.
Rendering unfortunately has no effect on BUG#2 in Premiere 7.1 (again, this bug/issue did not occur in Premiere 7.0.1)
Regarding "batch" stabilizing...I'm not entirely sure what you mean. We do stabilize dozens of clips at a time before editing because it's imperative for us to know which clips (the sections we've pulled) will stabilize effectively. And then once the longer edit is complete we end up pulling all the best shots from that long sequence and copy/paste it to another sequence to make a 2nd shorter edit.
To say we've gone back and forth about the use of stabilizers would be an understatement. The fact is that we've spent almost 4 years creating a unique way to shoot based almost entirely around the effectiveness of warp stabilizer. It's taken years of trial and error but our style of shooting effectively allows us to mimick and thus replace the need for stabilizers, sliders and cranes. The extra freedom allows us to get MUCH more varied coverage of live events. It's different, I know, but it's fun and rewarding having a unique style. Granted the extra work is passed on to the editing side, but it's worth it IMO especially if these issues were addressed/fixed.
Regarding the "unfortunate feature" I mentioned, I would be satisfied knowing the default method works great for others if one were simply able to apply a custom preset of the clip with the adjusted method and it activated automatically and began analyzing the clip without the need to manually go into settings and hit analyze. That would be nice.
Thanks again for your input.

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?

Premiere Pro CC 2014 TickTime Crash FIX (in some cases)

In my experience so far, Premiere Pro can return a TickTime.ccp error in several different situations. In some instances (too much Warp Stabilizer) just clicking okay a gazillion times is a usable workaround. In a case I had recently, Premiere Pro CC2014 crashed completely every time I tried opening the project file and all its autosaved versions. Here's a description of what I figured out to be the problem and how I solved it.
My project file was created in CS6, then edited in CC2014 on a Mac, then Windows. After this the crashing started on both Mac and Windows version of Premiere Pro CC 2014.
Symptoms:
An error message pops up on opening project [..\..\src\TickTime.ccp-290]. Clicking okay brings up another more serious one about a Serious Error and PP needing to close. Then it dies.
The problem:
Somewhere between CS6 and CC2014, Adobe seems to have changed their XML file structure from using a comma as decimal separator to instead using a period. Somewhere within my project file, Premiere left one as a comma.
My fix:
1. Make a copy of your project file and change the extension from ".prproj" to ".gz"
2. Use something like 7zip and extract the file, this should give you a new file with no extention.
3. Edit this file in a text editor (I'd reccomend Notepad++ or TextWrangler, but Notepad and TextEdit will also do).
4. Search for the term <PlaybackSpeed>. Most of your clips would have a numerical value of 1 directly after this, referring to a playback speed of 100%. Click Find Next a few times and look at the numbers following the selected bits. Anything that is not a multiple of 100 will be a decimal number, that should look like "0.5" or "1.2759984", (referring to speed values of 50% and 127.59984% respectively). If you see a comma, replace it with a full stop. My project had a value of "0,8845" I had to change it to "0.8845"
5. Save the file, and using 7-Zip, compress it into a new gz file.
6. Change the ".gz" extension to ".prproj" and you should be set to continue your edit.
If you didn't change the speed of any of you clips, chances are this is not your problem.

Hi Karel,
Thanks very much for writing this up. I hope this helps others having this issue.
Thanks,
Kevin

Where is a link to the Premiere Pro CC 2014.1 (8.1) update? - Can I get help with the ticktime.cpp-290 error?

Ola to precisando do premiere versao 8.1 caravan consegue o link?
Message was edited by: Kevin Monahan
Reason: needed better title

Hi Kevin,
I posted about the same problem (TickTime.cpp-290 error) in another thread, but since you're asking here specific questions to resolve it, I'm answering it here.
Re: Debug Event: [...\ ...\src\TickTime.cpp-290]
What were you doing when this error started to occur?
          Nothing special I remember. The only thing I do recall, is:
          I was working with Premiere Pro (where the main project is), After Effects but rendering some PNG sequence, and Adobe Media Encoder. I sent from AE to AME a project to render. Configured 2 outputs (PNG & MP4). The same way I sent from PP a project to render and one error occured. Unfortunately I didn't write down the error, but it was like a path C://AME_64/something. But the AME queue updated and everything seemed OK. I close AME to be sure that the error wouldn't be the source of future error during rendering, and relaunched it. And at that time I couldn't open it. I got the error "Adobe Media Encoder has encountered an unexpected error and cannot continue". The only way I found to resolve this is to remove the directory /Users/%USERNAME%/My Documents/Adobe/Adobe Media Encoder/8.0/". The problem seems to appear when I save the queue. And since that time, Premiere do the TickTime.cpp-290 error.
          Another thing I noticed, don't know if it was there before, is, the AEP file in AME queue setttings displayed framerate as "25 / 29.97 / 30 / ...", a 2 digits number for the framerate. But suddenly (I thought first it was because of the Premiere Pro file being added to the queue, but no because it appended after without it), it was displayed as "25 000 / 29 970 / 30 000", a 5 digit number.
          After that, the TickTime.cpp-290 appeared. Sometimes when opening project, sometimes and resetting or changing the workspace (because it was messed up), sometimes when closing.
Do you have iCloud installed?
          No.
Is this a Premiere Pro CC 2014.0 or Premiere Pro CC 2014.1 project that was updated to Premiere Pro CC 2014.2? If so:
          It started long time ago a draft in CS6, but since I reopen the project, I saved new versions in Premiere Pro CC 2014.2 (not sure if I have other version like 2014.1 or 2014.0). Is there a way to know which 2014 version are my files? If I look into the XML I only saw Version="28"
Do you have a copy that can be opened in an earlier version?
              An old draft version in CS6. But that version has footage in different framerate and not all be interpreted at the timeline framerate.
Do you get the same error in that earlier version?
               No error here, the file opens properly.
              Additional info: I tried to open the 2014.2 file on another computer (where PP 2014.2 is installed) and same problem (this computer is on Win7 64-bit)
Did you use any unusual footage types in your project?
     I used MOV (Animation), MP4 (H264), and PNG sequence. The framerates of the footages are 24,25,30 and 60fps (but everything has been interpreted in 30fps)
If you remove them, do you still get an error?
              When I had the error, but not when I open the project file, I resave the file removing anything not interpreted in 30fps (because at that time I still had footage interpreted in their original framerate). I was able to work for some time, but now I can't open it anymore despite that.
Was the fps interpretation changed in any of the clips?
     Since the error appeared, and because I saw in another thread that it could be related to footage of different framerate, my timeline is now in 30fps and all the footage have been interpreted in 30fps. Footage are MP4, MOV, PNG sequence in 24, 25, 30 & 60fps.
If so, restore them to their original fps and see if you still get the error.
              Unfortunately, since I can't open the project anymore, I can't test that.
Did you use Warp Stabilizer?
          No.
Do you have any browser plug-ins?
          What do you call browser plug-in in Premiere?
Are there any third party plug-ins used?
          I have Magic Bullet Looks 2, and I'm using it on this project.
If so, remove the effect from those clips and see if it improves the situation.
              Unfortunately, since I can't open the project anymore, I can't test that.
Some additional infos on my computer.
I use Windows 8.1 (64-bit), all Adobe softwares installed have the last update (for video apps, it's 2014.2)
The language settings are configured in French, but Windows and CC apps are in English.
If needed the 2014.2 project file is here:
https://dl.dropboxusercontent.com/u/68413846/showreel19_30fps.prproj
Thanks in advance to help us to resolve this weird bug.
Christophe.

Premiere Pro CC 2014.2 crashes when "locating media"

The problem;
Premiere Pro CC 2014.2 crashes when "locating media". I am working on a project that has not given me any problems for the last 200 hours. About a week ago I notice that the .proj file size was 276mb and found this odd because my largest project to date was never larger than 80mbs. I thought that the premiere was running slow because of the project size. As luck would have, when my client made their their final changes 2 days ago, I opened the project and premiere would hang on the locating media window and then would crash. I called Adobe and spent an hour on the phone with them to no avail.
Project workflow
- 700gb of 5d footage
- 20 sequences under 5 minutes
- Dynamically linked files with AE
- Warp Stabilized about a dozen clips of under 5 sec
- On every sequence color correction adjustment layer with RGB Curves, Three way color corrector and sharpen filter
- I kept old versions of the sequences (I was in version 5 before the crash)
What I have tried;
- Unsuccessfully tried to open auto-save files for this project.
- Successfully opened other older non relevant project
- Removed Mercury playback engine in the project settings
- Cleaned out media cache database through pp in media Preferences
- Manually deleted cache files in /Common/Media Cache Files and /Common/Media Cache
- Tried importing sequences into new .proj file; it would crash as a result.
What "worked".
I was able to open it on another computer. save it under another file name. bring it back to my original computer and open it without problem. I lost about 3 days working through this problem, I missed my deadline. and angered the client. I was able to use a friends IMAC to "fix" the problem, however I can't always count on him being there if it happens again.
Questions.
- What the hell happened? Why could I open it on one computer and not on the other?
- Is there a way to fix a corrupted .proj files on a PC?
- What should the average file size be, before it becomes unstable? (I'm pretty that my file size was bloated by all the previous versions of the sequences)
Windows 8.1 64bit
Premiere 2014.2
Intel Quadcore i7-4770 3.40GHz
16gb Ram

Hi,
I would suggest the following steps:
http://blogs.adobe.com/kevinmonahan/2014/09/10/premiere-pro-cc-freezing-on-startup-or-cras hing-while-working-mac-os-x-10-9-and-later/
Run a disk permission repair on your boot drive, and
Reset Home Folder permissions and ACLs Error | Apple Support Communities
Thanks,
Rameez

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

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 - warp stabilizer

Similar Messages

Maybe you are looking for