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-requ...@lists.iem.at wrote: > > Message: 4 > Date: Thu, 11 Jan 2024 22:15:00 +0100 > From: Jo?o Pais <jmmmp...@gmail.com <mailto:jmmmp...@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-3b86f8014...@gmail.com > <mailto:1d26753e-b344-4722-8b0d-3b86f8014...@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
