Google Pixel 8 videos cannot be handled properly

kazuhiko-m wrote on 10/27/2024, 8:21 PM

Hello

When I load a 1080/60p video file (MP4/H.264) shot with Google Pixel8 into Vegas Pro22, it does not play properly. The material status of the video file in Vegas shows 59.94fps. The project setting is 1080/59.94p.

There are actually two symptoms. The first is that when you watch it frame by frame, it seems to advance one frame and go back exactly half a frame at the next frame, and this is repeated. It's just like when you get the field order of an interlaced material wrong. The second is that it advances one frame, stops at the next frame, and repeats. One of these two symptoms occurs.

When I try installing Davinci19 and load this video file, the frame rate is displayed as 60.00fps. I export this at 59.94fps. When I load this exported material into Vegas, it can be treated as normal material.

If anyone knows, I would appreciate your advice.
I'm not good at English, so if there's anything that's unclear to you, I'd appreciate it if you could point it out.

Back to post

Comments

3POINT wrote on 10/29/2024, 10:18 AM

Fact is that using Shutter Encoder for "problematic" videofiles, to get files that are correctly interpreted by Vegas, is always a (timeconsuming) workaround and shouldn't be necessary. Till now I was always able to import those "problematic" files, that are offered here, without any issues into Davinci Resolve (or even into Powerdirector).

What makes the video engine of Vegas so complicate or incomplete, that a video sample is needed each time to get it editable/workable in Vegas?

Howard-Vigorita wrote on 10/29/2024, 11:30 AM

I'm not sure the conform part is necessary, what is the purpose? ShutterEncoder automatically makes it constant framerate.

I also tried Rewrap and Conform functions under -Without conversion in Shutter Encoder. They are very quick but did not solve the problem if I left the frame-rate unchanged. Both remained vfr. Conform did fix it, however, if I cut the frame-rate in half... but did not change vfr or the bitrate. I think maybe it dropped every other frame and stretched the others by changing the timebase without transcoding. In any case, it was just as quick as a rewrap.

kazuhiko-m wrote on 10/29/2024, 6:23 PM

@3POINT You're right. I'd rather not have to do the conversion process if possible, so I'm thinking I can deal with the problem by enabling the "file i/o" checkbox that you all mentioned.
I'm going to carry out some testing for a while.
I'm still inexperienced, so I made many mistakes and apologize for the inconvenience I've caused everyone.

johnny-s wrote on 10/29/2024, 7:10 PM

@kazuhiko-m

I conformed the pixel8 clip to constant frame rate (60fps) with no quality loss, external to Vegas Pro.

The clip then loaded and played without issues in VP.

VP properties picked it up as 59.94 but setting properties to 60 or 59.94 it still plays aok.

What's odd is that this conforming can normally be done within VP by selecting the video event, right clicking and selecting "Conform to project frame rate". However, in this clips case the issue is only fixed by doing it externally.

Nothing unusual that I can see with the GOP, it's 60 ... IPPP etc, no B frames.

johnny-s wrote on 10/29/2024, 7:15 PM

Doing the same for the "Open Camera" didn't fix the issue.

Using VP 22 b 122. Default I/O settings for both clips.

kazuhiko-m wrote on 10/29/2024, 7:36 PM

@johnny-s Thank you.
For beginners, it's best to be able to edit normally without having to worry about anything, like with Davinci.
However, I'd hate to give up the audio editing features of Vegas, which are like a DAW, so I'll do my best to make use of the solutions you've all taught me.

RogerS wrote on 10/29/2024, 8:41 PM

I'm not sure the conform part is necessary, what is the purpose? ShutterEncoder automatically makes it constant framerate.

I also tried Rewrap and Conform functions under -Without conversion in Shutter Encoder. They are very quick but did not solve the problem if I left the frame-rate unchanged. Both remained vfr. Conform did fix it, however, if I cut the frame-rate in half... but did not change vfr or the bitrate. I think maybe it dropped every other frame and stretched the others by changing the timebase without transcoding. In any case, it was just as quick as a rewrap.

Thanks, I think I'd misconstrued comments from the creator about the conform function vs the conform in advanced settings. For VFR footage he recommends the latter. https://www.reddit.com/r/shutterencoder/comments/pmgkkz/best_conform_by_setting/

I did just run VFR footage through ShutterEncoder convert to h264 with nothing selected in advanced settings and got CFR out of it.

VEGASSteve wrote on 11/1/2024, 5:55 AM

I checked the issue from @kazuhiko-m, there was an oddity in the VFR frame number adaption. We did not calculate the adaption correct in this case, where the frame lengths are very close around the real rate (in this case 1496 .. 1510 around the real value 1501). This shall be fixed in one of the next updates.

kazuhiko-m wrote on 11/1/2024, 6:29 AM

This shall be fixed in one of the next updates.

@VEGASSteve Thank you.
I'll be waiting with anticipation.

john_dennis wrote on 11/1/2024, 9:43 AM

@VEGASSteve Could you state units for "frame lengths". ms, ns, phempto-seconds, etc.?