rivafarabi / deckboard

Control your PC with your phone in easy way possible. News and updates on @DeckboardApp.
https://deckboard.app/
565 stars 30 forks source link

OBS microphone toggle in Multi Action [BUG] #1120

Closed lnaccarato closed 4 months ago

lnaccarato commented 5 months ago

Describe the bug

There is a problem when we select the microphone in multi action. It does not confirm the action resulting in non-execution.

To Reproduce Steps to reproduce the behavior:

  1. Go to 'New Button'
  2. Click on 'multi action> edit> add action.'
  3. Fill a value to '.Action=Audio source control>Select microphone>Toggle Mute'
  4. See error

Expected behavior

mute or unmute the microphone.

Screenshots Iimage

Server App (please complete the following information):

Client App (please complete the following information):

Required files

Additional context Your App is the best !

rivafarabi commented 4 months ago

Fix will be added in tomorrow's update. Thanks for the feedback

mordang7 commented 4 months ago

Issue still present in 3.0.2 fix unfortunately.

rivafarabi commented 4 months ago

Do you mind share the screenshot or screen capture showing the bug/issue?

mordang7 commented 4 months ago

Thank you for your help, as you can see in this picture, my mic in OBS is active, the icon on the PC side of Deckboard has updated its state to active, but the icon on the Android app - even though it does work - will just stay in the inactive state.

On Mon, Jul 1, 2024, 16:29 Riva Farabi @.***> wrote:

Do you mind share the screenshot or screen capture showing the bug/issue?

— Reply to this email directly, view it on GitHub https://github.com/rivafarabi/deckboard/issues/1120#issuecomment-2199433828, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFCNRJ5TYX4ZBNFCEY3RC2LZKEAMVAVCNFSM6AAAAABJVWOTAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJZGQZTGOBSHA . You are receiving this because you commented.Message ID: @.***>

rivafarabi commented 4 months ago

The main issue mentioned in the first post has been resolved in version 3.0.2 While the issue mentioned by @mordang7 here and in #1121 has been fixed in version 3.0.3

Feel free to open a new thread if you still face this bug.

Closing this.