Oof, my head: I wrote about a month ago regarding user experience and how much I love the Eyesy and have integrated it into my live setup.
And I just wanted to write again as the ‘PGM translation to modes’ issue is just becoming a headache.
Basically for you can use a PGM message to change to specific modes, but these PGM to Mode numbers are not fixed, meaning that every time you add or subtract a mode it means your programming values need to be rejigged completely based on how the mode numbers have shuffled around.
And it doesn’t appear fixed either - you don’t simply go back into your midi programming for these PGM values and just bump the number of every program up or down to get it back to your original editing state. It sometimes seems to jump around to other values that I have not seen a pattern for.
That’s all fine, I resolved to just not add any more modes to the Eyesy until we had an update.
However I have now found that even editing an already existing mode seems to have completely knocked many many hours of editing PGM sequence changes off balance. I was very careful to keep all my modes named as is, and to just work within an already existing mode.
And I’m pretty careful with this kind of thing - for 5 years I’ve been running a pretty large two tier rack of external gear, and have been fine tuning and handling a set based off midi PGM change values and I don’t have the crazy bugs I get with the Eyesy in this area.
It’s not fun having to quickly fix everything the night before a set for only making a small change. It does not seem comparable to the amount of effort that has to go back into programming the Eyesy to work with your set.
Please please I beg of you wonderful Eyesy gods: can we have this PGM issue fixed. I recall you mentioned a table that would allow you to only allocate specific modes to PGM values. Anything along this line would be of huge value.
Sorry for the rant
