Thanks, I know all formats are technically containers.

But the question is still the same - what is the best container/format to render out from an uncompressed master AVI of the project's video for purposes stated? Handbrake is useful but I've had some problems with it at some point so have stopped using it.

OR:

Should I skip the master AVI and render the project to an mp4 or mov codec that uses H.264 (or better -- I do not have H.265 at this juncture). Note I do not have any non-free 3rd party codecs installed. Tight, tight budget.

My two cents -  considering you are "obsessive"  - your words not mine   :)

1) render ONCE from your source material

2) Go most modern codec and high bit rate:   i.e.,    HEVC / h265 40 MBPS (or higher if it will play).

You can use x265 from Handbrake for free, but then you need an intermediate or to frameserve.   Or you can get HEVC from Vegas Pro 14.    So, as   usual, compromises must be made.

Thanks, Kinvermark.

After reading your post, I decided to give Handbrake an update, and whatever the problem I was having with it no longer exists now. You mentioned needing intermediate or frameserve - I never have had that need nor has Musicvid10 (long time veteran here) who did "the" original YouTube tutorial for making videos for the web for Vegas users through Handbrak (specifically for YT) mentioned that.

Until I had problems with Handbrake, I always used my master uncompressed AVI, then experimented with various RF and used H.264. I just did a test with a segment AVI in the project with that at 1920x1080, changed the default output from .m4v to .mp4, encoded and it played fine on Windows Media Player, VLC and GOM.

Then...

I switched over to H.265, encoded, and will play on VLC and GOM, not Windows Media Player (most likely because my WIndows Update is messed up and and the version is dated 2009, v.12x... Works fine for most things, just not H.265 -- for as I recall H.265 only became stable in the last few years, not in 2009.

As per Microsoft that player isn't compatible with my Win7 64-bit OS, so I think I purposely kept my older version running installed through compatibility mode for it's my favorite for viewing Netflix DVDs.

In fact, as far as I know, v.12x was the last one they put out.

But I digress.

Point is that since both VLC and GOM play the H.265 mp4 files made in Handbrake, now it's just a matter of finding the right balance in RF and file size for this particular website file size limit and sought image quality. That famous "compromise."

Last, at some point last year I read somewhere that it's prudent to stick with H.264 since it is so widely used and that not all websites can process/play H.265.

Or that wisdom may now be outdated. I haven't kept up with that kind of tech-vid news.

"What should I ask the site in terms of their (I don't know the technical term) their processing "engine" or modality?"

You're getting the cart before the horse. There's little to be learned from asking how the site makes the sausage. You should find out what specifications the site will accept. What if you decide that h.265 is the greatest thing since sliced bread, but then learn (after days of rendering) that the site can not or will not process your h.265 files.

Not stated or not clear to me is whether the site prepares the files for streaming to users.

I would avoid H.265 for now, and render with x264 in MP4 container. Even YouTube doesn't accept H.265 yet. Have a read of this, especially section 4: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-improve-the-quality-of-my-avc-h-264-renders--104642/

If you are delivering 4K UHD, the conversion to h265 is worth the enormous time spent.

Otherwise, it's cumbersome and usually not necessary.

John_Dennis, Nick & Musicvid,

Thanks for your combined replies. Looks like overall, I answered my own question in terms of the H.264 vs. H.265 but good to have confirmation. I'll go over the FAQ by Nick, though most of it isn't new to me. Handbrake is versatile enough for me to experiment with to find that balance between file size and image quality.

Some questions related to editing in part due to discovering that my source material isn't 1920x1080 as I had thought.
______________________



How to improve the quality of a pan-zoom clip?

Original interlaced footage is from my old Canon HV30 as .m2t

Below is a screen shot of one of the various parts of the same footage that I have chopped up into different events, each with their own pan-zoom to create variety from a one camera, one scene shoot.

The discovery was that it's all 1440x720x32. You'll notice that the default field order is "upper field".
So...

1. Change field to "progressive/none" in all of them, yes or no? What other properties should I change and/or other things could I do to those events to possibly improve final result? (Again, once finished, I do a master render as an uncompressed AVI, then hit Handbrake for the final to-be-uploaded video.)

2. How to improve the inevitable blur that occurs when doing pan-zoom past 50% of resolution size?

While one has to be careful to not overdo it -- and again, I'm not a pro like most of you yet been using Vegas since v.6 so not a newbie either -- in this case, I have used "Sharpen" and due to using the "Spotlight" feature in the Bump Map, both of these have improved the "pops out better" factor.

These tweaks have definitely helped, but obviously one can't match the image quality of a wide or medium shots on 1440 footage.

If you have any better or alternative ideas for that, please let me know.

3. Improve "time stretched"/slow-motioned m2t by making progressive 60 fps replacement events?

Note that ALL m2t's in the project have been slo-mo-ed to a pretty large extent already. Should I first make intermediary 60 fps uncompressed versions of all events and replace the m2t events with their 60fps counterparts?

Rendering at 60 fps not only will balloon the file sizes, and may not improve anything for it's kind of like baking a cake - if the batter isn't prime, no baking can improve it. But figured I'd ask anyway.

4. Render master AVI and Handbrake final mp4 in project and .m2t's NTSC 27.97 - or 30 or 60 fps?

As far as I know, the overall online norm is 30fps. But I've up to know stuck to keeping the fps consistent from original footage to final render the same (29.97). Same "baking" analogy applies here too.
____________

I've probably answered most my own questions here, but your input and/or corrections of my assumptions appreciated.

~ PSK

OT P.S.: @Musicvid - I've I'm not mistaken, you've regained your original username. For a period of years it seemed it had changed to Musicvid10. I haven't been able to regain my (just) Soniclight due to ongoing glitches, but I'm fine with my 2.0 version. :)

I thought the OP said  it would NOT be processed by "YouTube, etc."     Some clarification and details are required.

@Kinvermark - Thanks for response, but as pointed out by John_Dennis, that's ultimately irrelevant. What matters is how I render the final .mp4. And as stated by them and me, use H.264, not H.265. In short, unless some wish to correct or comment on my last 4 questions/observations, I've got a pretty good handle on what to do.

Glad you have arrived at a solution that suits you.

Still seems to me that there are two different goals mentioned in this thread:

1) best kind of file to send to YouTube (or you tube "like" service that)  WILL BE  RE-RENDERED FOR STREAMING

or

2) Best FINAL file for playback on whatever device (undefined, but presumably computer screen).

Anyway, H264 is a probably the safest bet, but for 4K TV's h265 gets the edge IMHO.

I would deinterlace and scale 1080i HDV to 1920x1080 59.94p (PAR 1.0) and bring back those as lossless intermediates to the Vegas timeline before any pan/crop or slomo. Personally I would do that with QTGMC in AviSynth and render to MagicYUV in VirtualDub, but that is complicated to set up. Noting that you're on VP10, there are easier ways to deinterlace such as the Yadif plugin mentioned in section 5c of the thread I linked to. Alternatively, Handbrake decomb makes a good job of deinterlacing (a little better than Yadif, at least did in 2011 when I last tried it) but I have no experience of doing the "double rate" 59.94 render in Handbrake and I'm not sure if you can do true lossless render that will play nicely in VP10. But low-CRF x264 should be OK and nearly lossless. Don't forget to match project properties to the intermediates.

(Above is full resolution 1920x1080 screenshot of the just before closing credits part of the test MP4 for upload mentioned in the latter part of this post, showing my usual rather heavy fx "ethereal" visual style.)
_______________

Thanks, Nick. As usual, so helpful.

And hopefully I'm not coming off as obtuse by keep asking you questions, but I want to do things right as well as keep learning. So here goes. (You are one of the people I long ago referred to as one of the Yodas of Vegas University for the likes of me at this community.)

In terms of that first de-interlace (I do have Yadif though have so far rarely used it). As I may have intimated, this entire project is one long shoot cut up into events for creative pan-crops, etc.. Visually, let's put it like this.

For simplicity, I'll call this .veg project "VIDEO.veg."

The blocks or events that are on 2-3 tracks:
----- ----- ----- ------ ---------- ------- ----- ------- etc.
The foundation single continuous 29.97 interlaced (let's call it) "ORIGINAL.m2t" that was unfortunately shot at PAR of 1.333 (HDV 1080i), not at 1920x1080i as I had thought.
_______________________________________________________________________

As I usually do, my .veg are at 1920 prog, Best, etc, as is this"VIDEO.veg" one.
In short, it's an up-rezing situation.

So...

• Do I open a new .veg file and separately de-interlace the "ORIGINAL.m2t", rename it "ORIGINAL-old.m2t", name the new de-interlaced copy "ORIGINAL-NEW" then find a way for Vegas to now reference to the latter in "VIDEO.veg"?

You suggested that this "ORIGINAL-NEW" be rendered at 1920 at 59.94p (PAR 1.0) - my guess being that then pan-crops and slower-mo will look a bit better.

• Does PAR 1.0 still apply since "ORIGINAL.m2t" is an MPEG 1440x1080x32 with a PAR of 1.333 (HDV 1080i) as per Media Properties? My guess yes, but feel free to correct me.

As to what container/encoding format "ORIGINAL-NEW" as a 1920x1080 59.94p file, doubling of frames obviously balloons file size.

• Due to that this is not for broadcast quality but still want it to come out decent, would an "almost lossless" or high bitrate MP4 (or ?) do?

For instance I did an in-Vegas MP4 test render of the whole project as a possible upload final with the Media Info settings closing this posting and it came out pretty decent. Probably good enough for a "ORIGINAL-NEW" foundation file for this project. Only a 2.93 Gb. folder imprint too.

Usually, I've erred on the side of uncompressed AVI in the past for certain re-renders of segments in a .veg, but those projects were 3-5 minutes. This one is 8:21 min.

Last but not least....

My sense is that this could turn into a minor nightmare for I'd have to go to each event in the "VIDEO.veg" Project Media do a "Replace" so it reads the new foundation "ORIGINAL-NEW" file. But it's feasible for there are only 26 event "blocks" in this project.

Maybe this shortcut of re-rendering the foundation file is not the way to go, Or it is.
Again, appreciate any wisdom and guidance here.

~ PSK

MEDIA INFO on the 2-pass MP4 test rendered out of Vegas to be a potential final for upload:

General
Complete name                            : D:\--- N E W - PRODUCTION\COUCH GLOW AU NU\UPLOAD MP4 FULL SIZE TWO PASS TEST.mp4
Format                                   : MPEG-4
Format profile                           : Base Media / Version 2
Codec ID                                 : mp42 (mp42/isom)
File size                                : 2.93 GiB
Duration                                 : 8 min 21 s
Overall bit rate mode                    : Constant
Overall bit rate                         : 50.2 Mb/s
Encoded date                             : UTC 2017-05-18 03:29:30
Tagged date                              : UTC 2017-05-18 03:29:30

Video
ID                                       : 2
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : Main@L5
Format settings, CABAC                   : Yes
Format settings, ReFrames                : 5 frames
Format settings, GOP                     : M=3, N=24
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 8 min 21 s
Bit rate mode                            : Constant
Bit rate                                 : 50.0 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 29.970 (30000/1001) FPS
Standard                                 : NTSC
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.805
Stream size                              : 2.92 GiB (100%)
Language                                 : English
Encoded date                             : UTC 2017-05-18 03:29:30
Tagged date                              : UTC 2017-05-18 03:29:30
Color range                              : Limited

Audio
ID                                       : 1
Format                                   : AAC
Format/Info                              : Advanced Audio Codec
Format profile                           : LC
Codec ID                                 : 40
Duration                                 : 8 min 20 s
Bit rate mode                            : Constant
Bit rate                                 : 192 kb/s
Channel(s)                               : 2 channels
Channel positions                        : Front: L R
Sampling rate                            : 44.1 kHz
Frame rate                               : 43.066 FPS (1024 spf)
Compression mode                         : Lossy
Stream size                              : 11.5 MiB (0%)
Language                                 : English
Encoded date                             : UTC 2017-05-18 03:29:30
Tagged date                              : UTC 2017-05-18 03:29:30

Do I open a new .veg file and separately de-interlace the "ORIGINAL.m2t", rename it "ORIGINAL-old.m2t", name the new de-interlaced copy "ORIGINAL-NEW" then find a way for Vegas to now reference to the latter in "VIDEO.veg"?

No need to rename it to ORIGINAL-old.m2t. Just work off the original file. And you could work in the same project, perhaps on a different part of the timeline.

I generally do colour correction on the original HDV file but pan/crop, slomo etc. on the intermediate.

You suggested that this "ORIGINAL-NEW" be rendered at 1920 at 59.94p (PAR 1.0) - my guess being that then pan-crops and slower-mo will look a bit better.

Correct. That's the intention. You really want to deinterlace before any pan/crop in particular.

Does PAR 1.0 still apply since "ORIGINAL.m2t" is an MPEG 1440x1080x32 with a PAR of 1.333 (HDV 1080i) as per Media Properties? My guess yes, but feel free to correct me.

The intermediate should be PAR 1.0 1920x1080 and your project settings should match that after you have replaced the original HDV with the intermediates.

As to what container/encoding format "ORIGINAL-NEW" as a 1920x1080 59.94p file, doubling of frames obviously balloons file size.

• Due to that this is not for broadcast quality but still want it to come out decent, would an "almost lossless" or high bitrate MP4 (or ?) do?

For instance I did an in-Vegas MP4 test render of the whole project as a possible upload final with the Media Info settings closing this posting and it came out pretty decent. Probably good enough for a "ORIGINAL-NEW" foundation file for this project. Only a 2.93 Gb. folder imprint too.

Usually, I've erred on the side of uncompressed AVI in the past for certain re-renders of segments in a .veg, but those projects were 3-5 minutes. This one is 8:21 min

Uncompressed is enormous. I use lossless MagicYUV RGB (8-bit) for my intermediates. UT Video codec is another lossless alternative. Cineform is a near-lossless alternative (you get that Codec by installing GoPro Quik Desktop). Various Vegas-native compressed formats would do as an intermediate if you use enough bitrate. If you choose AVC then read this post.

My sense is that this could turn into a minor nightmare for I'd have to go to each event in the "VIDEO.veg" Project Media do a "Replace" so it reads the new foundation "ORIGINAL-NEW" file. But it's feasible for there are only 26 event "blocks" in this project.

Depends on the complexity of the project. Replacing FX and pan/crop is easy with "paste event attributes".

Maybe this shortcut of re-rendering the foundation file is not the way to go, Or it is.

Again, appreciate any wisdom and guidance here.

Maybe you could try Yadif as a Media FX (rather than Video FX), or just drag it before Pan/Crop in the FX chain. You may find the result is pretty good. Why not try a section that way, and then compare it to using the intermediate-based workflow I suggested. Choose a test section with a lot of pan/crop and slomo.

@Nick - Long and not-best-of-days, so just a short acknowledgement Thank You - Again, for being so helpful. I'll come back and re-read your point-by-point reply soon and put it to good use. Then in due course report on the results. No response necessary.

~ PSK

SOME MORE DETAILED INFO ON CURRENT "FOUNDATION" M2T FILES

@Nick - Still not quite ready to take the plunge, in part because I wanted to give you some more info about said "foundation" m2t files used in this project. Screen shots are from Win Explorer, then from in-Vegas.

I went all high contrast creative to highlight them in all screenshots for easier reference.

Track view on second probably not necessary but gives you a sense of all the events rooted in these files. I say "files" for I discovered that there are actually 4, not 1 long one as I had first surmised. That just means I'll have to do what I'll have to do for each of them.

This info may or may not change any of the valuable advice you gave me, but what I am learning from you in this thread is important for something to be applied in the future if and when I still used interlaced "foundation" files again.

I say this for my old Canon HV30 from which the m2t's came from is on its last legs. So...

Wisely or not, I recently bought myself a DSLR (Nikon D5500) that shoots 60fps in 1920x1080. In part due to the suggestion by some such Farss, maybe JohnMeyer and another member a few years ago that switching to DSLR on my limited budget may be a good idea.

Autofocus is slower, but far more custom settings than a basic camcorder such as the HV30. And while I do take stills on a sporadic basis, I now have a decent camera to do so.

I'll probably open a thread on that the issue of setting this DSLR for best video use in due course here for more advice for it's not like my 35 mm Minolta I started on as a late teen in the mid-70s... A bit of a steep learning curve, I'll get there.

OK, here are the screenshots.
___________________

1. "FOUNDATION FILES OF THE PROJECT (in Win7 Explorer)

Full Size JPG Resolution: 1000 x 616

___________________

2.a ALL IN-.VEG "FOUNDATION" FILES INFO (Audio excluded for removed from m2t files)

2.b TRACKS CONTAINING THE PAN-CROP-ZOOM ETC. EVENTS OF THE CURRENT M2T "FOUNDATION" FILES

Full Size JPG Resolution: 1620 x 830



Note: I changed one of the foundation file's Properties to "Progressive" which is now moot. Original default for those files are as shown, Upper Field.

(Perhaps not the best organized workflow for I tend to keep backup muted copies of events I tweak in case I don't like the new-improved edits. I also prefer stacked Events on their own tracks for cross-fades over in-track ones due to that Pan/Crop and FX keyframes are less confusing to change when needed.)

___________________

Thank you again for taking the time to hang in there with me - and if anything needs to be added to what you have already taught me, feel free to do so.

No rush, but would like to finally finish the project relatively soon.

~ PSK

I can't get the Yadif plugin to deinterlace 29.97 interlaced fps to 59.94 progressive fps on the timeline, no matter what I do. It skips every other frame at 59.94fps and so would be poor for slomo. Yadif in its pure form should be able to produce a clean progressive frame for every field (i.e. doubling the frame rate). I may be doing something wrong as I never use this workflow myself. So unless someone knows how to make that work, writing intermediates from Handbrake might be a better option, if it can do that (which I also don't use because I use QTGMC in AviSynth for deinterlacing).

OK, I think I've found the easiest and fairly decent HandBrake solution for
THE DOUBLE FPS + DE-INTERLACE "Foundation" Files discussed above.

This thread as pretty much died out, yet hopefully someone will provide some last feedback on the below.

I tried the de-interlace via Vegas in (Sony) AVC and kept getting error popups with "unknown error." So switched to HandBrake which does have Yadif as de-interlacer.

Below are screenshots of the settings I chose for converting my interlaced 1440 x 1080 PR 1.333 to 1920 progressive 2x fps equivalent. PLEASE let me know if there are any I should change. I chose a high RF (10) on purpose). I left out the last two tabs/pages for neither Audio nor DVD-related chapters and such are relevant.)

I highlighted the consecutive page tabs in green so easy to spot.

Thank you for your help.

HandBrake v. 10.7 - 64-bit (2017)
______________________

Picture

Filters

Video

(See "P.S." for I had to change two things on this page back to default)

P.S.: Having Video tab's Encoder Tune at "High" and Encoder Level at "5.2" did NOT work (got all black render). So put those two back to Auto on first and default 4.0 on second. Then it worked.

Here's the MediaInfo for the successful encoding from Handbrake above as per screenshots and the P.S. addendum.

Q: Any way to have Handbrake do at least a 4:2.2. Chroma subsampling instead of 4.2.0? (4.4.4. would be ideal, but that's probably impossible considering the source file.) And/or any tweaks to Handbrake to get the best result?
___________________

General
Complete name                     : D:\--- N E W - PRODUCTION\COUCH GLOW\LE-COUCH-002-DBLFPS-DEINTERLACE.mp4
Format                                   : MPEG-4
Format profile                         : Base Media / Version 2
Codec ID                                 : mp42 (isom/iso2/avc1/mp41)
File size                                 : 878 MiB
Duration                                 : 4 min 54 s
Overall bit rate                         : 25.0 Mb/s
Encoded date                           : UTC 2017-05-21 23:41:41
Tagged date                             : UTC 2017-05-21 23:41:41
Writing application                     : HandBrake 1.0.7 2017040900

Video
ID                                       : 1
Format                                   : AVC
Format/Info                               : Advanced Video Codec
Format profile                           : High@L4
Format settings, CABAC           : Yes
Format settings, ReFrames        : 4 frames
Codec ID                                 : avc1
Codec ID/Info                             : Advanced Video Coding
Duration                                 : 4 min 54 s
Bit rate                                 : 25.0 Mb/s
Width                                     : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                    : 16:9
Frame rate mode                        : Variable
Frame rate                               : 59.940 (60000/1001) FPS
Minimum frame rate                    : 59.920 FPS
Maximum frame rate                    : 59.960 FPS
Color space                               : YUV
Chroma subsampling                 : 4:2:0
Bit depth                                 : 8 bits
Scan type                                 : Progressive
Bits/(Pixel*Frame)                       : 0.201
Stream size                               : 878 MiB (100%)
Writing library                           : x264 core 148 r2708 86b7198

Encoding settings                         : cabac=1 / ref=2 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=6 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=9 / 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=1 / keyint=600 / keyint_min=60 / scenecut=40 / intra_refresh=0 / rc_lookahead=30 / rc=crf / mbtree=1 / crf=10.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / vbv_maxrate=25000 / vbv_bufsize=31250 / crf_max=0.0 / nal_hrd=none / filler=0 / ip_ratio=1.40 / aq=1:1.00

Encoded date                             : UTC 2017-05-21 23:41:41
Tagged date                               : UTC 2017-05-21 23:41:41
Color range                               : Limited
Color primaries                           : BT.709
Transfer characteristics              : BT.709
Matrix coefficients                       : BT.709

In the old days, around 2011-2012 when @Musicvid's tutorials were made, Decomb was preferred over Yadif for high quality deinterlacing. I don't know if that is still the case.

If quality is really important and you don't mind the encoding taking longer, you could slide the "Encoder Preset" slider to the right (a slower setting). RF 10 with "Fast" encoder preset doesn't seem like a good balance. RF 10 is possibly overkill, but no problem if you have plenty of storage space.

That "Fast Decode" box may be worth checking if Vegas struggles at all playing the rendered files.

Anyway, to check things are working properly, put one of the 59.94p rendered files on the timeline, match project properties to it, zoom into the timeline, and step frame-by-frame through it with the keyboard arrow keys to check that you've genuinely got 59.94 different frames per second and that the deinterlace has worked well.

When you get into the slomo, experiment with disable resample vs force resample on the clips to see which you prefer.

OK, thanks, Nick. We can call this a wrap. I've got enough info to go and experiment on, unless someone has any other tip or trick to apply with Handbrake. But seems pretty well covered at this point.

~ PSK

I'm about ready to dive and do it, but have come up with a couple "Which way to go?" questions.

And again, since this a long thread, allow me to recap the purpose and project and that I'm using pre-Magix Vegas Pro 10e. Mission: To up-rez, de-interlace and double fps due to end project's use of pan-crop, slow-mo.

-- Original footage (4 clips): 1440x1080i, PR 1.333, NTSC 29.97
-- Desired new project "Foundation" files: 1920x1080p, PR 1.0, NTSC 59.94

1. Handbrake's Yadiz and Double-FPS - Results... Unsure

First, I've played around with Handbrake/HB's double-fps + Yadif and there must be a glitch in the program, in that as carefully as I go through the tabs, i.e. knock out audio since I don't need it, etc. every time I come back to the first Picture tab in which I have set it to up-rez (Canon's footage is 1440x1080i, NTSC 27.97) to 1920x1080, it keeps going back to the 1440.

IF I hit encode by staying on that Picture tab with corrected 1920 it tends to work. Presets do the same thing, set/save at 1920 but Picture reverts back to 1440 when applied to such m2t clips. So have to keep correcting it.

But when it does render out a 1920 MP4 at double fps -- and I don't know if this is a good or bad thing:

---- Even when I push the RF to 5, the output file size is not much bigger than original m2t. Seems that due to up-rez, de-interlace and double-fps, it should be at least twice as large a file. RF 5 is getting really close to uncompressed, but then this is an MP4 output, not an AVI.

Last, this latest version of HB does have the choice between Yadif and Decomb. So far have not tried the latter. Any advantage to one or the other?

1. Would Using Yadif - Within - Vegas Pro Do a Better Job at De-Interlacing than the Handbrake Version?

The advantage of the Handbrake approach I've applied so far is that I can do up-rez, double-fps and de-interlace simultaneously. But I wonder -- not knowing the kind of under-hood algorithmic stuff that goes on -- whether IF I did this all as a separate .veg just for this conversion:

A) Should de-interlacing only precede up-rezing as a separate render first, then double the fps - or the other way around, or do all three simultaneously?

If de-interlacing and up-rezing first and only, I'd have to set the .veg project to the original NTSC 29.97. Then import the four renders back into the project, change the .veg's fps to 59.94, then do the final double fps render.

B) Last, below is a screenshot of the in-Vegas Yadif default. What should I change as setting, if any?



Bottom line, I want to put in as much pixel real-estate into the result to improve the slo-mo/pan-crop stuff built on these new "foundation" files.

I've got a feeling I've probably got this order mixed up and/or I'm complicating-confusing myself. Any corrections of perceptions and/or settings fine-tuning suggestions in either HB or in-Vegas approaches appreciated.

Again, pardon my relative ignorance in all of this but I'm here to learn.

~ PSK