Softkeys not sending OSC commands

[n9yty]

The softkeys are displaying properly, including the "More SK". In fact, the "More SK" will change the set of softkeys, but they don't send anything. It is simple to fix, go into each softkey and select etc-eos: Press Key as the action, parameter being softkey_1 through softkey_6. When "More SK" is pressed, they still will send these same values. Works great.

[MBresin]

Updated and Fixed! Thought I had written this already, apparently this is when I started getting more work.

[n9yty]

I'm in the process of converting the Companion module to v3 format, and as a tweak I am working on getting encoder values send back. I have it working in general (by wheel numbers) but it seems the wheel numbers change for every fixture. {sigh} So I am going to see if parsing by wheel name is reliable enough to map to known variables instead of by wheel number. When I get done and finish updating your layout to match I'll send it over to you to play with.

[MBresin]

That would be great! Sadly I just haven't had a ton of time to work on Coverting over to v3. I would love to play around with what you make.

[n9yty]

Since I don't have your email, I'll attach a WIP copy of the mods I am doing to the companion module to work in Companion v3 and expose encoder parameter values... unpack it inside a parent directory and in the BitFocus app window (not the web confiugration) click the gear in the upper right and then set the parent directory as the Developer module path. I'll also attach a copy of your configuration that I have reworked a bit to take advantage of it. Let me know if you have problems. Maybe backup your existing configs and import this in its entirety as the connection probably has a different internal name and the links may not carry over. Unsure. I had to reconnect some things when I was testing here. (I updated the companionconfig after initial upload, forgot to check all the fine/ultra/coarse, I may have missed some. I need to figure out what you are doing with acceleration variables/values/etc ;) Nicely done though!)

There are some other color emitters not accounted for in here, like Lime... I wonder just how many can exist. :)

2023-05-17-14-36CST Updated the files.

Companion ETC EOS Module

Companion Configuration File

[MBresin]

I am playing with the Module and have fixed a few issues here and there. Thank you for this. I was hoping for the values to show up and this is great! I have a few things to update on the Config file, I am currently figuring out how I can switch up buttons. Also exploring the new features of V.3.

I will add in colors and such too.

[n9yty]

If you find other parameters that need to be exposed into variables to get value feedback let me know and I'll put them in a pull request. I'm sure I don't have ALL the LED emitter colors in there. Since any given fixture can theoretically define a new param/wheel I guess there is no comprehensive list. :)

[n9yty]

BTW: It sounds great, but maybe not manageable, but if Companion had scripting support internally, we could grab all the available wheels by their category number and build pages/assign buttons based on the live data coming in. But then things would move around. I think they do move around on the console encoders though, so it would be "consistent" with that. Right now, though, I'm quite liking how your config is working for the things I would most often reach for an encoder for. You can always pull up the ML controls to adjust an odd one that isn't in there. ;)

[n9yty]

Just a note that the latest beta for Companion, 3.0.0+5900, has the etc-eos module changes included so there is no longer a need for the developer directory code. I also added additional values for the shutter items (thrust/angle/frame assembly), as well as some other values I found being used in other projects online.

[n9yty]

Just pushed one more update through, hopefully it makes it in the next/future beta cycles to clean things up even more, and the thrust/angle/frame stuff wasn't complete in the implementation. I consolidated now so definition of parameters is only in one place and I can't forget to keep them in sync. :)

[n9yty]

It is not in the current betas, waiting for the pull request to be accepted, but just FYI I have added an action to send an OSC command with arguments (taken from the Generic OSC module) so it should require only one connection to do everything now, unless there was something else with a dependency on it that I didn't see.

UPDATE: just merged in, should be in beta builds after this point.

[n9yty]

@MBresin Here is another beta build of the module, ahead of sending in a pull request - more params. I tweaked your config a bit more to include handling gobos/etc and displaying values. I would imagine you may or may not like how I did it, but I look forward to your eventual release to take advantage of the variable values that are available now.

companion-module-etc-eos-beta_v2.0.4.zip

[MBresin]

I haven't had time to mess around more with the file. I have been on a job the last week. I will try to take a look at it this week. Thank you for all this work!

The only things I have touched so far was the Focus pages as it was doing some odd things with the first new build. but might not be an issue now.

[n9yty]

@MBresin - Would you mind emailing me?

I would like to run something by you that I am working on to capture all encoder wheels for any fixture to see if it would be useful before I push it through in the module.