ANOTHER SETUP QUESTION

USNRetired wrote on 4/4/2012, 12:02 PM
Shoot 1080 edit to Vimeo for private website use.

Open VMS HDP 10 and the welcome window opens, choice of New or Start.

Start gives you choice of Internet Video or Match media settings.
Choose Internet HD gives you 720.
Open Project Properties the template is HDV 720
Open match media settings and match media gives you custom 1080 template.
Edit video and go to Render As using Sony AVC or MainConcept gives you 720 template.
Or the correct selection was Match media setting vice Internet Video, thus giving you the Custom 1080 template to begin with?

Why do you setup for 1080 and then change to 720 to render?


Comments

Steve Grisetti wrote on 4/4/2012, 6:19 PM
As I say in my books, it's always better to set up your project properties to match your source video, not your output.

What model of camcorder is your video coming from and what format and resolution is it?

It appears to be some form of 1080 -- but is it 1920x1080, 1440x1080? Is it AVCHD or tape-based HDV or some other source, such as video from a still camera or pocket camcorder (or phone)?

The closer you can match your source video and project specs, the better the output results no matter what resolution you output.
TOG62 wrote on 4/5/2012, 2:01 AM
The closer you can match your source video and project specs, the better the output results no matter what resolution you output.

Is that really true Steve? I thought that matching source and project properties improved preview performance but not output quality.
Chienworks wrote on 4/5/2012, 6:09 AM
Correct. The only advantage of matching the project properties to the source is better preview performance. There is no quality benefit in the slightest because Vegas pretty much completely ignores project properties when rendering. The chosen rendering template overrides project properties in every detail except for deinterlace settings.

I always advocate matching project properties to the intended output. That way you get to see what the output will be like while previewing your edits. It also means that generated media will be produced at the best match for the output rather than being resampled/squashed/stretched.
Steve Grisetti wrote on 4/5/2012, 6:58 AM
Is that really true, Chienworks?

Are you saying that if I have a project set up for standard DV footage and I just throw DV, AVCHD and MJPEG from a still camera into the same project, it will all come out looking the same?
USNRetired wrote on 4/5/2012, 10:12 AM
If those that know have debate over procedures, imagine the wows of us beginners!

Steve-my HD comes from the GoProHero 2 camcorder that shoots MP4 and records onto a SDHC flash memory card. I shoot 1920x1080x29, it can be changed to lower settings. I have not shot anything from my new Panasonic HDC-TM900, I'm trying to solve these beginner issues before adding to my wows.

For us beginners using the VMS HDP software, I've taken the information provided from here and Vimeo to make a step-by-step worksheet. This helps to control the variables, there are some minor elements that may cause problems. Video bit rate has been bebated at different levels, depending on the level of action in the video (5-8). Matching media in setup, while changing for "Render As". Single media or multi media in one edit, this would give different results for each media within one edit.

Thus the benifit of forums like this, trial and error or success. I thank all of you for providing feedback vice say nothing to us beginners. Discussion moves the needle forward, not backwards.
Chienworks wrote on 4/5/2012, 4:20 PM
Steve: when you render, yes. If you render to SD then anything HD will be downrezzed to SD. If you render to HD then anything SD will be uprezzed to HD. Source that matches the output is left alone. If you're thinking that setting a project to SD would produce a poor quality HD output due to HD being downrezzed and then uprezzed again, this won't happen. Project properties are ignored during render.
Steve Grisetti wrote on 4/5/2012, 8:17 PM
So what's the point of project properties at all, if you can dump any type of video into any project and get the same outputs?
Chienworks wrote on 4/5/2012, 10:10 PM
Precisely to emulate what your final output will be so that you can see what your finished product will look like while you're editing.

Vegas *HAS* to work with some sort of parameters for frame size, rate, etc. You can't have video editing software that doesn't have some dimensions and speed while running through the timeline. It could be set randomly, it could match whatever size window fits on the screen, it could run sporadically or at some fps value that it judges the CPU to be capable of. However, wherever these values come from, they do exist. So why not have them meaningful?

Now, generally, i'd be willing to bet that the vast majority of edit sessions end up producing an output with the same properties as the input. In this case project properties are a no-brainer. In cases where they don't match, well, i already know what the source media looks like. I'd like to know what it's going to look like in the output, and i'd like to be able to see that as i make my edit decisions, apply effects, add titles, crop, pan, etc. And i'd like to be able to do that without having to render a snippet every time i make an edit. Setting project properties to match the output is what makes this all possible.