Sending to Speedgrade with Warp Stabilizer Effect

I finished a locked cut in Premiere CS6 and hit "send to adobe speedgrade". However, speedgrade won't display any clip that has the warp stabilizer effect. Anyone know how to fix this? I'm working on a mac. Thanks

Hi abcdlee,
I've used this many times with my Premiere Pro projects, didn't come across any issues in getting them to display in SpeedGrade. Is it really just particular shots with warp stabilizer or do you have other shots not  showing up properly as well?
Theoretically it should make no difference whether you use an effect such as warp stabilizer - as the images are being rendered before they show up in SpeedGrade, it should all work the same.
Thanks for your feedback.
Patrick

Similar Messages

  • How to "analyze" multiple clips with "Warp stabilizer"-effect preset

    Is there a simple way to "analyze" multiple clips that have the Warp Stabilizer effect attached?
    I have a sequence with 100 clips, which all have a customized Warp Stabilizer effect preset attached. I can attach the effect to all the clips very easily, but afterwards I have to manually press "Analyze" on each clip, which is quite irritating... Is there a shortcut?
    I don’t use nesting because I have to tweak the effect-settings on some of the clips…

    https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
    Yes, sadly custom presets with warp stabilizers don't work correctly. You have to go hit analyze manually for every clip. For you that may be quicker than changing your two settings for each clip. It is a bummer though. We actually use this effect several hundred times per week and prefer the "Position, Scale, Rotation" method in the settings but we can't use the custom preset because it doesn't properly re-analyze automatically like the default effect does. I'm not sure whether it'd be a bug report or a feature request (in my opinion it's a bug) but definitely report it to the link above.

  • Help with Warp Stabilizer in After Effects CS5.5

    Hey guys, I am currently experiencing some crazy problems with warp stabilizer.... Everytime it warp stabilize, yes the footages is smooth and all, but the whole footages wombles and warp... Views start to get distorted... I changed the stabilisation method frm sub-space warp to position, but then the stabilization is not efficent at all... My video isnt a green screen, so I cant use tis guy's method of outsmarting the warp stabilizer... http://www.cameraman.com/2011/stabilize-your-shots-with-ae-warp-stabilizer
    Please help... My client needs my STABLE FOOTAGES, soon....

    Watch the videos by Chris Meyer pointed to from here:
    http://blogs.adobe.com/toddkopriva/2011/04/warp-stabilizer-in-after-effects-cs5-5.html
    They explain all of the parameters and how to use them to get around various problems and get better results.

  • Clips with warp stabilizer minimizes?

    Hi,
    I have some interview clips on my V1 in premiere, and on the V2 I have some clips with motion which has the warp stabilizer on. When the V1 and the V2 overlaps, the warp stabilized clips is minimized and fills only a bit of the screen (at the top left corner). I have tried different settings, but it is still a problem.
    What am I doing wrong?

    Rameez
    Not sure what to do here. I need to get something out and this issue is not letting me do this. I too am getting a weird flickering
    on the clips that have a warp stabilizer effect on them.
    I tried changing my frame rate to 30p from 29.97 and then switching to the playback to GPU Acceleration software only.
    When I add this to the queue and export from Media Encoder, I still get the flickering. And then when I try top exporting from PP with the GPU acceleration software only selected,
    it is giving me an unknown error after a min of trying to render.
    I have tried exporting it several different ways and out if PP, still no luck.
    Not sure how to reset my preferences.
    Darcy

  • Flickering video with Warp stabilizer

    Hi all,
    I have a problem what more of you maybe have seen the past month, the flickering with warp stabilizer.
    Now i already changed the renderer setting in project settings into Mercury Playback Engine to Software Only, but this didn't solve the problem.
    My specs:
    Macbookpro 15 inch retina end 2013,
    2,3 ghz i7
    16 gb ram
    nvidia GT750M 2gb
    OSX 10.9.5
    Will update to Yosemite solve it or not?

    Hi Dave
    I solved my problem with the next 2 things:
    - changed the renderer setting in project settings into "Mercury Playback Engine Software Only
    - changed the renderer setting in media encoder into "Mercury playback engine software only
    Hope this will solve your problem to.

  • Crashes after effects with warp stabilizer

    I have some problems with after effect cs6.
    When I try to warp stabilizer an mov file  in after effects I have crashes every time.
    My Pc runs Win 7 Ultimate
    12 G Ram memory
    Graphic card NVidia GTX 480
    In the preferences I have no GPU accelleration it tells me that tha graphic card is not compatible , in stead in premiere pro I can select the redering
    In Premiere Pro I can select  this option and it works fine

    Thanks for the reply.
    After modif the raytracer_supported_cards.txt file now I can select the GPU option . Here are the settings for the GPU informations.
    Fast Draft:
    Available
    Texture Memory:
    1000,00 MB
    Ray-tracing:
    GPU
    OpenGL
    Vendor:
    NVIDIA Corporation
    Device:
    GeForce GTX 480/PCIe/SSE2
    Version:
    3.0.0
    Total Memory:
    1,45 GB
    Shader Model:
    4.0 or later
    CUDA
    Driver Version:
    5.0
    Devices:
    1 (GeForce GTX 480)
    Current Usable Memory:
    1,24 GB (at application launch)
    Maximum Usable Memory:
    1,50 GB
    Results Event viewer
    Faulting application name: AfterFX.exe, version: 11.0.1.12, time stamp: 0x4fab6f50
    Faulting module name: hdavasiopx.dll, version: 2.0.0.7, time stamp: 0x4db8e7b1
    Exception code: 0xc0000005
    Fault offset: 0x0000000000002932
    Faulting process id: 0x53c
    Faulting application start time: 0x01cd91cef9878216
    Faulting application path: C:\Program Files\Adobe\Adobe After Effects CS6\Support Files\AfterFX.exe
    Faulting module path: c:\windows\system32\hdavasiopx.dll
    Report Id: 26ff269f-fdcb-11e1-9d44-20cf300b0ea6
    After modif the settings the problem is not solved.
    I have the following message after the crash : Last logged message was:<xxx><alalyzer Server><5><Start xxxxxx.....>
    I will try to convert the file and se wat the results are.

  • Problems with Warp Stabilizer -Testversion After Effects, who can help ?

    Hey can someone tell me why the Warp Stabilizer is not working at the testversion. Is is only activ on the registrated version ? Wanna figure out whats better at this stabilizer compares to the final cut Motion 3 d stabilizer befor i buy a expensive software that doesn´t make it better, thanks a lot for any answer..simon germany

    thanks..will wait and try....thanks for the link
    Am 17.04.2011 um 05:57 schrieb Todd_Kopriva:
    The trial version will be available in May. See http://blogs.adobe.com/toddkopriva/2011/04/improved-trial-version-for-after-effects-cs5-5. html.
    >

  • Error with warp stabilizer

    I've graded a couple of clips from DaVinci Resolve and exported as ProRes 4444 from sony F55 RAW.
    Now I'm importing them in my Premiere Pro CC timeline, edit them and apply warp stabilizer.
    The effects analyzes correctly the video, but when I try to export them (via Premiere, Media Encoder or After Effects) I get a generic error.
    I tried to export the clips as ProRes 422 files but get the same error. Without the warp stabilizer the timeline renders without issues.
    Does someone know how to solve this issue?
    Thanks

    What firewall/antivirus software are you using?
    After Effects communicates with the background camera tracker process using TCP, and some overly aggressive firewall/antivirus software can block this communication. That may be the problem in your case.
    See this document for a closely related issue:
    http://helpx.adobe.com/x-productkb/multi/startup-screen-hangs-premiere-after.html

  • Trouble with Warp Stabilizer in Premiere Pro

    I have one simiple clip that I keep trying to stabilize and I can't see the effect.  I've had this problem for months with several different projects with no luck.  It goes through the motions of analyzing and stabilizing but won't show the resulting effect.  It just freezes on various last graphics seen.
    I've tried matching sequence settings, tried nesting the sequence into a separate sequence and can't seem to see the stabilized video.  It just freezes on one frame, or a gray screen or holds whatever was the last video in the program frame.  It even shows the desktop sometimes.  When I turn off the effect the clip plays fine (unstabilized).  I'm trying to stabilize a time lapse I shot on a windy day... so it was bouncing around a little.  I've tried moving all of the scratch disks to another drive that was clear and free of space.  I'm still getting nothing in playback. 
    Any help is appreciated.

    That worked!  You rock Bob Peru!  Thanks so much for the reply!

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

  • Warp Stabilizer through After Effects Dynamic Link Locks up in CS6

    Hey Gang,
    I've been using Warp Stabilizer through dynamic link in CS5.5 without issues.  However, when I go through dynamic link into AE, then apply Warp Stabilizer, AE locks up?
    I can apply any other effects through this path in AE without issue, but when I try to apply WS, I get the "Analyze", but AE stops cold there. 
    I've tried:
    -Opening new project in PP with basic 5 second clip.  Then going through dynamic link into AE, and applying warp stabilizer first thing.  AE locks up there with the simplest flow.
    -I have the latest downloads of the entire production CS6 suite.
    -If I apply warp stabilizer directly in Premiere CS6 (which I did not know previously I could do), it works fine! (Just noticed Warp Stabilizer is present in PP CS6, but not in CS5.5). 
    -If I try to import the Premiere project from AE, AE locks up doing that?
    It appears there are multiple issues here:
    1. I can't apply Warp Stabilizer in After Effects, and doing so crashes AE.
    2. I can't import a Premiere project into After Effects, and doing so crashes AE too?
    I'm assuming I'm going to need to download AE again?
    Thank you for any help and suggestions you may have!
    Derek...
    Message was edited by: Derek Emmett

    Hello Mylenium,
    thank you for your input.  Naturally I would expect if my work flow in CS5.5 works great, I would not have to make any changes in CS6 to accomplish the same task.  With that said, I made it as simple as possible for CS6 AE to handle the Warp Stabilizer effect, and it crashed?  If I went directly back to CS5.5, no problems at all in AE (same source footage, but of course different projects).  When I first tried CS6 AE it appeared to work fine, even when doing Warp effects.  So when I ran into the issue I saw above, I started thinking it was possible the update I did to AE may have caused some other issue.  By the way, the projects I open in both CS5.5 vs. CS6 were independent, meaning, I did not convert a CS5.5 job to CS6, etc...   (See notes below).
    My setup is standard:
    i7 960
    16G mem
    Nvidia Quadro 4k
    Footage is Canon 5D Mkii 1080p
    All drivers up to date.
    -I think going back and forth between CS5.5 and CS6 may have caused some issues?  When I rebooted my system, CS6 AE seems to work fine when applying Warp Stabilizer effects again. 
    -What I did find more interesting and effective, was that CS6 Premiere has Warp Stabilizer right in its own effects now!  Works great in the premiere flow and plays back far better then going through the Dynamic Link with After Effects!  When playing Dynamic link effects back in Premiere, I'm sure everyone sees performance issues in the playback.  However, in at least with applying Warp Stabilizer directly in Premiere, the playback performance is much better.
    Thank you
    Derek...

  • Warp stabilizer not working with latest update

    After latest update (updated 10/10) Warp stabilizer stopped working. Already stabilized clips in project show black / transparent in preview, besides small area left or right upper corner. Changing Video rendering from GPU acceleration to Software makes stabilized clip come back... however now it creates flickering to all stabilized clips. Deleting "Warp stabilizer" effect from clips removes flickering. What might help?
    Editing with Lenovo Thinkpad, i7 2.4ghz, 8GB, Intel HD integrated graphics
    Message was edited by: Mikko Lehvilä
    Added picture

    I'm experiencing a similar thing.
    2014.1 (October Update) on OSX 10.9.5
    For me, Warp Stabilizer is working on regular clips. But when I try to apply it to a nested sequence, the result is exactly as you describe. Video is fully visible while analyzing and stabilizing, but once stabilized it's just black (actually, I did some tests, and it's actually transparent).
    I can replicate this even with codec-agnostic footage like bars & tone.
    Adobe - what's up here?
    Edit: sometimes I get the top-left-corner thing, and sometimes it's completely blank. Trying to track down the pattern.

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

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

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

Maybe you are looking for

  • BPM Collect Message dependent AND time dependent

    Hi I have a IDOC to file scenario where I have to collect all the IDOC until I receive a stop IDOC. Once the End collect IDOC is received I have to do a n:1 transformation and write the file to the FTP. The problem is, at times the IDOC which is supp

  • Compilation failed while executing : dsymutil

    Hi, Trying to compile a standard package for ios with major failure. The fast-version works perfectly without any errors. I'm on mac os x lion and using flash builder 4.5.1. The error I'm getting is as follows: Error occurred while packaging the appl

  • List of employees with a wage type

    Hi, Is there a way of finding the list of employees who have a particular wage type? thank you r s

  • Unable to logon to Alert Configuration in RWB

    Hi, Someone asked this question was asked a coule of weeks ago but it was never answered. I am trying to logon to the alert configuration and alert inbox sections of my runtime workbench. None of my users seem to work including XIRWBUSER or XISUPER.

  • Osx 10.4.6 to 10.4.7 update killed airport

    earlier i installed the update for osx 10.4.7 and now i am getting the error, no airport hardware found, on imac g5 2.1 20" isight images http://www.t1h.org/imac/Picture%204.png http://www.t1h.org/imac/Picture%205.png http://www.t1h.org/imac/Picture%