Skip to content
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

Send a midi message from a lablel just after the MIDI send event is changed #2062

Open
jefferycrowley opened this issue Nov 30, 2024 · 1 comment
Milestone

Comments

@jefferycrowley
Copy link

Hello all,

I have recently been attempting to port Sysex messages to my 3 LCD Screens on my Virtual Organ console. I have only been partially successful.

Last night I finally got the [sequencer position] from the MIDI Objects menu to display on what was supposed to be one screen but it ended up on all three screens. I also attempted to get the Organ Name and Temperament label to appear on the first (1) LCD Screen and also get the current file name and General Bank on two separate line on the second (2) LCD Screen. I configured the [sequencer position] to be on the second line of 16 characters of the third screen (3).

The sequencer position label appears now on all three screens (this was after attempting to set-up all three screens) albeit the sequencer position is showing correctly on all three screens, but the organ and temperament, current file and general bank are not showing at all on screens 1 & 2.

I have set up the Device ID = 1 on both Organ Name = Device: Any Device>Event: = SYSEX Hauptwerk 16 Byte String Name>Start-Position: = 1> Length: = 16. Then the Temperament as Device: = Any Device>Event: = SYSEX Hauptwerk 16 byte Sting Name>Start-Position: = 17> Length: = 16.

Nothing appears on the screen except the sequencer position - Do I have to restart the Organ in Grand Orgue to make this work?

For the second LCD Screen Device ID = 2 for both Current File Name=Device: = Any Device>Event: = SYSEX Hauptwerk 16 Byte String Name> Start Position: =1>Length: =16. For General Bank Label= Device: Any Device>Event: =SYSEX Hauptwerk 16 Byte String Name> Start Position:: =17> Length: =16.

For the third Screen I have set [sequencer position] as Device ID: = 3. Device: = Any Device>Event: = SYSEX Hauptwerk 16 Byte String Name> Start Position: = 23> Length: 3. Because I want the Sequencer Position to appear in the center of the second group of 16 available spaces.

I would really appreciate if you would consider to make the General/Divisional last pressed AND the Button Pressed to appear as a Label item and not a fixed stop-like image so that we can then implement them as an on-line graphic for the sample-set and that is what I would like to program to appear on LCD Screen #3 - first 16 characters.

Well, I must have set the wrong Event for the Sequencer Positions as SYSEX Hauptwerk 32 byte String Name because now I cannot get the sample-set to load properly because the is an error: Out of range value at section 'SetterCurrentPosition' entry 'MIDISendLenth001':32 - see pop-up error in images of the message. It will not allow me to open up the organ in Grand Orgue to correct the situation.

Two questions: Do I have to restart the organ in order to get the Organ Name, Temperament, Current File Name to appear on the correct LCD Screens?

Outside of renaming the Organ completely is there a way to open the organ, bypass the critical stop error and correct the situation or do I have to rename the organ and then fix it starting fresh with the MIDI Objects?

You all are doing a fabulous job - keep up the good work!

Jeffery
Error with Sequencer

@oleg68
Copy link
Contributor

oleg68 commented Dec 1, 2024

Do I have to restart the organ in order to get the Organ Name, Temperament, Current File Name to appear on the correct LCD Screens?

For now, GO Labels send MIDI events only when their text is changed. So you have to reload an organ, change a temperament and switch to another combination file for they to be displayed.

I think we may add sending midi events on changing MIDI send for a Label as well in a future version.

Outside of renaming the Organ completely is there a way to open the organ, bypass the critical stop error and correct the situation or do I have to rename the organ and then fix it starting fresh with the MIDI Objects?

#1707 allows to start GrandOrrue with an invalid MIDI settings starting with 3.13.2. Seems we are using a very old GrandOrgue version. I suggest you to install the latest version from https://github.com/GrandOrgue/grandorgue/releases/tag/3.15.3-1

@oleg68 oleg68 changed the title Attempting to port Sysex messages to LCD Screens - Setup issues Send a midi message from a lablel just after the MIDI send event is changed Dec 1, 2024
@oleg68 oleg68 added this to the 3.16.0 milestone Dec 1, 2024
oleg68 added a commit to oleg68/GrandOrgue-official that referenced this issue Jan 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants