Resolve 17 playback breaking, makes software unusable

Either immediately after launching my project, or after jumping around the timeline, or using the blade tool, the program becomes semi-unresponsive. The issue feels nondeterministic for when it occurs. I can still use the menu bar to do things like quit or generate logs, but playback does not work, and I can't change from the Edit tab at the bottom. I can still cut stuff with the blade tool, but without the preview or playback working it's unusable. Restarting "fixes" the issue until it randomly appears after seconds or minutes.

I am editing a 350MB mkv file generated from OBS.

Code: Select all

Running DaVinci Resolve v17.4.6.0004 (Windows/MSVC x86_64)
BMD_BUILD_UUID 9cb0a7fc-ac3c-4ace-a835-87f06545dbd0
BMD_GIT_COMMIT 02202f962b16f0d0e861d9284b1b1dcb10a68182
Starting GPUDetect 1.2_1-a9
Done in 98 ms.
Detected System:
  - OS: Windows 10 Pro (Build 19044)
  - Model: ASUSTeK PRIME X570-P
  - System ID: b96cc0e6-6c79-4e2f-bc67-ebcb1aca78c9
  - CPU: AMD Ryzen 5 3600X, 12 threads, x86-64
  - RAM: 16.2 GiB used of 31.9 GiB
  - AMD GPU Driver: 21.30.23.04-211216a-376209C
Detected 1 GPUs:
  - "AMD Radeon RX 5700 XT" (gpu:eef92761.cf044b46) <- Main Display GPU
    Discrete, 254 MiB used of 8.0 GiB VRAM, PCI:10:0.0
    Matches: AMDDL, DirectX, OpenCL, Win32


Code: Select all

$ ffprobe '.\2022-06-27 13-06-11.mkv'
ffprobe version 4.3.1-2020-11-19-full_build-www.gyan.dev Copyright (c) 2007-2020 the FFmpeg developers
  built with gcc 10.2.0 (Rev5, Built by MSYS2 project)
  configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-lzma --enable-libsnappy --enable-zlib --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libdav1d --enable-libzvbi --enable-librav1e --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libilbc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint
  libavutil      56. 51.100 / 56. 51.100
  libavcodec     58. 91.100 / 58. 91.100
  libavformat    58. 45.100 / 58. 45.100
  libavdevice    58. 10.100 / 58. 10.100
  libavfilter     7. 85.100 /  7. 85.100
  libswscale      5.  7.100 /  5.  7.100
  libswresample   3.  7.100 /  3.  7.100
  libpostproc    55.  7.100 / 55.  7.100
Input #0, matroska,webm, from '.\2022-06-27 13-06-11.mkv':
  Metadata:
    ENCODER         : Lavf58.76.100
  Duration: 01:26:16.20, start: 0.000000, bitrate: 550 kb/s
    Stream #0:0: Video: h264 (High), yuv420p(tv, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], 60 fps, 60 tbr, 1k tbn, 120 tbc (default)
    Metadata:
      DURATION        : 01:26:16.200000000
    Stream #0:1: Audio: aac (LC), 48000 Hz, stereo, fltp (default)
    Metadata:
      title           : simple_aac_recording
      DURATION        : 01:26:16.149000000


Full logs and NFO file attached, but the logs don't seem to reveal much.

I would love to keep using this software, please advise on how to fix this issue.

An mkv out of OBS can give you problems in DR. Try a simple editing software.

- MKV is a recent addition to DR and some folks have already reported difficulties with it.
- OBS can record constant frame rates, but may fail to do so depending on the hardware and additional load.

I suppose I'll convert to mov using ffmpeg following this for now
https://gist.github.com/gsilano/939c696 ... ef183c1c83

If there's something better than the above for best practices then please let me know

Have you tried transcoding the problem clip to a format that's optimized for Resolve?

On that macOS side, that would be ProRes and on the Windows side that would be Avid's DNxHD.

Seems to have been the MKV, been editing for a few hours without issues using MOV file.
Unfortunate, but it shouldn't be hard to swap back for final export I suppose.
Thanks for the info, would love for more stability to avoid having to reencode D:

You don't necessarily have to re-encode. Did you try to simply re-wrap from MKV into MOV?
Both are just containers.

Good call on the not having to reencode. I tried switching back to the mkv for final render, but that failed.
Instead I was able to copy the media to a mov without reencoding using

Code: Select all

ffmpeg -i '.\2022-06-27 13-06-11.mkv' -c:a copy -c:v copy hq.mov

which produced a better file than the github gist I linked earlier.