Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

9
  • I tried to use 61, 62, 80 and so on and that does not work. The amount of frames affectiva returns is way too less. The fps is around 60 (dividing the number of frames over the timestamps of Affectiva) but the amount of frames does not correspond to the video and also the timestamp Affectiva returns only goes until around 130s (for a 19min video). In terms of video duration I only get the correct result when I use 60 (but then the fps is only 30). Commented Jun 17, 2019 at 8:50
  • Normally you get that kind of problems when the video has a variable frame rate but as you made sure the video has a constant one I'm not sure what's going on. Commented Jun 18, 2019 at 6:24
  • I have edited my post. I think I found the problem. Do you know a solution? Commented Jun 18, 2019 at 23:07
  • I just saw the edit. It doesn't throw any exception? Btw, mp4 is just a container format but I have personally processed hundreds of mp4 videos using Affectiva and I only had problems with the ones encoded using variable frame rates. Commented Jun 19, 2019 at 7:44
  • I'm encoding it with libx264 using ffmpeg. Should I perhaps use another one? It does not throw any exception, it just terminates. I also wrapped everything in the main method in a try-catch block but there was no exception. Commented Jun 19, 2019 at 10:53