Warp stabiliser choppy and corrupting source footage

I am having huge problems with Warp Stabilizer - it creates choppy footage and actually messes up the source files (after removing all effects the choppyness remains, and viewing the original files shows the problem has been transferred over/files corrupted in some way. NO IDEA what the cause is or the fix. Any help appreciated!
warp stabilizer malfunction.mp4 - Google Drive

Hi,
What are the sequence settings that you have selected in the project?
Thank You
Arjun

Similar Messages

Suddenly, any new music or podcast I download - from any source - will be choppy, and corrupted. What's happened?

No matter which site I use as the source, anything I download will be choppy and corrupted. Music and podcasts both end up unlistenable. This has only started happening in the last few days, with nothing I can think of that has changed in that time to cause this. Steam cannot update itself, or install the new Skyrim patch - it keeps flickering between "x% complete" and "Starting download". Some pictures also look garbled or entirely absent.
I've already tweaked and then uninstalled Quicktime; I've reset Firefox; and I've kicked the desk a few times. All useless. What is going on?

Do you have this issue with another browser? Have you checked out our help articles? This could also be an issue with your internet connectivity (contact your ISP for that reason)

Imported MOV files are running choppy and I can't edit in the source window..anybody can you walk me thru how to fix?

My MOV files are choppy in the SOURCE window where I'm trying to edit. Please help....I have a camera that I use for that is drone footage no audio and it imports fine; never choppy easy to edit. Now I'm trying to import video from my Lumix; it's bringing in audio that I don't need but the files are choppy and am unable to edit. Have been watching tutorials but I can't seem to fix the problem still.

Thanks for your patience with me. I have tried what you mentioned and dragging the clips in question to the new item icon. Sometimes it works fine and others it gets hung up again. However, I'm used to editing when the file is in the source area (upper left corner ...see file attached...screenshot). When I do the task you mentioned it immediately puts the entire clip before I edit in the lower right and it doesn't appear i can edit as easily. Does that make sense?
I'm starting to think my computer isn't powerful enough? ):
Currently the Premier settings are set up like this
General
Editing mode: QuickTime DV NTSC
Timebase: 29.97fps
Video Settings
Frame size: 720h 480v (1.2121)
Frame rate: 29.97 frames/second
Pixel Aspect Ratio: D1/DV NTSC Widescreen 16:9 (1.2121)
Fields: Lower Field First
Audio Settings
Sample rate: 48000 samples/second
Default Sequence
Total video tracks: 3
Master track type: Stereo
Audio Tracks:
Audio 1: Standard
Audio 2: Standard
Audio 3: Standard

Changed sequence settings to match source footage but only half footage now matches even though they're from the same camera and same aspect ratio

My source footage is 1920 X 1080 from a canon 60D. I changed my sequence settings to Digital SLR 1920 X 1080 to match. On the program window I have it set at "Fit". Only about a quarter of my footage now fits the program screen and looks to be the matching aspect ratio. The rest of the footage when on "fit" fills a tiny portion of the viewing window so it appears they don't match the sequence settings. I don't understand why this is happening because this footage is from the same camera, shot the same day, and have the same aspect ratios.
Can anyone tell me why this is happening and how I can fix it??

First of all, the setting that you mention is on Fit is the Zoom Level of the Program Monitor. It controls only how the sequence is shown in that monitor; it has nothing to do with how any sources are handled in the sequence.
Please provide the following information:
Exact version of Premiere Pro
Exact version of operating system
Graphics card and driver
Also, please post a screenshot showing the following
Project panel with the Video Info column visible
the Timeline visible
one of the problematic clips selected and the Effect Controls panel visible, with the Motion section twirled open.

AE CS6 and tearing of XD CAM EX Mp4 source footage

Hi I'm getting tearing artifacts in CS6 when using XD CAM EX MP4 source footage. This does NOT occur on a colleague's CS5.5 install with the same files. I found a discussion from last year at http://forums.adobe.com/thread/1009064 , where the issue was apparently resolved with a CS6 update. I, however, did not install After Effects until March/April of this year and I am experiencing the same problems as the unfortunate users of Premiere and After Effects in the beforementioned discussion. Screenshots in that discussion are exactly like the issues I am seeing, I've posted a couple of frames below. FYI, I'm on windows 7 pro and using the calibrated{Q} XD decode and MP4-EX import QuickTime Pro extensions, graphics card is a GTX 680 with stable drivers, and 16Gb RAM on the mobo - I just checked Creative Cloud and AE CS6 is up to date. Does anyone have any helpful tips about what I could do here, or insights into what the 2012 problem was and why?
addition: my present workaround is to stay at frame zero, apply effects and layers, clear disk cache and purge all memory... then set to render (without ever scrubbing or RAM Previewing)... this sometimes works. Of course, I need to define the endpoint of the clip as well... prior to the render run I make the duration decisions I need to (which is why the media cache file deletion is required), save and quit out, then come back in for the render session... less than ideal. The workstation has a fast Tb drive, it's only a few months old... I am almost certain this is a CS6 decoder interpretation issue not a source footage or hardware issue.
... also, once I scrub through the timeline and notice an artifact it stays on that frame consistently for that session (and it also means there will be other torn frames on the clip), and purging memory can make it go away - but further scrubbing in the same session will introduce an artifact again either in the same place in-frame or somewhere else. The source footage is presently interpreted as upper field dominant, if I change that to bottom field it moves the artifact somewhere else on the frame... once again, purging all memory and clearing the media cache makes it disappear back to it's *original* state. I'm also noticing that the artifact ISN'T a frame or field next to the *bad* frame, but a fair distance away on the timeline, and not consistently so (eg: not 25 frames away, some seemingly spurious amount).

Rick Gerard wrote:
If you are having problems decoding footage the first step would be to transcode the footage to something like a JPEG compressed Quicktime. Just use the AME or AE or Premere Pro to do so. If you don't know what I'm talking about then type rendering in the AE Search Help field at the top right corner of AE and read some of the materials you'll find.
I'm trying to avoid having to transcode, Rick In fact, I'm more interested in why you're suggesting I should transcode for CS6 when it's not necessary for CS5.5 (which I don't have access to unfortunately, it was a colleague's 5.5 version that we tested on with the same XD CAM EX footage, and it's being used on another project). I dearly hope that isn't the only solution, although thanks for the suggestion

Saving source footages and FCP project in EXTERNAL Hard drive

I have ran out of space in my Inbuilt harddrive of the computer....
Now i have got a new project to be done and i have external 1 TB hardrive.....
So my question:
1.) Can i save the source footages in External HD?
2.) Can i save the project in External HD and edit it and do everything as in External HD?
I have never done such thing so help would be acknowleged.
Thanks and if i am missing any information then do let me know!

Hi
YES - BUT
• External Hard Disk - MUST BE - Mac OS Extended (hfs) formatted (all mine are journaled)
• Should be FireWire or Thunderbolt - as USB/USB2 performs badly to me and especially when filling up.
• I do - create a folder on My external HD named as Movie project + date
- then Start FinalCut
- AND set up ALL Scratch disks to this folder
- then SAVE projects - and direct this to same folder
- then I also make a folder in this project folder (on ext.HD) named material - and in this I collect all photos, audio-files (all converted to .aiff - NO .mp3 or other) AND all texts in a text document to copy from e.g. Title, contributors etc. SO also a document describing how the project is to be done - sort of synopsis.
PROBLEM
When changing Scratch-disks in FinalCut Express or Pro (FCP-X i don't know) one must when starting up next time - FIRST CONTROL - where they are set - as they do not orient after project but after last settings. All material and Captures etc - can be stored in a very wrong location IF one doesn't keep this in mind !
MY OWN experience - very tedious to clean up - BUT at least FinalCut Pro can help in collecting in all parts if they go astray.
Yours Bengt W

Warp Stabilising footage after changing the size of the video frame size

Hi everyone. I was wondering if anyone could resolve a problem I'm having with Warp Stabiliser in Adobe Premiere Pro CC. So I'm editing a video for a client and unfortunately a few scenes feature some camera shake, which don't look that aesthetically pleasing so I'm trying my best to get rid of the shake using Warp Stabiliser. I altered the frame size of the video from 1920x1080 to 1920x800 so I can have the 12:5 anamorphic look, however when I try to use Warp Stabiliser now a message pops up saying that it requires clip dimensions to match sequence and that I can fix it by nesting. I'm confused by this, I was wondering if anyone could help me by letting me know how to get round this, cause I would hate to have to do the entire video agin just because I altered the frame size. Thanks a lot.

For the warp to do its thing the clip needs to be the same as the sequence settings.
If not you get a warning like you have experienced. The only way to solve this is to nest the clip and then apply the warp to that nest.
On a side note i would edit everything in 1820x1080 and on export make it 1920x800.
For reference in your edit you can make a pillerbox matte in the titler.

AE: Warp Stabiliser error in CS6

I am attempting to stablise some footage in After Effects CS6, but am receiving the following error:
After Effects error: Could not launch Adobe Analysis Server (515)
( 25 :: 101)
I have tried everything on a discussion that deals with a similar issue, but have been unable to resolve it: http://forums.adobe.com/message/3657081
I have re-installed After Effects, restarted my computer, checked to ensure that dynamiclinkmanager.exe is running (it is).
Some information:
- I am using the latest install of After Effects CS6 (vers 11.0.0.378)
- My operating system is Windows 7 (64 bit) vers 6.1
- I have tried different types of source footage (uncompressed footage from a Canon 7D, as well as a compressed H.264 .mp4 file). My clip is about 4 seconds long (around 17 mbs, at its most intense compression), so definitely not too big for AE to handle. It's all running off an internal disk drive.
- I have only just installed CS6, and have never been able to use the warp stabiliser before.
Yesterday, I was attempting to do this in CS5.5. AE would crash as soon as I applied the warp stabiliser effect (prior to even analysing the footage).
Today, I'm able to apply the effect without crashing AE (again, prior to even analysing the footage), but it gives me an error message.
- I'm not running any other sofware. I have 8GB RAM allocated to my Adobe products, and I am multi-processing with 4 CPUs. I comply to all OpenGL and Adobe AE requirements. I am not using third-party plug-ins.
I am defeated. Please help?

Ah, I beg pardon for the general statement. I meant to say that I'm not running any other Adobe software (or any other RAM-sucking programs).
I am using Microsoft Security Essentials. I've checked through its history, and been unable to find anything refering to Adobe activity.
Could you please clarify what you meant by 'network configuration is properly configured as is your devices'? I changed my network's channel number a few months ago, which has only gone to improve my connectivity. I have no other custom configurations.
I've just downloaded the Process Monitor and will run it when I've got After Effects up again. Will post back with details once I get them.

Warp stabiliser in Premiere CS6 crashes

Hi
Been playing with Premier CS6 since downloading yesterday.
I am getting regular crashes (windows tells me premiere has stopped working)
I add a clip onto he timeline, I add the warp stabiliser, analyise then play back - I go back to effects to change some warp settings, and the crash occurs.
Anyone else seeing this before I report to adobe
Thanks
Chris Anderson

Project file WITHOUT Warp Stabilizer on my clip was 3.5MB. WITH Warp Stabilizer it jumped to 7.6MB....
Now you're seeing it...
Here's where I realized something was amiss: I had a less than two minute sequence, all hand-held footage, that I wanted to stabilize. There were only about 6 or 7 clips in the sequence, and no other effects. I dropped Warp Stabilizer on the clips, and let it analyze... it took awhile, but I was OK with that. When it was done, despite Warp Stabilizer being a GPU-accelerated effect (after analysis), most of the clips were red bar. Hmm...
So, thinking maybe I just needed a restart, I saved my project. And I waited. And I waited some more. About a minute later, my project final stopped saving. Weird. So I tried to do something in the Timeline... and it was like running through a tar pit.
I killed off Pr, and went to check my project file... it was over 50MB... for a 7 clip, less than two minute sequence. That's a problem. When I finally got the project open again, I purged all the Warp Stabilizer instances, and saved a new copy of the project. This time, it was about 1.3MB. That is a HUGE difference, all attributed to Warp Stabilizer. Needless to say, I'm very reluctant to Warp Stabilizer do its damage to my project files, regardless of how good the output is.
So, let this be a cautionary tale. If you think you'll only need to stabilize a few seconds here or there, or you're totally cool with working in a completely different project to stabilize your footage (though look how well that worked for me), go for it. Fair warning...

After Effects : Warp Stabiliser issues

I've been hitting the Warp Stabiliser in After Effects pretty hard and have noticed that it likes to get distracted by moving objects in a scene. I can't work out what is the triggering factor? It's attention will wonder, even if there is relatively stationary content present in the image. Here is an example video...https://www.youtube.com/watch?v=C_F57iP3tSQ
I thought that I could fix some of the issues by dialing 'stablisation' in and out, but there is no way to turn the 'smoothness' up or down.
Strangely Adobe hasn't included a handy animate stopwatch button on any of the Warp Stab. functions apart for the 'additional scale' option. It would be nice if we could define an area with the mask tool and have the Warp Stabiliser use the area under the mask as it's reference data.

Thanks for the comments.
What concerns me with using this feature in the future, is the unpredictability of it's 'solves'.
Warp Stab works great for most things, including the little girl in the example video, but her arm flying out suddenly ruins the track?!?!
I had a long section of footage that I wanted to use. The Plug-in didn't flinch at her bouncing about or other limb moments. The reaction to her arm was the only error, and I was compelled to remove Warp Stab from the entire section to maintain continuity (link to final piece https://www.youtube.com/watch?v=P_tEqSgDjLg ).
Despite the plug-in being extremely speedy, I feel that now I'm going to have waste some time doing a 'test run' to see what unpredictable event will break the effect.
I chose all of these examples deliberately to illustrate common video content that we have to deal with. Bread and butter stuff.
There are no radical camera moves, outlandish colour combinations, or extreme lighting set ups.
These are the sort of shots that an editor might say 'chuck Warp Stab at it cause there is nothing worth spending a lot of time on in here'.
I appreciate the 'ripples in a pond' example, which is why I was disappointed that there is no way to 'dial in/out' or 'dampen' the effect.
Isn't Bijou like ten years old? I would have thought that technology would have moved beyond it's capabilities?
I feel that this feature should be more accurately titled...
The 'Smooth out any motion when someone is moving along a liner path' plug-in

Problem:Imported video is choppy and then camera stops playing

I'm using a Sony DCR-HC96 connected to my Macbook, tried both Imovie HD and Imovie 08 and I have the same problem. When I try to import the video, the playback from the camera is very choppy, and after a few seconds the camera stops playing. If I just play the camera without importing, the footage is good. Sometimes the choppy-ness is right away and other times i will be able to import a few minutes and it starts again...
Addendum: Just realized I posted this in the Imovie 11 forum. My Bad, as the saying goes..I will post it in the Imovie 08 as well.
Message was edited by: J.M. Lachance

As the drive fills and you're going farther and farther into the disk it gets more and more problematic. When the drive is empty you're writing on the outer portion of the disc. The more it fills, the disk area gets narrower and narrower and slower and slower compared to the outer portion. USB drives that deliver information in bursts have more problems with this than drives that have sustained throughput like FireWire. For video, which requires sustained data delivery, this can be a problem. Depending on the computer and how full its drive is you can sometimes get better performance with DV capturing to the internal. It might be worth a try.

Application Builder and Corrupt VIs

Howdy All,
I'm developing a Medium-sized application in LabVIEW 7.0 used for instrument control. This application has grown over-time, and currently contains approximately 400 VIs. The basic structure of hte appliation is one main VI that has an instrument status display on the bottom, and a sub-panel on the top, into which all dialogs are loaded for user interaction. Each major task has it's own VI that is loaded into the subpanel as appropriate.
I've read a few stories on the developer exchange about VIs becoming corrupt. I thought these were freak occurences, because by and large, it appears that LabVIEW is fairly stable. However last week I had a VERY scary experience.
I was demonstrating to a collegue the properties of an XY graph control. We changed the colour of one of the plots, then hit cancel. LabVIEW complained of an internal error involving undo.cpp and proceeded to crash. I figured the crash was caused by some strange sequence of events, didn't think much of it, and reloaded my application. After making some changes, I went to the Application Builder to build the application. However the application Builder was complaining about a "missing board" in the DEFAULT build file. I knew immediately that something was VERY wrong. (When I say default build script, I'm referring the default script that is loaded when you press the "Build application or shared library..." button in the tools menu).
(As a side note, does anyone know why the LabVIEW application builder gives such terrible error messages? I always get that "missing board" error when either: one of my support files cannot be found, or one of my dynamic VIs is not executable. Since the error doesn't pinpoint a file, I neeed to go through the files one by one - which is a pain because I have a lot. Another question, why does the application builder ALWAYs ask if you want to save changes to build script, even if you haven't made any changes?)
After loading my build script for the application (which I've used HUNDREDS of times), I got the "missing board" error. I didn't think there was a problem with any of my paths or VIs, but I went throgh each included support file and dynamic VI in the build script to make sure it was there. Though there seemed to be no problems with any of the files, LabVIEW continued to complain.
I figured the problem was specific to the computer I was working on, so I copied the source to another development machine to complete the build. I was VERY scared to find that I got the SAME error on the DEFAULT build script! Also, my actual build script refused to load properly.
This was late at the end of a long day, so I decided to turn of my machines and go home. The next morning, everything worked fine - I was able to build the application, and I haven't had a problem since. (Maybe it was a bad dream, but I have clumps of hair on my desk from the night before...)
I found this experience to be UTTERLY TERRIFYING. Once I had to revert to an archived copy of one of my main VIs, because the current version refused to open, claiming it was corrupt. Since I don't know what's going on behind the scenes in LabVIEW, I'm afraid that tiny internal LabVIEW errors might be adding up. I back-up the source very regularily, since it is such a large project, however I have *real* way of inspecting the integrity of the source.
Does anyone know (A) why this might have happened - especially when the problem reproduced itself on multiple machines (B) has anyone had similar experience with internal LabVIEW errors or corrupt source (C) what sort of internal errors might be piling up that might cause a VI to claim it is "corrupt".
All input is appreciated.
WG

Hi Robert,
For the undo.cpp error, I got a couple different line numbers but didn't write them down. If I get them again, I'll be sure to get the specifics for you.
As for the "missing board", I also got that description a little wrong - the error I'm talking about is:
"Error 7 occured at Inovke Node in Dist read linkages.vi->Dist Cmp Settings to Disk Hier.vi->Build Application.vi
Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for hte operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Unix.
NI-488: Non-existent board."
As you can see, I meant "non-existent board". This error is very easy to reproduce - m
ake a build script and include some extra files. Save and close the build script. Move or rename some of the extra files included in the build. Reload the script. You should get that not very helpful error.
Now that I think about it though, maybe that NI-488 error refers to GPIB control, which I think I have installed, but don't have a GPIB card installed... hmmm... no reason that error should be popping up *there* though...
I could have *sworn* I would also get that error when one of the dynamic VIs in the build is not executable, but I can't seem to reproduce that right now.
Tying back to the original thread - what makes a VI corrupt? I imagine if you cracked the binary file open yourself and messed around with some bits you would probably make the VI corrupt, but I'm assuming that editing a VI normally (ie through LabVIEW) should NOT cause the VIs to become corrupted. Any information on VIs becoming corrupt? Is it somehow related to the undo.cpp errors?(when trying t
o undo some last change that wasn't recorded properly, the VI is modified improperly - after you save and close, it won't reopen?)
Victrick

Source footage is 16:9 but canvas doesn't match

http://www.youtube.com/watch?v=JDLJQalRTxo
Above is the link to 6 seconds of footage. The first 3 seconds is a still that shows the aspect ratio of the canvas, and the second shows the aspect ratio of the source footage in QT. I am trying to figure out how to get my canvas to properly represent the source footage. The canvas is cropping the footage and distorting it.
I shot this on a PD170 with the 16:9 setting on, with the addition of a wide angle lens. I also have the sequence set to anamorphic.
Any suggestions are appreciated.
Ryan

Ryan Andrzejewski wrote:
Thank you for the post. I've tried to right click on the clips and select that option, but it tells me that it is not available for those files. Is there somewhere else I should be looking?
I'll break it down step-by-step in case you're skipping a step
Make sure your Browser is in List View.
Select all of your offending clips (I guess everything you've captured) in the Browser
Scroll the Browser to the right until you see the Anamorphic column (it might be a lengthy scroll)
Once you see the column, right-click in the column for any one of the selected clips and select Yes from the shortcut menu. All of your clips will now be anamorphic.
But be sure to right-click, simply clicking (or left-clicking) will only toggle the property for a single clip (and deselect all other clips).
As JSL has already mentioned, you might need to re-edit your clips into your sequence if you've begun editing. (Either that or clear the distort property of the clips added so far, but please confirm that your sequence is set as Anamorphic.
Or is that what you've been doing?

AE6 on OSX 10.6.8 - blank source footage upon import

Hi.
This is driving me mad.
Running AE 6.0 on Macbook Pro OSX 10.6.8.
I am having an issue when importing .mov source footage. The clips play fine elsewhere, but upon import to AE, the thumbnail is blank and when dragged into the timeline the comp shows the clip as blank. No audio either. I do NOT have wireframe enabled, although it does show me the bounding box pixels and center marker of the clip. When I import the same way something like an mpeg or .psd image, they display fine.
They are Apple Intermediate Codec .mov files. I also tries transcoding to ProRes. No change. Same problem. Tried reinstalling QT 7.6.6. I have that version as well as QT 10 installed.
What the hell is going on?

Why do you have two versions of QuickTime installed?
What exact version number of AE CS6?
Also, try this: troubleshooting QuickTime errors with After Effects

Warp stabiliser rendering not improved by gpu

I have two PCs, both of which have an Adobe approved GPU installed. One PC has an Nvidia card, the other PC an AMD card. Both PCs/GPUs are recognised by the Mercury Playback Engine hence enabled in Premiere Pro. Although generally, I can see the advantage of the hardware accelerated effects in Premiere Pro, there's one effect which despite being supported, appears to be no different, and that's the Warp Stabiliser .
If I apply the warp stabiliser effect to a clip, the time taken to render is no different, regardless of whether the Mercury Playback Engine is hardware accelerated or not. I'm using the latest version of Premiere Pro CC on both PCs, and this is the only effect (at least from the hardware accelerated effects I've used) that I see no difference.
So two different PCs, both hardware configurations supported, and clearly the GPUs are doing their job - except for Warp Stabiliser. Is this expected behaviour, or something else?
Steve

I have two PCs, both of which have an Adobe approved GPU installed. One PC has an Nvidia card, the other PC an AMD card. Both PCs/GPUs are recognised by the Mercury Playback Engine hence enabled in Premiere Pro. Although generally, I can see the advantage of the hardware accelerated effects in Premiere Pro, there's one effect which despite being supported, appears to be no different, and that's the Warp Stabiliser .
If I apply the warp stabiliser effect to a clip, the time taken to render is no different, regardless of whether the Mercury Playback Engine is hardware accelerated or not. I'm using the latest version of Premiere Pro CC on both PCs, and this is the only effect (at least from the hardware accelerated effects I've used) that I see no difference.
So two different PCs, both hardware configurations supported, and clearly the GPUs are doing their job - except for Warp Stabiliser. Is this expected behaviour, or something else?
Steve

Warp stabiliser choppy and corrupting source footage

Similar Messages

Maybe you are looking for