googie

For those seeking quick solution for missing codecs, here are bash scripts that use ffmpeg to convert any input clips (including these problematic h.265/h.264) to format acceptable for DaVinci

  #!/usr/bin/env bash
  
  set -euo pipefail
  
  INPUT_DIR="${1:-}"
  TARGET_FPS="${2:-30}"
  
  if [[ -z "$INPUT_DIR" ]]; then
      echo "Usage: $0 <directory with clips> [target fps (defaults to 30)]"
      exit 1
  fi
  
  if [[ ! -d "$INPUT_DIR" ]]; then
      echo "Error: directory does not exist: $INPUT_DIR"
      exit 1
  fi
  
  OUTPUT_DIR="$INPUT_DIR/conv"
  mkdir -p "$OUTPUT_DIR"
    
  EXTENSIONS=(
      mp4 avi wmv mpg mpeg mov
      mkv m4v flv webm ts mts m2ts 3gp
  )
  
  shopt -s nullglob nocaseglob
  
  for ext in "${EXTENSIONS[@]}"; do
      for file in "$INPUT_DIR"/*."$ext"; do
          filename="$(basename "$file")"
          name="${filename%.*}"
  
          output="$OUTPUT_DIR/${name}.mov"
  
          echo "Konwersja: $file -> $output"
  
          ffmpeg -y -i "$file" \
              -map 0:v:0 -map "0:a?" \
              -vf "fps=${TARGET_FPS}" \
              -vsync cfr \
              -c:v prores_ks -profile:v 1 \
              -pix_fmt yuv422p \
              -c:a pcm_s16le -ar 48000 \
              "$output"
      done
  done
  
  echo "Results in: $OUTPUT_DIR"

and then converting final exported video to h.265:

  #!/usr/bin/env bash
  set -euo pipefail
  
  INPUT="${1:-}"
  CRF="${2:-21}"
  PRESET="${3:-slow}"
  
  if [[ -z "$INPUT" ]]; then
      echo "Usage: $0 <input file> [crf=21] [preset=slow]"
      exit 1
  fi
  
  if [[ ! -f "$INPUT" ]]; then
      echo "Error: file does not exist: $INPUT"
      exit 1
  fi
  
  DIR="$(dirname "$INPUT")"
  FILE="$(basename "$INPUT")"
  NAME="${FILE%.*}"
  
  OUTPUT="$DIR/${NAME}_h265.mp4"
  
  ffmpeg -y -i "$INPUT" \
    -map 0:v:0 -map '0:a?' \
    -c:v libx265 \
    -preset "$PRESET" \
    -crf "$CRF" \
    -pix_fmt yuv420p \
    -tag:v hvc1 \
    -c:a aac \
    -b:a 192k \
    -movflags +faststart \
    "$OUTPUT"
  
  echo "Ready: $OUTPUT"

You encouraged me to try again and somehow, blackmagically ;) it works this time. It may be that recent DaVinci version has made some improvement. I'm so happy!

Installation still requires workarounds and codecs support is limited, but having that aknowledged and accepted, the application is finally usable!

PS. I don't know where the h264 (and other codes?) limitation come from, since ffmpeg has full support of it. Or is it just business model? Weird.

Thanks, but as far as I read it, it's all about the library file names mismatch, which is mostly covered by guides I mentioned earlier. I've done that and I got my DaVinci running. It was just audio output that did not work, despite hours spent on trying to get it work.

I wish they (authors of DaVinci Resolve and the Photo Editor) paid more attention to Linux platform. Theoretically DaVinci Resolve runs on Linux, but getting it run is a very bad experience on Ubuntu/Kubuntu 24.04. I even paid for the DaVinci license, as I read somewhere that for Linux it's necessary in order to have all codecs supported. It did not help. Fortunately there were no problems with refund.

There are whole guides online how to walk around these issues and even then I could not get the audio working. Somehow it relies on some old ALSA API, which is no longer maintained/supported on Ubuntu/Kubuntu, or I'm just too stupid to make it work. AI assistants could not provide working solution for me either.

I've moved back to Linux a year ago after around 10 years of Windows (and I used to use Linux Slackware for ~15 years beforehand). I am amazed how big progress the KDE made and whole Linux ecosystem. Gaming these days is just as easy as on Windows, which was my primary reason to switch to Windows. My printer just works now. Even music production is excellent on Linux now. There is plenty of great software options to choose from and they just work - as I would expect from the mature ecosystem.

This all feels so good, given how Linux is not pushing trash into my computer (OS-bound spyware/bloatware), has excellent, customizable UI. Full freedom. I do feel that I own my hardware.

Yet I miss DaVinci Resolve. For now I use Kdenlive, which is nice for simple editing, but feels unfinished, or I just don't know how to use it correctly.

I've got your file and I see where the problem is. I've created an issue to track and improve it for upcoming release.

Okay, never mind. I managed to reproduce the situation from your description. That's a tough one, but I will try to do something about it.

Weird behavior indeed. I don't observe it myself on MacOS 10.11 and I had feedback from couple of other Mac users, where it worked fine - even on older MacOS than yours. I really cannot imagine what could cause your MacOS to log out. Sorry.

The file you linked is around 388kB in size. Are you sure it's the one you intended to link? I've checked it anyway and I see no problem for SQLite to open and query views from that db file.

You can right-click and run from the context menu, in which case it should start. Contributions are welcomed.

Author here. I'm surprised and honored to have my pet project here ;) As mentioned in another comment, I'm currently in the process of bugfixing/polishing 3.4.x branch. Then I will focus more on 3.5.0, which will bring many big features. One of them being ERD (read & write).