A ProRes file with a frame rate of 59.94fps is read as 60fps, which unfortunately causes one frame to be duplicated every now and then. Does anyone have an idea how to force Vegas to read the file as 59.94fps? Slowing it down to 0.999x gives even worse results.
https://i.imgur.com/QO0m7GV.png
https://i.imgur.com/73gGxlZ.png
Build 208.
You do know that you can add images to your post. Use the up arrow to upload them.
Also, a sample of the problematic footage in the cloud could possibly help.
You do know that you can add images to your post. Use the up arrow to upload them.
Also, a sample of the problematic footage in the cloud could possibly help.
And here's where weird things happen. If I cut the file into pieces (using ffmpeg -ss -t), then such a piece is already correctly read by Vegas as 59.94fps. BUT! But on condition that I don't cut to the last frame. So if I cut a 6-minute file into pieces of 1 minute each, only the last part is read as 60fps. The earlier ones are correctly read as 59.94fps.
The whole thing is over 100GB, so uploading it is impossible.
@rgr Select Project Properties. Select Frame rate and change to 59.94.
I loaded a Prores 59.94 FR clip and it came in as 59.94. I then changed the PP's to 60.
Using latest VP.
Unfortunately, as you can see in my screenshot, this option is grayed out.
@rgr That's because your screenshot shows "Media" properties, not "Project properties" = ALT + Enter
@rgr Select Project Properties. Select Frame rate and change to 59.94.
I loaded a Prores 59.94 FR clip and it came in as 59.94. I then changed the PP's to 60.
Using latest VP.
Unfortunately, as you can see in my screenshot, this option is grayed out.
@rgr That's because your screenshot shows "Media" properties, not "Project properties" = ALT + Enter
This is not a solution because a 59.94fps clip recognized at 60fps will then have duplicate frames.
Sorry, but that's the best I can offer.
To be clear the example I gave was setting the frame rate to 60 using a 59.94 test file to show that it can be done.
In your case u would set it to 59.94 in Project properties since u believe it is actually 59.94.
@rgr Just fired up vp21 b208 on my laptop and had no trouble setting an empty project to 59.94 fps... try doing that first before dropping the media in. If it asks to change the project fps, just say No. Btw, splitting with ffmpeg makes new containers with new metadata. Doing a repackage with the copy-codec (-c:v copy) does that too and might fix things if the problem is with the original clip.
@rgr Just fired up vp21 b208 on my laptop and had no trouble setting an empty project to 59.94 fps... try doing that first before dropping the media in. If it asks to change the project fps, just say No. Btw, splitting with ffmpeg makes new containers with new metadata. Doing a repackage with the copy-codec (-c:v copy) does that too and might fix things if the problem is with the original clip.
There is no point in changing the project settings -- the MOV file is incorrectly recognized as 60fps, so it will still play incorrectly. Unfortunately, copying with ffmpeg is only partially effective.
Use Shutterencoder to conform the videofile to the correct 59,940fps setting. Also I would like to see the Mediainfo of the original videofile.
Use Shutterencoder to conform the videofile to the correct 59,940fps setting. Also I would like to see the Mediainfo of the original videofile.
ShutterEncoder uses ffmpeg -- and ffmpeg couldn't handle it. Besides, according to ffmpeg (first post) the file is 59.94fps. Media Info shows the same.
@rgr If you tried a rewrap and that didn't fix it, then the problem is not the metadata listed in the header of the clip, even if it might be incorrect. The problem is the video stream itself. Makes me wonder if it was captured or transcoded with vfr enabled. I don't think the official Apple ProRes libs used by Vegas support vfr. You could try a transcode with the prores_ks codec which should fix it assuming ffmpeg can read the clip correctly.
Btw, ffmpeg and MediaInfo dump the same clip header. To read the actual metrics frame by frame, you need to use ffprobe or some other utility that looks at all the frames.
@rgr I'm trying to understand why "we" are still talking about this issue and yet you have not shared a sample file on a cloud share so others can do less anecdotal and more scientific analysis of the issue.
@rgr I'm trying to understand why "we" are still talking about this issue and yet you have not shared a sample file on a cloud share so others can do less anecdotal and more scientific analysis of the issue.
The size of the ProRes file probably exceeds the upload/download possibilities...
@rgr IYou could try a transcode with the prores_ks codec which should fix it assuming ffmpeg can read the clip correctly.
Btw, ffmpeg and MediaInfo dump the same clip header. To read the actual metrics frame by frame, you need to use ffprobe or some other utility that looks at all the frames.
The file is CFR and is just encoded with prores_ks. Well, I'll do it again (I have to anyway) and at most I'll throw in a dump from ffprobe.
I recommend reading my post from 2/6/2025, 3:18 PM
Unfortunately only those in your time zone will see that date and time as the forum displays the date and time in our local time. What is your time relative to UTC so I can determine which post you are referring to?.
It should be feasible to upload a short clip somewhere (10-30s?) or the prores_ks recipe so one of us can replicate it exactly.
And here's where weird things happen. If I cut the file into pieces (using ffmpeg -ss -t), then such a piece is already correctly read by Vegas as 59.94fps. BUT! But on condition that I don't cut to the last frame. So if I cut a 6-minute file into pieces of 1 minute each, only the last part is read as 60fps. The earlier ones are correctly read as 59.94fps.
I suspect that fixes it because all the internal timestamps are re-calculated in the new files.
Exploiting that idea, have you tried merging/concatenating a very short piece of video (with the same codec/resolution/frame rate) to the front of the main file e.g. using something like Shutter Encoder which uses ffmpeg underneath - https://www.shutterencoder.com/documentation/#Functions-Merge . Then just trim it off in Vegas.
It should be feasible to upload a short clip somewhere (10-30s?) or the prores_ks recipe so one of us can replicate it exactly.
Here's a sample. Vegas sees it as 60fps. Any advice is welcome :)
@rgr, link? 😁
It won't upload as an attachment. I'll put it somewhere else.
https://files.fm/u/d4cw6rewrt
It was suggested early on in this thread that you set the Project Properties to a frame rate of 59.94 fps.
... but you seem to have confused Project Properties with the event's properties judging by the image that you uploaded in your original post (which was not Project Properties) and then referred to later on.
Yes, importing your .mov media into VP21 appears as 60 fps if you select the option to set the project properties to match the media thus setting the Project Properties to 60 fps (which logically it shouldn't do), but if the project properties is first set to 59.94 and then import the .mov media without the 'match' option (i.e. it is set to 'no'), then the project properties remains at 59.94 fps. Give it a try.
Don't you see how absurd this solution is? Not only does this not solve the first error, it causes another one. Now, not only will the file play at the wrong speed, but it will also drop frames.
I don't know if there's a worse solution...