Replay Mod Forums

Cannot render a video with default quality
    • User
    • 31 forum posts
    User53293
    #1

    Mar 06 18, 12:21 AM | Last edited: Mar 06 18, 12:25 AM

    When I try to render a video, the game shows its dirt loading screen like usual, but then stops responding. I've waited a long while but nothing happened, and I had to force quit the game. I could not find a crash report. I tried this with multiple replays, each time the same effect. Every time I try this, a .mp4 file of exactly 262 bytes does appear in the replay videos folder, but it appears to be a corrupted file; when I try to play it I get an error.

    However, when I change the Encoding Presets to "MP4 - Potato Quality" it does render it as expected. But the output quality is absolutely horrible, to the point where it's hard to see what's going on. I also tried some other presets like "MKV - Lossless", which also worked, but the filesize is huge, about 808 MB, and I am unable to play that video back because of this. Using "PNG Sequence" worked but it took ages to render, and the output wasn't so useful anyways. Using "WEBM - Custom Bitrate" with a bitrate of 5 mbps didn't work.

    Nothing interesting appeared in the log apart from this:
    [23:08:48] [main/INFO] [replaymod-render]: Starting C:\Users\joche\AppData\Roaming\.minecraft\ffmpeg\bin\ffmpeg.exe with args: -y -f rawvideo -pix_fmt rgb24 -s 1920x1080 -r 30 -i - -an -c:v libx264 -preset ultrafast -pix_fmt yuv420p "2018_03_05_23_02_41.mp4"
    [23:08:53] [main/INFO] [FML]: Applying holder lookups
    [23:08:53] [main/INFO] [FML]: Holder lookups applied


    Some technical specs:
    OS: Windows 10
    CPU: 4x AMD A4-5000 APU with Radeon(TM) HD Graphics
    Java version: 1.8.0_25 64bit
    Forge version: forge1.12.2-14.23.2.2624
    Replay Mod version: replaymod-1.12.2-2.1.1
    FFMPEG version: ffmpeg-20180227-fa0c9d6-win64-static
    No other mods installed.
    No resource packs enabled.

    This is in .minecraft/exports.log:

    ffmpeg version N-90173-gfa0c9d69d3 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-cuda --enable-cuvid --enable-d3d11va --enable-nvenc --enable-dxva2 --enable-avisynth
    libavutil 56. 7.101 / 56. 7.101
    libavcodec 58. 13.100 / 58. 13.100
    libavformat 58. 10.100 / 58. 10.100
    libavdevice 58. 2.100 / 58. 2.100
    libavfilter 7. 12.100 / 7. 12.100
    libswscale 5. 0.101 / 5. 0.101
    libswresample 3. 0.101 / 3. 0.101
    libpostproc 55. 0.100 / 55. 0.100


    Has anyone experienced this issue before, or can anyone help me resolve this issue? I have spent hours into trying to find out the cause but I'm clueless. This is the first time I render a video from this account, I'll try on another computer tomorrow to see if I get the same issue. Thanks in advance.


    • User
    • 31 forum posts
    User53293
    #2

    Mar 06 18, 12:57 AM | Last edited: Mar 06 18, 01:02 AM

    Update: I think the issue has to do with bitrate. I set the Encoding Presets to "MP4 - Custom Bitrate" and tried out some bitrates. At 63 kbps, it properly renders, and at 64 kbps it stops responding. So yeah I think I found the limit. But still, 63 kbps is a horrible bitrate, and I'd love any help to be able to record at normal bitrates like 10mbps.


    • Developer
    • 1883 forum posts
    User10
    #3

    Mar 06 18, 01:06 AM

    Hmm.. probably has to do something with ffmpeg then because we pass the bitrate field straight through to it, no questions asked, and that's also about all we do with it.


    • User
    • 31 forum posts
    User53293
    #4

    Mar 07 18, 08:01 PM

    I tried installing a different version of FFmpeg (3.4.2) and now it appears to work. Thanks for the help!