ahh, that makes sense. I'll give it a go.
EDIT: Hmm, didn't seem to work for me. I created the script and made it executable then put the path to the script in Kdenlive's settings. I can right-click in the project bin and click "create animation" which gives me a .JSON file but I see no way to edit it. Double-clicking it just shows me its properties and right-clicking and selecting "edit clip" does nothing. Interestingly if I execute the script from terminal it starts Glaxnimate as expected. I also went ahead and created a similar script for Pinta as my image editor since I'm also running the Flatpak version of that and had the same result as Glaxnimate when trying to edit images. I also entered the path for Audacity as my audio editor, but it's installed as a system package so I pointed Kdenlive directly to the binary and got the same result when trying to edit audio files. Maybe I'm just not understanding this, or I have something setup wrong in Kdenlive... Any ideas?
haha, yeah figuring out those ffmpeg flags is an absolute nightmare. My problem there isn't so much the output format from Resolve, but source format I'm using. My camera only has the option to record in H.264/H.265 (consumer grade, what can you expect?) which Resolve can't properly import on Linux. I could take the time to transcode them with ffmpeg before editing, but I'm usually working with ~2 hours worth of video per project and I don't really want to wait all day for a transcode job to finish before I can even begin editing. On top of that my camera (rather neatly) generates its own proxy files while recording, and I've found leveraging these is necessary for getting good timeline performance on my aging rig. Now I could let Resolve generate its own proxy clips like I have in the past, but that's more time waiting around before editing. I was SUPER stoked to see Kdenlive can natively utilize the proxy clips my camera generates.