Closed cefn closed 6 years ago
Although I have the flatpak version running on my machine, I would ideally like to be able to track the Github version and contribute to testing which requires the packages being installed locally and running it as 'script-only' version.
It is not hard to use flatpak for development. To build it yourself:
$ flatpak-builder --install --ccache build_dir io.github.jliljebl.Flowblade.json
$ flatpak run io.github.jliljebl.Flowblade
You can use a local git repo as a source in the json build file.
That's really useful, thanks, and definitely how I would continue with testing if I had the opportunity.
However, I have found that every third type of operation I attempt in Flowblade leads to a crash or hang, even using the flatpak version with blessed MLT libs, so I sadly won't be able to continue. This is partly because I've no idea why these crashes are happening or how I can avoid them or properly report them expecting an improvement in the situation.
Running KDenlive on the same system (backed by a lot of the same libraries) has not crashed once during hours of editing the same footage.
I've spent two or three days trying every combination I could hoping I could get it stable enough to crash only once in a while, so I could help improve the software, but the frequency of crashes has had such an impact on productivity in every configuration that I'll have to leave it for a few months. Perhaps I move and click my mouse more quickly than average (and hence create unusual conditions), or have unusual media or something (though it's mostly just footage from Android phones and FFMpege x11grab), but I'm really struggling to limit the damage from Flowblade's instability.
What's the best way I can usefully document the crash situations if I return to the effort again in the future? I'd really like Flowblade to be my editor in the long run and I'm willing to spend a bit of effort on documenting occasional crashes that I can recover from, assuming I can still actually edit video :) For my current project work I'll have to drop back to KDenlive, though.
This does not reproduce on my current system, issue likely dependent on affected system.
Please include the following information. 1) Flowblade version (Help->About):
1.16.0
2) MLT version (Help->Runtime Environment):
Built from source.
3) Your distribution (Ubuntu, Debian, Mint etc.):
Lubuntu Artful Aardvark
I noted https://github.com/jliljebl/flowblade/issues/485 was closed saying that upgrading to 6.6.0 would fix the issues with a segmentation fault when trying to load SDL.
Unfortunately, upgrading to 6.6.0 doesn't solve the problem, (at least if using the Kdenlive-built packages on Artful).
My theory was that's because they don't include the proper flags when building.
I installed 6.6.0 from https://launchpad.net/~kdenlive/+archive/ubuntu/mlt/+packages and encountered the same error as before when launching the standard .deb for 1.16 (as expected)...
I then tried to build the 6.6.0 .debs from source with modified flags. I uncommented the line...
deb-src http://ppa.launchpad.net/kdenlive/mlt/ubuntu artful main
in /etc/apt/sources.list.d/kdenlive-ubuntu-mlt-artful.list to make source packages available, then followed https://wiki.debian.org/BuildingTutorial#Get_the_source_package to try and successfully build my own copy of the Kdenlive mlt .debs using
before incorporating the changed build flags documented at https://github.com/flathub/io.github.jliljebl.Flowblade/blob/master/io.github.jliljebl.Flowblade.json#L431 and repeating the process.
You can see my attempt to include the suggested flags into the debian/rules file at this Mergely.
This process then created .deb files OUTSIDE the source package folder (took me a while to realise it creates .debs as a sibling of the parent folder!), so I set about installing these to replace my own .deb files. I removed everything to be sure, then installed the newly built .deb packages (packages which were meant to have the proper flags hopefully)...
Unfortunately after reinstalling flowblade, apparently now running against the modified packages, I still get the SDL segmentation fault like this...
Any suggestions for how the flags should properly be specified in the debian/rules file so that the SDL support gets built into the mlt .debs built from source in this way?
Although I have the flatpak version running on my machine, I would ideally like to be able to track the Github version and contribute to testing which requires the packages being installed locally and running it as 'script-only' version.
I almost forgot to say that the Flowblade project is unbelievably good from a design and usability standpoint, as long as I can get the stability I need.