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.

...or if you didn't mean the import() SQL function, but in general importing functionality (through Import Dialog) and it's still slow there, then please contact me and I will see what can be done to improve it - https://sqlitestudio.pl/contact/

In few days there will be another 3.4.x branch release (3.4.7), which addresses this exact problem - https://github.com/pawelsalawa/sqlitestudio/issues/5119

Yes, please! You can contact me directly through email, or through github discussions or issues. Details are at https://sqlitestudio.pl/contact/

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.

Actually the project is much older. It started in 2007. More details on this can be found at https://sqlitestudio.pl/about/

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).

For example it has context-aware syntax autocompletion, easy D&D for tables between databases, and many more - you can see longer list at https://sqlitestudio.pl/features/

Author here. This was never reported. I haven't noticed it for myself either. Feel free to get in touch through the official email (mentioned on the homepage) or through GitHub issues. I'm in the process of polishing 3.4.x branch, eliminating as many bugs as possible, before focusing on 3.5.0.

Note, that I have the CUDA installed. Still the imaginAIry runs on CPU :(

How to make it use my GPU (I have RTX 3070)? It complains about using sloooow CPU, but I don't see option to switch to GPU, which I think should be sufficient...? I'm running it on Windows 10.

It does.

Yet another free, open source and multiplatform GUI is SQLiteStudio ( http://sqlitestudio.pl/ ).

I'm not familiar with Erlang. Nevertheless there are two main issues with this threading model:

1) Application memory consumption grows more than it should, because same extensions have to be loaded several times in the same application, but in separate threads;

2) Resources such as images (or any other kinds), or OO objects, cannot be transferred between threads efficiently, the only way is to serialize them to scalar representation, which then can be passed through either tsv (mentioned above) variables, or through a message to another thread - then deserialize them there. Apart from precious time which it costs, you also make a full copy of resource/object, growing memory consumption even more.

SQLiteStudio developer here. I think it's a project which could be considered big. Version 2.x.x was written entirely in Tcl and the main problem was memory sharing with threads. There's none. Threads can communicate only by messages. Worse than that - each thread has to load very same packages and same procedure definitions (into separate memory segment) for each thread that wants to use them. Threads in Tcl are like processes that can communicate through pipe. It's a major pitfall of this language in context of more complex projects. Besides that it is a very nice language to use and read. Gives quick results with little effort. I still use it almost every day, just not for complex projects.

I'm aware of tsv package (shared variable), but this is just sharing scalar variables or arrays. You cannot share objects, procedures, namespaces, resources, etc - and that is the major reason for sharing memory across threads.