Premiere Pro CS6 - Warp Stabilizer BUG causes project to crash

Hi!
Sometimes Warp Stabilizer causes Premiere CS6 to crash. I found out what steps cause this so hopefully a fix can be made in an update soon:
1) Add the WARP STABILIZER to a clip. It Analyzes and then is applied to the clip.
2) TOGGLE OFF the effect in the effect controls window
3) Adjust the clip duration and RE-ANALYZE while the effect is TOGGLED OFF still and Premiere crashes.
Happens every time. BUG Report was filled out.
(If the effect is toggled ON when you RE-ANALYZE it, everything works okay.)
So why not just not do this? Well, I usually don't but sometimes in the middle of working with hundred of clips I toggle on/off the effect to check certain things and then leave it off. If the clip is adjusted later or I come back and try to click ANALYZE again while the effect is toggled off, everything crashes.
That's the pop up. If Premiere doesn't allow for you to re-analyze a clip while the effect is toggled off, then the ANALYZE button should not be active or at least a popup saying "Cannot Analyze this clip while it is toggled off". Instead Premiere crashes and upon reopening the project you are forced to rename the project which fortunately is usually fully recovered.
Running 6.0.2 on a suped up 2011 27" iMac with 16gb ram and AMD 6970M 2gb video card.

I know I'm piggy-backing on an old post here, but I've just had real issues with a similar thing on Mac. Unfortunately, my Premiere CS6 is crashing and becoming totally unresponsive whenever I simply apply the Warp Stabilizer. The moment I drop it on my clip, BLAM! I get that same pop up you posted. I click 'OK,' and then nothing. Just beachbal of death until I force quit. What's more annoying is that, not only has the camera operator made the stabilizer essential, but I've been using it for the past week with no issues up till now.
At first I thought I was overloading Premiere by dropping the effect onto two clips at the same time. But I tried it one at a time and had the same problem. My recovery project files seem to be ok, but that's not even nearly the point. I simply can not use a great and essential tool. Help?

Similar Messages

Premiere Pro CS6 Warp Stabilizer not using GPU/CUDA why?

Hi,
I installed CS6 and tried the Warp Stabilizer, I undestand that only part 2 of the process (stabilize part) is GPU accelerated, but I can't get any acceleration from GPU, my GPU is idle at 1% usage (GTX580) and all the processing is going to CPU. The renderer/playback is marked CUDA so its not that.
Is there anything I'm missing?
Thanks

OK, this surprised me a bit. I have a state-of-the-art new PC with plenty of RAM, a fast processor and lots of cuda cores. See the specs here: http://www.stevengotz.com/
It took over 10 minutes to stabilize one minute of video - 1800 frames. It wasn't all that shaky to begin with, but it was handheld and therefore looks better after using Warp. There was one section that was so bad, I sliced the clip up and chose not to stabilize that part after the fact. So I thought that it might have added a little to the problem. But no. I tried just 180 frames of reasonably stable hand held video from the same clip and it took almost a minute.
Now, once the process was finished, I had no problem playing it back in realtime without rendering. But what is taking so long? I understand that there is a lot of work to do, but why isn't it using the power I have provided?
This is a screen shot of my resources about two minutes into the process.
I would love to know what I need to do to speed up this process. I get that it is working in the background. Is it possible to make it work in the foreground? I would not mind if it maxed out the RAM or the CPU or both if it would help.
edit: I just submitted a Feature Request to let Warp run in the foreground using every available resource.
Steven
Message was edited by: Steven L. Gotz to include additional information.

Premiere Pro CC - Warp Stabilizer causing "Heat Waves"

I'm using Premiere Pro CC 2014 and when I apply Warp Stabilizer to certain clips I get this weird heat-wave, shimmer-like effect. For the life of me I can't figure out why this is happening. I've tried singling out every variable that I can but nothing matters.
You can see what I'm talking about here: Dropbox - With WS.mp4
And here is the clip without WS applied: Dropbox - Without WS.mp4
The clips I'm trying to stabilize are actually pretty stable already so it shouldn't be an issue for WS normally. It doesn't seem to make a difference whether they're in a 720 timeline or 1080.
I've tried every setting in WS that I can, including 'detailed analysis' and 'enhanced reduction' on Rolling Shutter Ripple. The only thing that kind of seems to help is applying the rolling shutter repair plugin but even then it's still somewhat choppy.
The shots themselves don't have any noticeable rolling shutter ripple (slow moving grass shot on a monopod) and they look great UNTIL I add Warp Stabilizer and they get the weird effect. Even though the clips are already pretty stable, I just want to add WS to smooth some of these clips out a little bit. When I replace the clips with an AE comp and WS in AE it's fine! But I want to figure out why this is doing it inside Premiere so I don't have to use dynamic link every time I want to use WS.
I just got this machine, maybe that has something to do with it...I have no idea.
System info:
Mid-2011 27" iMac
3.4 GHz Intel Core i7
12 GB 1333 MHz DDR3
AMD Radeon HD 6970M 1024 MB
OS X 10.9.5
Adobe Premiere Pro CC 2014.1
Shot on a 5D Mk. III with either a 24 (1080p) or 60 (720p) frame rate and resolution.
Can anyone help? Thanks

I don't have answers for you. Sorry. But I have seen that once before on a clip I stabilized. Much like the grass shot you show in your mp4. Mine was of a guy sitting at a pool and the bright plants behind him where flickering like a heat wave/desert-like effect. Only one clip had it and it made me go "hmm...never seen that before." I stabilized hundreds of clips in that project and that was the only clip with that heat wave thing happening. I was on 7.2.2 at the time. And eventually went to 8.0.1 with no change. It didn't bother me enough to do anything about it so I left it. It was shot at 1080p60 from a Panasonic PX270. Strangely I have the same computer as you (except I have 16gb of ram and I'm on 10.8.5). That is very interesting to me that it worked great in AE. Interesting indeed. I'll follow this thread in hopes of a revelation. Fortunately, I don't see that issue much or I'd be screwed.

The Next Version of Premiere Pro CC - Warp Stabilizer

With the recent post of what's coming in the next version of PPro CC, I was sad to see no mention of Warp Stabilizer. As amazing of an effect as it is, it needs a bit of help. I know there are improvements and fixes that probably weren't mentioned in the post so I'm still holding out hope. We use Warp Stabilizer more than anyone I know. Several hundred times per week. Yes, per week, no exaggeration. Over the last few years, we've built an entire style of shooting around the strengths of this awesome effect that emulates the use of a slider, steadicam and crane all without having to have them. So we've become really familiar with its PROS and CONS.
Here is a short list of SEVEN things that should be addressed with regards to warp stabilizer within Premiere Pro CC to maximize its effectiveness (and yes we did submit multiple Feature Requests for these so far to no avail):
FIrst and foremost and by far MOST IMPORTANT to us - Allow users to create a CUSTOM PRESET with any altered settings that will engage (or begin Analyzing/Stabilizing) automatically when added to a clip!! This is huge. If you double click on Warp Stabilizer with a clip selected, it is applied to that clip and begins the process of stabilizing that clip. However, the vast majority of the time we need to alter the settings of the effect. If we create a custom preset, that's all fine and good, but when we add that to a clip, it does NOT begin stabilizing. Instead you have to manually go into the Effect Controls for each clip and select ANALYZE. Huge waste of time when adding this effect to hundreds of clips. PLEASE FIX!
BUG when saving projects!!! - If this is not a bug, it needs to be fixed because it's awful. - If you have more than one sequence with multiple warp stabilizations added and GPU ACCELERATION IS ENABLED, then after you SAVE a project (or if it auto-saves) when you toggle between the two sequences you are hit with a delay or freeze while the render bar goes from Yellow to Red...and finally back to yellow again. No work can be done during this delay/freeze. The more stabilized clips, the longer the delay. For us, on our larger projects this delay is sometimes 30 seconds to almost a full minute! Once it turns back to yellow, you can toggle between sequences without the delay...but as soon as it saves again...and you toggle between sequences, the delay hits again. If this is a bug, or somehow a result of Premiere Pro's way of CACHING projects after it's saved, then I sincerely hope it's fixed asap. It's awful!
The third is more of a feature request than a fix - Add the ability to set the maximum scale to work WITH the smoothness control so that if you never want your clips to scale more than say 105%, you can set that and have Warp Stabilizer stabilize the clip and adjust the "smoothness" percentage from the default "50%" down to whatever it needs to be in order for that clip to be fully stabilized and scaled to no more than 105%. Correct me if I'm wrong, but this is not possible currently. Right now we have to manually adjust each clip if it is initially scaled too much by dropping down the Smoothness %.
Another great feature would be the ability to manually keyframe the scaling so that if you have a longer clip that starts fairly steady, then needs to be smoothed out a bit more in the middle, before it ends relatively steady again, you can slowly and seamlessly ramp up the stabilization/scaling so that the whole clip doesn't have to be scaled to make up for the misgivings of one portion of the clip.
Minor bug - sometimes when you have extended the length of a clip, the clip needs to be re-analyzed again. However, the "analyze" button is often greyed out. You need to click away from the clip and then click on the clip again to make that button appear again. Nothing big, but still, a small bug.
After Effects Warp Stablizer VFX feature carried over - It would be nice to carry over to Premiere the ability to isolate what in frame is supposed to be stable (sometimes someone nodding their head can trick the effect into thinking that it's the camera shaking). Great to have it in AE, but would be nice to carry over to Premiere Pro CC.
Finally, I've always believed that no matter how cool "Subspace Warp" sounds, it is not as effective as "Position, Scale & Rotation". This SHOULD be the deafult "method" within the Warp's settings. I'd say 95% of the thousands and thousands of clips we've stabilized we ended up switching the "Method" within the settings to "Position, Scale & Rotation" because it either scaled the shot less or created less "wobble" in the resulting stabilized clip. I know everyone shoots differently, and sometimes Subspace Warp is the way to go, but we have stabilized all sorts of shots with great success by simply switching this setting. Granted...if #1 on this list was taken care of we could then easily have this set as our default setting.
Hopefully this list either reaches someone within Adobe that can do something about them or at the very least inspires others to write feature requests and bug fixes as we have. Even resolving #1, #2 and #3 would be HUGE and would save our editors probably 10 hours per week. It's an awesome effect, far better than "smoothcam" on FCP7, it just needs a little love.

CoSA_DaveS wrote:
All good points, thanks for posting.
For #1, you can make this work in AE at least. This tip is from my colleague DanW:
If you make a preset by only selecting the values you change (and not a preset for the whole effect) then it will auto-analyze on apply.
Simplest way: apply WS, make edits, hit UU to reveal changed params, select all "i-beams" in the Timeline, drag them to the Effects & Presets panel.
For #4, you can get manual control over the scaling by setting Framing to Stabilize Only, and then keyframe Additional Scale to taste. At one point we were going to try to automate this, but found automatic scaling to be very subjective as to the best way to handle it.
For #6, Warp Stabilizer will not track areas with zero alpha channel. So you can pre-mask the input to reveal just the parts you want to stabilize. Do this inside a nested sequence, with Warp Stabilizer applied downstream (in the outer sequence). The just-announced masking & tracking capabilities of the next CC version should be handy for this.
-DaveS, Adobe Dynamic Media, Advanced Product Development
Hi DaveS!
Great to hear that you guys are taking a look at this list. Hope it helps make it better. #1, #2, and #3 are by far the biggest time killers for us so hopefully they'll be able to be fixed/resolved within Premiere soon.
Regarding your note about #1: Allowing this functionality within Premiere specifically would be very helpful. Would it be possible to eventually allow Premiere to auto-analyze when a saved custom preset is applied to a clip? I tried it in AE as you suggested, and couldn't figure it out. But realistically we use Warp Stabilizer on so many clips that round tripping literally hundreds of short clips to AE would be just as time consuming as going into the settings in premiere for each one and adjusting the parameters. We usually adjust the method and then adjust the smoothness scale so that it doesn't "Auto-Scale" more than 104%. That's where our #3 suggestion would help. I didn't quite understand how to make a preset of specific changed values. I tried, but couldn't follow DanW's suggestion. Granted, I'm not that great with AE. I really just use it for the Warp VFX's ability to isolate what in frame is stabilized (hope that comes to Premiere one day) and that's about it. And I really only have to do that a couple times per project. Anyway, I'm sure I'm doing DanW's suggestions wrong but regardless, I'm not sure it would save us much time when we have several hundred individual little clips that would all need to be sent to AE. Any hope for adding this auto-analyze functionality (hopefully allowing a custom preset on the whole effect and all it's adjusted parameters) in Premiere CC?
Regarding your note about #4: That is a valid work around for now. I appreciate that thought. Thanks!
Regarding your note about #6: I think I half understand what you described. I'd have to try it. Although, as I said before, the AE way of doing it is ideal and I just hoped that ability to show the tracking points and delete them over time would come to Premiere CC one day. When the next CC comes out I'd love to try this masking method although I think I'll have to claify exactly what you want me to do just to be safe. Is there no hope to port this added functionality that's in AE's Warp VFX over to Premiere's Warp Stabilizer? Again, not the end of the world for us. I'd rather #1, #2 and #3 be addressed inside Premiere Pro CC for now.
Fixing the first 3 on this list would be HUGE time saver for us.
Thanks again DaveS to you and the rest of the Adobe team for looking into this list. Very much appreciated.

Premiere Pro CC Warp Stabilizer with activated Mercury Playback Engine - GPU doesn't use the Nvidia GTX Titan GPU - CUDA

Windows 7 Pro, fresh installation, include all updates
Premiere Pro CC - actual version
Gainward GTX Titan Z - actual firmware and driver
SSD Hard Drive
Intel i7/ 960/ 3.2GHz/ 32GB RAM
Mercury Playback Engine - GPU is activated.
Card is known by standard in cuda_supported_cards.txt
Selected Clip: 1920x1080i, 25fps, AVCHD/mp4
Seleceted effect: Warp stabilizer with Subspace-Warp (Standard-parameters)
Step 1: Analyse the clip
The Intel i7 is working with 90%, not the GPU
The status monitor of the Nividia-card shows 0% used performance
Playing the analysed clip (informations from the Cuda Render System):
Total render time: 26ms
Display FPS: 0.82
Scheduler FPS: 2.28
Target FPS: 25.00
Rendered FPS: 3.50
Total: 239
Dropped: 234
=> Playing the analysed clip is dropped extremly.
Step 2: Rendering the clip
The Intel i7 is working with 90%, not the GPU
The status monitor of the Nividia-card shows 0% used performance
The Warp Stabilizer is shown as a GPU-Cuda supported effect.
The GPU doesn't help the Intel i7....?!
Please help me!

Thank you for your fast response!
Warp-Stabilisation shall be a GPU accelerated effect.

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.

Premiere Pro CS6 - Project frame won't retain its layout or location between opening and closing?

I filed this as a bug, but perhaps I'm thinking through this wrong and would like to seek help.
I'm finding that the Project frame in Premiere Pro CS6 does not retain its layout between opening and closings.
Here's what I do:
1) Open a project.
2) Create several bins and populate them with media. Expand the contents of a bin by clicking the disclosure triangle to the left of the folder.
3) Undock the Project frame only.
4) Close the Project frame with Command-W
5) Use ****-1 to reopen the Project frame.
Repeat steps 4 and 5. The result is that the Project frame does not remember which bin was open. Furstratingly, it also does not retain which bins were expanded or collapsed.
And worst of all, it will also open in random areas of the screen. (The expected result is that it would reopen in the same spot of the desktop where you last closed it, no?)
I'm a big organizer -- tons of footage across many different bins. I open bins, close them, keep some open, close others... easily dozens or hundreds of times during an edit session. I'm beginnging to feel like I'm swatting flies or playing whack-a-mole just to get my bin views correct!
Or mm I approaching this wrong?

But really, the real solution for me was to not update Premiere Pro CS6 after a reinstall. The most recent updates just do not like my computer, I guess.
Figured I should post this solution here in case anyone in the future has this problem. (relevant: xkcd: Wisdom of the Ancients)
-Sam

Weird hissing bug in Premiere Pro CS6

I'm having a very strange problem with audio in Adobe Premiere Pro CS6.
Whenever I make a cut in an audio clip, a few seconds of broadband hiss is introduced into it after the cut. The hiss is only there in the exported video. It does not appear after every cut but about 10% of them.
The hiss is equally there when I export into different video/audio formats. It is there when I used different editing codecs. It might only be there for clips I recorded using some not so good microphones on a Canon 5D II, but the hiss only shows up after I make an audio edit and export the video/audio or just the audio. Sometimes though it shows up right away in PP before export. If I clean up the hiss in Audition for a given clip I no longer hear it in PP but again it reappears after export.
It seems like the problem shows up when editing video shot on a Canon 5D MII with the in camera mic or several shotgun mics, but not with a decent lavalier mic. Changing the edit and export codecs doesn't help the problem.
(i7 960 3.3 GHz, Win 7 sp1 12GB, Nvidia GeForce GTX 470 1280MB, PP 6.02)

I have not encountered the "hissing bug"
But have encountered something similar to what you describe - but with differences.
When Audio is Cut at a point, that is not a Zero-Crossing, depending on the point on the Waveform, that the Cut was made, there can be a "pop," at that spot. Adobe Audition has the ability to set Cut at Zero-Crossing, but I do not think that PrPro has that capability.
Now, all of my encounters with a non-Zero-Crossing Cut has been the formation of a Transient, which does sound just like a pop (not a hiss) sound. I have never heard a hiss, and I do not think that what you are hearing, is what I am, with non-Zero-Crossing Cuts - they just happen to appear AT an Audio Cut.
Still, you might want to look at the Waveform very closely, just to rule out non-Zero-Crossing Cuts, in case that IS causing what you observe, but just producing a different sound, due to the difference in your Audio material.
Also, have you done a side-by-side comparison in Audition between one of the files with the hiss, and the original sourse file? What differences do you see, where the Cut was made, if so?
Wish that I had more to offer than a slightly similar problem, with a different sound.
Good luck,
Hunt

Premiere Pro CS6 Project Manager gives error & will not manage project - OS X Lion 10.7.5

Premiere CS6 project manager reports an error and will not manage my project. I have tried several times with both "Create New Trimmed Project" and " Collect Files and Copy to New Location". I have also tried to manage the project with options checked and unchecked (Include Preview Files, Include Audio Conform Files, Rename Media Files to Match Clip Names). Every time I try to manage the project, the process takes a few hours and then gives an error asking me to try again.
The project is 90 minutes long and uses multiple footage formats:
Sony FS100
Sony NEX7
Sony NEX-5n
Canon C300
Canon 5DmkII
Panazonic HVX200
My computer is:
Processor 2 x 2.66 GHz 6-Core Intel Xeon
Memory 12 GB 1333 MHz DDR3
Graphics ATI Radeon HD 5770 1024 MB
Software Mac OS X Lion 10.7.5 (11G63)
Is this a bug, or are there specific things I can do to troubleshoot the problem? I have read of issues with AVCHD. I have confirmed all of my AVCHD folders are intact. Any other Ideas?
THANKS!

I have this same problem on a Mac with CS6. I was simple trying to archive a project using the "collect files" option. After five or six hours of troubleshooting (Thanks Adobe) I have narrowed it down to MXF clips that came over in a Final Cut EDL (Projects created in PP with MXF files seem to be fine). In other words, as I was transitioning from FCP to Premiere Pro, I sent four or five projects out of FCP as an EDL, opened them in PP and continued to edit. It seemed to work really well until I attempted to archive my media. If there was a single raw MXF file in the timeline (Not the project panel for some reason) the Project Manager would give me the standard error:"An unknown error occurred during the Project Manager operation. Please save your project and retry the operation.".
I have found two solutions that seem to work, both of which are a pain in the ax.
Option 1: Save the original project file only to an archive folder. Then delete all the old timelines from the project, and save the project with a new name. Create a new timeline and just drag all the raw video and audio into it. (Project Manager needs a timeline of some sort to archive) Then use the Project Manager to archive the modified project. If I need the project in the future, I'll need to open the original PP project and relink all the media from the archived "media only" project folder.
Unbelievably, if you were to take this route and then re-edit the project in the future, it looks like you would run up against the same archiving issue AGAIN next time (At least using CS6). You'd have to go through all the steps above to archive it a second time. Depending on the size of your project, you may want to take option 2 and get the pain over with once-and-for-all.
Option 2: If you only have a couple of MXF files in the timeline (in my case I had mostly renders from AE by the time I was done and THAT raw project had archived in AE just fine) you can export the raw MXF files to another format, then replace the media in your project panel. Finally, use the Project Manager to archive the project like you should have been able to in the first place if Adobe had written the code well in the first place!

Project Bloating and Repair in Premiere Pro CS6; Max Project File Size? Adobe Coders Welcome...

Greetings.
After a few browsing sessions, I haven't found direction for a specific problem within a project bloat. First and foremost; we're always backed up. I have a restoration copy of the project that I will reference herein. Check that off the list.
Numerous people have posted here and around Creative Cow with problems regarding an expanding file size using CS6; watching files go from 300mb to 2.8gb. The unfortunate problem is when the project crosses a magical line that results in an inablity to open, import, export, or access sequences contained therein. Has anyone addressed a solution to repairing Premiere CS6 save files? Reducing file bloat? I haven't seen anything (recall the FCP7 repair days... solutions existed because problems were frequent; thankfully not so bad with Adobe).
Does anyone inside the code size know the maximum project file size that Premiere can read? I created a monster... Over 200 sequences utilizing 4.5TB of footage, stretching from Red codecs to EXCam to MPEG4 and H264. And for some time, the project size was manageable. Then, it inflated. And one day, randomly stopped opening. None of the auto-saves open.
Just curious. Files aren't the problem, but the 2.8GB save file is. Machine specs // etc. are openly available if required; no bad ram, no problems with all projects (just this one beast).
Cheers,
Jon Michael Ryan

REALLY_ Mac has a history of being more stable than PC with Premier ...
Pastor Bernie
International Evangelism Coordinator
Global Teen Challenge
visit us on FACEBOOK (http://www.facebook.com/bernie.gillott) or on
twitter-just tweet globalcry
~~~~Pray Big or Stay Home~~~
www.bgillott.org (http://www.bgillott.com/)
426 Newport News Ave, Hampton VA 23669
Phone (757) 728-0347 cell (757) 218 8499
In a message dated 6/2/2013 5:50:50 P.M. Eastern Daylight Time,
[email protected] writes:
Re: Project Bloating and Repair in Premiere Pro CS6; Max Project File
Size? Adobe Coders Welcome...
created by joe bloe premiere
(http://forums.adobe.com/people/joebloepremiere) in Premiere Pro - View the full discussion
(http://forums.adobe.com/message/5373302#5373302)

How to work on a portion of a larger Premiere Pro CS6 project on another computer?

I have a very large Adobe Premiere Pro CS6 project that I'm working on at home. While I'm gone for the holidays, I'd like to take a small portion of that project (whole project is 6tb and too large to take, so I'll take 1tb of it), work on it, and then return and reintergrate it into the larger project. Is there a way to do that?
Thanks,
Lucian

Mark,
I migrate Projects with external FW-800's all of the time. To ease working on those Projects, I locate all of my Scratch Disk, Same as Project, and everytihng is always there, and ready for use. I do give up a bit of ultimate performance with this configuration, but never have any issues.
One thing that I do for each external is to assign the same, unique drive letter to it in the OS of each computer. Have you done this? Does your RAID box come up with the same drive letter in each computer - always?
Good luck, and with migration between computers, you might want to relocate the Scratch Disks. Please let us know if that helps.
Hunt

Time Warp Effects in Premiere Pro CS6

Enabled Time Warp Effects in Premiere CS6: Ctrl+F12, TimeWarpFilterEnabled > true.
http://translate.google.ru/translate?sl=ru&tl=en&js=n&prev=_t&hl=ru&ie=UTF-8&eotf=1&u=http %3A%2F%2Fwww.efxi.ru%2Fmore%2Fpremiere_pro_cs6_time_warp.html

Works on my Android Nexus 7.
Anyway, here it is:
Turning Time Warp effect
Consider the example of the inclusion of qualitative change speed with the aid of the Time Warp (creating the effect of "stretching" the time or time warp) in the program Adobe Premiere Pro CS6. As we all know by default, this effect has been disabled in the version of Adobe Premiere Pro CS5, but you can turn it on. Press the keyboard shortcut: Ctrl + F12 and panel Console, switches to Debug Database View:
Paragraph TimeWarpFilterEnabled instead of trying to drive a false true. Restarting the program Adobe Premiere Pro CS6.

Premiere Elements Project file wount open in Premiere Pro CS6

My friend Just bought Premiere elements 13 and created a Project. I cant open the Project in Premiere Pro CS6. Getting this error message:
"The Project appears to be damaged, it cannot be opened."
The Project workes fine in Premiere Elements 13
What can I do? What is wrong?

If you have done this:
Import a Premiere Elements project (Windows only)
   Select File > Open Project.
   Browse to an Adobe Premiere Elements project file, with file extension PREL.
   Click Open.
Premiere Pro converts the Premiere Elements project file to a Premiere Pro project file.
and it wont work Elements 13 is probably too new for CS6.

Premiere Pro CS6 crashes whenever I go near Project Settings

Hi all
I am using an official trial version of Premiere Pro CS6 as part of Creative Cloud. I am editing on my MacBook Pro 17" (newest model) with h.264 footage recorded on my Canon 550D.
Everything works fine, imports and edits like a dream. However, during editing, if I simply go to Project -> Project Settings -> General - then don't even change anything, just ok out of the dialog box then it crashes.
When I say crashes, the video disappears and I cannot do anything at all until I exit out and reboot. No messages appear until I do a 'force quit' and then I get the standard "A serious error has occurred" etc.
Of course the obvious solution is to not select Project Settings when editing! Which I will do for now, but I would like to think that I can change any settings I like without it crashing every time!
Any thoughts?
Regards
Jason

On reading the advice on a separate thread I updated OSX from 10.7.3 to 10.7.4 which seems to have fixed the problem. Probably should have checked that first!

Premiere Pro CS6, large project file size - crashing etc

Working on a project in Premiere Pro CS6 - also incorporating after effects and using 2 external plugins (Beauty Box and Factory Pro FX). Project is over 500MB, lots of comps, titles etc. project seems to be corrupt on my machine. .The project crashes continually. I cannot save my work, I cannot export, I cannot create XML and media is linking incorrectly. When I pull the project in on my laptop (separate machine) which has CC 2014 running, the project is FINE. That said - I need to work off of the more powerful machine to do this job - so need to find a way to troubleshoot. Note - project opens on my partner's machine, she can save + export, etc - however the media in still linking incorrectly on her machine as well (note partner does not have the 2 plugins, beauty box and factory Pro FX) - that said, it still links to the wrong media.
We have worked out a work-arond where we pull all of the AE sequences out of Premiere and into separate AE project which has made the project workable again but we know something is WRONG and we need to fix for future ASAP.
please help!
thank you

REALLY_ Mac has a history of being more stable than PC with Premier ...
Pastor Bernie
International Evangelism Coordinator
Global Teen Challenge
visit us on FACEBOOK (http://www.facebook.com/bernie.gillott) or on
twitter-just tweet globalcry
~~~~Pray Big or Stay Home~~~
www.bgillott.org (http://www.bgillott.com/)
426 Newport News Ave, Hampton VA 23669
Phone (757) 728-0347 cell (757) 218 8499
In a message dated 6/2/2013 5:50:50 P.M. Eastern Daylight Time,
[email protected] writes:
Re: Project Bloating and Repair in Premiere Pro CS6; Max Project File
Size? Adobe Coders Welcome...
created by joe bloe premiere
(http://forums.adobe.com/people/joebloepremiere) in Premiere Pro - View the full discussion
(http://forums.adobe.com/message/5373302#5373302)

Premiere Pro CS6 - Warp Stabilizer BUG causes project to crash

Similar Messages

Maybe you are looking for