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

Fader actions not working properly #6

Open
iddqdosc opened this issue Mar 23, 2022 · 4 comments
Open

Fader actions not working properly #6

iddqdosc opened this issue Mar 23, 2022 · 4 comments

Comments

@iddqdosc
Copy link

iddqdosc commented Mar 23, 2022

Hi, the "Increase fader level continuously" does not work. Nothing happens when I press the button. Is it possible to add an action that increases/decreases level by a user-defined value? So we can hold the button to increase or decrease the volume.

Also, "Increase Group fader 1 level" only works for group number 1, no matter if I change the value to other groups that I need to control. I believe this is consistent across all channel types, everything other than number 1 does not work.

Latest Companion version 2.2.0+3998. I also tried the most recent beta 2.2.0+4024-beta-2fa804e4
Windows 10 21H2, MOTU Ultralite AVB

Thank you.

@iddqdosc
Copy link
Author

iddqdosc commented Mar 23, 2022

I found out that if I add a "Group fader level" action first and then change to a different channel, it will unlock the "increase group fader 1 level" to work with different channels as well. Seems like a bug but at least I made "group fader 1 level" work with all channels temporarily (if I close the companion app and open again, "increase fader 1 level" stops working).

Still can't find a way to enable "fader level continuously" at all.

@ivan-ef
Copy link
Contributor

ivan-ef commented Nov 7, 2022

stable 2.3.1 / beta 2.4.0 release

only "increase/decrease !CHANNEL! fader level continuously" action works.

Group, Main, Monitor inc/dec continuously action doesn't react to stop inc/dec action and goes to infinite loop with log error:
instance(motu): Fader level state for channel: Channel undefined unknown. Please set value manually first.

@josephdadams
Copy link
Member

It's because their protocol does not offer any feedback, so we can't increase the fader level until we know what the fader level is first (i.e. setting it manually)

@ivan-ef
Copy link
Contributor

ivan-ef commented Nov 8, 2022

what the fader level is first (i.e. setting it manually)

Fader Level is already set with “set main or group or monitor level” action.
and increase/decrease 1db action works. But continuous action only works for channel, not for main, group or monitor. I gues it uses same variables.

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

3 participants