Vegas to Youtube, Vimeo, Web -- A New Look

musicvid10 schrieb am 12.01.2011 um 17:17 Uhr
This thread is intended to lead to a productive discussion. So feel motivated to offer constructive insight, rather than hen-pecking. Thanks!

Those who have been following the many discussions going back a year or so, know that a handful of us have become interested in using Handbrake as an output engine for the web. Finding an acceptable intermediate between Vegas and HB was a roadblock, until Laurence and I discovered that DNxHD in "709 mode" does not throw the colorspace error with x264 that almost every other YUV/YV12 codec we tried does. Note: Sony's mpeg-2 based MXF also works, and Cineform does not.* So, with that in mind, and based on the collective base of knowledge that has grown since, I have made a number of assumptions.

-- That x264 holds up better below 10Mbs than does Mainconcept AVC.
-- That 720p is currently a better upload medium than 1080i, from an upstream postprocessing standpoint, and playability on most consumer systems and connections.
-- That yadif is a more versatile deinterlace method than blend or interpolate, in most situations.
-- That lanczos3 resize is better than bicubic, with or without sharpening, in most situations.
-- That uploaded media must be strictly conformed to 16-235 levels, to prevent clipping at both ends. Includes generated text and media, and FTB levels!
-- That uploaded media should be streaming-ready.
-- That a DNxHD 220Mbs intermediate is probably overkill for 4:2:0 source, and is probably not worth the extra time and file size over 145Mbs.
-- That the time spent encoding the intermediate and again in Handbrake is reasonable, compared to say, 2-pass VBR in Vegas.

So, using material graciously provided by amendegw, stringer, and kimberly for this purpose, and input from laurence, Nick Hope, amendegw, farss, John_Cline, and many others, here is my second draft of sample video to be included in an upcoming tutorial this winter. Note that this footage has been conformed to 709 levels, and minor gamma tweaks have been applied, so it may not look "exactly" like the originals, but I tried to retain the shooters' intentions as closely as possible..

Be sure to view at 720p. The original uploaded mp4 will also be available at Vimeo, and the DNxHD 145 1080i intermediate (2.4GB) will hopefully be on MediaFire in a day or so.

http://vimeo.com/18690771

Youtube version is good, but no way to get around their splotchiness in FTB/FFB transitions. Be sure to view at 720p.



Kommentare

musicvid10 schrieb am 12.01.2011 um 17:37 Uhr
As far as the levels actually being returned by the Youtube Player, this looks pretty encouraging.

amendegw schrieb am 12.01.2011 um 17:39 Uhr
musicvid,

Very Good! Can you post some screenshots of the settings you used in Handbrake? Particularly interested in the "Video Filter", "Video" & "Advanced" tabs.

If you need a site to host these images, email them to me & I can put them on my site.

Good Work!
...Jerry

System Model:     Alienware M18 R1
System:           Windows 11 Pro
Processor:        13th Gen Intel(R) Core(TM) i9-13980HX, 2200 Mhz, 24 Core(s), 32 Logical Processor(s)

Installed Memory: 64.0 GB
Display Adapter:  NVIDIA GeForce RTX 4090 Laptop GPU (16GB), Nvidia Studio Driver 566.14 Nov 2024
Overclock Off

Display:          1920x1200 240 hertz
Storage (8TB Total):
    OS Drive:       NVMe KIOXIA 4096GB
        Data Drive:     NVMe Samsung SSD 990 PRO 4TB
        Data Drive:     Glyph Blackbox Pro 14TB

Vegas Pro 22 Build 239

Cameras:
Canon R5 Mark II
Canon R3
Sony A9

amendegw schrieb am 12.01.2011 um 17:48 Uhr
Hmmm... I did notice some pixelization in the fade at the end of the stringer clip. Wonder why? All other fades looked fine.



...Jerry

System Model:     Alienware M18 R1
System:           Windows 11 Pro
Processor:        13th Gen Intel(R) Core(TM) i9-13980HX, 2200 Mhz, 24 Core(s), 32 Logical Processor(s)

Installed Memory: 64.0 GB
Display Adapter:  NVIDIA GeForce RTX 4090 Laptop GPU (16GB), Nvidia Studio Driver 566.14 Nov 2024
Overclock Off

Display:          1920x1200 240 hertz
Storage (8TB Total):
    OS Drive:       NVMe KIOXIA 4096GB
        Data Drive:     NVMe Samsung SSD 990 PRO 4TB
        Data Drive:     Glyph Blackbox Pro 14TB

Vegas Pro 22 Build 239

Cameras:
Canon R5 Mark II
Canon R3
Sony A9

musicvid10 schrieb am 12.01.2011 um 18:11 Uhr
That's totally due to Youtube's low minimum vbr and the sensitive flat nature of stringer's source. No way to get around it; it's not present in the uploaded mp4, and a higher bitrate in the upload doesn't fix it. Baaad Youtube!

amendegw schrieb am 12.01.2011 um 18:21 Uhr
I love projects like this!!

You didn't say in your original post - I assume you rendered from Vegas to 1920x1080 and let Handbrake do the re-sizing to 1280x720?

Did I duplicate your render template correctly as follows?



...Jerry

Edit: Whoops, I think the framerate should be 29.97, correct?
Edit2: I've replaced the screenshot with the correct settings - just in case someone wants to use it as a reference.

System Model:     Alienware M18 R1
System:           Windows 11 Pro
Processor:        13th Gen Intel(R) Core(TM) i9-13980HX, 2200 Mhz, 24 Core(s), 32 Logical Processor(s)

Installed Memory: 64.0 GB
Display Adapter:  NVIDIA GeForce RTX 4090 Laptop GPU (16GB), Nvidia Studio Driver 566.14 Nov 2024
Overclock Off

Display:          1920x1200 240 hertz
Storage (8TB Total):
    OS Drive:       NVMe KIOXIA 4096GB
        Data Drive:     NVMe Samsung SSD 990 PRO 4TB
        Data Drive:     Glyph Blackbox Pro 14TB

Vegas Pro 22 Build 239

Cameras:
Canon R5 Mark II
Canon R3
Sony A9

musicvid10 schrieb am 12.01.2011 um 18:33 Uhr
Yes, my results are much better keeping the intermediate at 1080i, and resizing / decomb in HB.

Yes, that looks like my settings, EXCEPT I had the Vegas framerate at 29.97 (project setting).
Got to go do some work, but I will be around later this evening to post some Handbrake settings, also the levels for your poppies, which were tricky.
musicvid10 schrieb am 12.01.2011 um 19:26 Uhr
OMG, the Vimeo version rocks!
And no blocking in the transitions.
Vimeo-processed mp4 is available for downloading.
http://vimeo.com/18690771
John_Cline schrieb am 12.01.2011 um 20:53 Uhr
The Vimeo version is essentially flawless. Nice job.
amendegw schrieb am 12.01.2011 um 21:13 Uhr
"...also the levels for your poppies, which were tricky. "Ha! I just followed the rules of the assignment - "The footage should be well-lit, not clipped, and contain motion as well as static detail. Tripod is a must. Prefer colorful subject material"



btw, one thing I noticed after I sent you the clip - my camera is searching for focus at full-zoom. Maybe no one else notices this, but I do. Hope no one attritutes this "glitch" to your test.

...Jerry

System Model:     Alienware M18 R1
System:           Windows 11 Pro
Processor:        13th Gen Intel(R) Core(TM) i9-13980HX, 2200 Mhz, 24 Core(s), 32 Logical Processor(s)

Installed Memory: 64.0 GB
Display Adapter:  NVIDIA GeForce RTX 4090 Laptop GPU (16GB), Nvidia Studio Driver 566.14 Nov 2024
Overclock Off

Display:          1920x1200 240 hertz
Storage (8TB Total):
    OS Drive:       NVMe KIOXIA 4096GB
        Data Drive:     NVMe Samsung SSD 990 PRO 4TB
        Data Drive:     Glyph Blackbox Pro 14TB

Vegas Pro 22 Build 239

Cameras:
Canon R5 Mark II
Canon R3
Sony A9

musicvid10 schrieb am 13.01.2011 um 03:05 Uhr
Jerry,
I knew I was going to have to tweak levels, but your poppies presented a challenge, although the luminance was within gamut.



Youtube would have muddied the saturated reds and blocked up the shadows somewhat unless we brought the chroma into range as well. What I arrived at (after some failed attempts) worked well after upstream postprocessing, especially on Vimeo.

Kevin R schrieb am 13.01.2011 um 03:57 Uhr
Man, Stringer's street scene looks familiar... is that Eugene, OR?
UlfLaursen schrieb am 13.01.2011 um 05:09 Uhr
This is great - thanks guys for alle the work you have done that we all can benifit of.

/Ulf
apit34356 schrieb am 13.01.2011 um 06:56 Uhr
A great forum posting! This is very useful for the YouTube crowd! A great example of workflow. Thanks musicvid and all others that worked on this!
amendegw schrieb am 13.01.2011 um 09:32 Uhr
musicvid,

I'm a neophyte in the area of color correction (but I want to learn!).

Did you use the Color Curves FX to make your adjustments? I was able to approximate your results using the Glenn Chan "Legal Colors Only" preset.



...Jerry

PS: I hope this is not moving this thread "off topic". If a discussion ensues, I'll start a new thread.

System Model:     Alienware M18 R1
System:           Windows 11 Pro
Processor:        13th Gen Intel(R) Core(TM) i9-13980HX, 2200 Mhz, 24 Core(s), 32 Logical Processor(s)

Installed Memory: 64.0 GB
Display Adapter:  NVIDIA GeForce RTX 4090 Laptop GPU (16GB), Nvidia Studio Driver 566.14 Nov 2024
Overclock Off

Display:          1920x1200 240 hertz
Storage (8TB Total):
    OS Drive:       NVMe KIOXIA 4096GB
        Data Drive:     NVMe Samsung SSD 990 PRO 4TB
        Data Drive:     Glyph Blackbox Pro 14TB

Vegas Pro 22 Build 239

Cameras:
Canon R5 Mark II
Canon R3
Sony A9

farss schrieb am 13.01.2011 um 10:24 Uhr
I'm not Musicvid, pardon my interruption.

You've somehow managed to clip the red and green channels, perhaps you somehow overexposed the shot to start with. The curve that you're using is probably not helping either.

Given that most camera today go over 100% by design it's oftenly better to roll the highlights off than to clip them. A curve such as the following may give better results



Another thing I'm not 100% certain of given that your original footage is probably a bit overexposed is it seems to have too much edge enhancement. If your camera permits dialing down the Detail setting to a negative number might help.

Bob.
amendegw schrieb am 13.01.2011 um 14:13 Uhr
@farss: Thanks for the input. I've moved this discussion to a new thread: http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=745934

...Jerry

System Model:     Alienware M18 R1
System:           Windows 11 Pro
Processor:        13th Gen Intel(R) Core(TM) i9-13980HX, 2200 Mhz, 24 Core(s), 32 Logical Processor(s)

Installed Memory: 64.0 GB
Display Adapter:  NVIDIA GeForce RTX 4090 Laptop GPU (16GB), Nvidia Studio Driver 566.14 Nov 2024
Overclock Off

Display:          1920x1200 240 hertz
Storage (8TB Total):
    OS Drive:       NVMe KIOXIA 4096GB
        Data Drive:     NVMe Samsung SSD 990 PRO 4TB
        Data Drive:     Glyph Blackbox Pro 14TB

Vegas Pro 22 Build 239

Cameras:
Canon R5 Mark II
Canon R3
Sony A9

TeetimeNC schrieb am 13.01.2011 um 15:13 Uhr
Excellent thread musicvid. I'm trying to determine which, if any, or your assumptions apply to the way I shoot. In general, I shoot progressive rather than interlace, and don't usually resize unless downsizing for DVD.

Following are my questions and/or assumptions regarding the points you posted. I'm posting these in an attempt to better understand the applicability of your findings to my workflow. Perhaps there are other Vegas users who also follow a workflow similar to mine.

-- That x264 holds up better below 10Mbs than does Mainconcept AVC.

I have also assumed this and always encode web media and home streaming video using Sony AVC.

-- That 720p is currently a better upload medium than 1080i, from an upstream postprocessing standpoint, and playability on most consumer systems and connections.

I tend to agree. My assumption here is that, all else equal, you can use a lower bit rate on 720p than 1080.

-- That yadif is a more versatile deinterlace method than blend or interpolate, in most situations.

N/A - no interlace here.

-- That lanczos3 resize is better than bicubic, with or without sharpening, in most situations.

N/A - no resizing here.

-- That uploaded media must be strictly conformed to 16-235 levels, to prevent clipping at both ends. Includes generated text and media, and FTB levels!

This surprises me since I thought computer displays could handle 0-255 (or at least 16-255). I would like to learn more about this. What is "FTB levels"?

-- That uploaded media should be streaming-ready.

Why? If you are talking YouTube and Vimeo, don't they add the streaming flag when they transcode? I use SmugMug and they don't stream - the clip downloads then plays.

-- That a DNxHD 220Mbs intermediate is probably overkill for 4:2:0 source, and is probably not worth the extra time and file size over 145Mbs.

Glad to hear that. I am rendering straight from AVCHD - no intermediate.

-- That the time spent encoding the intermediate and again in Handbrake is reasonable, compared to say, 2-pass VBR in Vegas.

It isn't so much the time that bothers me, as the extra manual steps in going to intermediate and Handbrake. So my question is: Do you think the Vegas->Intermediate->Handbrake workflow would yield a significant benefit for the case where there is no deinterlace or resizing required?

Thanks again for sharing your findings on this.

/jerry



musicvid10 schrieb am 13.01.2011 um 15:48 Uhr
TeeTime,
Here are my impressions to your questions in order:

1. Holds up better than Sony AVC, too. Also, Sony is CBR, meaning larger files for a given source with or without motion.
2. Yes, 65% lower bitrate, all other things being equal. That figures into the playability piece on many systems and connections.
3, 4. If you are starting with 720p, the biggest advantages offered by Handbrake (resize, decomb) are off the table. I would probably just render in Vegas in this case, to save a couple of steps.
5. Youtube and Vimeo both do an automatic cRGB mapping, whether your footage needs it or not. Thus if you give them 0-255, it will chop them, destroying highlight and shadow detail, and give an unwanted increase in contrast. This is true with all upload formats. Getting wysiwyg from these services is something we've spent a lot of time investigating. See video link at bottom.
6. If you give them non-streaming source, the upload servers must do an extra preliminary pass to find the metadata, taking up more time and resources than is necessary. This has a cumulative effect on overall server response.
7. I am unable to see any difference, either in the intermediate or in the final mp4 output. (I don't have an objective method to determine this).
8. Probably not (see 3. above).

Thanks for the level of inquiry. Although I don't claim to be right on all my assumptions, if it serves to get others thinking about it, we are all bound to benefit.


musicvid10 schrieb am 13.01.2011 um 17:53 Uhr
"Can you post some screenshots of the settings you used in Handbrake? Particularly interested in the "Video Filter", "Video" & "Advanced" tabs."

Here's a simple slideshow I put together in Irfanview. Few of the settings are etched in stone, and I invite refinements as we become more experienced with them.

Use the Normal profile as your starting point in Handbrake.

http://ovationplayers.com/yttut/Thumbnails.html
amendegw schrieb am 13.01.2011 um 18:15 Uhr
Ah! Those are exactly the same settings I've been using - save one. I've found that if I set video encoding to 2-pass VBR, I can get away with ridiculously low bitrates (often < 1Mbps) as long as there is not continously fast motion in the video clip.

...Jerry

PS: Obviously, the audio settings can be varied as well - not much need for very high bitrates if music is not involved.

System Model:     Alienware M18 R1
System:           Windows 11 Pro
Processor:        13th Gen Intel(R) Core(TM) i9-13980HX, 2200 Mhz, 24 Core(s), 32 Logical Processor(s)

Installed Memory: 64.0 GB
Display Adapter:  NVIDIA GeForce RTX 4090 Laptop GPU (16GB), Nvidia Studio Driver 566.14 Nov 2024
Overclock Off

Display:          1920x1200 240 hertz
Storage (8TB Total):
    OS Drive:       NVMe KIOXIA 4096GB
        Data Drive:     NVMe Samsung SSD 990 PRO 4TB
        Data Drive:     Glyph Blackbox Pro 14TB

Vegas Pro 22 Build 239

Cameras:
Canon R5 Mark II
Canon R3
Sony A9

musicvid10 schrieb am 13.01.2011 um 18:26 Uhr
Yes, I noticed that 2-pass VBR (non-turbo) is better at very low bitrates.
But for Youtube and Vimeo uploads at 6-10 Mbs, Constant Quality is a lot faster render.
I appreciate your work in squeezing the most quality out of very low bitrates. Few of us own the server space to offer huge HD files, thus the move to embedded players for many.
musicvid10 schrieb am 13.01.2011 um 18:35 Uhr
"not much need for very high bitrates if music is not involved. "

What, people actually upload video without music? Pure heresy I say!
amendegw schrieb am 13.01.2011 um 19:02 Uhr
"What, people actually upload video without music? Pure heresy I say!"You're absolutely correct! What was I thinking? {grin}

...Jerry

System Model:     Alienware M18 R1
System:           Windows 11 Pro
Processor:        13th Gen Intel(R) Core(TM) i9-13980HX, 2200 Mhz, 24 Core(s), 32 Logical Processor(s)

Installed Memory: 64.0 GB
Display Adapter:  NVIDIA GeForce RTX 4090 Laptop GPU (16GB), Nvidia Studio Driver 566.14 Nov 2024
Overclock Off

Display:          1920x1200 240 hertz
Storage (8TB Total):
    OS Drive:       NVMe KIOXIA 4096GB
        Data Drive:     NVMe Samsung SSD 990 PRO 4TB
        Data Drive:     Glyph Blackbox Pro 14TB

Vegas Pro 22 Build 239

Cameras:
Canon R5 Mark II
Canon R3
Sony A9

VMP schrieb am 14.01.2011 um 15:52 Uhr
Hi,.

What about PAL video?
Should that also be uploaded as 29,97 fps?

It is originally 25 fps.

Original source:
Camera VX2000 (SD)
DV PAL, avi.

Clip size 3-6 minutes.

My current render settings for youtube:

Video: Mainconcept MP4

Profile: Baseline
Video 25 fps (PAL)
Frame size: 720 x 550 Progressive
Option x enabled x: Allow source to adjust frame rate
VBR: maximum (Bps) 6.000.000 - Average (Bps) 4.000.000


Audio: AAC

SR HZ 44.100
Bitrate 320

Does youtube accept this or does it rerender it as 29,97?

Thanks