[Wayne Waag]

“I am convinced it is a flaw in Vegas.”

I still have a copy of Vegas 9 on my system and it works fine. One thing that you have not provided is your Project settings. For example, if you want to make a DVD and your project settings are simply NTSC DV (720×480), a high-res photo WILL appear blurry on the timeline, especially if you have a large preview display area–E.g. on a 2nd monitor. Change that to an HD project (e.g. HD-1080 60i). Once you apply these project settings, the timeline will become much sharper. In any case, it really doesn’t matter how it appears on the timeline–it only matters how it looks on the final rendered output.

wwaag

[Wayne Waag]

I took the liberty of downloading your file from YT. When streamed from my PC to a Sony Blu-ray Player, I could just detect judder on the first lower right to upper left pan, none on the next two, and perhaps just a little on the last. There were never any noticeable jumps or jitters, no tearing–just smooth playback. If you’re concerned you might back off on the amount of zoom or increase its duration, but really, I think it looks quite good, as is. Any noticeable jumps, jitters or tearing are due to poor PC/internet performance.

wwaag

[Wayne Waag]

To me, it looks like your pans are simply too fast, resulting in judder. If you can, try an external media player just to make sure they produce the same effect.

wwaag

[Wayne Waag]

Is the problem only when you play it on Youtube or does it also show up on the rendered file directly from Vegas when you “play” it using your onboard Media Player? At 30fps you will certainly get judder if your pans are very rapid. I do a lot of animation from stills mostly using Proshow Producer, but always at 60fps. I’ve found that files that play well on my PC or external media player, are often jittery when uploaded to Youtube or Vimeo, regardless of whether I’ve rendered and uploaded at 30fps or 60fps. My suspicion is that this is mostly an internet problem. If you right-click when playing a YT video, there is Stats for Nerds, which gives info on frame rate and dropped frames. Since the motion you create from stills is very predictable, any disruption in terms of change of frame rate or dropped frames will be readily seen as a glitch. Anyway, this is just my speculation. Maybe, just a faster internet connection would solve the problem.

wwaag

[Wayne Waag]

I’ve put together quite a few scripts over the past few years although I’m not a “script writer” from scratch. My understanding of programming goes all the way back to Fortran and Basic and little beyond. Although not the best way, I’ve taken the approach of learning from scripts that have already been written. I start with what I want the script to do, search for existing scripts that do similar things or at least have a similar process, and then learn enough to make changes. There are lots of free Vegas scripts that have been written over the years–just search. And if you get stuck, you can post your problem on the Vegas Pro scripting forum and usually get the help you need. This is NOT the best approach, but it does work. Just my nickels worth.

wwaag

[Wayne Waag]

For the easiest way of encoding with Handbrake from Vegas, do this.

https://www.vegasvideo.de/vegas-2-handbrake-en

Frameserve–No intermediates. As many would say, it works a treat. Try it.

wwaag

[Wayne Waag]

“Tech Support wanted me to reapply the CPU thermal Paste.”

This really sounds completely ridiculous. Even with stock cooling, your temps should not get that high. I have an older 3700k i7 that’s OC’d from 3.5 to 4.3 Ghz and air cooling works well–never above 70 deg C. during long renders. I’ve only had a BSOD once during the summer, backed the OC down to 4.2 and all was well. Although a hassle, your vendor should bear the responsibility.

wwaag

[Wayne Waag]

Thanks so much. I do have Vegasaur and had forgotten it also saves Toolbar info. I found another thread on CC where a part of the registry could be exported, but use of Vegasaur seems a lot safer. Again, thanks.

wwaag