Hello! i need help for a weird issue with Netreceive which is receiving messages from Send2Pd of a Python script.
in the past i followed this article https://guitarextended.wordpress.com/2012/11/03/make-python-and-pure-data-communicate-on-the-raspberry-pi/
and i was receiving the messages (i received a nice Bang every time the code on python was running)

Now Puredata doesn't seem to receive the messages anymore but i'm using the same patch/ same script!
This is totally weird to me and i can't really understand why. It looks like they are on 2 different worlds.
This is probably something very stupid but indeed i need help!
What could be now the obstacle?
thanks for any help!

@nhouse The port could be blocked by security (antivirus?) or the firewall or in use by another program.
If it is a localhost port then being already in use is most likely.
I assume you are using Linux as using python.
In a terminal you can check port status with "netstat -a"
You should see either localhost:3000 listen or 0.0.0.0:3000 listen...... which will tell you that the port is listening.
Unfortunately it doesn't tell you which program opened the port.
Maybe run netstat before opening the patch to see if the port is already in use......... and then run the patch to see whether Pd has opened the listening port.
David.

chenged port and it doesn't change anything.
also, "netstat -a", shows that the port 3000 was free.

if someone would be so kind to try this on their computer, i uploaded the 2 patches on github:
https://github.com/Nhouse111/Python_to_Puredata.git

@nhouse said:

https://github.com/Nhouse111/Python_to_Puredata.git

Tested and It works on OSX, as soon as you put the same port number (your script has 6000 and your pd patch have 3000 in your exemple)

@60hz yes was a mistake when i saved the patch for the test.
As i imagined. (all this stopped working at same point, now they are not working neither on my macbook nor on the Raspberry Pi.
no idea what is blocking such communication. It really could be a strike?

@nhouse Maybe python cannot actually find the pdsend binary?
Does it need to be copied from Pd/bin into a folder known to python or registered somehow with the OS?
So has that link (Python finding pdsend.linux) been broken when updating Python for your original setup and not made at all (pdsend.darwin) for your OSX test?
David.

@whale-av said:

Maybe python cannot actually find the pdsend binary?

Maybe yes, under OSX, I changed to an absolute path in order to make it work actually...

@whale-av i thought about a similar issue, but i really don't know how to check or fix!
i have tried:

• old mac/same puredata/same python 3.8
• old raspberry(linux)/python 3.7
• freshly new installed Raspberry/python 3.9
• new mac/new puredata/new python3.9
• new mac/new puredata/new python2.7

i'm thinking that maybe i'm doing something wrong because i tried to run the Pd patch and the python script on a different computer (again mac) but it doesn't work.

@60hz can you tell me what you have done to change to an absolute path?
do you get the bang message in the Puredata window as intended?

@nhouse
Under OSX, I just replaced the os.system line with:

os.system("echo '" + message + "' | /Users/path_to_pure_data/PureData.app/Contents/Resources/bin/pdsend 3000")

And yes, the bang came into pd for me

@60hz it works! so that was really the issue! will try to understand the reason now (and eventually how to fix it)
thanks to both of you! @whale-av

Hi,

trying to figure this out too. Followed the same tutorial. Nothing happens.

I am on OSX 10.14.6 Mojave running Pd 0.51-4

netstat -a --->

tcp46      0      0  *.hbci                 *.*                    LISTEN     
tcp4       0      0  localhost.51108        localhost.51109        ESTABLISHED
tcp4       0      0  localhost.51109        localhost.51108        ESTABLISHED
tcp6       0      0  localhost.51108        *.*                    LISTEN     
tcp6       0      0  localhost.51108        *.*                    LISTEN     
tcp4       0      0  localhost.51108        *.*                    LISTEN     
tcp4       0      0  192.168.100.86.51101   dj-in-f95.1e100..https ESTABLISHED

Python code:

import os

#write code here

def send2Pd (message=''):
    
    # os.system("echo '" + message + "' | pdsend 3000")
    
    #quoted out above and replaced with:

    os.system("echo '" + message + "' | /Nicklas/Applications/Pd-0.51-4.app/Contents/Resources/bin/pdsend 3000")


def audioOn():
    message = '0 1;' #Id = 0 (DSP), message=1 (turn it on)
    send2Pd(message)

def setVolume():
   vol = 80 #Set volume value (0-100)
   message = '1' + str(vol) + ';' # make a string for use with psend
   send2Pd(message)

print ("send to Pd done?")

Pd code

@cfry I am seldom an OSX user........ but maybe the path should be........
/Users/Nicklas/Applications/Pd-0.51-4.app/Contents/Resources/bin/pdsend 3000
...... i.e the path from root (C:/ ?) ...... as in a previous post?
David.

@whale-av actually this is the absolute path

/Applications/Pd-0.51-4.app/Contents/Resources/bin/pdsend

that is what I get when I drag pdsend to Terminal

Is there some flag I should use in Pd?

I noticed that when I open the help patch and try it while already started my patch, Pd log window reports that [netreceive] channel is already active. So something is happening, at least.

It looks like you forgot to call your functions at then end of your script. So simply adding those lines before print make it work for me:

audioOn();
setVolume();

@cfry Yes........ your patch has made the connection....... but when you open the help patch it contains another [netreceive] with the same address........ 3000..... so the terminal tells you that the port is already open in your patch.
You can avoid that by using a different port in your patch.
David.

@60hz Well, that was easy! Thanks!