The Quelea repository is a dying project — abandoned slowly and painfully.
Obviously, there have been no commits, no bug fixes, and no new features for quite some time.
This has been clear to me for years now. Despite that, being both hopeful and stubborn, I decided to create an experimental fork, hoping there would be some interest.
Well, there was hardly any. No surprise, I suppose!
I added some much-needed features and improved a few things (quite nice, actually!).
However, bug fixes are not really suitable for an experimental fork.
I mainly implemented the features I wanted and made improvements based on how I see things—things I actively use.
Bug fixes, on the other hand, should be in the main repository because they affect everyone.
I managed to narrow the main issue down to the GStreamer video module and its interface.
I suspect it’s an initialization/de-initialization problem—when a new video is loaded, the resources from the previous one don’t seem to be properly released.
It’s possible that the bug originates from the Java-GStreamer interface rather than Quelea itself.
However, I don’t want to spend more time digging into it.
If the maintainer has other priorities and the community isn’t actively engaged, I don’t see myself making many more contributions.
That said, I’ve brought my experimental fork to a nice state.
Here’s the link: Checkout this Quelea expansion pack build with Improvements and experimental features! - #7 by JessyJP
If anyone is interested in working with me, we could:
- A) Fix bugs—especially this major one.
- B) Build a macOS version (someone with a Mac would be needed).
- C) Add revamped APIs for new Bible and song searches, as well as remote theme selection.
- D) Finish work on web remotes and some theming improvements.
Then we can revitalize Quelea and provide builds every few months at least.
My team is regularly using my fork
We’re quite happy with it so far, so I won’t be changing it anytime soon.