-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Organ fails to start with invalid configuration #1696
Comments
A workaround: delete the old .cmb file from the GrandOrgue/Data folder, start GrandOrgue and make the configuration from scratch. Don't use 32 as the midi message length due the bug #1686. A more complex workaround: unpack the text file from the .cmb file, change the MIDISendLength001 value to 31 and replace the packed .cmb file with the plain text file. |
Thanks Oleg. Your first work around works well. I can now open the Pitea organ once more and continue my console development. Would you be able to suggest an app for opening the cmb file? My ubuntu graphical extraction tool does not seem up to the job. I'm inclined to leave my issue open as it underlines several issues:
Thanks so much for your help. I'm keen to explore your second option of inspecting the .cmb file, and might even try building GO later this evening to try to investigate further. |
File->Settings->Organs, select the organ and press to also
Agree. It will be the subject of the issue. |
Right click on the .cmb file in Nautilus. As usual, the recommendation is that one doesn't edit the .cmb files manually, but sometimes it can indeed save the day... |
Thanks Oleg and Lars for your very helpful suggestions. I must have fumbled the .cmb file extraction previously. Using 'nautilus' aka 'files' I successfully extracted and viewed the .cmb file and located the troublesome field value of [SetterCurrentPosition]...MIDISendLength001=32. Yesterday I re-created the organ configuration avoiding the field value of 32, so I'll not risk file editing this time around. The source code build instructions for debian work perfectly on rpi4 taking 50 minutes to compile. I do have a much faster Ubuntu x86 machine if you would like me to test any fixes for this issue. Thanks Lars for the excellent video series. Is the Barton 3-7 organ sample set featured in your Full and 2nd touch video available for download somewhere please? Maybe I should consider designing a velocity sensing pedal board! |
While trying to understand the format of sysex messages to my LCDs which seem to vary in text start position I suspect that I configured the metronome displays (BPMinute or BPBar) of PiteaMHS badly. Now the organ fails to start with the following log message displayed:
Selecting the panel tab, where I would expect to see the Metronome panel, a blank rectangle is displayed. This prevents me from updating/correcting the configuration so I am stuck. I cannot even determine what the bad configuration item is. The organ was running nicely before I closed and restarted it.
Ideally I would like to be able to restore the organ configuration to something that starts without losing the unrelated receive and send event configurations. The problem occurred running grandorgue-3.12.3-1.linux.aarch64, and persists with grandorgue-3.13.0-1.linux.aarch64. This seems like a bug to me.
The setup is:
Any help, or suggestions for further investigations much appreciated. Thanks for such a wonderful project.
The text was updated successfully, but these errors were encountered: