Thanks Lethal. I dont post a lot on here but I do read a lot of the threads on here and I feel like you're the one person who gives the most definitive answer every time. I know my question isnt the most technically challenging question ever asked but when I read answers/solutions/advice that you give it's the most straight forward/logical/practical reply. I feel like a lot of people who post on here give people the run-around on what to do or they're giving answers that they might not fully understand themselves. No disrespect to anyone else but I just feel like if somebody were to ask me something about my job I should know it because that's what I do for a living and if I didnt know it, i shouldnt just give them a somewhat knowledgeable answer. And i understand that not everyone edits video for a living but either way, you shouldnt give someone advice on something you fully dont know. Basically, I just wanted to thank you Lethal for being a proper and reliable source on this forumopen it in QuickTime and then do command+i
Sorry to say, it's not so simple.Thank you
Thanks man! Your simple tip helped me a ton!
Depends. We had footage from a drone come in recently and QuickTime, VLC, MPGStreamClip, Catalyst Browse and Davinci Resolve all reported variances between 22 and 29fps!Sorry to say, it's not so simple.
Quicktime player is NOT a reliable source of the frame rate of a file.
I have had files which I know are 25fps and Quicktime Player says they are 18.7. I put the same file into Cinema Tools and Premiere and Mpeg Streamclip and they all show the proper frame rate of 25fps. It may be that it's because my file is double wide: 3820 x 1080. It's a known and very old bug in Quicktime Player. For some reason Apple has not seen fit to fix it.