Bug Report MKV files are saving with a 1000 frames/second

[Draznar]

I can record at MP4 with no issues, but want to use the MKV file format which allow multi-audio tracks with my editing software. The issue is that the MKV file generated is showing Frame rate of 1000 frames/seconds on the details and will not properly load in my editing software. I am using identical settings, just changing the output file type. I have attached a screenshot of the details. Due to recording in 4K it is hard to get a video file under 1 meg.

My Last log file: https://gist.github.com/c9427250d444108e0d4f6cd2bf08eb51

 

[Fenrir]

This has been reported and confirmed several times, but not sure at this time what the cause is.

EDIT: Looks like this is just an expected side effect of the MKV format. It's just metadata being read incorrectly by the player, safe to ignore.

 

[LB_]

Even the latest versions of ffmpeg are reading 1000 fps and incorrectly transcoding the video, I would expect that a project so widely used as ffmpeg would know how to properly detect the framerate. Example output for a 25fps video:

>ffmpeg -i "2018-04-05 13-44-19.mkv"
ffmpeg version N-90335-ga7a8320c4f Copyright (c) 2000-2018 the FFmpeg developers
  built with gcc 7.3.0 (GCC)
  configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth
  libavutil      56. 10.100 / 56. 10.100
  libavcodec     58. 14.100 / 58. 14.100
  libavformat    58. 10.100 / 58. 10.100
  libavdevice    58.  2.100 / 58.  2.100
  libavfilter     7. 13.100 /  7. 13.100
  libswscale      5.  0.102 /  5.  0.102
  libswresample   3.  0.101 /  3.  0.101
  libpostproc    55.  0.100 / 55.  0.100
Input #0, matroska,webm, from '2018-04-05 13-44-19.mkv':
  Metadata:
    ENCODER         : Lavf57.84.100
  Duration: 00:17:23.32, start: 0.000000, bitrate: 46843 kb/s
    Stream #0:0: Video: h264 (High 4:4:4 Predictive), yuv420p(progressive), 1280x720, 1k fps, 25 tbr, 1k tbn, 50 tbc (default)
    Metadata:
      DURATION        : 00:17:23.320000000
    Stream #0:1: Audio: aac (LC), 48000 Hz, stereo, fltp (default)
    Metadata:
      title           : Track1
      DURATION        : 00:17:23.307000000
    Stream #0:2: Audio: aac (LC), 48000 Hz, stereo, fltp (default)
    Metadata:
      title           : Track2
      DURATION        : 00:17:23.285000000
    Stream #0:3: Audio: aac (LC), 48000 Hz, stereo, fltp (default)
    Metadata:
      title           : Track3
      DURATION        : 00:17:23.285000000
At least one output file must be specified

I've been using mkv output for a long time and this issue only cropped up recently. These are the recording settings:

Here is the log file: https://hastebin.com/vayuwevige

EDIT: For comparison I re-encoded the file with ffmpeg using the same settings as OBS Studio (and -r 25), and the framerate is correctly reported from the metadata by both Windows and ffmpeg. This means ffmpeg and OBS Studio are storing the framerate in a different way. The 5.68GB files are only a few thousand bytes different. I'm planning to do some more tests with smaller files.