-
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 communication output #56
Comments
Hello again! |
Hi @pushkhy I'm very sorry for my delay. Do you mean you would like to have a different messages ie Fist o or 1, spread pose 0 or 1 etc? Where are you sending the messages to? Maybe I can help in that. |
Hello! No worries at all! For example, for /orientation/scaled you will get Myo parameters: If you look at the screenshot I've sent before, you will see that for /orientation/scaled, Osculator (the window with yellow squares) is getting 3 Messages (0, 1 and 2) where: For /pose (also in screenshot) In this setup, it would be useful if rest, unknown, fist, fingerSpread, waveIn, waveOut and doubleTap were outputted as individual Myo Parameters and consequently Osculator would interpret them as individual messages leading to separate individual Midi messages to Ableton. Thank you!!! |
Hello @balandinodidonato ! |
Hi @pushkhy I apologies. I just took a Lectureship at University of Leicester have been crazy days. I intend to do some work on in in the future, but not sure about the future of the software give the Myo is discontinued. I'm hoping to do new builds and fix bugs on windows. Any particular request? |
Hello @balandinodidonato Early this year we've discussed the /pose limited resources when combining MyoMapper with Osculator. I am sending OSC to Osculator (https://osculator.net), which then translates OSC to Midi, which then goes to Ableton. For example, for /orientation/scaled you will get Myo parameters: If you look at the screenshot I've sent before, you will see that for /orientation/scaled, Osculator (the window with yellow squares) is getting 3 Messages (0, 1 and 2) where: For /pose (also in screenshot) In this setup, it would be useful if rest, unknown, fist, fingerSpread, waveIn, waveOut and doubleTap were outputted as individual Myo Parameters and consequently Osculator would interpret them as individual messages leading to separate individual Midi messages to Ableton. Recapitulating, for some reason Osculator is getting for all different /pose gestures ( fist, fingerSpread, waveIn, waveOut and doubleTap) the same message. I hope this is not confuse!! It's a shame Myo is discontinued, what a powerful tool! Thank you so much for your attention! |
Allo allo @balandinodidonato I don't think you got back into the software but double-checking... Thank you for your attention! |
Allo allo @balandinodidonato I hope you are well on these singular times we are living! 2020 has been a crazy year and it seem that 2121 won't be very different. Due to the lockdown and internacional situation, I will be staying home for a few months. After reading all the thread again, I concluded that, willing to give you as much as information possible that it turned confusing. Thank you so much for your attention! Obrigado! |
Hello! I am really new with MyoMapper and programming and my question might seems really amateur. I've tried for a while to solve it on my own before asking.
I am sending MyoMapper output to Osculator where I assign midi that is consequently sent to Ableton.
Shouldn't the Hand Pose have values from -1 to 5?
Osculator only displays 0 & 1.
Thank you!
The text was updated successfully, but these errors were encountered: