Warp Stabilizer progress status

Hi,
I need to get an alert when the stabilization process is complete.
So i try this :
i am reading the first three text labels on the effects panel :
During analysis:
the first label is empty
the second label display alternatively 
Time remaining : 41 seconds
or
64 % (frame 70 of 188)
the second label display :
Stabilization
During stabilization:
the first label is empty
the second label display
188 frames @ 0:00:21:18
and the third label display alternatively
Stabilization ..
(the number of dots and spaces varies)
When stabilization is complete :
the first label is empty
the second label display
188 frames @ 0:00:21:18
and the third label display
Stabilization
So i can read the label and deduce the process state.
// in a scheduled task
function checkStabProgress()
var effect = currentComp.layer(1).Effects.property(1);
var label = effect.property(1).name;
var label2 = effect.property(2).name;
var label3 = effect.property(3).name;
if(label == "" && label2 != "" && label3 == "Stabilization"){
     alert("Stab Complete");
It's seems to be a crappy way and sometimes an alert prompt before stabilization complete.
Is there a better way to do what i do ?
like event listener ? or something more clean and formal ?
thanks ++

Although it's easier (more convenient) to accomplish the mission in After Effects, you can do it in PrPro as well:
1. Nest your shaky footage.
2. Within the newly  created nested sequence apply Garbage Matte onto the footage to separate the woman on the foreground. E.g. draw Eight-Point Garbage Matte around the woman.
3. Create a Color Matte, pick e.g. R:7 G:7 B:9 to more or less match its colour to your footage background and drop this Color Matte above your footage with Garbage Matte.
4. Copy Garbage Matte from the footage and paste onto the Color Matte, delete or disable Garbage Matte on the footage. Optionally apply Fast Blur effect onto the Color Matte and dabble with Blurriness value so as to soften (feather) Matte's edges, adjusting Garbage Matte points if necessary.
5. Jump back to your master sequence and apply Warp Stabilizer onto the nested sequence, formerly your shaky footage. Set Stabilization to No Motion.
6. When done, switch to your nested sequence, disable the Color Matte eyeball, switch back to the master sequence, enjoy.

Similar Messages

  • How to make the warp stabilizer analyze interlaced (upper + lower field) instead of progressive?

    I am having a little problem since I am new to Premiere pro.
    Until now I always used the warp stabilizer in After Effects for single shots in need of that. But this time, I was handed a project that requires a whole lot of stabilization. My plan is to drop the whole timeline (FCP 7/ProRes422 HQ Interlaced) via XML into Premiere Pro and apply the effect there to multiple clips.
    PROBLEM: When I do this, the warp stabilizer always (no matter how I interpret the footage or set the sequence) analyzes the footage progressively. At least that is what the effect preferences tab says during analysis.
    In After Effects I always see which field is beeing analyzed (it is indicated by a L and an U behind the frame count). Not so in Premiere Pro. Here it always seems to analyze full frames.
    I made a test and compared the results from After Effects and Premiere Pro: The file generated in Premiere Pro is much softer then the one out of After Effects even though I export both with the same output settings.
    Any help would be greatly appreciated !
    Regards, franse

    I just verified and the Description for Products (and possibly other objects too) are stored in table COMM_PRSHTEXT.
    The relevant Data element is COMT_PRSHTEXTX which has the domain PRSHTEXT40.
    If you look at this domain you have a parameter "lowercase" which is available as a flag option.
    <u><b>The explanation about this Flag is the following:</b></u>
    Lowercase letters allowed/not allowed
    If this flag is set, upper case and lower case are distinguished when you enter values with screen masks.
    Otherwise all the letters entered will be converted to upper case when you enter values with a screen mask.
    This mechansim is in effect for all the fields referring to this domain.
    <b>Solution would be</b> to verify if for this data-element the same Domain is used.
    If yes, you can flag this option in the domain.
    this should solve your problem.
    kind regards
    davy pelssers
    please reward if helpful.

  • 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.

  • 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.

  • Script Warp Stabilize

    Hi there,
    Currently, our workflow within our business is taking large numbers of JPEG stills (50,000 and growing), and stitching into a lossless video, to then be stabilised and deflickred in order to send to clients as a regular view of the progress on their site.
    As the number of images/cameras grow, this workflow is starting to mean our two editing stations are almost always stabilizing footage, rather than editing (not ideal...)
    As we have a Hyper-V server (16 core, 64gb RAM) that can help with rendering, i'm looking to offload it onto this if possible -
    I've managed to script a batch render of stitching the images together into an Apple ProRes file (using FFMPEG), all that remains really is to stabilize
    I know I can do this by batch using aerender with command lines of my choice to take in the project files however applying the warp stabilizer will require a script?
    I've looked through some examples, and my basic java knowledge is getting me nowhere!
    As mentioned, I can already organise as part of my existing scripting a video for example to be saved as "INPUT.mov" ready for AE
    This then needs to put into a composition (same resolution and frame rate, but 1080p25 incase I need to specify) warp stabilised, and then output to OUTPUT.mov, and then I can write scripts to take this video and move it/rename to its relevant location.
    I know this is possible but its where to start! I've searched the web and forums but come up with nothing for warp scripting, i've only found people using the results of an already completed warp stabilizer in their scripts.
    Any help would be much appreciated, it's becoming obvious this workflow isn't scalable and if I could get this working I could ensure all stitched videos are rendered overnight ready for our editors and clients in the morning
    Thanks,
    Jay

    Here's some example code that might help. If you're applying the Warp Stabiliser as a preset you'll first need to add a copy to a layer manually, change any settings as required and save it as an Animation Preset.
    var activeItem = app.project.activeItem;
    if (activeItem != null && activeItem instanceof CompItem) {          // only proceeds if one comp is active
      if (activeItem.selectedLayers.length == 1) {          // only proceeds if one layer is selected
        var theLayer = activeItem.selectedLayers[0];
        var theEffect = theLayer.property("Effects").addProperty("Warp Stabilizer");          // the regular way to add an effect
        theEffect.remove();
        // thePreset = new File("place preset path in here to hard code it in instead of asking user for it");
        var thePreset = File.openDialog("Choose your preset");          // ask user for preset location
        if (thePreset != null) {          // if user didn't cancel the file dialog
          $.writeln("preset path = " + File.decode(thePreset.absoluteURI));          // use this as reference if you want to hard code in the preset path
          theLayer.applyPreset(thePreset);          // apply the preset
          theLayer.effect(1).property("Detailed Analysis").setValue(0);                    // prompt analysis to start

  • Black Magic and Warp Stabilizer

    I am working with 6.0, Footage is P2, Sequence is Black Magic Progressive @ 29.97 / 1920x1080. Black Magic board is Decklink 3d Extreme.
    Black Magic Drop Down in "New Sequence Setting Box" shows no 1280x1080 option which is P2.  All Black Magic options are 1920x1080, progressive or interlaced.
    When I drop the Warp Stabilizer onto a clip (P2) I get the message:
    "Warp Stabilizer requires clip dimensions to match sequence"
    How do I get around this, using the Black Magic Sequence and P2 footage?

    With CS6, you shouldn't.  Any sequence should output via the hardware just fine.  Though I've never used that hardware, so I can't comment specifically on how to get that going.  See if this helps.
    http://tv.adobe.com/watch/cs6-creative-cloud-feature-tour-for-video/get-better-playback-pe rformance-with-mercury-transmit/

  • Help: warp stabilizer

    hi everyone,
    when i apply 'warp stabilizer' it shows 'initializing...' but no progress. when after minutes it stops without stabilization.
    when i see a tutorial i see 'initializing...(processing something)' but mind is just saying 'initializing...' and nothing happens.
    any idea how to fix it?
    thank you,

    any idea how to fix it?
    Not really since you didn't tell us anything useful - no computer specs, no operating system, not the kind of footage you are using nor your AE settings for memory handling, caches and multiprocessing. This could be anything from permission issues at the system level to file access problems with MediaCache to simply the footage being shot the wrong way and the stabilizer not detecting any patterns for stabilization...
    Mylenium

  • Warp Stabilizer dropping

    I have tried dropping the Warp Stabilizer on a number of different types of media files, 7D, uncompressed 1080 25p, 23,97, interlaced, progressive, mp4, Red r3d, DNxHD, Animation... you name it. Sometimes I get an error "Unable to aquire rendered frame" which pops out three times after eachother before dropping the analyze part. Other times, it just stops without any message at all, going back to "press analyze to start analyzing".
    It's frustrating because I need to babysit a lot of rendering and I often have to reanalyze after it drops out right in the end. I have set up the RAM accordingly to each thread and everything and other functions within AE seems to work fine, just not the warp stabilizer.
    I have searched for answers and just found another thread in here that speaks of the "Unable to aquire rendered frame" message, but no answers in there.
    So what is this? Maybe it needs to be patched?

    My system specs are:
    Intel i7 3,7 Ghz
    16 Gb RAM
    Geforce GTX580 3Gb
    Primary disk: Intel SSD
    Win 7 Pro
    AE is up to date, footage as mentioned is from a lot of sources, so source files doesn't matter.
    It's stored locally and are streamed through a 6Gb/s eSata.
    It dops out randomly whenever it analyzes. If I babysit it and press "analyze" every time it drops out of analyzing, then after a while I seem to get it analyzed, but I can't sit infront of it if I have a lot of clips going through stabilization.

  • Warp Stabilizer Doesn't Render

    Hi, I've been having trouble lately using Warp Stabilizer in Premiere CC 7.1. I had used the effect many times successfully, then it suddenly stopped working. It analyzes the clips without problem, however it seems to get stuck on the "Stabilizing" phase. It just sits there. As I try to playback the clip in the timeline, it simply shows up as black video in the viewer. The space above the clip on the time line is yellow. Has anyone experienced anything similar? I've done a full uninstall and no luck. I don't have any other problems in Premiere Pro CC 7.1 right now.
    Steve

    I've had some problems with the effect completing, but usually only on clips what were especially long or demanding (like 4k with lots of movement). Additionally I have either encountered or read of others encountering these issues:
    With OpenCL Rendering on, stabilized effect rendering does not complete
    Large amount of memory is somtimes used when during Warp Stabilizer analysis phase (which is probably the root cause of the first problem I mentioned)
    Long progress pause (minutes) during auto-save while applying Warp Stabilizer
    Hang when saving project after extending warp-stabilized clip and re-analyzing
    Those don't all necessarily occur reliably, but they have happened for some users. I'm not necessarily saying they;re causing or even related to what you're seeing, but perhaps they offer some clues. In any case, it doesn't sound like an issue that would be addressed by uninstall/install, but it could be addressed by doing things like clearing your media cache, checking your available memory, etc...
    The workaround I would have suggested is to use AE if possible which it sounds like you did successfully already.

  • 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.

  • Warp Stabilizer VFX, did you know

    I have been using After Effects 5.5 [AE] for a while and this is about Warp Stabilizer is After Effects CC [Ae]. Yes Warp Stabilizer in [Ae] is about 3 times faster that [AE] and also offers some very good added features.  Sometimes you need the added features, other times you do not. 
    But did you know:
    While you cannot run multiple instances of [AE] or [Ae] on a single computer, if you have [AE] and [Ae] both installed, you can run both of them on a single computer because they are separate programs.  So now you can do two things at once including Warp Stabilizer.

    Yes, both Warp Stabilizer and the 3D Camera Tracker run as separate, external processes that send their results back to the main After Effects application when they're done.
    Details here:
    memory and storage tips for Warp Stabilizer and 3D Camera Tracker
    Regarding the speed improvements: You say that you've noticed a 3x speedup. We've found that the speedup varies a lot depending on the characteristics of the footage being processed, so I wouldn't count on it being 3x in all cases. I think that our marketing materials ended up saying that the speedup was ~80% (so nearly a 2x speedup) across all of our various tests.

  • Steps to send a clip to AE to utilize Warp Stabilizer VFX then back to Premiere Pro CC

    So I use Warp Stabilizer for about 200 clips per project. It's effectiveness has shaped how I shoot. It's awesome. Now there's VFX in AE...Can someone layout the steps involved in the following:
    a) Taking a clip from Premiere Pro CC and sending it to After Effects CC (I'm not that versed in using AE having not used it in quite a while)
    b) Then how to apply the new Warp Stabilizer VFX (I assume just go to effects>distort>WarpStabilizerVFX ???) ... (if there are tutorials on how exactly to use it, especially detailing exactly how to utilize the new feature of isolating what in the frame is to be stabilized that would be great too)
    c) Then how to send it back to Premiere Pro CC. (I'm guessing I just save it and let dynamic link take care of the rest?)
    I've tried right-clicking on a clip and selecting "replace with AE composition" (is that what I should do?), then applying the effect but I get a "warp stabilizer VFX analysis doesn't work with Collapse Transformations" message so I stopped. If it makes any difference, the majority of my footage is shot at 60p and then interpreted and edited at 23.976fps. Thanks!
    NOTE TO STAFF: I've said it before and I'll say it again as someone who uses warp stabilizer several hundred times per week, I still think the default "method" in the settings should be "Position, Scale, Rotation" instead of Subspace Warp because it works FAR better (less wobble and less scaling about 90% of the time). Can't help myself I had to bring that up again here.

    a) Select a clip in PrPro timeline, right-click and choose 'Replace With After Effects Composition'. Take care of handles if you might need them (that's rather general tip).
    Warning about Collapse Transformation switch indicates that you have 'Scale to Frame Size' option enabled for your clips in PrPro timeline. If that was done intentionally, you can simply toggle the Collapse Transformation switch (small sun icon) off. If not, rather disable 'Scale to Frame Size' for your clips in PrPro timeline.
    b) Quite a boring but covering almost all necessary details tutorial on basic work with Warp Stabilizer in AE CC from Adobe TV:
    Some advanced techniques from Lynda.com
    and Mathias Möhl:
    c) When you're happy with your work in AE and going to lock it, render a digital intermediate out of AE, import it into PrPro and replace your dynamically linked composition in the timeline with that DI (see this good old thread on Dynamic Link workflow, pay attention to Todd's comments).
    If you leave the 'Include Project Link' checkbox in the Output Module Settings dialog enabled while rendering your DI, you can easily get back to appropriate AE project so as to maybe tweak some settings: just select your DI in PrPro timeline, right-click and choose 'Edit Original'.
    Mind the bloating issue, keep the amount of applied Warp Stabilizer instances in a single AE project reasonable.

  • When is Adobe going to fix Warp Stabilizer?

    I asked this question back in February but I only got one reply. Warp Stabilizer may provide decent footage stabilization, but it is incredibly poorly coded, especially when compared to Mercalli Pro, or the Edius 7 Pro stabilizer, which I believe is a lite version of Mercalli Pro. One would think that since it was introduced at least 3 years ago (I can't remember if the first version it came with was CS6 or a previous one), Adobe would have troubleshot it and fixed its terrible performance. I mean, we're not talking about a stabilizer that is half as slow as Mercalli Pro. Warp Stabilizer is 14.5 times slower than Mercalli Pro. These are times for one minute of footage, the same footage in both NLEs:
    Edius Pro 7 Stabilizer: 29 seconds
    Premiere Pro Warp Stabilizer normal analysis and solving: 12 minutes 16 seconds
    Warp Stabilizer detailed analysis and solving: 14 minutes 28 seconds
    This is on a six core i7 3930k CPU with 32 GB of RAM and two GTX770 cards with 4 GB each (even though WP doesn't use the graphics card for analyzing and solving, only for playback)
    And the terrible analyzing and solving times are not the only problem. If you decide to run WP on a long clip, say 13 minutes long, even after the two hours that it takes to analyze and solve, the next time you open that project, be prepared to not be able to use Premiere for who knows how long. I say who knows because about 30 minutes ago I opened Premiere, loaded the project, and it froze completely when it was loading the footage files. For the last half hour, Premiere has been stuck with the spinning circle mouse pointer. Task Manager shows that Premiere has zero CPU usage and about 3 GB of RAM usage. So it's doing nothing at all, just frozen because Warp Stabilizer is one of the worst coded pieces of software not only from Adobe, but from any company.
    Putting aside the terrible analyzing and solving times, and the eternal wait next time you load the project, there's the fact that as soon as you use WP on a few clips, or on one long clip, saving times are unbearably slow.
    So I'm just asking, what makes a company with the huge resources Adobe has, not only launch a plugin that performs so terrible, but also doing nothing to fix it for three years or more?

    In this case, yes, I have a 13 minute long take that I have to stabilize. However, the original footage clip is a few minutes longer, so I'm not trying to stabilize the full clip, only most of it.
    I could spend a lot of money on the plugin, but I usually don't have a lot of footage that needs stabilization. Besides, I already have the plugin that came bundled with Edius 6, so I just use that when I need to. However, since Adobe advertises Warp Stabilizer as part of Premiere, and the plugin is absolutely dreadful, it seems to me that it's false advertising. I would much rather use WP in my Premiere project rather than having to load the footage in Edius and then export to a gigantic file to avoid losing picture quality.
    As for drive space, I have two 3 TB very fast hard drives that have plenty of empty space. Besides, Mercalli Pro in Edius analyses and solves this long clip in about ten minutes, as opposed to the over two hours WP needs for the same clip. In fact, in Premiere I only applied WP to part of the clip, when in Edius I loaded the original AVCHD clip so I can just do a replace in Premiere and have the same ins and outs.

  • Adobe Premiere CC 2014.2: losing rendered files when using warp stabilizer

    Hi,
    I am constantly losing rendered files when using the warp stabilizer. So far I have tried about every hint I could find on the web such as cleaning the cache, rebuilding the rendered files, creating additional sequences etc etc.
    Honestly I am getting tired of using a product that isnt cheap in the first place to rent and where a bug like this apparently persists over several product versions without being fully fixed (I have had this problem throughout 2014 but according to forum postings others seem to have problems with much earlier versions as well).
    I would be really grateful if somebofy has any suggestion how this can be addressed.
    I am also happy to help testing fixes - if there are any fixes available.
    Thanks a lot and Happy New Year!
    Martin

    Hi Catherine,
    Welcome to the Adobe forums.
    Please try the steps mentioned below and check if it works for you.
    1. Launch Premiere Pro and create a Project, go to File menu>Project Settings>Renderer and change the Renderer to Software only mode, delete previews if you get a prompt and then try to import the clip.
    2. If step 1 fails or the Renderer is already on Software only mode, go to Start Menu and search for Device Manager, go into Display Adapters and Right click on the Graphics card to select Update driver software option, on the next screen choose "Browse my computer for driver software", then choose "Let me Pick from a list..." option and from the list select "Standard VGA Graphics adapters. You might need to change the screen resolution of your screen and once done restart the machine again.
    Launch Premiere Pro and import the clip to check.
    Regards,
    Vinay

  • AE project crashes on startup - due to Warp Stabilizer and Highlight/Shadow

    I've got a head scratcher here...
    Firstly, I have been working on this project file for several days with no problems. Everything was running smoothly... working, tweaking, rendering... all successful.
    A couple days after doing a final render, I went to re-open the project and got these two errors, followed by AE crashing:
    To the best of my knowledge, I changed nothing on my system.
    I've tried removing my 3rd parth plugins (Video Copilot Optical Flares, Element, etc...) but to no avail. The program still crashes when opening this file.
    I've since installed the updates to AE CS 6, but still no luck.
    Removing Warp Stabilizer and Shadow/Highlight allow me to open this project file (obviously telling me that its missing both).
    I've tested out both plug-ins in a different file, and I'm able to open those no problem.
    I'm running this on a Mac Book Pro running OSX 10.6.8
    Model Name:
    MacBook Pro
      Model Identifier:
    MacBookPro8,2
      Processor Name:
    Intel Core i7
      Processor Speed:
    2.2 GHz
      Number of Processors:
    1
      Total Number of Cores:
    4
      L2 Cache (per Core):
    256 KB
      L3 Cache:
    6 MB
      Memory:
    8 GB
    AMD Radeon HD 6750M:
    Chipset Model:
    AMD Radeon HD 6750M
      Type:
    GPU
      Bus:
    PCIe
      PCIe Lane Width:
    x8
      VRAM (Total):
    1024 MB
      Vendor:
    ATI (0x1002)
      Device ID:
    0x6741
      Revision ID:
    0x0000
      ROM Revision:
    113-C0170L-573
      gMux Version:
    1.9.23
      EFI Driver Version:
    01.00.573
    Any thoughts???

    We've isolated the bug that is causing this behavior. It seems to only affect instances of the Shadow/Highlight effect on an adjustment layer over layer(s) with the Warp Stabilizer.
    There are a couple of workarounds:
    - One is to remove the Shadow/Highlight plug-in from the plug-ins folder and then open the project (and then fix the project to not have this effect on an adjustment layer over a Warp Stabilizer instance).
    - Another is to precompose the layer(s) with the Warp Stabilizer effect.
    We're working on a fix for this.

Maybe you are looking for

  • Help! hard drive failure and data recovery

    I am a happy PC-traitor who has been using my Macbook successfully for over a year now. I love the Mac. Until now. Last night, while downloading torrents onto my computer, it froze. I restarted. A blinking folder with a question mark was displayed. I

  • Flex 3 AIR Liquid layout

    Hai Freinds, I have issue on Flex AIR liquid layout, actually i have an WindowedApplication in which i have VBox(width:955, height:600) and so on.., but i need it to be liquid layout, It could be great helpful if any body help me Thank you

  • Message mapping crashes only in INterface Mapping

    hi guys, i have an issue with one of my interface mapping. the message mapping crashes when i run the interface mapping. however when i run the message mapping separately it works fine. any hints? thanks, ali.

  • Any Telephony API available in J2ME ?????

    hi, anybody tell me that any telephony api available in j2me???, b'cz i want to block incomings calls using j2me...........

  • Iphone in Dominican Republic

    Anyone been to the Dominican Republic with their iphone? Does the phone work there?