Closed muranyia closed 6 years ago
I'll check it out. Thanks!
On Feb 24, 2018 12:31 PM, "muranyia" notifications@github.com wrote:
It seems that tempo gets saved into the first pattern, and after deleting the event and saving the file it reappears. It also seems that this tempo does not have anything to to any more with the tempo set in the GUI (it is insisting on 130 for me, which I've already changed some time ago to another value).
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ahlstromcj/sequencer64/issues/141, or mute the thread https://github.com/notifications/unsubscribe-auth/AHnVqI-4HZ5xlYwvk6Luh7ydojfbYh1xks5tYEd9gaJpZM4SR-F7 .
I have removed that feature; now, if you want a tempo event, you have to add one in the event editor or log one using the button on the main window. That makes more sense, thanks for the report. Currently available in the active branch, qt5_reconcile, and I'll merge it when it is time for 0.94.6.
I think this is solved. Thanks!
It seems that tempo gets saved into the first pattern, and after deleting the event and saving the file it reappears. It also seems that this tempo does not have anything to to any more with the tempo set in the GUI (it is insisting on 130 for me, which I've already changed some time ago to another value).