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

OSC communication output #56

Open
pushkhy opened this issue Mar 22, 2019 · 8 comments
Open

OSC communication output #56

pushkhy opened this issue Mar 22, 2019 · 8 comments

Comments

@pushkhy
Copy link

pushkhy commented Mar 22, 2019

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!
Screen Shot 2019-03-22 at 11 03 58

@pushkhy
Copy link
Author

pushkhy commented Mar 23, 2019

Hello again!
I understood that Hand Pose is a parameter with values that range from -1 (unknown) to 5 (double tap) (Message console inside Osculator)
Using Osculator, each one of this values is understood as the same message sent by Hand Pose parameter.
Is there a way to separate this values in order to make them separate messages?
I reckon that with this setup MyoMapper+Osculator probably not...
Thank you!!

@balandinodidonato
Copy link
Owner

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.

@pushkhy
Copy link
Author

pushkhy commented Mar 30, 2019

Hello! No worries at all!
I am sending OSC to Osculator (https://osculator.net), which then translates OSC to Midi, which then goes to Ableton.
The "event type" options in Osculator then allows me to combine different signals and make it really easy to Midi map in Ableton (again, my programming knowledge is quite basic and limited so combining softwares is initially the best option to get it practical).

For example, for /orientation/scaled you will get Myo parameters:
Yaw Scaled
Pitch Scaled
Roll Scaled
Each one of them with a range from 0 to 1.

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:
0 is Yaw Scaled
1 is Pitch scaled
2 is Roll Scaled
Each of one of them can be individually assigned to a different Event Type and Midi Channel.

For /pose (also in screenshot)
Osculator is getting 2 Messages (0 and 1) where 1 is all the poses (where fist, fingerSpread, waveIn, waveOut and doubleTap are "just" different values), because Pose is ONE Myo Parameter (MyoMapper Output) then translated to ONE Message in Osculator.
For Osculator, fist, fingerSpread, waveIn, waveOut and doubleTap are basically the same Message and will output one midi signal.

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.
Then in Osculator, it would have for /pose
0, 1, 2, 3, 4, 5, 6 and 7.

Thank you!!!

@pushkhy
Copy link
Author

pushkhy commented Sep 9, 2019

Hello @balandinodidonato !
Have you made recent changes to MyoMapper?
Thank you for your work!

@balandinodidonato
Copy link
Owner

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?

@pushkhy
Copy link
Author

pushkhy commented Sep 14, 2019

Hello @balandinodidonato
Please don't apologize! Actually my apologies for asking you!

Early this year we've discussed the /pose limited resources when combining MyoMapper with Osculator.
I hope you don't mind if I copy part of our past conversation:

I am sending OSC to Osculator (https://osculator.net), which then translates OSC to Midi, which then goes to Ableton.
The "event type" options in Osculator then allows me to combine different signals and make it really easy to Midi map in Ableton (again, my programming knowledge is quite basic and limited so combining softwares is initially the best option to get it practical).

For example, for /orientation/scaled you will get Myo parameters:
Yaw Scaled
Pitch Scaled
Roll Scaled
Each one of them with a range from 0 to 1.

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:
0 is Yaw Scaled
1 is Pitch scaled
2 is Roll Scaled
Each of one of them can be individually assigned to a different Event Type and Midi Channel.

For /pose (also in screenshot)
Osculator is getting 2 Messages (0 and 1) where 1 is all the poses (where fist, fingerSpread, waveIn, waveOut and doubleTap are "just" different values), because Pose is ONE Myo Parameter (MyoMapper Output) then translated to ONE Message in Osculator.
For Osculator, fist, fingerSpread, waveIn, waveOut and doubleTap are basically the same Message and will output one midi signal.

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.
Then in Osculator, it would have for /pose
0, 1, 2, 3, 4, 5, 6 and 7.

Recapitulating, for some reason Osculator is getting for all different /pose gestures ( fist, fingerSpread, waveIn, waveOut and doubleTap) the same message.
Is there a way to make them individual messages?
As you replied to me earlier, "Do you mean you would like to have a different messages ie Fist o or 1, spread pose 0 or 1 etc?"

I hope this is not confuse!!

It's a shame Myo is discontinued, what a powerful tool!
Have you heard about the Mi-Mu gloves? They look really interesting too but super expensive!

Thank you so much for your attention!

@pushkhy
Copy link
Author

pushkhy commented Jan 22, 2020

Allo allo @balandinodidonato

I don't think you got back into the software but double-checking...
Sorry for insisting!

Thank you for your attention!

@pushkhy
Copy link
Author

pushkhy commented Feb 17, 2021

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.
I am locked down in Portugal where t situation was quite dramatic few weeks ago but is now getting "under control".

Due to the lockdown and internacional situation, I will be staying home for a few months.
This way I am back on the Myo project, and, I am sorry for that, but here am I, once again asking for your help.

After reading all the thread again, I concluded that, willing to give you as much as information possible that it turned confusing.
So, yes you are right:
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?
It would be amazing if you could make this update on MyoMapper!

Thank you so much for your attention!
And once again, I am sorry for insisting but I really can't do it on my own...

Obrigado!

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

2 participants