Ok, this would be a bug then. It *should* work but perhaps we need an additional flag when setting up the socket on Windows. When we did the networking handling refactoring, I'm pretty sure we tested this on Windows. What do you think Christof?
Do the multicast examples in the netsend and netrecieve help files work? For example, you start the multicast receiver in one and send to it form the other help?
On Jan 11, 2024, at 11:15 PM, pd-list-request@lists.iem.at wrote:
Message: 4 Date: Thu, 11 Jan 2024 22:15:00 +0100 From: Jo?o Pais <jmmmpais@gmail.com mailto:jmmmpais@gmail.com> Cc: Pd-List <pd-list@lists.iem.at mailto:pd-list@lists.iem.at> Subject: Re: [PD] receive UDP message from 224.0.0.1 Message-ID: <1d26753e-b344-4722-8b0d-3b86f8014d7d@gmail.com mailto:1d26753e-b344-4722-8b0d-3b86f8014d7d@gmail.com> Content-Type: text/plain; charset="utf-8"; Format="flowed"
Are you opening with the following message?
[ listen 57120?224.0.0.1 < | [ netreceive -u -b]
The address is within the multicast range, so it needs to be given to netreceive in addition to the port.
It doesn't work in windows, but it does in ubuntu - although windows is my main work system. (latest Pd version on both)
Dan Wilcox danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
When we did the networking handling refactoring, I'm pretty sure we
tested this on Windows.
Back then it did work :) But this was on Windows 7. Will test again on Windows 10.
Christof
On 12.01.2024 16:25, Dan Wilcox wrote:
Ok, this would be a bug then. It *should* work but perhaps we need an additional flag when setting up the socket on Windows. When we did the networking handling refactoring, I'm pretty sure we tested this on Windows. What do you think Christof?
Do the multicast examples in the netsend and netrecieve help files work? For example, you start the multicast receiver in one and send to it form the other help?
On Jan 11, 2024, at 11:15 PM, pd-list-request@lists.iem.at wrote:
Message: 4 Date: Thu, 11 Jan 2024 22:15:00 +0100 From: Jo?o Pais jmmmpais@gmail.com Cc: Pd-List pd-list@lists.iem.at Subject: Re: [PD] receive UDP message from 224.0.0.1 Message-ID: 1d26753e-b344-4722-8b0d-3b86f8014d7d@gmail.com Content-Type: text/plain; charset="utf-8"; Format="flowed"
Are you opening with the following message?
[ listen 57120?224.0.0.1 < | [ netreceive -u -b]
The address is within the multicast range, so it needs to be given to netreceive in addition to the port.
It doesn't work in windows, but it does in ubuntu - although windows is my main work system. (latest Pd version on both)
Dan Wilcox danomatika.com http://danomatika.com robotcowboy.com http://robotcowboy.com
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management ->https://lists.puredata.info/listinfo/pd-list
On 12/01/2024 12:56, Christof Ressi wrote:
Back then it did work :) But this was on Windows 7. Will test again on Windows 10.
for me on Pd 0.54.1 Win11 it all works as expected. I used the help patch and was able to receive from localhost or from a Linux box (sending via a Pd 0.53.1). I used the help patch with
Linux machine:
[connect 239.200.200.200 3005( | [netsend -u]
Win11 machine:
[listen 3005 239.200.200.200( | [netreceive -u -f 3005]
--
Mensaje telepatico asistido por maquinas.
I tried again with my 3 computers (all same brand and similar intel network hardware) - it seems that the problem is the windows driver that doesn't allow multicast. While ubuntu in one of them seems to.
On 12/01/2024 12:56, Christof Ressi wrote:
Back then it did work :) But this was on Windows 7. Will test again on Windows 10.
for me on Pd 0.54.1 Win11 it all works as expected. I used the help patch and was able to receive from localhost or from a Linux box (sending via a Pd 0.53.1). I used the help patch with
Linux machine:
[connect 239.200.200.200 3005( | [netsend -u]
Win11 machine:
[listen 3005 239.200.200.200( | [netreceive -u -f 3005]
On 13/01/2024 14:30, João Pais wrote:
I tried again with my 3 computers (all same brand and similar intel network hardware) - it seems that the problem is the windows driver that doesn't allow multicast. While ubuntu in one of them seems to.
also check in the firewall:
Control Panel\All Control Panel Items\Windows Defender Firewall\Allowed applications
in my case y have Pd "allowed" in both "private" and "public" networks. I'm not sure if I did a change or if this is the default setting.
--
Mensaje telepatico asistido por maquinas.
Sorry to break in, but I may be setting up some Windows Pd instances using OSC in the near future; is this something that will need to be dealt with even when not using multicast?
Phil Stone Davis, Ca
On Jan 13, 2024, at 9:41 AM, Lucas Cordiviola lucarda27@hotmail.com wrote:
On 13/01/2024 14:30, João Pais wrote:
I tried again with my 3 computers (all same brand and similar intel network hardware) - it seems that the problem is the windows driver that doesn't allow multicast. While ubuntu in one of them seems to.
also check in the firewall:
Control Panel\All Control Panel Items\Windows Defender Firewall\Allowed applicationsin my case y have Pd "allowed" in both "private" and "public" networks. I'm not sure if I did a change or if this is the default setting.
--
Mensaje telepatico asistido por maquinas.
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 13/01/2024 14:47, Phil Stone wrote:
Sorry to break in, but I may be setting up some Windows Pd instances using OSC in the near future; is this something that will need to be dealt with even when not using multicast?
there should not be much trouble. Just install Pd. Then at some point, I can't recall when if a soon as you start Pd or as soon as you start a network object, a Windows-Firewall windows will pop, just check the 2 checkboxes (private and public) networks. That's pretty much all needed to be done.
--
Mensaje telepatico asistido por maquinas.
That’s very good to know. Thank you, Lucas.
On Jan 13, 2024, at 10:01 AM, Lucas Cordiviola lucarda27@hotmail.com wrote:
On 13/01/2024 14:47, Phil Stone wrote:
Sorry to break in, but I may be setting up some Windows Pd instances using OSC in the near future; is this something that will need to be dealt with even when not using multicast?
there should not be much trouble. Just install Pd. Then at some point, I can't recall when if a soon as you start Pd or as soon as you start a network object, a Windows-Firewall windows will pop, just check the 2 checkboxes (private and public) networks. That's pretty much all needed to be done.
--
Mensaje telepatico asistido por maquinas.
Sorry to break in, but I may be setting up some Windows Pd instances using OSC in the near future; is this something that will need to be dealt with even when not using multicast?
this problem doesn't happen when not using multicast - which I never heard of before this week - but have been using OSC for many years with no issues.
But it's confirmed, the problem is with the windows driver (or the system, firewall is open or even off for testing). Using ubuntu in both laptops I can multicast either to 224.0.0.1 or to the IPs in the help patch.
-
Christof Ressi -
Dan Wilcox -
João Pais -
Lucas Cordiviola -
Phil Stone