Bitrate for perfect uncompromising, yet not absurdly high quality work

Marty111 wrote on 10/4/2019, 2:50 AM

Good morning everyone,

I think it's time for me familiarize myself with bit rate and other settings that define the quality of a rendered video.

I don't want to trust my observing skills too much, because first I am not a professional, I have little experience, and no education at all about video editing, and second because I've been deceived countless times on thinking I was doing a clean job with video and also with audio. But let's talk only about video, not audio on this thread.

So I prefer to rely on others, let say not on any others, not on what people generally do, but rely on settings and figures true artists, (not your down the street old family tapes digital converter shop owner) rely on to have a perfect, uncompromising bit rate and settings. yet not absurdly high to the point a rendered file is 10 times the size of another and even the most trained eye can't tell the smallest difference between the two even after trying hard.

I'd like to have 720p and 1080p ready to use figures and settings I can rely on for Vegas most recommended codecs and also for xvid , h264 , and maybe h265 codecs, these three, I understand, have the advantage of having a smaller size but are hard or even impossible to preview in Vegas.

Comments

j-v wrote on 10/4/2019, 2:59 AM

All depends on what you do in editing your own files and the type of export you do.
So to me the best for yourself is trying small pieces, with certainly movements in it, with different bitrates and look on your own screen(s) to the result what is the minimum needed for you.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

Marty111 wrote on 10/4/2019, 3:00 AM

I usually hear "liberal" things like "turn up the bit rate until you get the quality you desire", but that doesn't mean much if nothing at all, when like me you don't know what you're doing. So I need a strict "fascist framework" to be sure I'm using the right settings.

Edit : @j-v : I just saw your answer after I was typing mine. Well i know you mean well, but that's exactly what I hear all the time from people who are trying to help, stuff like "pick what suits you", "Try different things". It's just too liberal for me.
I need more precise and directive advice and figures.

As for the purpose right now I need an intermediate template because my original files are xvid, and previewing them in Vegas is hard. I'm also looking for a final rendering template, but not right now.

Rednroll wrote on 10/4/2019, 8:26 AM

I had a very similar question and someone posted these graphs and information for me. Sorry, their username slips my mind at this point but it seemed like exactly what we were looking for. Honestly I don't fully understand all of this at this time because I'm more of an audio person than a video person currently, and hope as I learn more about the ins and outs of video it will start to make more sense but my take away was that a 20Mbps bitrate was a good rule of thumb starting point of the perfect balance between video quality and file size.

 

Here's their original message:

"Here's a chart I made comparing x264 bitrates versus quality over increasing RF settings. A measurement called SSIM is used to compare accuracy to the original, with 1.000 being a perfect copy. It's been found that "optimal" quality for modern encoders ( including x265) is at SSIM 0.995, the maximum reasonable quality without throwing LOTS of bits at it."

As you can determine from the chart, "optimal" bitrate for x264 occurs at 20-28 Mbps, or RF 18-20. Above that, the eyes can perceive no differences (as their resolving power has long since been surpassed), so quality is essentially as good at 25 Mbps as it is at 144 Mbps, despite wasting nearly 6x times more space!"

They also posted this which I don't fully understand as well. 😊

 

Rednroll wrote on 10/4/2019, 8:42 AM

The above information made sense to my audio brain since I had done similar studies in the past for audio bitrates. It was often said with audio 128Kbps bitrates was "CD quality" and I have often downloaded video with bitrates of 128kbps but my ears and studies didn't agree this was CD quality. I could often hear artifacts not present on the CD audio. For audio my minimal bitrate is 224kbps, where like video it will highly depend on the source if you can perceive a difference or not. Using 256kbps bitrates I have had a very hard time perceiving any differences on any type of source audio, but I tend to encode using 320kbps bitrates just to ensure any differences are not perceivable.

In the past, I did spectral analysis of the audio and found 320Kbps did not discard audio frequencies on a spectral graph for anything below 20Khz, which is the same point most agree we can no longer hear above. 256Kbps cut-off the frequencies around 18Khz and above. So therefore for my range of acceptable audio encoding of quality vs file size is between 224Kbps - 320kbps bitrates.

If a reduced file size is a concern, then 224Kbps is what I use and if not I use 320kbps. The happy medium for me is at a 256Kbps bitrate.

128kbps, 160kbps, and 192kbps I categorize as "acceptable" audio quality bitrates but definitely not in the ranges where you're not introducing highly potential noticeable artifacts and definitely not "CD quality".

frmax wrote on 10/4/2019, 12:50 PM

https://www.vegascreativesoftware.info/us/forum/uncompressed-vs-sony-yuv-vs-magic-yuv-the-shootout--113650/

I9900K, RTX 2080, 32GB RAM, 512Mb M2, 1TB SSD, VEGAS Pro 14-20 (Post), Magix ProX, HitfilmPro
AMD 5900, RTX 3090 TI, 64GB RAM, 1 TB M2 SSD, 4 TB HD, VP 21 Post, VP22

Monitor LG 32UN880; Camera Sony FDR-AX53; Photo Canon EOS, Samsung S22 Ultra

3POINT wrote on 10/4/2019, 1:25 PM

Edit : @j-v : I just saw your answer after I was typing mine. Well i know you mean well, but that's exactly what I hear all the time from people who are trying to help, stuff like "pick what suits you", "Try different things". It's just too liberal for me.
I need more precise and directive advice and figures.

I'd like to have 720p and 1080p ready to use figures and settings I can rely on for Vegas most recommended codecs and also for xvid , h264 , and maybe h265 codecs, these three, I understand, have the advantage of having a smaller size but are hard or even impossible to preview in Vegas.

 

What's wrong with the present rendering templates in Vegas?

Sylk wrote on 10/4/2019, 1:49 PM

@Rednroll you have to consider and precise what codec, because mp3 and aac are not same. AAC 160kbps is the same quality than MP3 320kpbs.

Software:
[OS]  : Windows 10 Ent. x64 v1903 (18362.535)
[NLE] : Vegas Pro 17.0 (Build 321) // (Build 284 if posted before 9/24/19)
[DRV] : Studio 536.23 (Display, PhysX, HD Audio) // (Game Ready 436.15 if posted before 9/24/19)
Hardware:
[GPU] : Gainward RTX 4090 Phantom / GTX 1080 Phoenix GLH
[CPU] : Intel Core i7-2600K @3.4GHz OC@4.5GHz (HyperThreaded) | AirCooling: Noctua NH-D14
[RAM] : 16GB (4x 4GB GSkill Ripjaws X DDR3 1600MHz 9-9-9-24) @1333MHz
[SSD] : Samsung 860 Pro 1TB
[MOB] : Asus P8P67 Deluxe (Rev.1), No iGPU support
[SND] : Asus Xonar Essence STX
[PSU] : Corsair HX750
Devices:
[DSP1]: 30" DELL UltraSharp U3011 @2560x1600
[DSP2]: 28" Samsung U28D590 @3840x2160

[UPS] : Eaton 5PX 2200i RT

[CAM] : GoPro Hero8/4/3 Black. Apple iPhone 11Pro/6S.
[REC] : Zoom Handy Recorder H4.
john_dennis wrote on 10/4/2019, 2:54 PM

@Rednroll "Sorry, their username slips my mind at this point..."

That graph was posted by @Musicvid in collaboration on my original work in this thread...

Analysis of Rendering to a Target Bit Rate vs Constant Rate Factor 

My name slips minds very frequently. I expect I'll be buried in an unmarked grave.

On topic:

I shared my favorite render method in this thread. I don't use it all the time for every application. I tailor my output method to suit the target usage. Picking one method is futile.

Marty111 wrote on 10/4/2019, 3:33 PM

@Rednroll Now we're talking! 🙂. That's the kind of approach I was looking for.
So I h264,
28 Mbps, and I'm done ? Is that it ? Is it good only for final rendering or also for an intermediate render for good preview in the Vegas timeline ? is it 28Mbps for 720p and 1080p too ?

Mats wrote on 10/4/2019, 3:52 PM

My bitrate "philosophy" is to render to the same bitrate as my source file from the camera. In my case 28Mbps (1080P ). I have done some tests to rerender the rendered file several generations (about 5 or 6) and can´t see any loss in quality, comparing the last rendered file to the original.

Former user wrote on 10/4/2019, 4:54 PM

 

If a reduced file size is a concern, then 224Kbps is what I use and if not I use 320kbps. The happy medium for me is at a 256Kbps bitrate.

128kbps, 160kbps, and 192kbps I categorize as "acceptable" audio quality bitrates but definitely not in the ranges where you're not introducing highly potential noticeable artifacts and definitely not "CD quality".

128kbs is just too low because depending on what's being recorded it can fall apart completely. I remember back when people encoded at 128kbs the song called LoveFool by The Cardigans was a great example to show how terrible a song can sound like that anyone can notice. In 2019 where storage isn't a concern & video is much larger there's no reason to ever use the low bitrates for authoring. Producing encode for a website etc(no re-encoding) is a different story as there's a lot of compromise involved

Marty111 wrote on 10/4/2019, 5:56 PM

@john_dennis "Picking one method is futile."

Yet it's what I need. I don't want to be bothered thinking about it each time I render something.

john_dennis wrote on 10/4/2019, 7:49 PM

Memorize this.

john_dennis wrote on 10/4/2019, 7:53 PM

@Mats

That “philosophy” will break down as you start acquiring video with more capable cameras.

Marty111 wrote on 10/4/2019, 8:13 PM

Memorize this.

-Asks for simple perfect ready to use figures
-Gives you a 79 pages long powerpoint written in hermetic technical language with pro and cons so that even if you understand something you'll still dither about what to choose.

john_dennis wrote on 10/4/2019, 8:21 PM

3Point always has more than three good points.

Marty111 wrote on 10/4/2019, 8:25 PM

Edit : @j-v : I just saw your answer after I was typing mine. Well i know you mean well, but that's exactly what I hear all the time from people who are trying to help, stuff like "pick what suits you", "Try different things". It's just too liberal for me.
I need more precise and directive advice and figures.

I'd like to have 720p and 1080p ready to use figures and settings I can rely on for Vegas most recommended codecs and also for xvid , h264 , and maybe h265 codecs, these three, I understand, have the advantage of having a smaller size but are hard or even impossible to preview in Vegas.

 

What's wrong with the present rendering templates in Vegas?

Do you suggest that they are already perfect?

Sylk wrote on 10/4/2019, 11:33 PM

There are no perfect universal settings, like PNG is better for solid color but not for photos, while JPG is better for photos but not for solid colors.

Perfect settings for quick and constant movements of a realistic F1 race video are not the same than for a static bicolor video of a Tetris session.

Also, the resolution is a factor to consider.

But yes, in most of cases default settings are very good.

 

Last changed by Sylk on 10/4/2019, 11:41 PM, changed a total of 2 times.

Software:
[OS]  : Windows 10 Ent. x64 v1903 (18362.535)
[NLE] : Vegas Pro 17.0 (Build 321) // (Build 284 if posted before 9/24/19)
[DRV] : Studio 536.23 (Display, PhysX, HD Audio) // (Game Ready 436.15 if posted before 9/24/19)
Hardware:
[GPU] : Gainward RTX 4090 Phantom / GTX 1080 Phoenix GLH
[CPU] : Intel Core i7-2600K @3.4GHz OC@4.5GHz (HyperThreaded) | AirCooling: Noctua NH-D14
[RAM] : 16GB (4x 4GB GSkill Ripjaws X DDR3 1600MHz 9-9-9-24) @1333MHz
[SSD] : Samsung 860 Pro 1TB
[MOB] : Asus P8P67 Deluxe (Rev.1), No iGPU support
[SND] : Asus Xonar Essence STX
[PSU] : Corsair HX750
Devices:
[DSP1]: 30" DELL UltraSharp U3011 @2560x1600
[DSP2]: 28" Samsung U28D590 @3840x2160

[UPS] : Eaton 5PX 2200i RT

[CAM] : GoPro Hero8/4/3 Black. Apple iPhone 11Pro/6S.
[REC] : Zoom Handy Recorder H4.
3POINT wrote on 10/5/2019, 1:51 AM

But yes, in most of cases default settings are very good.

 

Indeed.

Perfect would be when Vegas would be able to render "smart" (like my other NLE). Means leaving original content untouched and render changed/edited parts with the same resolution and bitrate as the original. This will give the highest quality but also ofcourse the largest files, but those files are perfect for archiving. For viewing, the best compromise between filesize and quality gives in my opinion a rerender of this "smart" rendered archive file by Handbrake. In that case I can decide afterwards, if I want for example a downscale of my 2160p original file to 1080p or 720p. Or to deinterlace a 1080i original file to 1080p.

Last changed by 3POINT on 10/5/2019, 1:58 AM, changed a total of 1 times.

3POINT, Theo Houben, Vegasuser since version 5 and co-founder and moderator of the Dutch Vegasforum https://www.vegas-videoforum.nl/index.php

Recware: DJI Osmo Pocket/Mavic Mini, GoproHero7Black, PanasonicFZ300/HCX909.

Software: Vegaspro365+Vegasaur, PowerDirector365, Davinci Resolve 20

Hardware: i910900k, 32GB, GTX2080super, 2x1920x1200 display

Playware: Samsung Qled QE65Q6FN

Rednroll wrote on 10/5/2019, 7:25 AM

@Rednroll you have to consider and precise what codec, because mp3 and aac are not same. AAC 160kbps is the same quality than MP3 320kpbs.


While I agree AAC is definitely a better codec than MP3, as it should be since it was developed after MP3 with a goal to improve the audio quality over MP3 at lower bitrates, but saying AAC 160kbps is the same quality as MP3 320kbps is a bit far fetched. Most tend to agree 256kbps AAC is equivalent to 320kbps MP3 but if you would like to show some spectral and L/R correlation graphs of 160kbps AAC vs 320kbps MP3 encoding using 20-22Khz uncorrelated pink noise as your source audio, I would be interested in seeing those. I've done those type of studies on MP3 and WMA encoding in the past, so that's what I'm familiar with at this time in regards to bitrates.

Marty111 wrote on 10/5/2019, 8:20 AM

Could we leave the audio part out just for now and focus on my particular demand?
As I said, right now, I need an intermediate template because my original files are xvid, and previewing them in Vegas is hard.
Quoting myself :

"It has to be perfect, meaning uncompromising bit rate and settings. yet not absurdly high to the point a rendered file is 10 times the size of another and even the most trained eye can't tell the smallest difference between the two even after trying hard."

Rednroll suggested h264, 28 Mbps. But isn't h264 good only for final rendering or also for an intermediate render for good preview in the Vegas timeline ? And is it 28Mbps for 720p and 1080p too ?

Sylk and 3point suggested the default rendering templates in Vegas, if it's the case I need only one that obeys this rule :

"It has to be perfect, meaning uncompromising bit rate and settings. yet not absurdly high to the point a rendered file is 10 times the size of another and even the most trained eye can't tell the smallest difference between the two even after trying hard."

Debates are interesting, but I need a concrete perfect template with concrete figures (numbers) and settings.

Marty111 wrote on 10/5/2019, 8:43 AM

There are no perfect universal settings, like PNG is better for solid color but not for photos, while JPG is better for photos but not for solid colors.

Perfect settings for quick and constant movements of a realistic F1 race video are not the same than for a static bicolor video of a Tetris session.

I don't know... I just want something that respects original content whatever it is.

3POINT wrote on 10/5/2019, 8:51 AM


As I said, right now, I need an intermediate template because my original files are xvid, and previewing them in Vegas is hard.

Before further advising, some more details are needed from your xvid files. Let Media Info https://mediaarea.net/en/MediaInfo analyze your xvid file and publish the result here.

Marty111 wrote on 10/5/2019, 9:10 AM

Well I 'm using 5 different xvid files for that project, and I'm looking for a template that I will use every time I need to convert xvid (and also mkv) files to an intermediate format suitable for smooth editing in vegas. So no need to focus on these particular files.
Until now I was using extracts from youtube videos and had no problem to use them in vegas. This just changed since now I'm also using extracts from files from torrents. Vegas doesn't fully supports formats from files from torrents.