Sampling Setting For Slideshow

tygrus2000 wrote on 1/26/2006, 6:37 PM
Working on a final render of my slideshow. I have very large stills on the timeline - they haven't been resized prior to adding them. Vegas is going to have to do it.

This part I have yet to figure out. Do I set Force Resample, Smart Resample or Disable Resample for the best final output quality.
thx.

tygrus

Comments

johnmeyer wrote on 1/26/2006, 7:30 PM
Leave it at default (Smart). For better quality, resample outside of Vegas or you'll likely get "shimmering" on horizontal lines. Lots of posts about this. Turning on "Reduce Interlace Flicker" for each still photo event helps somewhat (there are scripts that can do this automatically.
Chienworks wrote on 1/26/2006, 7:35 PM
Resampling affects frame rates, not image resolution. The setting that would matter to you is Better vs. Best under Project in the custom rendering window.
johnmeyer wrote on 1/26/2006, 9:06 PM
Oops. Thanks, Kelly.
Jayster wrote on 1/27/2006, 2:30 PM
Chienworks, suppose only part of a project has stills and you don't want to use "Best" for the entire project (huge render times). Would it work to make a nested veg file for the stills and then set the project setting to "Best" on only the nested file (e.g. with a 2nd instance of Vegas)?
farss wrote on 1/27/2006, 2:42 PM
As a nested project only imports the T/L data I think you'll find it'll all get rendered as Best regardless. You could render the required sections at Best to say Sony YUV and bring that into your final project and render all at Good, need more disk space of course.
Bob.
farss wrote on 1/27/2006, 2:55 PM
Here's my formula for getting excellent results from HiRes still in V6.0c:

Set project as 1080 HD. Apply GB to bus at 0.001 Vertical, 0.000 Horizontal. Encode to mpeg-2 as per normal. IF zooming stills apply Reduce Interlace Flicker to those stills only.

Why set the project to 1080?
Vegas calculates the amount of GB based on the project settings, if set to SD res you get way more GB than you'd like!
Now that amount of GB will not get rid of ALL line jitter etc, it'll get it to reasonable limits without blowing the res noticeably. My thinking on this is as more and more program is watched on non interlaced display devices the problem is going to just go away gradually in the future. At this setting the results are no worse than a lot of broadcast material (lots of line twitter in that too) and I've still kept heaps of the resolution. If however the remaining twitter really bugs you increasing the Vertical GB to 0.003 will kill all of it or else only apply 0.002 to the offedening stills or else do the following:
Make a duplicate of the photo on a lower track, apply no GB to the photo on the top track and 0.003 Vertical to the lower track. Use the Cookie Cutter to cut out those parts of the photo with twitter on the top track. You can use chained CCs to handle several parts of the image.

My 16:9 DVD PAL DVD with 1,500 HiRes stills looks stunning, thanks to Glenn all levels are even within Legal. Coming to an ABC shop near you shortly.
Bob.
Chienworks wrote on 1/27/2006, 5:04 PM
Jayster, there isn't any "good, better, best" setting for a project. These apply to the preview window and the rendering process. The rendering setting overrides the preview window setting. When you render, everything gets done by the setting you choose when rendering. There is no way to specify it by project or .veg file.