I disagree, the gopro is recorded at 120fps and tagged at 120 fps and so plays normally. Just like 60 fps or 240 fps or 24 fps or 25 fps or 30 fps all play at normal speed
that is what is meant to do -- that is what it does with media players, vegas, and gopro's own apps
it might be different with your panasonic gh5 which i believe is tagged at 24p regardless of the frame rate it is recorded? so anything shot at above that will play in slow motion
I don't think either one has 'wrong' metadata
when the gopro video comes into vegas the project is set to 120 fps. If you slow it down in half 50% and output at 60 fps you get every frame output and it plays at half speed because you have effectively changed the tag
if you want to convert to 24p, you would slow it down to 20% and render to 24p you would get every frame and it would play at 1/5 speed
try it, i have a link to my video
There is absolutely no point in shooting or rendering video at 120fps. There isn't a single TV on the market that will take in native 120fps video and display it at that refresh rate. There are many that take 60fps or less and upscale it using frame interpolation to 120hz or higher, but none I've ever seen that take in 120hz video natively and display it at that rate. The HDMI spec itself is not capable of carrying 4k video above 60fps. As such, the only benefit of recording above 60fps is if you plan on using slow motion, otherwise you are not only wasting card/disk space, but you are making it harder for Vegas to decode with no added benefit.
Granted, I will sometimes speed up my slo-mo video so I can have sections of it appear to play at normal speed and then have the ability to slow it back down up to 6x (10x on GH5s) without the framerate getting choppy at 24p, but you can do this with video shot at 120p but encoded at 24p, there is no reason to have it play back full speed at 120fps, so yes, it is a bug in the metadata, or is well ahead of its time being that TVs with native input refresh rates above 60 are unlikely to come around any time soon... especially on any sort of mass-adopted scale.
The proper way to make an intermediate for a file like this, which is telling Vegas it should be playing back faster than it should, would be to right click on the file, go to its properties, and set the frame rate to 23.97fps. This should tell Vegas to play it back at the proper 24fps speed, then encode the prores at the same frame rate, 23.97. You will get a clean playing prores that plays back in slow motion with zero frame interpolation going on, and you'll have the option to speed it up at will back to normal speed with no loss in quality.
The reason to shoot at 120fps is for slow motion.
No, setting the properties to 23.9 and rendering to 23.9 does not produce slow motion video.
the only way to create slow motion video is to change the velocity of the clip and then render.
yes, you can right click and change the default playback speed for the clip, slow it down and then render it as slow motion
the properties in the project don’t matter, what matters is the rate selected when you render as far as what the FPS will be
as far as I can tell, what I did is the same thing, reduce the playback speed of the clip and output at a slower FPS than it was recorded, hence slow motion with no missing frames
We will just have to disagree whether it is a bug that the video plays in real speed or not, do you want to have the video play in slow motion and then speed it up to view real time? Or do you want to view real time and slow it down to view slow motion
6 one way, half a dozen another.
btw there are some TVs that take 120 hz, monitors, and of course 60 hz is very common on monitors.
24fps is slow for monitors, is that a bug? Shouldn’t it be 60 FPS? See the point here? 24 fps is completely arbitrary.
Anyway enough said on this subject. Appreciate the discussion and tip on resample.
Good editing
I don't take it as negative feedback. I think the problem is solved, isn't it? Due to low playback performance David-Purdy rendered an 59,94 fps intermediate from the 119,88 fps source file. In the beginning the problem was the resampling which generated "ghost" frames. Resampling turned off, problem solved. Right?
Correct. Thank you.
If the OP is happy, then I am happy. :)
But, FYI, on my system it really is not playing back CHOPPY in Windows Movie and TV, it is playing back TOO FAST.
(Attempting to playback at 120 fps in Vegas (or other NLE's) is CHOPPY, as expected, so I know what that looks like.)
This may make absolutely no practical difference to you, but for others, it may be something to look out for in GoPro files.
Actually it plays fine in windows 10 movies and tv, iPads, etc. it plays at normal speed like it should if it’s choppy, you might need a new computer.
"as far as I can tell, what I did is the same thing, reduce the playback speed of the clip and output at a slower FPS than it was recorded, hence slow motion with no missing frames"
The problem is, you should be slowing the video to the slowest possible frame rate that is divisible by 120, which is 24. You encoded at 60fps, and 24 doesn't evenly divide into 60. Now, if your target frame rate is 60fps at normal speed, and you want to be able to do a 2x slomo by shooting at 120, rendering at 60 with velocity set to half will produce a file that (assuming resampling is disabled) will not have any frame interpolation going on. However, if your project is supposed to output at 24p, then 24 doesn't divide evenly into 60, so a 60fps intermediate would not be the choice you would want, you would want to slow down 5x playback speed and then render out to 24p prores.
I personally would render to 24p, as that would be my target frame rate in many cases. Many people prefer its cinematic look, I only go higher when shooting for TV or sports. It also turns 2x slomo you get at 60fps into 5x, so there's that.
HDMI 2.1 does allow 4K at up to 120fps, but it will be a long time before these devices become standard... perhaps GoPro is allowing native 120p playback in anticipation of these devices, but for now it is a waste of resources.