> 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


_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list