-
Notifications
You must be signed in to change notification settings - Fork 8
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
OSC messages not received by MyoMapper #40
Comments
Hi @najiglass is it happening with any of the OSC messages you send to Myo Mapper or only when you the vibrate one? |
@balandinodidonato Thank you for the quick reply. I tested with "/myo1/pitch/setMin 0.2" as well but didn't see any impact on the min value in the Status window. |
which version are you using? could you test with these examples? |
I'm on 3.1.6, reinstalled to make sure. I can't test on Max right now but the Ableton examples work fine, though they don't seem to be sending anything to Myo Mapper, only receiving from it. |
I don't have touch designer. Anyway the vibrate function does not work for now. I did disable it due to a bug I cannot fix yet. I'm working on it though. About the scaling option you have some issues in your code. You try to set Myo Mapper's Pitch inMin value by doing Try in this way and let me know how it goes :) PS I do apologise there was a bug in the wiki, please check it now. |
Thank you! I tried with the new line to send "/myo1/pitch/inMin 0.2" but the values aren't changed in MyoMapper unfortunately. Not sure where the issue is. Looking forward to the vibration feature! |
sorry my bad... try |
That works, thanks a lot! |
/myo1/Pitch/centre "centre" doesn't work though. Any ideas? |
sorry my bad it should be |
Great, works now! |
Sending out OSC messages to the configured port has no effect on the Myo.
OSC Receiver set to 5425, and the test message is /myo1/vibrate "long"
When (temporarily) monitoring the port the message comes through correctly, but MyoMapper doesn't get it / doesn't send it to the Myo.
MyoMapper is sending out the OSC messages correctly (e.g. /myo1/pose "rest")
Any advice?
The text was updated successfully, but these errors were encountered: