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

[ossia-max] / [ossia-pd] problems connecting ossia.device and ossia.client via oscquery #831

Open
evanmtp opened this issue Oct 12, 2023 · 0 comments

Comments

@evanmtp
Copy link
Contributor

evanmtp commented Oct 12, 2023

I'm exposing an ossia.device using non-default ports (osc: 1235, ws: 5679). I'm having difficulty connecting an ossia.client to the ossia.device using some of the methods listed in the help patcher.

  • connect oscquery 5679 doesn't work. This error is printed to the console: "HTTP Error: No connection could be made because the target machine actively refused it"

image

  • connect my_device (where my_device is the name of the remote device) also doesn't work.

image

  • connect oscquery ws://127.0.0.1:5679 works.

This problem occurs with both the Max and the Pure Data versions of the objects. I'm attaching Max and Pd test patches.

Steps to repro:

  1. In ossia.device_connection_problems.maxpat:
    a. Click register.
    b. Click name my_device.
    c. Click `expose oscquery 1235 5679
  2. In ossia.client_connection_problems.maxpat:
    a. Click connect oscquery 5679.
    b. Click connect my_device.
    c. Click connect oscquery ws://127.0.0.1:5679 . This should work.
    d. Click namespace, and verify that the addresses are visible in the jit.cellblock.
  3. In ossia.client_connection_problems.pd:
    a. Click connect oscquery 5679.
    b. Click connect my_device.
    c. Click connect oscquery ws://127.0.0.1:5679 . This should work.
    d. Verify that the sliders are moving.

ossia.client_device_connection_problems.zip

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

1 participant