Page 1 of 1
v5 Beta 3 - doesn't save the BPM settings
Posted: Sat Jan 27, 2024 12:37 pm
by JanXD
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.
Re: v5 Beta 3 - doesn't save the BPM settings
Posted: Mon Jan 29, 2024 10:26 pm
by mcallegari
This should be fixed upstream now.
Thanks for reporting.
Re: v5 Beta 3 - doesn't save the BPM settings
Posted: Fri Apr 04, 2025 10:22 am
by JanXD
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.
Re: v5 Beta 3 - doesn't save the BPM settings
Posted: Sat Apr 05, 2025 12:02 pm
by edogawa
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.