Premiere Pro CC - Warp stabiliser issues

Hi,
Hopefully someone can help me out.
In Premiere CC whenever I apply warp stabaliser to a clip when It's finished stabalising it puts the clip in the top left corner. the clips moves around as if its being stabalised.
Any ideas?
Thanks.

Warp Stabilizer bug in new Premiere update

Similar Messages

Need help with premiere pro cs6 having performance issues please help

need help with premiere pro cs6 having performance issues please help

Welcome to the forum.
First thing that I would do would be to look at this Adobe KB Article to see if it helps.
Next, I would try the tips in this ARTICLE.
If that does not help, a Repair Install would definitely be in order.
Good luck,
Hunt

Premiere Pro CS3-CONSTANT Memory issues when editing/rendering/exporting

Alright, as said in the title I am currently using Adobe Premiere Pro CS3, and my issues are horrendous
No matter what, within 10 minutes of editing, Premiere will warn and then crash because of memory issues, starting with the message:
"Adobe Premiere Pro is running very low on system memory; please save your project and proceed with caution"
Also, whenever I try to export this project, within 800 frames of a 7000 frame project (currently), it displays the message:
"Error Compiling Movie", and then the previous message above if that hasn't already happened before
And eventually, the program will crash out of nowhere, with random windows errors
Here's my specs:
Intel i7 920 Processor
6 GB DDR3 RAM
Nvidia 480 GTX
750 watt power supply
24" Dell Ultrasharp Monitor
Now, I've noticed that whenever Premiere is getting close to crashing, my RAM gets up to around 4.7 GB being used, and then it crashes.
I have already gone into Edit-Preferences and tried switching from Performance to Memory; that hasn't fixed anything
I noticed that when I was just running my video over and over again, it stayed stable at 4 GB or so, so maybe its a rendering issue?
I have already tried lowering my number of processes running at any given time, including my antivirus program (Kaspersky) and even explorer, but it still crashes no matter what.
========================================================================================== ========
This is a SERIOUS issue for me, as even with all the normal crashes I could finish the video; but now I cannot even export my video at ALL without it crashing, and I have a plenty strong-enough computer to handle this, so what gives?
Please help

Ok, well this has been getting me nowhere
I tried importing (both my CTRL-X method, and literally importing the project), and now the program won't even RENDER the footage, it just errors out at 800 frames (just like exporting)
What is going on???
I used to use Premiere Pro 2.0 all the time, on a separate computer, but I have 6 GB of RAM, is this really impossible???
EDIT:
And now, even after finally getting it to render (by saving after rendering before what crashed, and then starting it up and rendering again), all my footage looks like crap XP

Premiere Pro CC - Warp Stabilizer causing "Heat Waves"

I'm using Premiere Pro CC 2014 and when I apply Warp Stabilizer to certain clips I get this weird heat-wave, shimmer-like effect. For the life of me I can't figure out why this is happening. I've tried singling out every variable that I can but nothing matters.
You can see what I'm talking about here: Dropbox - With WS.mp4
And here is the clip without WS applied: Dropbox - Without WS.mp4
The clips I'm trying to stabilize are actually pretty stable already so it shouldn't be an issue for WS normally. It doesn't seem to make a difference whether they're in a 720 timeline or 1080.
I've tried every setting in WS that I can, including 'detailed analysis' and 'enhanced reduction' on Rolling Shutter Ripple. The only thing that kind of seems to help is applying the rolling shutter repair plugin but even then it's still somewhat choppy.
The shots themselves don't have any noticeable rolling shutter ripple (slow moving grass shot on a monopod) and they look great UNTIL I add Warp Stabilizer and they get the weird effect. Even though the clips are already pretty stable, I just want to add WS to smooth some of these clips out a little bit. When I replace the clips with an AE comp and WS in AE it's fine! But I want to figure out why this is doing it inside Premiere so I don't have to use dynamic link every time I want to use WS.
I just got this machine, maybe that has something to do with it...I have no idea.
System info:
Mid-2011 27" iMac
3.4 GHz Intel Core i7
12 GB 1333 MHz DDR3
AMD Radeon HD 6970M 1024 MB
OS X 10.9.5
Adobe Premiere Pro CC 2014.1
Shot on a 5D Mk. III with either a 24 (1080p) or 60 (720p) frame rate and resolution.
Can anyone help? Thanks

I don't have answers for you. Sorry. But I have seen that once before on a clip I stabilized. Much like the grass shot you show in your mp4. Mine was of a guy sitting at a pool and the bright plants behind him where flickering like a heat wave/desert-like effect. Only one clip had it and it made me go "hmm...never seen that before." I stabilized hundreds of clips in that project and that was the only clip with that heat wave thing happening. I was on 7.2.2 at the time. And eventually went to 8.0.1 with no change. It didn't bother me enough to do anything about it so I left it. It was shot at 1080p60 from a Panasonic PX270. Strangely I have the same computer as you (except I have 16gb of ram and I'm on 10.8.5). That is very interesting to me that it worked great in AE. Interesting indeed. I'll follow this thread in hopes of a revelation. Fortunately, I don't see that issue much or I'd be screwed.

Premiere Pro CC Warp Stabilizer with activated Mercury Playback Engine - GPU doesn't use the Nvidia GTX Titan GPU - CUDA

Windows 7 Pro, fresh installation, include all updates
Premiere Pro CC - actual version
Gainward GTX Titan Z - actual firmware and driver
SSD Hard Drive
Intel i7/ 960/ 3.2GHz/ 32GB RAM
Mercury Playback Engine - GPU is activated.
Card is known by standard in cuda_supported_cards.txt
Selected Clip: 1920x1080i, 25fps, AVCHD/mp4
Seleceted effect: Warp stabilizer with Subspace-Warp (Standard-parameters)
Step 1: Analyse the clip
The Intel i7 is working with 90%, not the GPU
The status monitor of the Nividia-card shows 0% used performance
Playing the analysed clip (informations from the Cuda Render System):
Total render time: 26ms
Display FPS: 0.82
Scheduler FPS: 2.28
Target FPS: 25.00
Rendered FPS: 3.50
Total: 239
Dropped: 234
=> Playing the analysed clip is dropped extremly.
Step 2: Rendering the clip
The Intel i7 is working with 90%, not the GPU
The status monitor of the Nividia-card shows 0% used performance
The Warp Stabilizer is shown as a GPU-Cuda supported effect.
The GPU doesn't help the Intel i7....?!
Please help me!

Thank you for your fast response!
Warp-Stabilisation shall be a GPU accelerated effect.

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.

Macbook Pro Retina 2014 Top Spec - Premiere Pro CC Graphics Card Issue

Hello,
For 12 months I have been having graphics card issues which all started on my 2011 MBP, which Apple replaced 12 months ago. I Then got a new shiny, 2013 highest end retina macbook pro from apple, in which after a couple of weeks had the exact same graphics issue. As soon as I start working in Premiere Pro with my 1080P DSLR footage, once the fans get up high, then the graphic colour hologram like start pooping on my screen. Now I got that retina replaced as I alerted apple about it, now they have given me the highest end 2014 model, and guess what? The problem is twice as bad.
I think it's definitely got something to do with the Apple software. It's weird though, because on the rare occasion, the graphic poop will show up on my screen when I am on Youtube (only once in a blue moon it does that) - it does it every single time 15-20 mins into editing with Premiere Pro, once the fans get hot. I can click on the graphics poop and it makes it disappear, which is weird, maybe that proves it software issue?
I don't know, but this problem has caused me to go through two of apples most powerful laptops, 60 phone calls to Apple, 1 investigation lodged to the Apple Engineers (the people who are above the Senior Apple Care Advisors) - Nothing seems to fix it, and I haven't been able to create any more intriguing films on my laptop because Premiere Pro CC just brings up all the graphics poop.
Screenshots:
http://imageshack.com/a/img537/653/IgdBK9.png
http://imageshack.com/a/img538/9601/WLQYnM.png
http://imageshack.com/a/img538/152/EIFd22.jpg
Does anyone know what causes this exactly? How do I fix it?

JGFilm88
Thanks for the follow up information for my video card/graphics card question that came to mind out of curiosity.
I do not have Premiere Pro and am strictly and Elements Windows user. Otherwise I would look into this matter for you first hand. The place you want to be is in the Adobe Premiere Pro Forum, although, as you already mentioned, the screen display irregularities have appeared when Premiere Pro was not being used. Have you tried uninstalling Premiere Pro to determine if its removal from the computer resolves the screen display irregularities for whatever you are doing in the computer applications like iMovie? For that matter, do you see the problem in iMovies?
Just some thoughts to think about as you compose your inquiry for the Premiere Pro users in the Premiere Pro Forum.
Best wishes
ATR

Premiere Pro CC 2014 encoding issues due to graphic opacity settings?

Our marketing team has been working on some instructional video content in Premiere Pro CC 2014 and have encountered issues with encoding the completed sequences. Our output format is HD video with the H.264 codec, 1920 x 1080, 30 FPS.
The symptom of the problem is that the encoding process cannot proceed beyond 50%, and in some cases, does not start at all. Simply put, we can't encode any videos to completion.
We think we have isolated the issue, which we initially believed was due to video format differences between the two cameras used to shoot the footage. An EPS logo was present throughout the video with reduced opacity (80%). When we removed the logo, the videos began encoding properly, and to completion. When the EPS logo was included at 100% opacity, the videos also encoded properly and to completion.
Has anyone else been encountering similar issues in Premiere Pro or After Effects CC 2014? If so, what was the resolution? Is there a known issue with the opacity of graphic assets in video encoding?

I've occasionally seen problems with say multiple masks & final render-out/exporting, but I've not seen one here on a graphic's opacity causing a problem. It's a very common part of the tool-kit, of course, for most pro/semi-pro editing. Even a lot of amateur stuff.
Which leads me to wonder what would happen if you created a fresh graphic of some sort, applied it a partial & full opacity, on a SHORT clip ... just to test things. Trying to establish if it's graphic opacity in general as your problem, or this specific graphic and/or its settings.
Neil

Premiere Pro CC audio corruption issues

Hello Adobe community,
I've been editing happily on Adobe for several years now, and I'm not sure if it's CC, Mavericks updating and/or getting a brand new top-of-the-line 16GB/ram MacBook Pro to edit on, but every time I close and re-open premiere pro CC, the majority of my audio simply disappears -- sometimes it does it in the middle of an edit. The clips are still there, but they no longer have waveforms and don't play back. Sometimes it's most audio clips, sometimes it's ALL audio clips. It's inexplicable. I don't have any plugins installed or effects, it seems arbitrary as to which clips drop out.
There is a temporary and EXTREMELY aggravating fix, which is to match-frame each corrupt audio and then manually re-insert every single corrupt audio clip.
However, once a project gets to a certain point (what point, I still have no idea), the audio is BEYOND saving. I can't match frame and hear anything. I also can't re-link the corrupt file to its original -- the audio will never come back. This is so frustrating I can't stand it. Entire projects have simply become corrupt and it's not even possible to open a back-up successfully (once the audio drops out on one version, it seems to exist across the board across prior versions). I never had any issues when I start and work on projects from my hefty iMac -- it seems to have something to do with being on a MacBook Pro. So when a project gets corrupted, I've even tried immediately opening a clean back up on my iMac, but the audio is STILL corrupted.
I have tried so many fixes for this I'm going insane. It seems to happen most when I'm running off of an external harddrive, though I've tested it with so many different brands, capacities and connections (thunderbolt to FW800 to USB3.0) -- it doesn't seem to make a difference. I've lowered my buffersize to the minimum, have tried mimimizing all of my tracks so no waveforms are visible, i've tried rendering everything, moving scratch disks, pre-transcoding all footage to Pro Res 422 with 48khz audio, everything. I've also filled out bug reports to adobe, which I have no idea if they're ever seen or not. I rely on Premiere for my livlihood and I'm so desperate I'm about to go back to FCP.
Does anyone have any clue what this could be or any way you might be able to help?
Any help would be greatly appreciated.
Matt

All my footage is ProRes 4444 shot on the Alexa. Audio was recorded separately on a mixer, I can't tell you the model for sure but it generates poly track wav files. The wav has 6 separate tracks - five of which are being used. I've got another project, same footage/camera, same mixer/audio files and I haven't had any problems. There aren't near as many edits in that project and only four of the six tracks on the wav were used. They're still there, just no audio.
I'm using a 10 TB lacie big disk via thunderbolt in raid 0. I've had no other issues with the device or either port.
When it fails to playback I get the following error on the events screen:
'A low-level exception occurred in; Adobe Player (Player)'
I also used pluraleyes 3 to sync the project. When it output the xml for premiere it gave me a window that said 'this contains 5.1 audio data and pluraleyes may not handle it properly'. I didn't, in the timeline all the audio tracks were the same, it was the master mix on 6 tracks - no iso's. The wav files in the project widow had the proper tracks when I viewed them in the source monitor. Because the duration of the audio tracks were the same - I cut the iso tracks into the sync sequence I got from pluraleyes and deleted the audio tracks that originally appeared in the sequence. I mention this because as I said, I have another project that I used the same workflow for and haven't had these issues - yet. I also didn't receive the 5.1 message when I came out of pluraleyes.
Initially when I was having playback issues (the audio waveforms vanishing has been constant), I converted the 44.1 mp3 music files to 48 wav's to match the audio from the mixer. This solved the problem temporarily but now I can't get the audio from the mixer and the music to play in the same timeline. The only way I get playback is to take out the music, strip all the effects from the mixer audio and not have more than two tracks of audio simultaneously on the timeline.
Thanks in advance for any help/advice.

Premiere Pro CC 2014 Playback Issue / Crash Mac Pro 2011

Hi,
I've been having a big crash issue on Premiere Pro CC 2014, since the 2014.1 update.
2014.0 has been working fine this year but the update has crashed some of my biggest current projects.
Programs just starts fine, workspace responds, but anything related to playback just crashes or freezes Premiere.
My config:
Mac Pro Mid 2010
Processor : 2x2,93 6-core Xeon
Ram : 24Go 1333
2x ATI Radeon HD 5770.
I've been reading all major topics on this, this i did :
- disable Mercury Transmission
- Flushes Premiere cache
- Reinstall premiere
- Updated to Mavericks (issue happened both in 10.9 and 10.10 - thought updating drivers+opencl would help, then again no)
- Repaired permissions
- Tried with another user session
… and so on.
Nothing yet has solved my issue, anyone to help me on this major trouble ?
Thanks in advance, best regards !
Paul

Hi Paul,
Try the following:
Sign out from Creative Cloud, restart Premiere Pro, then sign in
Update any GPU drivers
Trash preferences
Ensure Adobe folder preferences are set to read/write in all 3 locations.
Delete media cache
Remove plug-ins
Repair permissions
In Sequence Settings > Video Previews, change the codec to one that matches your footage
Disconnect any third party hardware
Disable App Nap
Reboot
I placed the chief culprits in bold.
Report back if anything here worked for you.
Thanks,
Kevin

Premiere Pro CS6: Media Manager Issue

I can´t use Premiere Pro CS6 media manager. It begin analyze project but then come couple error messages. All my graphics files are .psd, all my video files are 4K .r3d and all audio is .wav files. Does Adobe team trying to solve this problem already? Below are links to the screen capture images about issue.
https://www.dropbox.com/s/qbnj7ctnzir21hn/premire_CS6_error.png
Dropbox - premire_CS6_error#.png

I would recommend doing all your file work with a proper file manager, like Finder.

Premiere Pro CS6 Mac Playback Issues

I've searched for similar issues, and while I found plenty of playback issues, I didn't see anything like what I'm experiencing.
MacPro Quad-Core Xeon 2.26 x2 (8b cores)
12 GB ram
OS 10.6.8 (can't update this due to other infrastructure)
Nvidia GeForce GT 120
FAST Fiber attached SAN
Local Raid0 media drive
I know the GPU isn't compatible with the Mercury hardware acceleration.
I've been a Premiere Pro user since version 2 and have kept current through the years. I'm happily running CS5.5 on PC's in my home office. I recently installed the trial version of CS6 on my Mac at work to evaluate for that environment, and I'm pulling my hair out trying to get over some basic issues. I have no problems with Media Encoder or AE.
In Premiere using preview or program (timeline), playback stops after roughly a second... though it varies by several frames each time. I tested this with various video files, .wav files, stills (jpeg, psd), etc. I even tested with black video and bars generated inside Premiere. The problem persists with all of the above... click play, and playback stops after about a second. Scrubbing works great... I've tried different playback resolutions. I'm not using any 3rd party monitoring devices or I/O cards on this machine.
I have FCP 7 installed on the same machine and have no trouble editing and playing 1080i video all day long.
Any ideas?
Thanks in advance!

The above suggestion worked for me briefly, but the problem keeps re-occuring.
I too am using Snow Leopard 10.6.8, NVIDIA gfx card (8800) and an ATI Radeon 5500.
Premiere played back fine in Lion and Mountain Lion, but I downgraded because I have old quicktime files and Final Cut 7 projects that i need to work with so Lion is not an option for me.
Bizarre behavior if you ask me.
Any help on this?

Adobe Premiere Pro CC render pixeled issue

Hi
i have a user who have an issue when she render the video she made with adding text to the video the render Windows look like pixeled ...
the image is not sharp very fuzzy and the text also is bad.
what can we do ? she add the latest version of adobe premiere cc
Thanks

Hi
this is what i have
What version of Premiere Pro? Include the minor version number (e.g., Premiere Pro CS5.5 with the 5.5.2 update). CC v8.1
Have you installed the recent updates? (If not, you should. They fix a lot of problems.) All of them
What operating system? This should include specific minor version numbers, like "Mac OSX v10.6.8"---not just "Mac". Windows 7 64 bits 32 gb of ram
What kind(s) of source footage? When telling about your source footage, tell us about the codecs, not just the container types. For example, "H.264 in a .mov container", not just "QuickTime".
Chemin d'accès au fichier : C:\Rachelle\OL Projets Vidéo\OL- Connect Launch\Assets\Vidéo\SONY\00009.MTS
Type : Séquence MPEG
Taille du fichier : 2,0 Go
Taille d'image : 1920 x 1080
Fréquence d'images : 29,97
Format audio source : 48000 Hz - compressé - Stéréo
Format audio du projet : 48000 Hz - 32 bits en virgule flottante - Stéréo
Durée totale : 00:12:40:15
Rapport L/H en pixels : 1,0 (1,0)
If you are getting error message(s), what is the full text of the error message(s)? none
What were you doing when the problem occurred? Working normally
Has this ever worked before? yes
What other software are you running? After effects
Do you have any third-party effects or codecs installed? no
Tell us about your computer hardware. Be especially certain to tell us about third-party I/O hardware (e.g., AJA, Matrox, Blackmagic, MOTU). none
Are you using Mercury Playback Engine GPU Acceleration? yes
Does the problem only happen with your final output, with previews, or both? Fully rendered previews are at a very low quality, when they are unrendere they look great (see attached photo)

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

Premiere Pro CS3: Rendered video issues.

My friend gave me her old copy of CS3, and I've been using it for quite some time now.
About 5 months or so ago I had to format my computer and lost a lot of stuff, after reinstalling premiere pro I got back to work recording my Let's Play videos.
Well when it came to editing everything worked the same. No issues whatsoever. It wasn't until I started rendering them out through Adobe Media Encoder that I started to have problems.
I've been using Fraps to record the gameplay footage, and created the project to match everything that the raw videos had.
Same framerate, size, audio, etc. Same thing with the rendering options in Adobe Media Encoder
I usually split my videos by 10 minutes to keep peoples attention on youtube, and use the uncut stuff for my blip.tv page. I generally stay within a 55 minute window, and those renderings used to work completely normally.
Now when I try to render longer vids (and on occassion I will get the issue with the short 10 minute ones) I will watch the video after rendering and see the audio and video start to desync as time goes on, sometimes the video freezes and the audio continues to play, and some other times the video will go completely black and the audio will continue on. It's very strange, and very aggrivating because it makes me waste more time to render the video again.
My computer deets:
Windows XP pro
AMD athlon II X2: 3.1 Ghz Dualcore
4 GB ram
Nvidia GeForce 9800 GT: 1 Gig VRam

>using Fraps
I don't, but some saved discussions that may help
these notes are for Premiere Elements, but may help with PPro
http://forums.adobe.com/thread/871095
http://forums.adobe.com/thread/943772
http://forums.adobe.com/thread/967201

Premiere Pro CC - Warp stabiliser issues

Similar Messages

Maybe you are looking for