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
That’s very good to know. Thank you, Lucas.
> On Jan 13, 2024, at 10:01 AM, Lucas Cordiviola 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
>>
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
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 wrote:
>
> On 13/01/2024 14:30, João Pais
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
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
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
ast 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
Cc: Pd-List
Subject: Re: [PD] receive UDP message from 224.0.0.1
Message-ID: <1d26753e-b344-4722-8b0d-3b8
gt;>
> Cc: Pd-List 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; cha
Context: the original LANdini (custom networking protocol) implementation and
demo software was on supercollider, so used the default SC port number for the
broadcast pings. I kept that default in the MobMuPlat port in order to allow
for interop between various clients.
Sent from my iPhone
>
On 1/11/24 22:15, João Pais wrote:
It doesn't work in windows, but it does in ubuntu - although windows is
my main work system. (latest Pd version on both)
a quick check on the internet suggest that you might have to explicitely
enable multicast on Windows (not giving any links, because i
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.
However, you can check if some other program already uses port 57120!
On Windows you can do this by running "netstat -abno" in cmd.exe as Admin.
I had a look at the report, 57120 doesn't appear.
Also, have you tried with other port numbers?
This is an open source app. In order to do that
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.
> On Jan 11, 2024, at 10:34 AM, pd-list-requ...@lists.iem.at wrote:
>
> But with [netreceive
I don't use SC, but I'll check anyway if some years ago I installed it
and then forgot about it.
Ok, then this was a red herring. That's a pretty strange coincidence,
though. Anyway, sclang.exe must not only be installed, but also *running*.
However, you can check if some other program already
I don't use SC, but I'll check anyway if some years ago I installed it and
then forgot about it.
It is a multicast address - I might be able to change it to the normal
broadcast address, but I wouldn't count on it. So for now, it's better to
assume that this can't be changed.
Hmmm... 57120
Hmmm... 57120 happens to be the default port of sclang (the
SuperCollider language interpreter). Could it be that sclang(.exe) is
running? Check the task manager to be sure.
Explanation: Generally, only one application can listen to a port at a
time. Normally, applications will just refuse to
Hi everyone,
I'm trying to receive some UDP data from a mobile device into Pd. The
data arrives in the computer (windows or ubuntu), here is a description
from wireshark:
Frame 173: 90 bytes on wire (720 bits), 90 bytes captured (720 bits) on
interface
18 matches
Mail list logo
