search

bitfocus / companion-module-behringer-wing

MIT License
6 stars 8 forks source link

WING Firmware v3.0 causes an error #24

Open sackboydad opened 1 month ago

sackboydad commented 1 month ago

Looks like Behringer changed something in the communication protocol with WING firmware 3.0, which supports the three new mixers they announced yesterday.

After loading FW 3.0, the yellow triangle appears in any button that calls on the WING module. On the modules page, it shows an error "Cannot Get Status" (or something like that... sorry I had to leave and forgot to write the exact error down)

After downgrading to FW 2.1, the error went away.

elliotmatson commented 1 month ago

It looks like this is similar to #22. I'm currently in the middle of re-writing the module to support Companion v3.0. Once I'm done with that, I'll start adding some of the new requested features and support for Wing FW3.0

sackboydad commented 1 month ago

It looks like this is similar to #22. I'm currently in the middle of re-writing the module to support Companion v3.0. Once I'm done with that, I'll start adding some of the new requested features and support for Wing FW3.0

Thank you. Yeah, I had the yellow triangle warning in the "connections" tab in Companion since we bought the WiNG lsat February. But never had the Yellow Triangle on any WING button itself until just today, after upgrading to FW 3.0.

sackboydad commented 1 month ago

FWIW, I re-installed FW3.0 and of course, the error triangle in all the WING buttons came back. But I tested to see if the stuff actually worked. Everything actually worked, including buttons updating with fader levels, fader commands, etc. I still downgraded back to FW2.1 but thought I'd share a little testing with you. I suspect the module is looking for something that the new FW has changed the syntax on or something. I know they've made major changes like all mix buses can now feed into all mix buses (instead of only 1-8 being able to have re-entries). And they changed the Matrices in a huge way.... they're essentially mix buses now (without being able to re-enter)

Question, on your re-write do you plan on adding support for the WING-Live card? Right now, I use generic OSC commands to control it but feedbacks or like position, etc would be nice. Thanks for all you do on this module!

elliotmatson commented 1 month ago

Yes I do! I currently do the exact same thing with our Live card!

sackboydad commented 1 month ago

Yes I do! I currently do the exact same thing with our Live card!

Hey, maybe in later FW, they've increased the subscription method to have more than one....

andrewinalaska commented 3 weeks ago

@elliotmatson Thanks so much! If there's anything you need help with or tested, let me know. I've got a pretty good feel for the changes in the v3.0.x WING firmwares, and had already had a few tweaks in mind to the module... I know enough git to clone the repository and enough JS syntax to get what I need changed, but can't seem to get companion to load edited modules from my dev path. I'm afraid I'm pretty wet behind the ears in this context. I'll try to track down the changes I was trying to make previously, but now that v3.0.x firmwares are out, some of the big changes will be enumerating the matrices as send points for channels and auxes (and limiting matrix the Direct INs to 1 selection from the 4 sources that remain), enumerating all busses as send points for all other busses, a bit of renaming ("Monitor A"->"Phones", "Monitor B"->"Speakers"), etc. If I recall, I was working a change to fix how Fader Adjust works, so that it could work in dB instead of %-of-fader-travel... and a few other odds and ends. Anyway, if there's anything I can do to help as you dig into it, please let me know!

istnv commented 3 weeks ago

@andrewinalaska

can't seem to get companion to load edited modules from my dev path. I'm afraid I'm pretty wet behind the ears in this context.

You would first need to recode the module for the companion 3.0 api before it will run from the dev directory.

If I recall, I was working a change to fix how Fader Adjust works, so that it could work in dB instead of %-of-fader-travel... and a few other odds and ends. Anyway, if there's anything I can do to help as you dig into it, please let me know!

Fader 'set' works that way. Internally the console 'thinks' in percent and calculates dB on the fly. You would need to reverse the 'dB' to '%' calculation to send the proper value to the console.