Warp stabilizer cropping/position issue?

So I don't think I've ever had this issue and I'm wondering if has to do with using it on a 13" macbook, since i've never had this issue on my iMac, but when I place the warp stabilizer effect the clip turns into a small cropped corner like so in the photo. This happens with any clip even if I try to adjust the stabilizer settings. Any help would be appreciated!

Hi mlhidalgo,
Please go to File > Project settings > General and change the GPU Acceleration to Mercury Playback Engine software only. After you will click ok, it will ask you to delete previews or keep previews. Choose Delete previews and see if it helps.
Also, please report if you have Intel Iris graphics.
Thanks!
Rameez

Similar Messages

  • Warp Stabilizer crops bottom of video if videos layers are beneath it for no reason.  Why???

    Warp Stabilizer crops bottom of video if videos layers are beneath it for no reason.  Why???
    remove the layers beneath and it's fine.  Hopefully adobe addresses this issue asap to save all of us a good amount of time.

    I have noticed similar: apply crop to a layer and with all settings at 0 a line of underlying video can be seen at the bottom.

  • Warp stabilizer crops bottom of video!

    When I try to stabilize some footage shot with my GoPro Hero 3 Black, warp stabilizer crops off the bottom of the video and greatly reduces the res of the video.
    The steps I am following:
    Import video using GoPro Cineform software (This leaves me with an .mp4 file)
    Create new sequence from clip in CS6
    Apply warp stabilizer to section of the clip
    Render
    Watch - and the clip has the bottom 1/3rd cut off and the video looks out of focus.
    I cant for the life in me figure out what is going on! Please help!
    Thanks

    So, the first image is jsut before it gets to the stabilized section....
    Then, as soon as it reaches the selected area that has had the warp stabilizer applied the bottom is cut off!
    Am I missing something stupid here?
    Thanks

  • Warp stabilizer crops clip off screen - help!

    Adobe Premiere Pro CC - most current update.
    When I apply the Warp Stabilizer effect, it crops/moves the clip almost completely off screen in the preview window. It also remains this way when I export.
    I am uploading dslr footage with these properties:
    File Path: /Users/Braedin/Desktop/Banff trip/Friday/MVI_9850.MOV
    Type: MPEG Movie
    File Size: 52.5 MB
    Image Size: 1280 x 720
    Frame Rate: 59.94
    Source Audio Format: 48000 Hz - 16 bit - Stereo
    Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
    Total Duration: 00:00:10:03
    Pixel Aspect Ratio: 1.0
    I then slow down footage to 40% to a 24fps look (orginally 60fps)
    I then "Nest" the footage to be able to apply the Warp Stabilizer effect.
    This is what it looks like without applying warp stabilizer:
    This is what is looks like after applying warp stabilizer and rendering the clip:
    These are the properties of the "Nested" clip with Warp Stabilizer:
    Nested Sequence 03
    1280 x 720
    00;00;04;22, 59.94 fps
    48000 Hz - Stereo
    Finally, here are my current Sequence Settings in which I am having the issue:
    Any help would be greatly appreciated as I suspect its an issue with sequence setting.
    Thanks,
    Braedin

    If you have a Retina Macbook Pro you can download the latest NVIDIA drivers from their website, which will enable you to use CUDA GPU acceleration in Premiere Pro, which fixed the problem for me, and is faster to render etc than Software Only.
    More info at this link, which also contains a link to the NVIDIA drivers:
    Enabling CUDA for Premiere Pro and After Effects in the MacBook Pro Retina

  • Warp Stabilization crops to letterbox?

    I cant quite put my finger on just what is going on here,
    but I think Warp Stabilisation is pulling a bit of a weird crop job on my footage.
    The letterboxing effect seems to increase as I decrease the maximum scale slider.
    What im doing is replacing a clip with an after effects composition in premiere pro,
    and then simply dragging the warp stabilizer ontop of the footage to let it do its thing.
    Any advice or ideas on whats going on?
    Running windows 7 64bit, AE version 10.5.0.253, PP version 5.5.0.233

    Youre indeed right about there being lots of movement, this is the start of a video with a small airplane darting off.
    Your arguement that maximum scaling is too small doesnt seem to hold up to my problem though.
    If I increase the maximum, the letterboxing gets even worse.
    My goal is to get a steady shot of an aircraft in the air.
    Tracking points dont seem to take hold of them, and warp stabilize also seems to get confused.
    The only program that can do it flawlessly is deshaker in virtualdub.
    How I wish I had that plugin for Premiere Pro.

  • Dynamic link warp stabilizer 5.5 issues

    Been messin around with the demo while I patiently wait for my upgrade to 5.5 and I've come across an issue with the warp stabilizer when sending multiple clips from the timeline to and from PPro 5.5. If I send out a clip, use warp stabilizer in AE and save the project the results are fantastic and it's right there on the timeline. Groovy.. Until I send another clip out. The second clip looks great in AE... stabilizes fine. Save project as new name in AE, exit... back to PPro and the clips will be the same! It'll duplicate the first stabilized clip! Sometimes I can delete the instance from the timeline, and drag the AE comp from the bin back to the timeline and it'll work until I do another clip then it'll be a duplicate again. Also, sometimes it'll flicker from one comp to the new comp and back again. Like it's confused about which comp to play in PPro. I'm hoping that when I export it'll be fine, but this seems quite serious.
    I've tried dumping the cache, cleaning out the project, saving the AE comp projects to different folders and drives. Doesn't seem to matter.
    Oh... btw.. specs:
    i7 970
    Asus P6x58D-e
    24GB G-Skill 1600 kit
    C: Revodrive 2 120GB SSD
    D: WD Black 1TB for apps (not Adobe apps, they are on the SSD)
    E: WD Black 2TB for video
    I: Removable dock with 1TB Samsung spinpoint F3
    F: LG BDR
    MSI GTX 560 Ti OC (Works great with MPE modified .txt file!)
    Win 7-64 Pro (because of 24GB)

    This bug has nothing to do with Warp Stabilizer, it affects all DL's and has been around from the beginning.
    It is a PITA.  If you keep all your compositions in the "same" AE project it seems to work better.  If you do a "save as" and rename AE project the bug will appear again.
    Also DL's are always "un-linking" for some reason in CS5, CS5.01, CS5.02 and CS5.03.
    I hope CS5.5 fixes this issue.

  • Warp Stabilizer - focus / blurring issue

    I have some Canon 5D Mk II 1080p (25 frames per second) footage. A 90 second long shot on a steadycam from the back of a car  following a guy on a motor bike.
    There is a bit of mild shake going on and so I tried Warp Satablizer in Premier Pro CS6.0.2 (Mac OS Mountain Lion), which smoothed the shot out quite well.
    But it does generate a side effect of the shot almost going out of focus for a half second or so about every 4 or 5 seconds. Looking at the footage it's as if the frames are blurring into each other as the stablizer tries to work out whats going on. I tried reducing the Crop Less - Smooth More setting to 50% and that reduced the crop but still left with the focus issue.
    Any tips on how to reduce this blurring effect.

    Hi mlhidalgo,
    Please go to File > Project settings > General and change the GPU Acceleration to Mercury Playback Engine software only. After you will click ok, it will ask you to delete previews or keep previews. Choose Delete previews and see if it helps.
    Also, please report if you have Intel Iris graphics.
    Thanks!
    Rameez

  • Warp stabilizer crops when it shall scale up to full screen?

    the picture says it all.
    1 hour ago it worked fine, but suddenly it all changed and I don't know why.
    do you?

    I don't not really know what you are meaning..
    Which resolution, which zoom lever? comp, clip?
    Look on these pictures...
    Tell me in detail how to.
    Thanks for answering.

  • How to shoot 1080p/60, output to 720p/60, so Warp Stabilizer or zoom/crop has no quality loss?

    I'm new to AE, and making a painful transition form FCP to Premiere, so please be patient, I don't understand many of the subtalties of these apps yet.  :-)
    Also, please forgive the long explaination, I'm having trouble articulating the problem...
    I'm shooting in 1080p/60, AVCHD.  I plan mainly to output to 720p/60.
    The idea being, that if I need to warp stabilize footage, or zoom/crop, I can do so without any quality loss.
    I don't want to edit the project in 1080p/60, because if I stabilize it, and it blows up the image, it will result in quality loss. Then when I scale down for final output, that pixilated/crapified footage will be present just in scaled down form.
    I don't want the footage to be scaled down first, then, when I stabilize it, I'm blowing up 720p footage (thus defeating the whole purpose of doing this) and once again, outputting pixilated/crappified footage.
    What are the steps / workflow to set up Premiere and the stabilizing shots in AE, such that I'm working in 720p, but using the 1080p footage, so that extra resolution is available when I need to crop, zoom, stabilize, etc. the footage... and can do so without any quality loss?  It would be great to have that ability to zoom in on elements in post, almost 2x, and not see any loss of quality.
    Thanks in advance!
    -Jason Wallace

    100% positive.  There is a family of lesser known Prosumer Panasonic cameras (my particular model is the TM700) that record 1080p/60.  It's a 3-chip, CMOS, that genuinly records at that resolution and frame rate.  Has audio input, headphone output, shoe mount, zebra stripes, touch screen, good battery life, and a manual focus ring (fly by wire, can be set for exposure, framerate, or focus).  Also has very good low light capabilities, that are much better than the published specs would lead you to believe.  The firmware is a bit goofy, and was clearly designed by engineers, not people who have ever shot video.  For example some things that should be easily accessible, are buried in menus, while other useless "fluff" features are front and quickly accessible.... but if you can live with a few stupid firmware compromises, it's absolutely AMAZING bang for the buck, and well under $1k to buy.
    Note: if I'm not mistaken, the camera can only output via HDMI 1080i/60, but for absolute certain the video files being recorded are genuine 1080p/60. (This has lead to some confusion and forum arguements as to whether the camera is actually 1080p/60)
    This was one of the main reasons for my moving from FCP to Premiere, as Premiere Pro handles the 1080p/60 AVCHD files, while FCP requires they first be transcoded and inflated to a intermediate codec.
    -Jason W

  • Precomposing & Cropping & Warp Stabilizer? *Beginners Question*

    Hi guys,
    I'm new to AE and have been trying to follow instructions from this link (http://www.sinusdigitalus.de/2011/05/06/my-first-test-with-the-new-adobe-cs55-warp-stabili zer/)
    I've taken out the important bit here -
    "i´ve imported my sequence and applied the warp stabilizer on it. the first instance of the stablilizer was to stablize only the movement of the position, scale and rotation with a crop but with no rescale to keep the image quallity. i´ve precomposed the shot and resized the comp with the new dimentions of the shot after the crop. on this i applied a new warp stabilizer and this time i´ve stabilized the perspective also with crop but no rescale. again precomposing and rescaling the comp to the new dimensions. then i applied a third warp stabilizer on this new comp and did it again. this time with the subspace stabilization."
    - As he mentions at the begining, it's not an indepth tutorial so where I'm tripping up is the precomposing and cropping.
    I'm trying to stabilise a jpeg sequence using this guy's method (he passes it through Warp Stabilzer 3 times).
    When I hit the Precomopse button it gives me 2 options and a box to tick whether or not to open new composition, which ones do I pick? And when that's done, how do I crop it so it's applied to the whole jpeg sequence before I use Warp Stabilzer agiain?
    Thank for your help.

    Not tried it but could you make a 2.7k sequence and warp stabilise that, using stabilise only or stabilise and crop. Then add this sequence to the 1920x1080 sizing to suit.

  • Warp Stabilizer 4K to HD - does PPcs6 interpolate first then downsize when using "stabilize, crop, autoscale?

    I am using CS6. I have warp stabilized my 4K footage and want to output to HD at the best quality I can. I have two choices: I can either have warp stabilizer "stabilize, crop auto scale" then I simply render to HD or I can set "stabilize, crop" and then get rid of the black border (crop) using AME in export settings. So my question is: If I use option 1 does PP interpolate the footage and then "downsize" to HD thus reducing quality? Or Does PP make all the calculations "in one go" so the footage isn't actually interpolated then reduced? I hope I have explained this clearly - though I fear not :-) Thank you for any comments. Paul

    I've been experimenting exactly the same.  My conclusion is that stabilize, crop, auto scale does indeed crop the video first, then rescale back to the original frame resolution. So there is some loss of quality.  I've been working on 4K video and warp stabilizing first (no crop, no auto scale), then cropping as a nested sequence to HD (with key-framing to follow the action).  Depending on the amount of crop, what the video content is, and because you're starting with 4K footage to begin with, it's debatable as to whether the final HD rendered output is visually any different whatever method you choose.  I guess you'll only find out by trial and error.
    Steve

  • Warp Stabilizer Output Issue

    Ever since the update to Premiere Pro when I go use warp stabilizer all it outputs is a small rectangle at the top with a small piece of footage inside of it. I've tried tweaking the settings and resetting my preferences but it always comes out with the same result. It works out when I use After Effects, but that can be pretty inconvenient considering the render time and what not. What am I doing wrong here? Heres an image of the output.

    Hi Gjhobbs13,
    Please check the below discussion and check if it helps.
    https://forums.adobe.com/message/6826226#6826226
    Regards,
    Vinay

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

  • Possible to turn OFF "Rolling Shutter Ripple" correction in CS5.5 Warp Stabilizer?

    Is Rolling Shutter Ripple redcution on by default in CS5.5 Warp Stabilizer?  Can I turn it off?
    I am having some strange results trying to stabilize some night-time astro timelapse sequences I shot from a moving car.  There seems to be some warping and "zooming" of parts of my frame, regardless of which stabilization options I choose -- motion, no motion, scale-crop-rotate, subspace, etc.  I've tried every combination possible, including the various border options.  The only thing I can think of, at this point, is that the Rolling Shutter correction function might be struggling to deal with frames shot from a moving car at 4/10ths of a second at night.  Is there any way to turn off the rolling shutter compensation?
    Thanks!

    Thanks Jim.
    The source stitched 176 frames for my test are about 1gb. So trying to get to the bottom of it without someone having to dl them (and it will take a while to put them up). The 8 frame version shows the same effect happening, just exaggerated. But its a fair call to assume maybe it would not happen with enough information to work with.
    The original http://dl.dropbox.com/u/7070604/full_ae_1080.mov I had tried at the time using detailed analysis as well to see if it fixed the issue, and the results were very similar.
    I'd also found that using subspace warp instead of PSR (position, scale rotation), or even just P (position) seemed to generate some additional warping there in the output, and certainly for my footage did not result in making it better.
    However, I have re-run the full footage starting from frames not a movie using detail analysis and subspace warp since you running that over the originally processed 1080 footage seemed to do a pretty good job.
    The results are here : http://dl.dropbox.com/u/7070604/full_ae_1080_warp.mov?dl=1
    You can see the warp is really messing it up, and the zooming is not fixed. Left hand side easiest place to see it.
    Note I've found putting ?dl=1 on any of the links actually downloads them for anyone having issues with it simply playing in their browser. The way I am visiually checking any of these for issues (as many are at 1fps) is to load them into quicktime, change it to View, loop. Then In quicktime 7 holding FFWD. In quicktime 10 hitting forward until it runs at 8x. Looping at 8x is where you can really see the issue.
    The files I had not broken out seperately that are in the source files upload were the results in after effects just using the 8 frames. Here they are seperately.
    http://dl.dropbox.com/u/7070604/1080_rez_p.mov?dl=1
    Position only.
    http://dl.dropbox.com/u/7070604/1080_rez_psr.mov?dl=1
    Position scale rotate.
    http://dl.dropbox.com/u/7070604/1080_rez.mov?dl=1
    Unstablized.
    I presume even with subspace warp you get the same results or worse using these 8 frame files.
    If you ignore the extra warping/twisting in the new file, you have the same results as the original http://dl.dropbox.com/u/7070604/full_ae_1080.mov?dl=1
    played at 8x. The easiest place to see it is the mid left side where you can see it zooming in and out. The fact that it really only starts happening a 3rd the way through makes me think its simply not dealing with the changes in zoom, or the later pan changes in the source file. It wierd the photoshop processed version comes out fine though.
    I was really hoping it was a case of, "ah, I see why it can't deal with those 8 frames, it really needs a manual tracker/stablizer doing x,y,z" But of course I'd be even happier with a tweak to the automated warp stabilizer.
    If I do a 2nd run on the sample file http://dl.dropbox.com/u/7070604/full_ae_1080.mov I notice selecting P, or PSR does not fix it. Selecting Perspective or Subspace (which probably includes perspective) seems to go a long way and have a similar result.
    Leads me back to thinking selecting subspace on the original footage just warps it, selecting P or PSR fixes all but the zooming thing, and then reprocessing with perspective is tackling the persective in isolation which it could not effectively do before. I don't know if that is because you cannot select P&R without S scale. Or because AE's perspective adjustment cannot work effectively with images that have scale variences in them or ?
    I've now run the ouput from a frames start via P and PSR. Brought them back in and prosessed with subspace and P and PSR. Results seems to be no better. There is some special sauce here somewhere with the reprocessing. Maybe its the codec I am going out to in the middle, maybe its the aspect ratio, maybe its ???
    Might be time to u/l the full source files I guess.
    Thanks for sticking with me.

  • Projects Not Opening with Multicam and Warp Stabilizer - "[..\..\src\TickTime.cpp-207]"

    Editing a sequence with multiple nested multicam clips and warp stabilizer, if I close Premiere and reopen it, it says "Premiere Pro has encountered an error. [..\..\src\TickTime.cpp-207]" repeatedly until killed by Task Manager. I have restarted the computer, cleared the media cache and deleted preferences. I can import the sequence into another project and continue editing but if I close PPro I have to create another project and import the sequence again or I get the same error. Help!

    Hi Kevin!
    That is great news. I had a feeling the issue would be gone in the Next PPro. The issue can be easily duplicated by following these steps in CS6:
    1) User warp stabilizer on several clips (like maybe 6 or more or so).
    2) Take two clips and nest them and sync them for multicam on the same timeline as the stabilized clips (NOTE: these two clips don't actually have to be sync'd...just grab any two clips, stack them on top of each other, highlight them both and right-click and choose "nest", then right-click again and "enable" multicam.
    3) Save project. Close project. Re-open project and you'll get the error.
    If you do that in the NEXT version, does the error come up? Also, just while I have you...if you go into the settings of Warp Stabilizer, what is the default "method"? Is it still defaulted to "Subspace Warp" or did they smarten up and realize the option "Position, Scale, Rotation" is actually MUCH more effeciet causing less wobble and less cropping of the video 90% of the time? Just curious.
    Coltom Media Productions,
    I feel your pain. What also stinks is that the error pops up again when you export (or I should say when you queue) up the project into AME. I originally thought the number of continues equalled the number of warps applied but that's not always the case. Although, the more warp stabilizers applied the more times you'll have to hit continue. It often goes in numbers divisible by four. Why do I know all this crazy, useless info...hours and hours of trying to "solve" the issue. Every project I do, every single week has more than 100 clips that are stabilized and multiple multicam sequences so I often have to hit "continue" on the error 300-400 times or more on EVERY project. Can't wait til the next version!
    To see more on this issue you can see the original post on it here (note that the staff has recently (and graciously) led the charge to help isolate and resolve the issue):
    http://forums.adobe.com/thread/956692?start=40&tstart=0
    And then also, it definitely made my "Top 15 list" here:
    http://forums.adobe.com/thread/1179004
    Good luck!!!...oh, one more thing...the project will open...you just have to keep hitting continue. Sucks, but again, hopefully it'll be resolved soon.

Maybe you are looking for

  • Print PDF document with printer's name and date/time of print

    Hi, I'm pretty new to this... I have a PDF document and when I print it, I want the printer's name and the date/time of print to be showed on the printer's output. I have several printers (some local and some on network) and don't necessarly use the

  • CN43N: No objects were selected using the criteria

    Hi; recently i have loaded WBS into system through a BDC programme. When i check those WBS in Project Builder i can see them, on other hand when i execute CN43N it does not show me any record. Your valuable input is required. Thank you.

  • Purged Data in SAP

    How does SAP manage the purged data in SAP databse. Lets sa i have deleted a Business Partner or any transaion in SAP. what happens to it. I guess it resides somewhere in archive mode or format or files. WHere does it store all the purge data. Does i

  • SharePoint 2013 architecture

    We are planning to migrate to 2013 form 2010 soon.  When I say migration we want to build a new 2013 architecture and move site collections one by one. Ours is small to med organization and our 2010 architecture is 1ADM, 1WFE(internal), 1 WFE(Externa

  • Environment and RAID best practices please...

    hello dears... I have a scenario that I've never been to and its a very important one, so that I would like to receive some tips of you experts... I'll have to run Oracle 10.2.0.1.0 on Windows server 2003 ENTERPRISE edition on the following scenario: