Actually AVC H.264 are the first ones I tried after reading your advice. I'll try to shorten the story, but one of my cameras output file is realy odd. Windows 7 reads it's properties as an avi file. PD13 reads the file as being AVC H.264. The frameshots program will not process it and break it down into individual frame stills, but it will process avi files from other camera brands. Windows and the frameshots say this particular video is exactly 58 seconds and 0 milliseconds long. PD13 says it's 57.28 seconds long. All files from this brand of camera are like this, something about them is non-standard or corrupt.
Now this frameshots program will process this camera brands file if I run it through Movie Maker 2.6 or the newer Windows or PD13 as an avi file, however the framerate is 29.97 which throws the timing off for my project.
What I confirmed last night was that the properties read by PD13 is the correct reading for this file. This camera does output AVC H.264 files. So I had to try something else, and XAVC S worked, it gave me 30 fps and the frameshots program did it's job.
I'm working with wildlife night infrared cameras. Another oddity many of them do when creating a video is to make a frame, repeat this frame 1 or two times, then create a new frame, repeat it, and on and on. In other words, a 30 fps video will only have 10 new frames per second while having 20 repeats. In essence they are only 10 fps videos. The jerkyness of objects motion is sometimes quite obvious. This situation gives me headaches in the timing department.
If you're not bored or LMAO I'll continue. What I'm doing is clocking objects in motion to find their speed. An object passes by two known points on a surveyed plot where I know the exact distance, then I can caclulate it's speed by noting the exact frames it passes by both points and subtract the first frame milliseconds from the second frame and calculate the speed. Now I often use two or more cameras, which means their timeing has got to be syncronized down to the frame. It's an absolute nightmare trying to do this with an oddball 29.97 fps, but can be done, but creates timing errors.
So to boil it all down, what I'm using PD13 to do is to correct the corruptness of a certain brand of camera files so another program will accept it and so I can use those files to time objects in motion.
Later on I will use PD13 to create a documentary of my project.
Again, your advice really saved my day.
![[Avatar]](/forum/templates/default/images/avatar.jpg){kind=avatar}
![[Post New]](/forum/templates/default/images/doc.gif)
![[Thumb - PD13 Preferences Setting for 30 FPS not 29.97 fps.PNG]](https://forum.cyberlink.com/forum/upload/2015/10/6/5f1a11ff27e415fd1b664eac7d43719a_97165.png__thumb)
![[Disk]](/forum/templates/default/images/icon_disk.gif){kind=icon}