Why would video filmed at 120 fps on my iphone 12 pro max show up in vegas pro 18 at 111.33 fps in the project information? I was hoping it would remain at 120 fps. Something with the phone? The camera menu setting is set to 120 fps on the iphone. Your advice is greatly appreciated.
Probably the phone makes variable framerate ( something Vegas don't like) but to be sure post here the MediaInfo of the phone video, exactly following this tutorial: https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/
Here's the media info report you requested. Let me know if this is what you are asking for, OK? Thanks.
@Marc-Gold Similar information in this thread, VFR issues, https://www.vegascreativesoftware.info/us/forum/vegas-18-detects-wrong-source-video-frame-rate--126382/#ca786798
Here's the media info report you requested. Let me know if this is what you are asking for, OK? Thanks.
Exactly, thanks.
As you can see yourself the framerate of that file is different and move from minimum 29.630 - max. 126.316 fps.
And Vegas is performing very good at probably estimating the average to 111,33.
But much better for editing in a NLE is deliver footage with even framerate
I see. Thanks. Any idea why that framerate would be changing so much?
Any idea why that framerate would be changing so much?
You need to ask your camera that 😀
Different lighting conditions perhaps. Low light requiring longer exposure?
Any idea why that framerate would be changing so much?
Yes. your video is low-motion as indicated by very low bpp, allowing for longer frame duration. It's a compression trick.
Thanks very much for your interest in my situation. I'm so disappointed that I can duplicate the beautiful slow motion that I can see on playback on my iphone as compared with the clips in Vegas. Do you know of any way to record more compatibly on my iphone so it looks right in Vegas?
Do you know of any way to record more compatibly on my iphone so it looks right in Vegas?
As @EricLNZ said, the first point of access would be your camera's instruction manual, or the help file for its app's setting options.
To "rescue" this specific media file, you can try to convert it to a constant frame rate with a converter.
E.g.: with Handbrake, if you want it to be free of charge. https://handbrake.fr/
There is also very good support for high-quality processes here in the forum, such as Happy Otter Scripts. https://tools4vegas.com/home/
Check JN-'s signature for a tool to convert it.
If there is a setting to fix this with the IPhone that would be great, but I don't think it exists and is a problem for third-party apps, too.
And is filming at 120 fps normal?
It's not 120 fps. it's variable frame rate with no control how the rate is asigned to the sections.The use of variable framerate for current (long GOP) compression types is questionable on its own.
It's not 120 fps. it's variable frame rate with no control how the rate is asigned to the sections.The use of variable framerate for current (long GOP) compression types is questionable on its own.
So I really see that that these apps have been developed to save as much storage space as possible and to view the videos on the same device (smartphone) with the same app?
And that we will always have our problems, and have to create workarounds if we want to process these media files in a NLE?
It would seem that smartphone makers (including Samsung) list fps in their Settings as guidance only - it really means 'around about' whatever is selected because its VFR in reality. Smartphone video (no matter whether HD, 2.7k, 4K) is to my mind an absolute last resort. With both Samsung S5 and S8 - even with stabilisation activated - the image is far from stabilised even close to 'gimbal-like' (I'm not expecting the full gimbal experience though). That's okay, but putting the footage through Mercalli SAL or stabilisation in Mocha Pro mostly results in a disappointing result. Maybe because of the tiny phone image sensor and/or weird processing in the camera, various parts of the image 'wobble' about at different rates. So if I stabilise in Mocha Pro via one particular area of the image - which works - other parts of the image continue wobbling. Even highlighting multiple different areas for stabilisation in Mocha Pro often has a poor result particularly if the image has lots of different angles and action (like a shot looking down a city street). Sometimes I find its preferable to not stabilise some phone footage at all - the wobbly original footage is better than that achieved via stabilisation.
@Marc-Gold “I'm so disappointed that I can (cannot jn-) duplicate the beautiful slow motion that I can see on playback on my iphone as compared with the clips in Vegas”
Continue to use the high frame rate for your slo mo shots, just accept the fact that for optimal results in VP you should first convert all source clips to CFR, several utils/tools mentioned in this thread that can do that.
Simply factor this VFR to CFR step as an additional and necessary part of the project. VP18 sometimes doesn’t need this, probably all depends on the complexity of your project.
Thanks to all of you for your insightful suggestions. I understand exactly what you're all saying. Looks like I'm going to be downloading 'handbrake' to handle the variable to constant frame rate conversions.
@Marc-Gold 👍 Best of luck. Don’t forget that @wwaag's HOS tools and the util in my signature can also do the job, use what's easiest and you are most comfortable, familiar with.