<<<-- Originally posted by Edward Troxel : You have several options:

1) Use a velocity envelope and then manually resize the clip after applying the new velocity.

2) Hold down the CTRL key and resize the event to the proper size. This will also change the speed of the clip (but you are limited to a single speed change).

3) Use Excalibur's Velocity Wizard which will automatically add a velocity envelope and resize the clip to match the new speed.

p.s. remember you can also combine the velocity envelope and CTRL-Drag technique on a single event. -->>>


and where can i find this....Excalibur's Velocity Wizard? is it some plugin?

Paul,

Excalibur and Neon are at: http://www.vegastoolsandtraining.com/

I have both and highly recommend them. Also, you might want to take advantage of the last few days of the 'Vegas 5.0 Companion' and 'Authoring with DVD Architect 2.0' training DVDs on special pre-order pricing. Gary's previous DVD set was a tremendous help in teaching me the Vegas toolset and workflow.

I'm not paid by these guys, just glad they've made such a fine set of tools and training products to help me.

<<<-- Originally posted by Paul Bisaillon : and where can i find this....Excalibur's Velocity Wizard? is it some plugin? -->>>

Just click on the link below my name for info on Excalibur, Tsunami, Neon, and other things such as the free newsletter.

Edward,

You just reminded me that I've been meaning to pick up Tsunami. I want to add a Picture-In-Picture effect in a project I'm working on and while I know I could do it myself, why bother when you've written the script to do it for me.

Thanks a ton for taking the time to create your newsletter. I faithfully print them out in full color for an immediately available deskside reference and have found them extremely helpful.

yeha... not happy dude..

basically i had some interlaced footage i was editing ran afew different speeds of slo mo..

all good in the timeline, final render looked so shit i wanted to scream.. and thats WITH supersampling on to 4..

switched to render as progressive from interlaced footage, now my slowmos are nicer than standalone slow mo apps like DynaPels slowmo and thats without supersampling... its absolutely beautiful now :)

Peter, what speeds do you slow your footage to? The timeline "should" be an issue of WYSIWYG. I've never had any issues with slow motion looking bad on output. I always render on "HIGH"- with a constant bitrate of 8 mb/s beings my programs are usually under an hour.

Peter, let me understand what you did. You captured as interlaced and rendered as progressive and that worked?

I believe this footage was shot as progressive and I rendered as each option I could find with no luck. (Couldn't figure out how to supersample) I thought I might try After Effects as they are supposed to have a great slow motion. I really haven't figured a way around the timing problem other than slow motion. (Stills are out of the question)

Possibly there are other settings I haven't tweaked?

Additionally, the clip, at the part where the bridesmaid is walking in runs at 21fps. It doesn't seem to ever get up higher when looping. If I RAM render, then it gets to 30 frames and then it is jerky. PAL runs at 25. Is there a way to make the clip run at that frame rate in NTSC?

This is killing me!

Charlie the footage from Bernard's two XL-1s's were shot in "frame mode" which is a faux progressive achieved through frame blending. It's still technically interlaced.
I'd think, if anything, progressive would provide choppier slow motion than interlaced. That's why I don't quite understand what Peter was explaining.
The doc me and Jesse shot was completly in "frame mode" and was treated as normal interlaced (60i) without a hitch.

When encoding to MPG2 try and use a DVD Architect template/preset. Make sure video quality is set to "High" and try a constant bit-rate of around 8 mb/s. Try that on a small section and see how it works out for you.

Again I wouldn't encode it as progressive- but if the above doesn't seem to help....it can't hurt to try.

Edward, have any input on this?

You activate supersampling on the video bus track.

Since you say it looks better at a lower framerate, had you track changing the "undersample" value in the event's properties?

vegas' mpeg2 encoding
 

i read an earlier post regarding rendering with vegas to mpeg4. they mentioned something about downloading a codec.

is this true also for rendering to mpeg2? do i have to download a codec?

I can import the video by USB, as a file, then import to Vegas. Or, I can capture through a composite "Video In" on a video card. That you ask, I now wonder if one of those two methods is causing the problem. I have in the past used the video from this camera without the notorious black frames. I can't recall which method I used for which. I guess that will be the next test. Thanks for asking, and I'll let you know the results.

Rendering to MPEG2 comes standard with Vegas and Vegas+DVD. All you need to do is go to File - Render As and pick MPEG2 as the format. Then you can pick any of the presets. To change the bitrate, just click on Custom.

does printing straight to tape require hard drive space?
 

when printing a project straight to tape, does this process require a significant amount of hard drive space? if so, is there a way to know how much?

It requires "some" hard drive space and the amount is totally dependent upon your project. When you do a PTT, it must render all sections of video that have been modified. So, if you've only applied a few crossfades here and there, it won't take much disk space. However, if you've color corrected (or done anything else that affects) large portions of the video, then those entire areas must also be rendered taking a significant amount of space.

Once all of the video segments have been rendered, it will then render ALL of the audio into a W64 file. If you have a 1 hour project, that would probably take around 600 meg.

ok. that's fine. i was worried a 1 hour project with many effects, color corrections and fades will take up more than 5GB or something in that range.

THANKS