Wonder if this is the issue. Unchecked it

 

Looks great! Gonna spend some time tonight making that workflow a bit quicker for me. Also will try the things Howard suggested...maybe if I can stop the issue on the camera side of things I wont need to transcode.

Really appreciate all the help here guys.

@JD-RC First of all there's nothing wrong with your phone, That's how all camera phones are, don't understand the technical reason behind it, but software has adapted to handle VFR better. You see that with YouTube being able to decode the phone video just fine, while Vegas will drop frames in areas creating the reduced frame rate problem and jerkiness in areas.

The question still remains, Is Vegas terrible at processing Camera phone video and needs to be fixed or is every NLE likely to behave as poorly. We can answer that if you would upload your original camera footage to a file sharing site such as google drive, one drive, dropbox, mediafile, and place a link to your file here.

 

Hopefully this works.

If not I will create a drive setup (yea...I am a bit behind on tech things sorry).

https://www.dropbox.com/s/apm6o26grx59cjq/carvideo.mp4?dl=0

@JD-RC I studied the 2 videos and I think the only thing that'll help the choppy fence render is a higher bitrate and/or a better encoder. Might minimize the effect of panning a fence. Would suggest uploading a MainConcept Hevc render and maybe compare with hevc_cbr just below the bitrate of your footage in addition to hevc_vbr.

It could be that vp9 just can't cut it with this kind of high-motion, panned, rolling shutter content. You could try experimenting with vp9 rendering yourself and see if that's the issue. The latest Voukoder plugin can render VP9 (Intel QSV) directly in a reasonable amount of time. If you find a render setting that plays vp9 smoothly locally, maybe YT will refrain from wrecking it any more if you upload it in that format... I tried rendering and uploading vp9 once as a test and YT did accept it.

@JD-RC Looks to be a bug with Vegas decoding of VFR. I show a comparison between Vegas and Resolve.

Where the video stays dull and underexposed that is where Vegas is matching Resolve almost exactly, but you can see when play begins Vegas does not match Resolve, it then matches, then doesn't again. The areas where it doesn't match would be where Vegas stutters.

Because we know other software such as YouTube decoder and Resolve handles Phone Camera video much better the logical extension would be to use anything but Vegas to decode your phone video first, so to do this you would use a transcoder such as shutter encoder or Handbrake so Vegas never see's the VFR video.

I can't believe how helpful you all have been.

I had 6 cameras rolling for that shoot (old cell phones and 2 gopro's ) so you can imagine my frustration when the one that's giving me issues rendering is the brand new s23 ultra. It takes me a very long time to thread that all together and the last thing I needed was my new phone that I thought would help, ended up making things more difficult...lol.

The bounce to Resolve/Quicktime did seem to fix the choppy video but my lack of experience with all of these different formats has me struggling to do this efficiently and with high quality. Will dive deep into learning as much as I can about external (or using Resolve) for transcoding for the s23 vids. and make that a part of my routine for now. I have become very familiar with the editing section of Vegas & learning another program such as DaVinci is going to take away what little time I have to provide content for my little channel.

Thanks so much for all of this great support. Super appreciate it.

@JD-RC If Resolve is rendering better for YT transcoding, then you should try the free Voukoder plugin for Vegas. The Voukoder plugin uses the same ffmpeg libs as Resolve so if Vegas Magix hevc renders are the culprit, Voukoder renders should work as well as Resolves with subsequent YT transcoding. And hopefully eliminate the back and forth between Vegas and Resolve.

@JD-RC Btw, I'm really interested in how this works out for you. It so happens I'll be shooting something this coming weekend with an s23. And some Beast stuff which I should have sometime tomorrow.

@JD-RC Btw, I'm really interested in how this works out for you. It so happens I'll be shooting something this coming weekend with an s23. And some Beast stuff which I should have sometime tomorrow.

I assume shooting this in 2k would have not caused these issues...but what fun is that. Going to try Voukoder this week. Appreciate it and will update.

@JD-RC

Download and look at this file. If it meets your requirements, I'll 'splane how it's done.

https://drive.google.com/file/d/1QQu8jBrHdYqrx9HVyeQsomlwdnnokPSD/view?usp=sharing

With the original footage I did repro the choppy issue and minimized it to an acceptable result. 
@Former user has also uploaded a Galaxy S23 footage, I studied the two files, found out where the main problem is hidden. 

HW conditions -> my Signature
Project: 

Render template default (I'm not cleverer than VEGAS engineers, thus use the GPU default one -> if my HW can't be interacting, for what did I invest? 

AVC=Advanced Video Codec;
HEVC=High Efficiency Video Codec -> bestens for delivery. 
 

Recommendation: 
Every modern camera has its interne stabilization function, but even action cameras have their limitation - Please don't shake your lovely hands as if you were performing Kungfu. 

Exclusions: 

• No debate about NLEs; when I use VEGAS then I attempt to utilize it including how to solve problems. 
• No trans-/recode footage, unless VEGAS or my HW really can't deal with. 
• No proxy, it prevents me judging my timeline's real preview -> if my RAMpreview sees a problem, it's a true one needing to be treated in alarm A. 

So do I focus on my RAMpreview and have found out: 
The "Legacy HEVC Decoding" is the handicap for VFR footage with high framerate. 
Disable it solved, at least minimized the issue @JD-RC.

Negatively, some other "leagcy" files lost their uninterrupted decoding. 

But this is the current VEGAS20, and this, is the result: 

Tried a few things before bed last night.

Voukoder did not work and the end result was the same (will mess with it more tonight).

I 1st tried HandBrake to convert...but I must be using it incorrectly and the video was actually worse.

I then downloaded shutter encoder, selected H264 (from what I remember...was late) & it worked!

Seems very easy to use and the rendered video from Vegas came out as smooth as the direct file from the phone. Quality is slightly less but I will assume YouTube will render it all equal after the upload anyway.

So overall I will just need to dump any s23 vids into the encoder before I use in Vegas as mentioned by Todd and others.

I assume this wont be any sort of "patch" because it's probably a unique small issue I am having but I guess it would be nice if I did not have to convert the file 1st. No big deal I guess.

Wanted to mention shooting 4k60 with my Gopro 11 does not have choppy renders from Vegas.

John_Dennis....that file looked good to me as well.

I could not appreciate you guys more for all the great advice and quick help. The new phone was a bit of a splurge item for me and my disappointment after the render was slightly more then I expressed here...lol.

With the original footage I did repro the choppy issue and minimized it to an acceptable result. 
@Former user has also uploaded a Galaxy S23 footage, I studied the two files, found out where the main problem is hidden. 

HW conditions -> my Signature
Project: 

Render template default (I'm not cleverer than VEGAS engineers, thus use the GPU default one -> if my HW can't be interacting, for what did I invest? 

AVC=Advanced Video Codec;
HEVC=High Efficiency Video Codec -> bestens for delivery. 
 

Recommendation: 
Every modern camera has its interne stabilization function, but even action cameras have their limitation - Please don't shake your lovely hands as if you were performing Kungfu. 

Exclusions: 

• No debate about NLEs; when I use VEGAS then I attempt to utilize it including how to solve problems. 
• No trans-/recode footage, unless VEGAS or my HW really can't deal with. 
• No proxy, it prevents me judging my timeline's real preview -> if my RAMpreview sees a problem, it's a true one needing to be treated in alarm A. 

So do I focus on my RAMpreview and have found out: 
The "Legacy HEVC Decoding" is the handicap for VFR footage with high framerate. 
Disable it solved, at least minimized the issue @JD-RC.

 

Thanks so much for taking all the time to help figure this out.

Going to try settings in Vegas tonight.

For Shutter Encoder if it doesn't look as good give it more bitrate/ lower the CQ number.
For Handbrake try the Production Standard preset to start with and go through the settings carefully (easier to mess things up than Shutter Encoder).

It's also a lesson to me 😁😁.

@JD-RC

I took your sample media into Shutter Encoder to resolve the slight variable frame rate:

I chose to encode to Apple Pro Res to minimize the loss from re-encoding.

Under Advanced Settings, I chose to conform with SPEED because I assumed you were not doing time trials. You could chose an option that suits you better.

From Vegas, I rendered with Voukoder using the default HEVC (x265) encoder with CPU only.

Full Disclosure

All of my cameras shoot constant frame rate. I have a few friends and family members who shoot with devices that record variable frame rate video. Whenever they share video with me, I always look askance at them, but take the video anyway.

Your life would be much fuller if you would work to make your recording device(s) shoot constant frame rate video.