Comments

amendegw wrote on 2/28/2012, 3:31 PM
24p to 30p best practice ??

I think the only thing that isn't addressed specifically there is... you should nearly always match your project properties to your media (i.e. 23.976 fps). Test render a few seconds of your project to see if it looks better resampled or not (normally "disable resample" looks better to me, but read the last entry in the referenced thread).

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

royfphoto wrote on 2/28/2012, 5:03 PM
Well I read all that, apparently the Speedo beta has expired, so far disabled RS looks a lot better.
John_Cline wrote on 2/28/2012, 5:46 PM
Are you talking about converting 23.976 progressive to 29.97 progressive or interlaced?
royfphoto wrote on 2/29/2012, 6:34 AM
John:both progressive. in vegas disable resample helps, it seems that VirtualDUB does a nice job also..can't determine which is better. Setting project properties to 24 or 30 didn't seem to make much of a difference. The broadcaster I'm working with wants 1080 at 29.97p
Chienworks wrote on 2/29/2012, 6:48 AM
I have to respectfully disagree. In a situation like this setting the project properties to match the desired output will help you make critical choices that will affect the output.

After all, we already know the source media is ok. What we're trying to do is get the best output possible, so let's have Vegas help us by showing us what the output is going to be.
royfphoto wrote on 2/29/2012, 7:57 AM
Ok so who do I believe, you say to match to desired output, Jerry in the second post says to match to source?
Chienworks wrote on 2/29/2012, 8:09 AM
Me, of course! ;)

The advice to match source is to improve preview playback speed. Other than that, it really doesn't have much merit. Matching the output has every other advantage besides that in it's corner.
amendegw wrote on 2/29/2012, 11:36 AM
[I]"Me, of course! ;)"[/I]Heh, heh. I actually don't think it's going to make a huge difference either way. Suggest the OP try it both ways. I've found I rarely go wrong when I use the "Match Media Settings" wizard.

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

Laurence wrote on 2/29/2012, 12:17 PM
I've done a couple of 23.97 to 29.97 conversions recently for some movie theater preshow ads. I just turned off resampling and rendered it to the higher frame rate. Yes, some frames are doubled, but it really doesn't look any more juddery than it did playing back at 23.97 fps.
Chienworks wrote on 3/1/2012, 1:56 PM
Well, while it's true that the computer can play back any arbitrary frame rate, there's no guarantee that the screen updates at that rate. Say the screen updates at 60Hz and you're playing back native 23.97 footage. The frame rates don't exactly match up so some of the frames will display 50% longer than others, lasting for 3 refreshes instead of 2. You're going to be facing some sort of judder no matter what.