yes, if the websever is not working on the PC (but you can get it working on others) , then that does indicate a network issue.
it could just be a naming issue though,
if go to the organelle and type (which wifi is up… just assume this during his thread of conversation ;))
you will see the IP address of the wireless lan
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.94 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::800b:8576:6d16:a93 prefixlen 64 scopeid 0x20<link>
inet6 fe80::20f:60ff:fe03:a3aa prefixlen 64 scopeid 0x20<link>
ether 00:0f:60:03:a3:aa txqueuelen 1000 (Ethernet)
RX packets 19864 bytes 27540227 (26.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 19868 bytes 2950753 (2.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
here you can see it on line 2
ok, so try that on your PC.
PC… cool, yup that looks like all the externals needed
procedure sounds about right.
a) have oscpoxy running on both you PC and on Organelle (configured as discussed above)
b) then start PD on windows and open mother.pd
c) check the PD console logs, to see no externals are failing to load, or missing
d) now load main.pd from same PD instance, and again, (choose a simple patch, e.g. C&G basic poly!)
e) check the PD console logs, to see no externals are failing to load, or missing
when you start the patch…
a) do you get the patch text on the Organelle?
if not, then OscProxy on the desktop (PC) is not working , since OSC messages are not getting from the patch running on your desktop TO the Organelle (which is what OscProxy running on the desktop does)
the most likely cause of this, is you have the wrong hostname/ip address configured for the organelle on the desktop
test by using ping on the desktop to your organelle
b) wiggle the knobs on the organelle, do the knobs slider on mother.pd move?
if not, then OscProxy on the ORGANELLE is not working , since OSC messages are not getting from ‘mother host’ running on the Organelle TO the desktop (which is what the OscProxy running on the Organelle does)
the most likely cause of this, is you have the wrong hostname/ip address configured for the desktop on the organelle
test by using ping on the organelle to your desktop
generally using IP addresses causes less hassle (as the name service doesn’t get involved), but if your using DHCP then you might have to check your IP address (of both Organelle and desktop) does not change.
so Id get it working using IP addresses, then once your familiar with the ‘workflow’ you can try using the hostname on each.
the only other cause of issues, is if you have some kind of firewall setup, blocking UDP ports 4000 or 4001, this should not normally be the case, as this is all done on the local network.
(but who knows what whacky settings some have on their networks )
Im pretty sure I tested this on windows, but honestly it was a while back… so can’t remember for sure.
however, the OscProxy is very simple, so no reason for it not to work…
(and I generally do quite a bit of network dev, without issue on windows)