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

[Bug]: DEVICE - OSC Action - Argument not sent #707

Closed
AntP-vp opened this issue Jul 24, 2024 · 3 comments
Closed

[Bug]: DEVICE - OSC Action - Argument not sent #707

AntP-vp opened this issue Jul 24, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@AntP-vp
Copy link

AntP-vp commented Jul 24, 2024

What happened?

Hi all, I'm trying to send an OSC string from a device using the Action but TA is not sending the argument part.

The monitoring in the receiver software show that no arguments 'string' is received, using the same path and argument from Companion works good and a camera view is shown in the software.

Thank you.

TA Companion

Version

3.0.10

Distribution

Desktop

OS

Windows

What browsers are you seeing the problem on?

No response

If applicable, What Listener Clients are You Using?

No response

TallyArbiter configuration

No response

Relevant log output

No response

Error stacktrace (if applicable)

No response

@AntP-vp AntP-vp added the bug Something isn't working label Jul 24, 2024
Copy link

Hello there AntP-vp 👋

Welcome to TallyArbiter!

Thank you for opening your first issue for the Tally Arbiter project. Tally Arbiter fosters an open and welcoming environment for all our contributors. Please adhere to our Code Of Conduct.

If you have more to contribute to this issue, please comment down below! We will try to get back to you as soon as we can.

@AntP-vp
Copy link
Author

AntP-vp commented Jul 24, 2024

Here is the Log, all seems to be fine here.

TA Log

Also using a different OSC listner, shown that the argument isn't sent:

TA Log Listner

@Jocke4f
Copy link
Collaborator

Jocke4f commented Aug 8, 2024

Yes, there are two bugs in OSC RunAction.

  1. No data is sent.
  2. String is not identified.

The PR #713 solves this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants