Vegas to Youtube for the masses - a Tutorial

Comments

JHendrix2 wrote on 5/26/2012, 9:34 AM
the Advanced tab setting are quite obscure, you leave them the same for every type of encode? I just wonder why they are so different for each of the built in device presets
JHendrix2 wrote on 5/26/2012, 1:13 PM
decomb is unnecessary if i am using progressive source?
amendegw wrote on 5/26/2012, 2:17 PM
"decomb is unnecessary if i am using progressive source?"Correct!

Also, re: the advanced video settings, most were developed by musicvid (hurry back!) as a result of dialog with the HandBrake forum. We also did some testing and mods as a part of this project (don't remember the details at the moment).

...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

JHendrix2 wrote on 5/27/2012, 3:50 PM
Ok am i correct that the tutorial is for a vegas project that had project settings:

preset: HD 1080-60i (1920x1080, 29.97 fps)

and that is why you chose 1080i 59.94 in Avid Presets?

but also why you chose 29.97 as QT fps settings?

anyhow, i am using the preset: HD 1080-60i (1920x1080, 29.97 fps) for my project so wanted to make sure

also 32 bpp color is not better than 24?

amendegw wrote on 5/27/2012, 4:31 PM
"and that is why you chose 1080i 59.94 in Avid Presets?"That's 'cuz it's 59.94 fields per second. The render selection is 29.97 frames per second. The key is you want to determine an interlaced Avid setting. The Vegas framerate will determine the framerate of your render.

Actually, I believe you could select 1080i/50 and renders would turn out fine as the framerate is determined by Vegas.

...Jerry

btw: earlier you mentioned that you were not using the decomb filter because of progressive source. This post suggests that you have interlaced source - therefore you should use the decomb filter. If your source is progressive, you will want to render to progressive. If your source is interlaced, you should render to interlaced (and let HandBrake do the deinterlacing). Did that make sense?

Here are the custom render settings for progressive source:

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

JHendrix2 wrote on 5/27/2012, 5:36 PM
yes i was doing progressive on a different project but now my vegas project settings use this default preset: HD 1080-60i (1920x1080, 29.97 fps)
JHendrix2 wrote on 6/20/2012, 4:47 PM
but to better respond, my project is not that straight forward. because of a shooting error we ended up with 30p and 24PN mixed. it was determined the only way to save the project was to use a 60i timeline (and turn off re-sampling). this seems to have worked out OK but at render time for web (because we are talking about vegas > QuickTime > avid > handbrake) it gets a bit confusing.

I was advised that, with this odd-ball project, I would render 60i if for DVD but for web I would render 30p.

so i have a mixed format timeline with project settings accommodating that. and then for render to web (via handbrake).....i think...

leave project settings as is - HD 1080-60i (1920x1080, 29.970 fps) - upper field first
(except tun off deinterlace so handbrake can do it)

then render QT at 29.970000
progressive

with Avid - 1080i 59.94 DNxHD 145 8 bit

anyone know if that even makes sense????

so the confusing part is vegas (interlaced) > QuickTime (progressive) > avid codec (interlaced) > handbrake (progressive).....
amendegw wrote on 6/20/2012, 5:02 PM
"??? need some details.

...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

JHendrix2 wrote on 6/20/2012, 5:10 PM
sorry i forgot to delete that part of message...the rest of the message is valid.
amendegw wrote on 6/20/2012, 5:54 PM
Bear with me here... I'm not familiar with 24PN. Is this analogous to 24PF in Canon Cameras?

...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

JHendrix2 wrote on 6/20/2012, 7:45 PM
its P2 based

http://www.dvxuser.com/V6/showthread.php?48425-60P-24P-24PN-and-a-whole-bunch-of-others

the short story though is after consultation about using P2 24PN and Canon 30p the conclusion was use 60i to accommodate both. now just the confusion over the render settings.
amendegw wrote on 6/21/2012, 5:09 AM
Okay, you've boggled my mind.

Seems to me if everything on the timeline is progressive, I'd set progressive project properties and render progressive for web delivery.

I'd also explore DVD render setings using the "DVD Architect 24p NTSC Widescreen video stream" template. Also, make some short test renders with "disable resample" & "smart resample" to see which is more pleasing to your eye.

I think you're to the point where your best bet is to make some test renders and see what looks best (particularly if you're convinced that Interlaced Project properties are correct).

Good Luck (and I'd be interested to hear where you end up),
...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

JHendrix2 wrote on 6/21/2012, 10:08 AM
i think in this case frame size it whats making it hard. the thing that makes it tough is final amount of shots used are about 50/50, but the A cam was the 1280 24PN and generally looks slightly mushy (partly that it was 24PN but also it was 720 VS the rest was 1440) i have been test rendering to 1920.

i have panny 50% and Canon 50%

Panny:
Video: 00:12:23.242, 23.976 fps progressive, 1280x720, DVFilm Raylight Ultra 1.3.1
Canon Cam 1
Video: 01:05:18.248, 29.970 fps progressive, 1440x1080x12, MPEG-2

so the primary selling point of the hb workflow being better scaling and deinterlacing. in terms of scaling...its a lose lose because the 1280 looks best rendered out of vegas at 1280 and everything else looks better rendered out at 1920

makes it almost impossible to get HB to equalize it all out (even though i could do just that...go with 1920 from vegas and hope HB scales it all better somehow)
JHendrix2 wrote on 6/21/2012, 11:49 AM
regarding audio

quote musicvid:

"I wonder if you'll do a tutorial for musicians how to upload the best from Vegas?"

What an excellent question; as a music director and producer with decades of experience, I can tell you what a challenge that is.

It's a challenge because Youtube asks for and encodes to AAC audio, which is among my least favorite formats. Certainly 'faac' in Handbrake is substandard, and Youtube's downgrade to 160Kbps doesn't do it any further good.

------------------------------------------------

are there any particular highest qual audio settings that will be "as good as it can get - without causing added buffering in streaming situation" aac faac, aac passthru, aac ffmpeg, mp3 ??

from manual:

AC3, DTS, DTS-HD, MP3 or AAC (Passthru)

HandBrake can passthru these formats from the source.
This is the best quality, since it preserves the source audio bit for bit.

seems like the "best" - but will it stream?

oddly, when i choose aac passthru it switches to AC3 ffmpeg

-------------------------------------------------

im rendering HD video from Vegas via QucikTime / Avid DNxHD = .mov
audio format i choose - uncompressed 16bit 48K Stereo

playback will be in JW Player served by me (via AWS or Wowza using psudo-streaming or adaptive streaming) and not something like YouTube. the variable i guess would be using progressive dl I could have higher audio qual but using adaptive streaming might have to limit it more. due to the fact that high qual audio is important, I might have to limit the numbers of adaptive streams (not that concerned with great playback on cellular/iPhones in this case...targeting iPad wi-fii and desktops). but due to the what i am predicting will be limiting factors surrounding streaming just hoping to get the general "best" starting point (codec, mixdown, etc) and assume I will have to test at various audio bitrates
rraud wrote on 6/21/2012, 12:43 PM
I've been rendering audio separately to a WAVE, then encoding an AAC via the Nero AAC encoder. (not the CD/DVD burn app) Then adaptively mux the audio to the video only MP4. ( I can't get HB to pass-though the audio either) It's a PITA because of the extra steps but it encodes and muxes fast.
PS, In my tests, the Nero encoder adds12ms to the beginning, so I lop off the first 12ms of the source file prior to encoding the audio.
JHendrix2 wrote on 6/21/2012, 3:14 PM
OK so for now I am using this:

http://tinypic.com/m/fku2oz/1

Vegas:
1920i lower field first, no deinterlace
resample off

- this lets vegas output 24PN and 30P in 60i
- 720 P2 is up-scaled to 1920 by vegas and 30P 1440 is up-scaled to 1920 by vegas

QuickTime:
Audio: 48,000 Hz, 16 Bit, Stereo, PCM
Video: 29.970 fps, 1920x1080 Progressive
Avid 1080p/25 DNxHD 185 8bit

- made into progressive by QT / Avid

HB:
recommended settings from this thread except decomb off

-now HB scales project down to 1280

i also apologize for sort of getting OT from orig post but other people might have mis-matched media so maybe will help someone (even if just different frame sizes)

about the audio, on the handbrake forum i learned that the MAC OSX AAC encoder (inside handbrake) is considered better. so i have been booting int OSX.

still testing!
MikeLV wrote on 10/6/2012, 12:30 AM
So, to be clear, if my AVCHD camera shoots in approximately 16-255 levels, I should apply the change given at 9:05 - correct?