Dear community,
I created a patch on Pure data (test_hello_in_string_with_osc.pd ) capable of sending the word "Hello" over the network via the OSC protocol. Now, I want to send it to a Python script. How do I do this?

Through my research, I found works that send a message from Python to Pure data, but I want the opposite.

I appreciate the help.

@whale-av Thanks for answer.
it's because I had some doubts about the OSC message. At first, I was unable to send the word "Hello" over the network using OSC. Now, I find myself unable to send OSC messages other than using mrpeach.

In Python, I don't know how to indicate that it should receive the message from Pure Data.
Oh gosh ... this is hard

I was also asking which Python module you are using to send and receive OSC. @whale-av mentioned oscpy, but there are lots of Python modules for OSC communication. It's not that hard. Can you share some Python code, at least the one you're using to send OSC to Pd.

@romulovieira-me It should be very simple using MrPeach.

If you are using Pd-extended you need [import mrpeach]
For Vanilla maybe [declare -lib mrpeach]

Osc messages need an address.
I have put /python...... it could be /test or /anything.
The address can be longer......
You could have for example /mixer/fader1 and then /mixer/fader2 ...... the address tells the receiver how to differentiate messages on the same port.

"send" tells [packOSC] that it is a message that it should send.

If your receiver (python) is on the same computer then [connect localhost portnumber(
If it is on another computer [connect IPaddress portnumber(
i.e. [connect 192.168.1.67 9997(

David.

Hey-ho........ I just noticed you posted your patch.
I have not changed it.... I just changed the objects to their basic names and it works for me........
patch.pd
MrPeach is usually reliable sending OSC bundles in the correct format.
OSC can be sent in various formats and it can be necessary to set the format for each part of a bundle..... so for /test 0.5 hello 2 using the new vanilla objects the format would have to be set as fsi.....float symbol integer
But MrPeach does that automatically.
I have never coded in Python though.

@whale-av SOLVED

Thanks for the usual help.

1. I used the Pure data patch you posted and made some changes. In short, it was enough to use mrpeach and write the objects with their default name (patch: test_send_hello.pd )

2. to create the server in python, I used the base code of python-osc, available at: https://pypi.org/project/python-osc/
   I made the necessary changes so that I could send the messages in the format I wanted (code available at: osc_server.py )

3. to see the active server, I ran the python file on a linux terminal (I imagine it works the same on WIndows or Mac)

I really appreciate the help.

Is there a benefit of using mrpeach over the vanilla net send/receive objects? I don't quite see it, and I couldn't install mrpeach for some years, so I was surprised at the direction this thread took.

I vaguely recall that, some years ago, vanilla support for OSC was subpar and mrpeach filled the gap, but as I understand it now, vanilla support has improved and there isn't much concrete reason to add a dependency. But maybe I'm missing something.

hjh

@ddw_music There is no absolute reason not to use the vanilla objects..... but the mrpeach externals take care of formatting within the externals and they "just work out of the box".... so for a beginner they are first choice.
Also tutorials using OSC used mrpeach before Vanilla had any OSC objects....... and there have been very few tutorials since the explosion when Extended was released.
So beginners are naturally directed to using mrpeach and often unaware of the Vanilla objects.

The vanilla objects require formatting by the user...... and so a deeper understanding of the OSC specification.... so for most users they are much more difficult. There have been some quite terrible threads where OSC messages were simply exchanged by mrpeach and TUIO and trying to do the same in Vanilla was very difficult......... with symbols, integers and floats miss-specified in OSC messages.

Also Vanilla has a "bug" where all parts of the header are considered to be symbols.
Often the header contains an integer..... e.g. /mixer/fader/1... and the 1 being a symbol is only routable using [makefilename] to set a route individually for every possibility.
It can be a nightmare in vanilla..... and mrpeach is as easy as pie....

I am wary of pointing beginners to the vanilla objects if they already have mrpeach...... there is no reason to lead them into that minefield when they have just posted a question because they are already struggling......
David.

@romulovieira-me Thank you for posting your Python solution....... that will help someone in the future...
David.

@whale-av ah ok, so the problems are mainly in the handling of type tags. That's fair.

I knew about the numbers-in-command-path problem (surely that's fixable?). I hadn't thought about sending messages from Pd. SuperCollider at least just renders the value into an array so it doesn't complain whether the number is a float or int -- but now that you mention it, I could imagine other software that may require one or the other (and Pd being int-less would have an extra challenge there).

Thanks for the explanation.

hjh

@whale-av You are welcome. I hope to help those who faced the same problem as me