Piotr,

No

with a clip like this it has a strong light source or highlight that runs along the window with a nice straight edge being the window so I tracked this light first right, left, right, and on each key tilting left or right in pan/crop made sure that the car window edge was parallel with my pan/crop window bottom. Then analyzed

at the same initial zoom in my event pan and crop window, after the first analyze its easier to track as the footage is more steady. after the first initial zoom and stabilize I was well within the black boarder so I just tweaked the 3 keys and added a few more then hit analyze again

edit:.... or simply track the car window bottom right corner

Rory

Am I the only one having trouble accessing their Website?

Actually, the plug in works, as long as you apply it to the event, rather than the whole timeline. It does a very credible job of stabilizing, IMO, equivalent to Mercalli or DeShaker. It doesn't seem to be any faster or slower than those stabilizers, either in analyzing or previewing. I gave it a real nasty clip of hand held video of backpackers hiking and it did as good as could be expected with this "torture test". For simple stabilizing it works fine.

But it is still an edge/pixel tracker. I'm still partial to the "2.5 D" Mocha, which allows you to designate planar objects in the clip with a bezier curve outline. Unfortunately, Vegas is one of the few NLEs that Mocha can't work with directly. You have to use it in After Effects and then load the stabilized (and re-rendered) clip in Vegas.

Just my 2 cents. I recently purchased all of the Video Esentials packs and I love them. I find myself using them in every final project render. Their products are quality and reasonably priced. I for one will get the new plugin soon and add it to my toolbox. Love this company.

L.T.

Made it in , finally, through the "back door."

I tried it on some footage of a football game that a friend of mine shot with his handicam and asked me to put on DVD last year. It has some pretty shaky zoom shots in it and IMHO NewBlue did a better job than Mercalli hands down. It zoomed in less which left me with a more usable area of the frame and it was more stable than Mercalli. Also that smeared frame edges mode of Mercalli is a joke. Totally unusable. It looks like NewBlue is doing a better job there as well. I like what I see so far.

Kudo's to Todor and the team at NewBlue.

~jr

"Made it in , finally, through the "back door."" Mmmmm, Jay, no personal details! ;-)

You never know who's reading these posts and when they'll be "listed" in some court filing..... ;-) Just a little "shaky" humor.

I tried the stabilizer out, so far I like it. Gonna try it on my 64 bit machine, if it works as well there I'll be purchasing.

OK .. I am trying this out as well.

I have used all the suggestions so far in this thread, but the "Analysis Required" will not go away.

Is there some magic incantation I am missing?? And yes, I did click on the event before clicking on 'analyze' .

It went through some moments of analysis, but then what do I need to do?

TIA,
Tom

edit: OK .. think I found the problem. The clip I happened to pick was from a point-and-shoot Canon digital still camera. It produces Motion JPEG clips. Seems the stabilizer cannot handle the codec.

Once I rendered the clip to a new track as an NTSC DV clip, it all worked.

I've been playing with this is the better part of the morning--pretty cool tool.

Perhaps I did something wrong (not unheard of), but I got a strange result. Probably because I set "Camera Motion" to 100 just to see what would happen.

The result is it looks like the image is on a piece of mylar that is warpping slightly as the clip plays. Can you imagine what that would look like?

EDIT:

Yes, that's what did it. When I dropped "Camera Motion" to 50, it no longer has the warpping effect in it.

LT...
a couple more raves likes ours, and we'll have enough two cents contributions for a free cup of coffee... lol
* * *
I've Essentials I and III ... love it... the Light Rays thingy is so cool - makes titles and captions really pop ...
I'm downloading the trial myself this evening just to see for how it works...
I think it might have a few preset tweaks that might come in handy for an upcoming project...

I also like NB very much. . . especially since one of them responded here about the troubles a fe encountered... I really do respect a company willing to simply acknowledge customer questions and complaints, let alone respond and explain... simply amazing...!

Until that time... Earl J.

Todor, following up on John's post above, I've noticed that the terms in the Stabilizer's help information do not match the terminology on the UI.

In the help info it refers to the "Stabilize Group" and on the UI it's referred to as "Step 2: Stabilize."

In the help info (under "Stabilize Group") it references "Inertia" and "Allow rotation." On the UI it's "Camera Motion" and "Fix Rotation."

May I suggest that terms, references, and explanations be in unified so as to eliminate any confusion or misunderstanding on the users' part?

Thanks!

Jay,

Another oops. We made some last minute changes based on feedback we got to make the UI as understandable as possible, but these chanfes didn't make it back into the help.

We have updated the help files with the corrections along with some additional information for working In Vegas.

Also, this latest includes a fix for quicktime files, which were timing out because of slow file read times.

http://www.newbluefx.com/downloads/Windows/NewBlueStabilizerForWindowsSetup13.exe

Thanks,

Todor
Todor

Todor, your openess and your marvelous attitude have gone far to sell me on NewBlue FX's Stabilizer. Yeah, having a good product helped at little, too.

Thank you!

Marvelous customer support. My only knock is really, that kind of things should be caught in Beta. If a beta program is used. I know many companies cut back on that stuff these days since money is tight.

Should I need an integrated stabilizer in Vegas, I'll certainly give this a look. Just not a need I have right now.

Because of this thread, I installed the demo on 8.0(c) -- running Windows 7 64 Ultimate. The examples from other people looked great. Unfortunately:

It. Does. Not. Work. For. Me.

I ran into the maddening "select the clip first then press analyze" problem. After reading posts above, I thought I knew better and so I wouldn't have the problem of clicking "analyze" only to have the text "analysis required" stay on my preview window. Wrong. Here is what I did and observed:

1. Add event to timeline. (Separately tried DV, HDV, and HD at 24p and 60i).
2. Click FX, add NewBlue Stabilizer.
3. Select a preset.
4. With FX dialog box open, single click on video event so that it is selected as NewBlue has instructed.
5. Click analyze button. (OK, 5 & 6 is where folks got confused before, right? Not me, right?)
6. Wrong. What looks like an analysis progress bar in a separate box pops up quickly, then disappears. The "analysis required" in blue text still appears in my preview window.

Argh. Would someone please tell me what I'm doing wrong? This looks great, based upon the examples, but even following instructions perfectly it won't work (for me).

Thanks,
Steve

Steve,
Probably nothing - see my previous post.

I know you said you tried SD, HD etc., but I am suspecting something wrong with the way NB looks at the codecs.

It did for me exactly what you saw, with a clip using MJPEG, but worked fine with an HDV clip. Too bad it didn't throw an error before closing the analysis window.

Haven't done too much more with it than that.

I am on 9.0c 32bit on XP-SP3.

Tom

Ok .. did some more testing.

Todor - I hope you're checking in.

I have successfully stabilized both SD and HDV clips. But here's an interesting twist.

I have two events on the timeline. Added the stabilizer FX to the first one, analyzed OK and we're sweet.

Added the FX to the second clip, selected the event, clicked analyze and the analysis progress window comes up for a moment and closes and I still see the blue "analysis required" in the preview window.

Tried more than once, no luck.

I then had a suspicion. I deleted the first clip, moved the second one to the start of the t/l and now it worked fine. Added a second clip, tried the FX and no joy - progress window just closes.

Seems the latest download version somehow requires the clip to be steadied be the first or only clip on the timeline.

Curious if anyone else is seeing the same behaviour.

Tom

Tom, thanks for the tips. Based upon your comments, I dropped a DV clip onto the timeline. When the head of the clip was not at 0.0 seconds, NB didn't work (per my first post above). Then I nudged the head to 0.0 and, what do you know, I actually got the stabilizer to analyze the clip.

When I dropped another event onto the timeline at a point after the first clip, no go. Same story as yours. Closed and restarted Vegas.

This time I tried native HDV and Cineform avi files. Here is where things got really, I mean REALLY, sketchy. I got NB to analyze clips only when the heads were at 0.0, but then the analysis crapped out after about 25%. The "analysis required" text remained on the preview window. If I nudged the very same clip past 0.0s, selected the event, and clicked "analyze", forget it: back to the "analysis required" at all times.

C'mon NewBlue. Really? This looks nice, and it's obvious that you have a loyal following, but I just decided that you're not getting $99 from me. Sorry -- maybe something about my pristine system doesn't play nice with the plugin, but I doubt it. For now, I'm going to (try) to uninstall the demo. If the stabilizer can be fixed, I'd be happy to look at it again. Thanks for the demo download.

-Steve

Works on my system without any glitches.

Well, Jay, I gathered that from your previous posts. ;) And it works well for others, too.

I'm just thankful for a demo, which let me know that I likely was in for a lot of wrestling and head-scratching to get this to work. (FWIW, I checked out the system specs of a few, including you, on this thread and it looks like there is no common denominator that would suggest an OS or hardware culprit.)

"... there is no common denominator that would suggest an OS or hardware culprit."

Agreed, so is it possible that NewBlue isn't the problem? Just like Vegas works on some systems and not others. Therefore, one is left with the idea that it must be an individual configuration issue.