Need Rendering Setup for 1)email 2)website 3)Facebook 4)Youtube

will-3 wrote on 12/4/2019, 8:46 PM

I'm starting a new thread on this topic so it will snap out for others have the same questions.

FYI, I stopped video work back at Vegas Pro 12 & 13 so I've got a lot of catching up to do.

I've Googled these topics and read and watched tutorials but it all just becomes more confusing after awhile... so hopefully here someone can provide some bottom line guidance on this topic for me and others.

Here is the situation...

I've all of a sudden I've got a project that will require rendering many 40 second videos for multiple uses...

The 40-second videos will have the same 5-second intro and same 5-second tag but the 30-sec content is different for each... made up of changing text superimposed over the audio track. All content is simply text over audio with various text effects & transitions.

Each clip must be rendered for

Emailing: Easy emailing to non tech types so they can download and watch
Website: Uploading to the clients web site using HTML 5 to play them so that they don't "choke" when being viewed
Facebook
Youtube

Now the question...

which "project properties"
and which rendering choices should be chosen...
and how should they be modified for each of the 4 items listed above?

We are not looking for National Geographic quality here... but just some typical settings for common videos used for the four reasons stated.

I can tell from researching that there a zillion different ways to do it but that is zero help to just getting it done in a reasonable, aka typical, fashion...

So I'm asking Vegas Pro users here to suggest some simple settings that won't create a million GB file out of a simple 40 second presentation video.

I've been digging on this for 2 or 3 days now so any help would be appriceated.

Thanks.

Comments

Musicvid wrote on 12/4/2019, 9:44 PM

1. Don't do that bc they won't like it.. Kills their email quota. Email a link to YT.

2. Do all of your clients' websites maintain their own streaming servers? They will tell you what they want.

3, 4. Roughly the same. Their best practices are published everywhere.

If you have accepted an offer, I don't think you have any idea of the hours you've taken on. Hire a student to run the back-of-house delivery.

Former user wrote on 12/4/2019, 10:00 PM

I agree with Musicvid. Don't email a video file. It takes too long and if they are not tech savvy, they will not wait or not know how to watch it. Send a Youtube link.

john_dennis wrote on 12/5/2019, 12:06 AM

I've been using drive.google.com for distributing files to "clients". I send them a link via email, iMessage, etc. I state in the message, "Download and save locally. This link, like me, is not permanent."

Google Drive uses YouTube (or YouTube-like resources) to stream or download the files without the overhead of posting to Youtube. I stay within the 15 GB of free storage. If a project is over ~ 6 GB, I just give them a flash drive.

I keep going back to this and all the blog posts by Jan Ozer that follow on the subject of encoding.

Musicvid wrote on 12/5/2019, 12:25 AM

That is a good article, but leaves out an important factor called rate control, for which I am preparing a tutorial this month. The thing that reduces quality most noticeably is subpar bitrates in low-motion areas, while bitrate spikes in high-motion areas are what causes all the stutters and stalls in a confined streaming pipeline. bpp alone doesn't address the variations, although it is affected by them. The trick is in reigning in the outliers, while retaining an efficient compression playground between the two. It's more like audio limiting in that sense, while maintaining the same average bitrate.

It's a WIP, so stay tuned.

Limiting -> Compression ->

ByronK wrote on 12/5/2019, 2:25 AM

Please be aware of the Youtube's horrendous copyright claim policy and they will block your vids if they have any commercial audio. I do wedding vids and use vimeo to share drafts with clients.

Former user wrote on 12/5/2019, 3:17 AM

google photos and google drive video are not scanned for copyright or objectionable material.. It probably is, but only used for internal use/statistics and probably to assist law enforcement

will-3 wrote on 12/5/2019, 7:13 AM

OK, ignore emailing the clip for now... so that leaves 3 render targets for each 40 second video.

So let me ask the original questions in a slightly different way...

And to keep the "depends on the footage" issue from driving us down the road with a million forks...
Let's restrict the cases to a 40-second video with Media Generated (Legacy) Text changing each 5 seconds over a voice track...
(Then later we can consider other content like substituting a picture for one or all of the text slides)
.
Case 1: To render for a Website

What Project Properties do you use
What Render choice do you use after clicking File > Render As?
What Render customization settings do you use for your Render choice?

Case 2: To render for Facebook

What Project Properties do you use
What Render choice do you use after clicking File > Render As?
What Render customization settings do you use for your Render choice?

Case 3: To render for YouTube

What Project Properties do you use
What Render choice do you use after clicking File > Render As?
What Render customization settings do you use for your Render choice?

I really appreciate any help on this so please share your favorite "typical" settings for the above.

Thanks

Musicvid wrote on 12/5/2019, 8:26 AM

Case 1 - TBD by website. They all have their quirks. Vegas Internet templates are a reasonable starting point.

Case 2 - As published by Facebook

Case 3 - As published by YouTube. You can probably arrive at a happy medium and combine 2 and 3.

Note : Vegas doesn't employ rate control as j_d and I have been discussing, but you probably don't need it working from your description. Rate factors are the domain of x264 and x265, and more crudely in hardware encoding.

will-3 wrote on 12/5/2019, 9:18 AM

To set the website issue aside assume a typical small business website hosted on a server by one of the server farms... and remember... principally there are only three main variables that determine performance...
-- server power -- end-to-end bandwidth to the client -- power of the clients computer. --
(The HTML 5 code to serve the video to the client is simple and not an issue.)

So, given a scenario like this... I'm still looking for folks to share...

How do YOU (meaning any of the good folks on the forum :-) typically configure Vegas Pro to render for the 3 cases.

Case 1: To render for a Website

What Project Properties do you use
What Render choice do you use after clicking File > Render As?
What Render customization settings do you use for your Render choice?

Case 2: To render for Facebook

What Project Properties do you use
What Render choice do you use after clicking File > Render As?
What Render customization settings do you use for your Render choice?

Case 3: To render for YouTube

What Project Properties do you use
What Render choice do you use after clicking File > Render As?
What Render customization settings do you use for your Render choice?

Thanks.

j-v wrote on 12/5/2019, 10:47 AM

@will-3

I'm still looking for folks to share..

I'm using VPro 17 with far more possibilities to exact set the codecs and templates you have to use for your 4 tasks than the possibilities of VPro 12 and 13. There you have only a little choice of the older codecs for internetsharing from Mainconcept or Sony AVC. Don't know how that is for WMV and other 3th parties because I never use them anymore.

It is also very old fashioned to send the files or to place them on websides of owners.
My way of working is already for years to place it on a service as Vimeo for quality video or Youtube ( not much because of there is also a lot of rubbish) and provide a link to viewers and website owners to share those video's without any cost.

For friends and family I place the video on a cloudservice so they can download the files for themselves.

will-3 wrote on 12/5/2019, 12:14 PM

Yes, we have set aside emailing the demo video for the client to review before release.

- Now we will be placing the videos our site for review by the client.
- We will be providing an unpublished link to the client via email so they can view the demo video.
- We can't put them on YouTube or any other site where they can be easily viewed by the public before the client signs off on the video.
- Someone suggested putting them on Google Drive but then, I think, the client would have to download to view. Don't want to do that.
- Couple of folks have mentioned Vimeo but I haven't used the site... but if we put the demo video up there before the client had approved it would basically be available for public viewing... right If so, can't do that.

That said... we still do not know the typical way folks are rendering from Vegas Pro for the 3-cases mentioned.

How do you customize Project Properties? What do you click after you click File > Render as ?
And how do you customize that selection?

Seems like there should be a "Start here with these settings" reference somewhere for each of these popular cases...

john-brown wrote on 12/5/2019, 12:55 PM

YT - you can publish to YouTube as Unlisted, that way the public will likely not find it. You can change it to Public later if you wish, but if it is to only be accessed through a website, you can leave it as Unlisted.

j-v wrote on 12/5/2019, 1:48 PM

Yes, we have set aside emailing the demo video for the client to review before release.

- Now we will be placing the videos our site for review by the client.
- We will be providing an unpublished link to the client via email so they can view the demo video.
- We can't put them on YouTube or any other site where they can be easily viewed by the public before the client signs off on the video.
- Someone suggested putting them on Google Drive but then, I think, the client would have to download to view. Don't want to do that.
- Couple of folks have mentioned Vimeo but I haven't used the site... but if we put the demo video up there before the client had approved it would basically be available for public viewing... right If so, can't do that.

That said... we still do not know the typical way folks are rendering from Vegas Pro for the 3-cases mentioned.

How do you customize Project Properties? What do you click after you click File > Render as ?
And how do you customize that selection?

Seems like there should be a "Start here with these settings" reference somewhere for each of these popular cases...

This is my way in Vpro17 and on every site or screen it gives a very good picture of what I did.
What did I?
A 4K project of highresolution HEVC 4K sourcefiles from my GOPro 7 in a 1 minute test project I rendered to FHD 50p AVC with my VPro 17. You can see the settings I changed in customize from default and at least I played that file that can be uploaded to the the sites I told you with for everyone the possibles to look or download for itself.

will-3 wrote on 12/5/2019, 2:17 PM

Thank you j-v. BTW, how did you get the video to show in your post? Upload?
And, what file size did you end up with?

j-v wrote on 12/5/2019, 2:26 PM

This video is made with these customized settings. The bitrate can be that low because there is less movement as in fast moving pictures.

Alex-Pitel wrote on 12/5/2019, 3:19 PM

Use Vegasaur. It has feature to render regions with adding specified clip before and after region. It will be very easy.

Former user wrote on 12/5/2019, 9:48 PM

- Someone suggested putting them on Google Drive but then, I think, the client would have to download to view. Don't want to do that.

This is an example of a google drive link. It displays a Youtube type player, but the original quality video can also be downloaded. They may restrict video size to 1080p, not sure, as that video is 1440p buty only 1080p is showing in player for me. https://drive.google.com/open?id=1_T-ABxAJoVsDA5Sz2-V8p_dDtxE7zjqg

For Youtube, Vimeo, etc, you upload at the highest quality possible as the re-encode will suffer due to added complexity if your encode is not good, and the resulting encode lower.

If you are encoding for a website & serving a single video file you usually make compromises in resolution & quality for lowest bitrate, unless maybe your video is promoting your photographic video work. You might encode 720p and 1080p videos at 1136x640 , with x264 at a crf of 24. Below are instagram video (reported) values

cabac=1 / ref=2 / deblock=1:0:0 / analyse=0x1:0x111 / me=hex / subme=7 / psy=0 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=0 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=0 / threads=8 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=crf / mbtree=1 / crf=24.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / vbv_maxrate=2912 / vbv_bufsize=5825 / crf_max=0.0 / nal_hrd=none / filler=0 / ip_ratio=1.40 / aq=2:1.00

Vegas does not perform well with it's default internal software AVC encoding at low bitrates due to not having constant quality encoding. You can have a strange situation where Magix Nvenc Hardware encode can be perceived to look better. In reality they're both low quality but software encode is more pixilated/blocky while nvenc can give an illusion of better quality using Psycho Visual Tuning