It seems that parameter when you have sysex as message type does not always get the same value in the sysex editor under JSON. I have several times thought that I have something wrong with the parameter number. When I then look in the JSON, I see a different number. As soon as I change that number to the correct one, everything works as it should.
no sure what you mean… both screenshots show parameter 179. So they are the same, not different. All good. What am I missing?
What have you missed? Nothing because I uploaded the wrong screenshot 
Apologies for that.
Let me do it again with a better explanation.
First I change the parameter from 261 as in the image below…
…to 291 as in the image below
But the parameterNumber in JSON is still 261
If I change the JSON parameterNumber to 291 everything works.
Oh, I see. It’s not really a bug, rather a feature of working with Sysex. You need to consider the json, as being a collection of bytes you want to use in your Sysex. That can be a set of constants and a value from the parameter you send from, as in your example. But in a lot of other cases, the Sysex is more complex, and might have functions in it , a subset (bits) of parametervalues, or even values coming from other parameters.
In other words, once the json is made, you better not have that SysEx json change anymore because you change the characteristics of the parameter the sysex it belongs to. The correlation might be intended (like you want it) or not (as in some other cases), but it is certainly not considered as being fixed. At least that’s how I consider working with it.
So once the SysEx json is made, you have to attend to its changes yourself.
Ok I understand. Thanks for the explanation. I think that’s why I used the title “possible” bug
