Skip to content

OSC message arguments break commands #31

@dandln

Description

@dandln

Hi there,

Whenever I use one of QPlayer's OSC commands with arguments (such as firing or selecting a specific cue), the command will not work.

For example, these work as expected: /qplayer/go, /qplayer/down
These do not work (nothing happens when the message is received): /qplayer/go, 3, /qplayer/select, 3

I have also tried different variations such as /qplayer/go,3 (without space, as the documentation does not have a space between arguments, although this seems to be contradictory to the source code), or /qplayer/go, "3" (trying to use a string instead of the numerical), but neither work. The issue does not seem to be that the specified cue isn't found, as the error message the source code specifies for this case also doesn't appear in the logs. It is as if the OSC message just isn't processed at all if arguments are present.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions