I’ve pushed a couple of potential fixes, one I noticed from your debug log, to the CI release of Quelea here: Release CI-RELEASE · quelea-projection/Quelea · GitHub
If you fancy giving this a go then it might fix the issue, but I still can’t see an obvious reason for a lockup to be caused by either of the issues I’ve fixed so I’m not overly confident I’m afraid.
Sounds good I will give it a shot tomorrow morning. Thanks. I love crazy bugs.
David Guice
Well I installed it and gave it a quick test. So far so good. I guess the real test will be Sunday. BUT it loaded and worked fine. The first load did take a couple of minutes to load but after that it loads fast.
I will let you know how it goes.
Thanks my friend.
David Guice
Well Sunday went OK. I did have one crash and had to scramble to rebuild the schedule. I had saved it but the crash corrupted the save file. I think it may have crashed during a save. I was distracted so did not see when it happened and was rushed so did not get the log file. The only other things I noticed is slow transitions from one song to the next and saves took a long time to happen. I took a quick look at the debug log and noticed it appears that it is saving the MP4 background files into what looks like a zip file. If that is what is happening then that would explain the time difference.But the good news is the motion backgrounds do work. Oh and one other thing I did notice. I have one"song" that is actually an MP4 file with music. The preview pane shows the motion file AMD plays the sound! OOPS!!! Granted its only snippet of the sound file but I was not expecting sound! Its an easy fix on my end. Just hit the mute key on the keyboard till I need the sound.
Anyhow, I will keep you updated on any other issues I see.
Thanks for everything,
David Guice
Thanks for the report, much appreciated - yes, we should probably also mute the sound by default in the preview window for that reason!
Re: Backgrounds - I believe we do save those by default in the qsch file (which is essentially just a zip file) so if that took a long time and looked like it crashed that might explain why the file was corrupt. We should probably also put in a better check for these things (or exclude saving big video files to the schedule file by default maybe.)
Well thats not too bad. Yes its slow on the save but as long as it does not crash its no big deal.
David
Example.
Just adding a 1.4GB mp4 to a new schedule and saving the schedule (without doing any preview or live view) takes a lot time here: the write speed to my SATA HDD seldom reaches 50MB/s, most of the time much lower. The schedule folder is excluded from the anti-virus app.
I’ve pushed a potential patch to the 2026.0 CI release that may help with this. (It skips the compression step which wouldn’t help with videos anyway, but should make things go noticeably faster.)
I will give it a shot tomorrow night and update then.
David
Michael
That really speeds things up! So far no crashes as well.
David
Michael,
Hope all is going well.
I have another head scratcher for you my friend. I finally got around to installing 2024.0 on my other PC here at church. Same motherboard, CPU, SSD, and memory. Only differences in the two units is the video card! The motion backgrounds work like a champ on the other system! So there must be something weird about the card in my one system. I have no idea what but if you run into this issue in the future you have somewhere to start.
Crazy I know.
David
That is interesting, thanks! Do both systems have the latest graphics card drivers?
No I am going to do an update and see what happens.
Well I have tried swapping computers. I now with 2024.0 crash on the regular. I have attached a crash log. Hope someone can find the problem.
Thanks everyone
David
quelea-debuglog crash 11-9-2025.txt (92.3 KB)
Afraid there’s no clues in the debug log - do the crashes appear all the time, or just when showing videos / video backgrounds?
When I am trying to edit a song with a motion background. I am going to try static backgrounds next week and see what happens.
Well the static backgrounds work great and no lock ups. So it appears that the size of the files is the issue. But the good news is that the static backgrounds will work just fine.
David