Norman Black
Forum Replies Created
-
I downloaded and looked at the Youtube video frame by frame.
Not knowing what the source looks like I cannot comment much if at all but from frame 5 through 12 there is some big time contrast/sharpen/posterizing going on. I am not sure if this is what you state is the “bad” you want to get rid of. I don’t know if that visual is in the source video. Is that posterizing there or done in editing or happens in encoding or ?.You could upload 28 the sem 28 seconds of your source to Youtube for comparison.
I don’t see any resampling ghosts, so it looks like you have resample disabled everywhere.
-
[John Rofrano] “One last thing. Your source is DivX and Vegas “hates” DivX”
If his preview window looks fine, then if he gets good encode settings he should be okay. Yes/No?
I have not heard him complain that the Vegas preview window looks bad.
-
You are probably better off rendering to 1280×720 than 1920×1080 since your source size of 1280×768 is nearly identical. As John said there will be a crop, but there is nothing you can do to get around that due to the mismatch.
Anyway you are probably better off rendering to a little bit higher bitrate if you stick with 1080. The Youtube encoder is a bit better than the ones in Vegas.
Also since your source frame rate is exactly 120, I would render to exactly 30fps, not 29.97.
In the project properties, the field order is blank. Make sure it is progressive. I don’t know what a blank entry means to Vegas.
Not sure why you have 32-bit pixel properties set, but it should not harm anything. It will affect performance. It does not give you anything with 8-bit source video.
In your encoded video, not a Youtube result, is everything bad or only blocky in high motion scenes?
-
I don’t know what GOM player is.
Is the one on the right the original source video or something rendered elsewhere.
As for the one on the left (the Vegas one)…
what are the source video specs?
what are your project settings?
what were your render settings? -
[Omar Dorgham] “THE Question here: is there is anyways i can disable the auto graphics correcting in vegas pro ?”
You are going to need to be specific as to what is wrong/unexpected.
I know of no auto graphics correcting feature. Vegas as a rule does not auto correct/adjust anything at all.
-
I would suggest in order
1) Get the overall exposure where you want it. You can use color corrector, color curves or levels.
2a) Get your contrast where you want it. I suggest color curves.
2b) Get your color balance where you want it. Color corrector, HSL or Lab adjust, white balance. Color curves can be powerful here but it is a little harder to get desired results, at least for me.3) Get your saturation where you want it. Color corrector, HSL adjust.
This is an order but there is inevitably some iteration in this process.
-
[Debbie King] “Norman, a little over my head. Not sure of what you mean by nesting.”
Open the Vegas help. Go to the index tab. Enter “nest”. This will point you to a help topic names, “nesting projects”. Should be enough info to help you understand.
-
Youtube encode help
https://support.google.com/youtube/answer/1722171?hl=enI would encode to 10-12Mbps since the Vegas encoders are not quite as good as the x264 encoder used by Youtube.
Youtube re-encodes everything you upload and you have no control over that.
-
[Debbie King] ” It saves on memory. A complete symphonic piece can be saved in two to three stems.
“The only way to save memory and/or overhead is to render an audio mix to a file and then import that file onto your timeline.
If your audio is stereo you can use nested projects. Do your mix in a separate project and then place that project onto the timeline of some other project. Vegas only support stereo for nested project audio.
Other than that you have a track group as previously mentioned, likely running that mix through a unique audio bus as well.
It almost sounds like the stem you mention is like a video editor sequence. Vegas does not have sequences, but rather has project nesting.