Answers.Body: <p>That is way out of the h264 specs. According to Adobe After Effects the format constrains for h264 are at min. 10fps so even 2fps are (<strong>not</strong>, see below) out of spec and could result in issues with some players. So Avidemux seems to allow out of spec settings, that 1 fps isn't possible, is very likely an internal issue with how h264 gets encoded in Avidemux.</p>
  
  <p>Edit: It seems this is indeed an Adobe only constrain and or constrain for MP4, when using the QuickTime format with h264 I can render with 1 FPS.</p>
  
  <p>Still, I recommend you interpolate your video to be longer instead of decreasing the FPS unless you have very specific technical reasons for encoding with 1 FPS.
  Showing every frame multiple times per second instead of just once per second doesn't make a visual difference.</p>
  
  <p><img src="https://i.sstatic.net/9Fsvm.png" alt="After Effects format warning"></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-30T08:42:09.030Z
Answers.Text: I have not read full H.264 specs thoroughly [link]https://www.itu.int/rec/T-REC-H.264/, but I cannot find a minimum fps restriction. I cannot find it in x264 or avidemux docummentation either. In fact, level 1.1 in H264 defines 7.5 fps as max frame rate for CIF resolution. I think 10 fps is a min value for Adobe implementation of the codec, not for the  the codec itself. I need a subsampled (in time) clip as if one image per second was captured which is different from "slow playback" in terms of information shown.
Answers.UserDisplayName: jmm
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-30T13:44:22.380Z
Answers.Text: That of course could be the case, though usually the Adobe restrictions have a higher compatibility reason and are usually not a real technical limitation.
  
  Though showing the first frame for 25 frames per second or for 1 doesn't make any difference, you will have it much easier by simply "interpolating", which in that case just means repeat every frame by X.
Answers.UserDisplayName: timonsku
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-30T13:53:09.830Z
Answers.Text: See my edit, its indeed an Adobe only constrain.
Answers.UserDisplayName: timonsku
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-30T14:39:22.677Z
Answers.Text: Thanks for checking and it is indeed interesting for me that QuickTime format allows 1fps rendering. I will give it a try altough I would need my videos playback supported in some standard browser. I didn't understood your interpolating suggestion, sorry, I had already tried it, but the clips have bitrate constraints, so again, I cannot interpolate for technical reasons since interpolating increases bitrate.
Answers.UserDisplayName: jmm
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-30T14:45:37.573Z
Answers.Text: If done right it actually doesn't increase the bitrate all that much if at all, h264 is encoding based on differences per frame, set your keyframe interval to your FPS and you shouldn't see a lot of bitrate increase.
  Look for example at a Youtube video that is just a music track with a still frame for like 4 minutes but its not larger than your average mp3 file because the video track is just a few kb in size, h264 is pretty smart and can be optimized for specific situations like these.
Answers.UserDisplayName: timonsku
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-30T14:54:01.783Z
Answers.Text: I know, but I am working with "ultra low" bitrates (5-25 kbps for video, no audio). I did several tests (changing GOP size and other settings) and didn't manage to keep bitrate and quality.
Answers.UserDisplayName: jmm
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-30T15:17:49.157Z
Answers.Text: Let us [continue this discussion in chat](http://chat.stackexchange.com/rooms/15453/discussion-between-professor-fartsparkle-and-jmm).
Answers.UserDisplayName: timonsku
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-29T22:31:37.087Z
Answers.LastActivityDate: 2014-06-30T14:10:08.247Z
Answers.LastEditDate: 2014-06-30T14:10:08.247Z
Answers.UserDisplayName: timonsku
Body: <p>I'm trying to encode clips with x264 in avidemux. Problems come when I set video length to 10 seconds while I resample output to 1 fps (without changing duration): avidemux report "Too short" error and produces an invalid file.<br>
  There is no problem if I resample to 2fps or if select a clip 20 seconds long. I have also tried different GOP settings with no luck.<br>
  Any idea of the reason of this error?</p>
  
Tags: <encoding><mp4><framerate>
Title: Avidemux "too short" error
UserDisplayName: jmm
ThreadText: # Avidemux "too short" error
  
  (Asked by: username_0 on 2014-06-24)
  
  I'm trying to encode clips with x264 in avidemux. Problems come when I set video length to 10 seconds while I resample output to 1 fps (without changing duration): avidemux report "Too short" error and produces an invalid file.  
  There is no problem if I resample to 2fps or if select a clip 20 seconds long. I have also tried different GOP settings with no luck.  
  Any idea of the reason of this error?
  
  **Tags:** encoding, mp4, framerate
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-06-29. Score: 3
  
  That is way out of the h264 specs. According to Adobe After Effects the format constrains for h264 are at min. 10fps so even 2fps are (**not**, see below) out of spec and could result in issues with some players. So Avidemux seems to allow out of spec settings, that 1 fps isn't possible, is very likely an internal issue with how h264 gets encoded in Avidemux.
  
  Edit: It seems this is indeed an Adobe only constrain and or constrain for MP4, when using the QuickTime format with h264 I can render with 1 FPS.
  
  Still, I recommend you interpolate your video to be longer instead of decreasing the FPS unless you have very specific technical reasons for encoding with 1 FPS.
  Showing every frame multiple times per second instead of just once per second doesn't make a visual difference.
  
  ![After Effects format warning](https://i.sstatic.net/9Fsvm.png)
  
  > **Comments:**
  > **username_0**: I have not read full H.264 specs thoroughly [link]https://www.itu.int/rec/T-REC-H.264/, but I cannot find a minimum fps restriction. I cannot find it in x264 or avidemux docummentation either. In fact, level 1.1 in H264 defines 7.5 fps as max frame rate for CIF resolution. I think 10 fps is a min value for Adobe implementation of the codec, not for the  the codec itself. I need a subsampled (in time) clip as if one image per second was captured which is different from "slow playback" in terms of information shown.  
  > **username_1**: That of course could be the case, though usually the Adobe restrictions have a higher compatibility reason and are usually not a real technical limitation.  Though showing the first frame for 25 frames per second or for 1 doesn't make any difference, you will have it much easier by simply "interpolating", which in that case just means repeat every frame by X.  
  > **username_1**: See my edit, its indeed an Adobe only constrain.  
  > **username_0**: Thanks for checking and it is indeed interesting for me that QuickTime format allows 1fps rendering. I will give it a try altough I would need my videos playback supported in some standard browser. I didn't understood your interpolating suggestion, sorry, I had already tried it, but the clips have bitrate constraints, so again, I cannot interpolate for technical reasons since interpolating increases bitrate.  
  > **username_1**: If done right it actually doesn't increase the bitrate all that much if at all, h264 is encoding based on differences per frame, set your keyframe interval to your FPS and you shouldn't see a lot of bitrate increase. Look for example at a Youtube video that is just a music track with a still frame for like 4 minutes but its not larger than your average mp3 file because the video track is just a few kb in size, h264 is pretty smart and can be optimized for specific situations like these.  
  > **username_0**: I know, but I am working with "ultra low" bitrates (5-25 kbps for video, no audio). I did several tests (changing GOP size and other settings) and didn't manage to keep bitrate and quality.  
  > **username_1**: Let us [continue this discussion in chat](http://chat.stackexchange.com/rooms/15453/discussion-between-professor-fartsparkle-and-jmm).  
  
  ---
  
  