v5 Beta 3 - doesn't save the BPM settings

Report an issue that you found while using QLC+ 5.x.
Please provide as many details as you can, a sample workspace if available and don't forget to read the forum posting guidelines first !
Post Reply
JanXD
Posts: 3
Joined: Sun Aug 20, 2023 11:35 am
Real Name: Jan-Hend

When I save a project, it doesn't retain the BPM settings. Means the Tempo is not saved in the run properties. When I reopen the project, it reverts back to the default time setting instead of beats. This issue existed in version 5 beta 2, and I was hoping it would be resolved in beta 3. Unfortunately, it is still present.
User avatar
mcallegari
Posts: 4908
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:

This should be fixed upstream now.
Thanks for reporting.
JanXD
Posts: 3
Joined: Sun Aug 20, 2023 11:35 am
Real Name: Jan-Hend

Over a year has passed. Is there an update for version 5? A beta 4? The software is useless to me if the settings do not stay saved.
User avatar
edogawa
Posts: 650
Joined: Thu May 07, 2015 10:34 am
Real Name: Edgar Aichinger

In case you missed it, since quite a while we have a Github Workflow set up that tries to rebuild Windows exe binaries and Linux Appimages of both v4 and v5, with every source code change.
So, if Massimo tells "fixed upstream", the fix should be included in the newest build over there.
You can pick any of the green entries in the list and select your download at the bpttom of the page you get.
Post Reply