Stabilizing a clip

Let me try this approach to my problem - can someone advise me on the simple step-by-step method of stablizing a clip. I would like to (I THINK) keep each clip as a "standalone" processed clip identified by it's original numeric reference, and i'm not sure if i should leave AE open and running while i search for the next clip in my sequence to stablize, or shut it down after stablizing each clip, and if i should save the stablized clip as "clip33stablized" or something on that order, OR if none of that is necessary at all; i just need to assimilate the processed clip as it dynamically links back to Pr.
I am used to finding workarounds as an experienced AVID user, but am new to Pr - i have the complete suite CS5.5; plenty of horsepower dell 8300 8G at 3.4 Ghz and 5TB storage.
At this point, all i need to do with AE is stabilization, and have gotten it to work correctly - USUALLY - but have had a few quirky exceptions - namely, that the processed clip i end up with in Pr is NOT the clip i just stabilized...with the same result after several different approaches.
hopefully i have the vocabulary correct enough to explain myself..
thanks for any help!

Kevin~ thanks for your offer to help with this...
attatched is the response i have written, per your request for more details....
as a relavtive newbie, i am doing my best to assimilate the huge topic
of AE, but only want to use the stabilizer for now:
•What version of After Effects? Include the minor version number (e.g., After Effects CS5.5 with the 10.5.1 update).
Cs 5.5 with the 10.5.0.253 update
•Have you installed the recent updates? (If not, you should. They fix a lot of problems.)
Entire package was installed less than 90 days ago – is there a more recent update?
•What operating system? This should include specific minor version numbers, like "Mac OSX v10.6.8"---not just "Mac".
I’m running windows 7 home premium version 6.1 build 7601 SP1
•What kind(s) of source footage? When telling about your source footage, tell us about the codecs, not just the container types. For example, "H.264 in a .mov container", not just "QuickTime".    Please tell me how to get info per your suggestion (like H.264…) etc
copied from properties:
File Path: C:\Users\Don\Videos\2012-05-14 como shoot\00001.MTS
Type: MPEG Movie
File Size: 132.8 MB
Image Size: 1920 x 1080
Frame Rate: 29.97
Source Audio Format: 48000 Hz - compressed - Stereo
Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
Total Duration: 00:00:53:00
Average Data Rate: 2.5 MB / second
Pixel Aspect Ratio: 1.0
•If you are getting error message(s), what is the full text of the error message(s)?
Following is a step-by-step Sequence: (I am only documenting this as I go, and may NOT be the precise
Steps I had taken before. )
select clip on PrPro timeline, r click and select “replace with AE comp”; AE opens, and I name the project;
AE opens. I select my footage from the project panel, where there are 3 items listed. 00003.mts (my footage), and
“MPEG” as the type…and aqua label in the center with the standard AV file windows icon (a film strip with a
musical note superimposed) – above it is an Item with the same name, 000003.mts, a film strip icon and
sandstone label; the preview at the topshows this as the 1440X1080 (1.33) composition panel item, and the
one below says “ZOOshoot linked comp #65”,the ZOOShoot being the name of the PrPro project.
At this point, the indicator bar color in the timeline panel has changed to aqua from sandstone and
composition panel has three tabs showing composition 000003.mts, footage 00003.mts,and layer 00003.mts.
I select layer, and the composition panel now shows the timeline ruler and expected icons along
the bottom of the panel. I select Animation/Stabilize Motion from the top menu, and the stabilizer starts up, tracking
it’s progress.
I can see on my other monitor that the clip I originally selected turned to a lilac color as soon as it was
linked to AE (not sure if before or after naming the clip). After the stabilizer completes, the clip area render bar in
PrPro turns yellow, and I “render entire work area”. The clips plays normally. The audio portion has not changed
Color, as expected, and I see from the descriptor on the audio portion that this particular clip had and extended
Duration, playing at 68.22 %, but apparently integrated into the stabilization, since the clip fits perfectly.
Step #2 – I select a second clip, later in the timeline, right click and select “repl w AE comp” –, which is still running,
And I have NOT saved the previous clip THIS time, there is No request to name the project, which is a bit confusing to me, since THIS clip is definitely different, HOWEVER, AE responds with “saving project” popup window, and takes
A second to save it, before The new clip actually appears in the project panel. The appropriate three items appear
In the project panel, along with the original clip data that was already there. Other than the clip numbers now being
00010, the linked comp number has incremented, as expected. I select each “00010” item, and make sure that IT is
The image in the composition panel;.
AT this point, I am ceasing the processing, since I now have a situation where
The composition panel is showing inconsistent results in the tabs; i.e., composition 00010, footage 00010, and layer
00003.   I use ctrl-Z to back my way out, until there is NOTHING in the project panel, and the selected clip
In PrPro has now reverted from it’s lilac color – I begin the process over, notice that AE does NOT request a project name, but now the project panel has only items referring to clip 00010.   It may be that I have heretofore not
Observed each change along the way, but, even though having gone through the “basics” tutorials many times,
Have found no reference to specific steps that I am missing.
•What were you doing when the problem occurred?    See above
•Has this ever worked before? YES
•What other software are you running?   Usually nothing other than PrPro and AE, possibly Internet Explorer, and
MS Word, for reference and documentation.
•Do you have any third-party effects or codecs installed?   Not that I am aware of…
•Tell us about your computer hardware. Include CPU type and number of processor cores, amount of RAM installed, GPU, number of disk drives, and how any external drives are connected. Dell 8300 8 processors # 3.5 Ghz, 5TB storage
W 1.5 os drive, 3 external WD drives, 500G, 1T, 2T, those drives being USB
•Do you have any third-party I/O hardware (e.g., AJA, Matrox, Blackmagic, MOTU)? NO
•Are you using OpenGL features in After Effects?   I guess not…(?)
•Does the problem only happen with your final output, RAM preview, or both?   Originally, before problems developed,
I was using no preview at all, just returning to PrPro and rendering the stabilized clip.
•Are you using Render Multiple Frames Simultaneously multiprocessing NO
NOTE:   At this point, All I need to use in AE is the Stabilizer; being referred to the tutorials that “open an entire
World” of movie manipulation and FX is not helpful; I am perfectly willing to study that portion that relates
To my issue here, but have spent way too much time with non-useful tutorials.   In the interim, it has been
Suggested that the entire issue is with the dynamic link, and that I could simply START the process in AE, and
Export the link to my PrPro project, which is an acceptable workaround for me.
Thanks, Don.

Similar Messages

Stabilizing node clips the shot?

Hi all! I have a question that's driving me nuts:
(English is not my first language so bear with me)
I have a shaky shot that needs heavy cloning and painting. The plan was to stabilize the shot, paint and then destabilize it to apply the same movement it originally had (I read this in the manual) everything went fine until I destabilized it: I noticed the shot was now clipped where the first stabiliation node had run out of space (don't know if I'm explaining myself).
Shake composites in infinte space, right? Why is the shot being clipped, what am I missing?
My client is getting here tomorrow so any help would be ENOURMOUSLY appreciated! : D!

Sorry this is late for your client review...but...
Quickpaint clips the "infinite space" by cropping the image. It is an awful behavior.
Since you already did the paint work, you can do as Patrick outlines above - just use SetAlpha to make the image alpha solid 1 before the move/paint/move & then Over the painted/destabilized over the original. Bear in mind that the stable/destable operation will soften that image slightly. The original will not be similarly softened...so you'll have a hard edged division between slightly soft & original sharp. (This may not be visible to the normal naked eye...but if someone likes to pick pepper out of flyshit...). Also, if your paint breaks frame, this method will yield a hard edge somewhere...but it doesn't sound like you'll have this problem.
Next time, use the Crop node to enlarge the stabilized image enough to keep the image in view throughout the sequence. Paint that, destabilize & crop back down to your original size.
Best of luck,
-G

Stabilizing synchronized clips

I have encountered a problem when I synchronized two 5D clips with an external audio clip and then tried to stabilize the videoclips. In the synchronized clip the stabilizer is not active, so I opened it in the timeline and applied the stabilizer to the two videoclips there. It did stabilize, but did NOT apply a zoom to make the stabilization invisible. Instead the video wobbles around the frame. Tweaking the scale zoom handle has no effect. Does anyone have an idea how to solve this? Thanx!!

In other words in a synchronized clip everything is fine,when syncronized with the song audio...but when I put this syncronized clip on the same audio clip on the timeline I find it longer than the song audio , when I go inside this syncronized clip again the length is the same ...why on timeline the clip becomes longer and audio lags and gets distorted like a base voice......
I wish there was synchronization feature on the timeline than the event......

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.

FR: Big yet incredibly simple improvement to Warp Stabilizer

I love the Warp Stabilizer effect in PP. It's great! But depending on the footage and the effect's settings, sometimes it can actually make things worse. This means that any time this effect is used, users must review of the results after the effect finishes analyzing the clip.
Here's the problem:
Analysis takes a long time, often far too long for a user to stop editing and wait to review the results. In my case, I keep editing, but often I forget where my stabilized clip for review is located. In a multicam sequence, where every video clip occupies the same track, there's little to no visual cues to remind me where the Stabilized clips are. Setting an in and/or out point as temporary markers can work if you have up to two Stabilized clips. But what if you just stabilized 5 clips, and you want to keep editing while they're being analyzed? How do you visually recognize which clips they are? All current solutions add work for the editor, such as moving stabilized clips up a track and then back down after approval of the effect's results, etc. If you have transitions between a Stabilized and an adjacent clip, or clips on a track above it, the situation gets worse.
Here's the (incredibly simple) solution:
Give us a visual color cue any time a clip has the Warp Stabilizer effect added to it! This could be done through a new user selectable color category in the Preferences window's 'Label Defaults' panel.
It's interesting to note that while 8 different colors can be set in the Label Colors tab, only 7 are currently used by PP in the Label Defaults tab, so setting a unique color to this new eighth item should be even easier to program.
Adobe, this would make a great little addition to your next PP update!
What do others think?

Jim Simon wrote:
Your request calls for easy visual recognition of that one effect, mine calls for easy visual recognition of any effect, which I feel would be far more useful to far more editors.
Be as it may, even though I highly doubt that editors need an easier way to determine which clips have any effect applied in general, WS clips would still have to have a different color, otherwise editors wouldn't be able to differentiate WS effects from any other old effect that simply does not require the editor pause or return later to see the results. I've explained this pretty clearly but it seems you're determined to not get it.
Jim Simon wrote:
Or, if you don't want to wait for the effect to finish, add it after editing, as most editors do with most effects anyway. Then you'll have the time to wait to see the results.
Adding effects is part of editing, or isn't it? In case you don't know, editors work differently. If I want to add effects as I do my cuts, what's wrong with that? The software should be intelligent and flexible enough to accommodate a user's workflow. And if it isn't, then it should be improved. If you're an advocate against this kind of progress and think users should adapt to and accept a programs limitations, rather than speak up, which version of Premiere are you using? 4.1?
Jim Simon wrote:
Mark them, as you can do now.
The whole point of this thread and FR is for Premiere to remove steps from our workflow! Still don't get it, do you?
It seems that every time I expose a limitation in Premiere or an area for improvement, you suggest that I should change my workflow rather than have the software improve in a way that could benefit countless other editors. At this point, I really have to ask... what's in it for you Jim? What's your point?
"Then you'll have time to wait to see the results" Is that what you do, wait 10 minutes for a long clip to finish analyzing so you can see the WS results? You're just sounding more and more ridiculous IMHO. It would be nice if overall you made more intelligent contributions to my threads.
Frankly, I'm getting tired of this nonsense Jim. If you have something intelligent to say, please, by all means. If you don't, please stop diluting the message of my threads with your nonsense arguments/comments. If you want all clips with effects applied to them to be labeled with the same color, and thus make WS clips visually indistinguishable (which is the current problem I'm asking Adobe to fix), go ahead and start your own thread.

W530 Quadro K2000m and Premiere Pro CS6

Hi all,
I have a W530 with i7, Q K2000m, 32gb ram and 3 interal drives (1msata ssd, 2 hgst 7k1000 1tb in the other two bays). I don't know whether I have an issue or not, but:
1) CUDA acceleration is enabled. So we're OK in this.
2) When I assemble a few clips together, although the render line is yellow, after a few seconds, the videos start becoming choppy. So, I was wondering how can this because I am only editing a 720p timeline and I have not graded anything yet. Just warp stabilizer on some clips and some of them (since I shot at 60p) are slowed down to 24p.
3) When I run GPU-Z, I am only seeing a 8-15% GPU load rate.
4) Because I can't reverse time and stabilize at the same time, I stabilized a clip on another sequence and then nested that sequence in my main sequence. Now, when I reverse that nested sequence...I get a blank screen UNLESS I kill the hardware acceleration and switch to CPU only (this seems to be a Premiere Pro issue)
5) I did everything possible to make sure that the Quadro card was working. I turned everything to "Performance NVIDIA graphics) in the NVIDIA control panel. I installed the latest drivers from NVIDIA the day before yesterday. I even flashed my BIOS to the latest downloadabale from Lenovo's System Update.
Am I missing something? Or is the card just underclocked and under-powered on purpose? Why can it not run at beyond 15% load when the clips are choppy on playback?
You may noticed I am a bit frustrated...but hey...I love the machine so I hope I am missing something that I can set up to make it all run smoothly again.
Many thanks for any ideas, guidance.
PS: All captured clips are in the 1st HDD on the main bay and the scratch/preview disk is the 2nd HDD on the CD drive. Premiere is running from the mSATA SSD (Plextor M5M 256GB)
Solved!
Go to Solution.

I don't have Premiere, so I can't see by comparison what happens on my own W530 which only has a K1000m. I also don't know if your symptoms are due to hardware or sofware (i.e. Premiere itself). Do you have another machine of your own to try the same experiment against, to see what GPU usage measures at and whether the visual results are seemingly as poor as you describe on your W530, or are they much better visual results and much higher performing as measured?
Aside from our both doing something in common, to compare results, I just took a look at two video applications on my own W530: (a) VideoReDo TV Suite 5 editing both 720p and 1080i copy-freely WTV recorded videos made by Windows Media Center (on my HTPC), and (b) Windows Media Center running on the W530 and playing both of these 720p and 1080i WTV recordings. I opened GPU-Z while the video apps were running to monitor the GPU load. I also have Aida64 running, which also displays presumably the same "GPU utilization". I expect VRD to use less GPU horsepower than Windows Media Center uses.
Also, here is my Lenovo Power Manager setup, with my i7-3720QM 8GB W530/K1000m 512GB Samsung 840 Pro SSD powered into the wall. The display is external 24" Eizo S2433W monitor (miniDP->DP from the W530), 1920x1200, laptop screen OFF. I'm running "discrete graphics" in the BIOS, using "retail" nVidia driver 347.88.
And here's Windows Media Center playing a 1080i video (which involves hardware de-interlacing), and showing 57% GPU load through GPU-Z. Note that with Aida64 (on the right side of the image) it also shows 55% GPU utilization, so this number is clearly correct.
And the same clip being "edited" using VideoRedo. Note that GPU usage is now down to 35% (at least at this instant), as I expected. I'm quite sure hardware de-interlacing is also taking place.
Video performance with both apps is superb.
Anyway, without our being able to duplicate the other's test situation, I don't know what to suggest that you haven't already done. Unfortunately I don't have Premiere to try.

Stabilize not applying correction to video?

I am having issues with Stabilize in Motion 5. I have added a couple of trackers and run the analysis and Motion generates the motion vectors on screen. However, when I play back it appears the motion vectors are not being applied to the video - the video shakes just as much as it did before, and you can see the motion tracking overlay still showing the motion vectors. Am I missing something obvious here? How do I actually get Stabilize to stop the shaking?

First of all, I must confess that I have not used Stabilize very much at all. It usually works great with the default: add + analyze (no trackers.) So, I found one of the worst clips I could find and tried out various things with it and I have to admit, ***your problems are EASILY reproduceable***
PLUS, in Motion 5, once you get a bad track you will never get a good one!!! not in the same project no matter how many times you delete and re-add a Stabilize behavior. On that bad test clip I used, I got a good track ONCE. Then I Added (not duplicated) a new copy of the same clip and tried using a tracker. The track is perfect, the playback just moves the entire video around like it's a Match Move on the track. Tried deleting the tracker; Analyze again, and it's stuck with the same movement that went with the tracker. Tried deleting the retiming cache (it's used for Optical flow and other motion things) and nothing. [Meanwhile, rechecking the original perfectly stabilized *same* clip originally imported "new" — still perfectly stabilized — to add insult to injury, if I use the tracker data (that is, if I put the first clip in the drop well) from this clip in the 2nd import clip - the stabilization is exactly the same on the 2nd clip... which is completely pointless if you can't get the "right" stabilization to begin with!] [PS- by "perfectly" I mean it's the best possible stabilization I could hope for: most of the clip was rock solid, but high jitter/jerk areas still had some "blips" in it -- lined up fine -- but a quick re-scale kind of thing -- it was a really bad clip ]
Went into Motion 4. I didn't like the way Stabilize trackers worked for my test, deleted them, re-Analyzed with no tracker: WORKED PERFECTLY. No matter what I did to mess up the stabilization on purpose - I could always delete the trackers and re-Analyze without having to delete and replace the behavior - and start over again like I had just added the behavior. Motion 4 worked like you would expect it to.
So... I would have to say that Stabilize is YET ANOTHER BROKEN SOMETHING IN MOTION 5!
But back to your problem. If you have Motion 4, use it to stabilize your video, export (as prores) and import into your Motion 5 project. If you don't have Motion 4... Open a brand new project; import your clip; Add Stabilize (NO TRACKERS); cross your fingers. If you get a good stabilization, export it out for future use.
By all means, let Apple know of this problem via the Provide Motion Feedback menu item under Motion.
Your specific questions: I would say if you have Motion 4, you could use the tracking region in that way, but I tried it in M5 and the Region is also a tracker and that will mess up the stabilization. If you only have M5, create a new project, import your clip, add the levels and adjust it for a "bit" more detail, add the Stabilize and Analyze only. You basically get one shot to get it right... per project per clip (maybe that's pushing it). Even in Motion 4, if the clip is in pretty bad shape, Stabilize does its best to get "most" of the clip right— so you may have to opt trimming out pieces that won't stabilize as well [in my experience, most often, that will be at the beginning and the end when you make contact with the camera to both start and stop recording, or to zoom.] You might also consider trimming the ends of the clip a bit beforehand as well because, no matter how you line up the clilp in the timeline, Motion analyzes the *entire clip*, no matter what!
Anybody else notice the lack of a Motion 5.0.2 update when FCPX 10.0.2 came out?? I'm still waiting. Every day I check— at least 3 times. M5 must be really badly damaged to be taking this long (and I have found A LOT of problems with it... most of which won't affect the average user... but stil!)

Problems with After Effects on Mac OS

I find it insulting that Adobe does not respond to these posts.
At least tell us they are aware of issues and are working on them .. with some sort of timeline.
Of the dozens of crash reports that I sent directly to Adobe with their own Crash Reporting app .. I NEVER ONCE recieved a reply that they confirmed my reports.
I will have to spent a good portion of my time to make a complete report soon ... time I do not have due to lost workflow and projects that need to be redone.
The Mac OS X "Activity Monitor" is what tells me how the Adobe Suite is performing.
Currently ... I am "Warp Stabilizing" a clip. 12 of my 24 hyperthreaded processors ( 6 cores ) are actively analyzing the background and stabilizing.
Stabilizing .. Cropping .. and trimming / cleaning up clips is all I have been doing .. and it has been tedious.
To load a 1650 frames clip from PP to AE via Dynamic Link takes 3 min. Only 2 hyperthreaded processors of the 24 are in use while this occurs.
Everytime I add another clip .. AE saves the entire Project .. which takes an increasingly long amount of time everytime additional clip is added.
It locks up AE and PP while this occurs. Nothing is available. You just have to sit and wait. Sucks!
Stabilizing in AE can occur while you are using PP. This seems to be the .. cont.()

Yes .. Todd you have been more than helpful .. and I'm sure your familiar with my frustration ( and others ) by now.
Adobe policy should include at least a confirmation that the crash reports were recieved and at least read.
Im not sure that this makes sense to everyone ... but being a new PP / AE user ( and others who migrated from FCP ) have a unique experience coming to the Suite.
We can see issues and snags in the workflow that legacy users and employees are so used to that they are unnoticed and overlooked.
Take for instance this AE "Saving issue" I am experiencing:
There should be a way to turn it off.
There is no reason I should have to wait for AE to save and save and save everytime I load another clip in from PP via Dynamic Link.
Maybe this is the 'way' it's been done .. for Adobe .. but it seems to be cause a giagantic unneeded time consuming issue while working a project.
It is possible there is a Preference I have over looked .. and maybe another user / employee knows where to find it.
If not .. I can fill out the "Feature Request" .. which I have done before .. and which has NEVER been replied to that it was recieved or noticed.
I post here on the Forum mostly when my Mac Pro and Adobe Suite is locked up in 'processing .. and I can't do anything else with the project.
Maybe if other Mac User that read this .. and are frustrated too band together we will get noticed.
Maybe Todd your a good friend to us .. It seems so ... maybe one day you will get tired of my posts and print them, walk down the hall, and present them to the board of directors and ask that Adobe give us some extra attention before we / I post another negative comment.
I just want to get my work done .. I had big hopes with this system .. and one year later Im still aggrivated more than I should compared to other PC users that seems to have few of these issues.

Dynamic LinK to After Effect makes export freeze

Hi everyone,
I had previously posted on the Encore Forum, because the problem first appreared when trying to DL a sequence from Premiere to Encore: it took almost 6 hours for 15 mins of video, then it froze. Then I tried to export directly from Premiere, it took less (3 hours or so) but it froze nonetheless.
I found out that it froze exactly in the same spot, that is when it came to a DL from AE. It was a 30 secs composition in which I had simply stabilized a clip, no other effects were there. So, no matter what, when I try to expot the sequence, it blocks when it comes to the DL.
The problem is also that neither Encore nor Premiere showed me anything about it before exporting; both regularly started encoding, only to freeze at a certain point. In this way, I can't and I won't be able to realize when something like that will happen again. I mean: How could I know when a DL will create problem when exporting? The fact is that other DL worked fine.
Does anyone know if there is something I should check in order to have DLs work reguraly?
Thank You

Yes Jim, you're absolutely right - every 'common rule' is arbitrary, and it's up to everybody do decide what suits better in one's particular circumstances or a certain workflow!
Regard to 'several minutes' as a guideline, it was just a free quotation of Rick's comment in my thread about dealing with 'heavy' AE comps...

Final Cut renders motion files, but displays them as blank

I ran into a problem today with final cut. I had a clip I wanted to stabilize, so I selected the clip, right clicked, and sent to a motion project, stabilized the clip all fine in motion, saved it, and returned to final cut. Like it is supposed to, the click reappeared, but as the motion file. It needed to be rendered, so i rendered just that clip, and then tried to play it back, and everything was blank in that clip. There was audio, and no video. I would like to figure out why its blank.
Any suggestions, I'm running the latest version of final cut and everything is up to date.
Your assistance is greatly appreciated, and happy new year!
Message was edited by: markklassen

almost impossible to tell from here. First thing to try is to export the clip from Motion, render it from Motion, and open that movie. If it's blank, well, you've got a problem with the source media and we start with a long list of other questions. You'll probably solve this yourself by trying to make the process as simple as possible, open a new project, import a short clip (SmoothCam tends to analyze the entire source clip unless you know how not to do that), and process it from FCP, there's no need to send it to Motion for SmoothCam.
bogiesan

Chroma key after fixing movement in motion

I created baseballs flying around in fcp with a sky background. The moves were jerky so I sent to motion and smoothed the movement. I brought it back to FCP applied the chroma keyer to remove the green screen. When I do that the green goes away but the background goes black. Why does the sky layer below disappear when I turn on the chroma keyer?
Also why doesnt motion have croma keyer. Color keyer does not work as well as chroma key.

dougleax wrote:
I created baseballs flying around in fcp with a sky background.
You created them? You mean you edited together some video clips of baseballs? Or you mean you animated a graphic of a baseball? Big difference. Big difference in how we will advise you to move along.
-It is a video of rotating baseball against a green color animated to look like being thrown.-
dougleax wrote:
The moves were jerky so I sent to motion and smoothed the movement.
You should only process the original media. I cannot tell from this statement if you know how stabilization actually works. If you are chromakeying the stabilized video clip, you may want to perform additional work on it. For instance, is the shutter speed high enough to reduce image blur? Is the footage interlaced?
-No stabilization used. The movements is FCP were Jerky between keyframes. FCP motion is hard to control. Thats why we use Motion...to smooth the movement..correct?
dougleax wrote:
I brought it back to FCP applied the chroma keyer to remove the green screen.
Ah. So your original statement about creation in FCP was misleading or incompletely descriptive. Is this a still image of a baseball against green? Or are these video clips of off screen hands tossing baseballs across the screen? If they're video, don't stabilize them, reshoot it with the camera on a tripod.
-I brought it back to FCP. When I did the original Chroma Keyer was lost.-
dougleax wrote:
When I do that the green goes away but the background goes black. Why does the sky layer below disappear when I turn on the chroma keyer?
Then you're not using the keyer properly. You may be looking at the matte or the processed key and not the output or final image.
-turn on keyer the green goes away and the sky image appears where there was green, but the rest of the background goes black.-
dougleax wrote:
Also why doesnt motion have croma keyer. Color keyer does not work as well as chroma key.
The blue/green keyer in Motion is fabulous. Why are you using the color keyer?
-From what I see in tutorials, people suggest to use Primatte RT. In FCP Color keyer has more control over how it affects highlights and shadows, Hue range.-
Motion has 5 keying options. FCP has about 10. I just like the was Chroma keyer works for my purposes.

Can I export Warp Stabilizer Data?

I have two identical video clips, they match frame for frame, however one of them is under exposed and is a lot darker. Therefore it is a lot harder for warp stablizer to work.
Can I somehow export the data from the warp stabilizer on the clip that it works on to apply it to the under exposed clip?
I would use Mocha to stabilize the shot, but I am having difficulties with it, since it requires frames to match throughout and my shot is rotating.
Any help is greatly apprecaited TIA

If you have identical footage then you either had a motion control camera, and even then it's highly unlikely to be exactly frame for frame unless the rig was very big, heavy and expensive and your actors were robots because anything moving in the scene would throw off the warp stabilizing, or the camera was locked down and there was nothing moving in the scene. There must be some differences in the shots or there would be no need to work on the one that is under exposed.
There is nothing keeping from you from making exposure or color grading adjustments on the original clip then pre-composing or rendering a clean copy, and warp stabilizing that clip. I don't think anything else is going to work.

Memory using Warp Stabilizer

This is bull. Here are my specs. 12 core mac pro, 2.93 Mid 2010. 32 gb ram. Radeon HD 5870 graphics card, and ruinning on prmiere pro cs5.5 and after effects. I am tryiung to use the new warp stabilaztion effect in after effects and after effects in general does not utulize any of my cores let alone the ram. It is stupid. If you look to the top right of the pictures at my mac menu bar, you would see bars for all my cores and only one is utulized. check out some pics while stabilizing my clip:
What the hell am I supposed to do to speed this s=process up.

The Warp Stabilizer effect is processed in the background so that you can continue working in After Effects while the analysis is taking place. It is deliberate that the Warp Stabilizer isn't consuming all of your resources, allowing you to continue to work in After Effects as normal while the analysis is done.

How can I reset/undo a movement stabilized clip?

Hello everybody,
My question is regarding the dominant movement stabilization that Final Cut Pro X can do. It's very clever, but sometimes does more harm than good, the clips turn into funhouse funhouse mirrors. I believe it's doing its best with my shaky footage, but I can't figure out how to undo a stabilization of a given clip, or reset it – does anyone know how this can be done?
On non-stabilized clip I have the option to Analyse and Stabilize, as well as a Stabilization item in the Inspector. Here I can customize it manually.
But on a clip already stabilized via Analyze and Stabilize there is no Stabilization item in the inspector, and no mention that the clip has already been stabilized. It's a bit too Microsoft for my taste ('I know what's best for you') if I have to accept the application's fix.
Of course I could reimport the media all over and not have it stabilize it, but this clip is already edited on my Timeline.
Any input appreciated - thanks!
Thomas

Just some images for illustration.
Inspector for non-stabilized clip:
Inspector for stabilized clip (via Analyze and Stabilize) – no stabilization item:
And the contextual menu option Analyze and Stabilize on a non-stabilized clip, any mention of stabilization is gone on an already stabilized clip ...

Problem with transitions after stabilizing clip

Most often, but not always when I add a transition to a stabilized clip i get a jump, in frame size in the stabilised clip. Does anyone know how to fix this?
I've seen some one ask this but not had any replies.
Using latest which I think is 10.1.1

Try turning the clip that "jumps" into a compound clip and apply the transition to that. (I'm just guessing here...)
Also, the "latest" FCPX is 10.1.2 which seems to have fixed a lot of problems that were cropping up in 10.1.1.

Stabilizing a clip

Similar Messages

Maybe you are looking for