OSC listener trouble on high Sierra
-
@bonemap said:
@eight, I know you will be all over this, so you have now got me worried about moving to High Sierra!
Regards
BonemapPersonally, this is one of the reasons why I only ever update my OS to the second most recent iteration. It allows me to never have to deal with issues caused by the OS when it's new(ish), and then by the time I do update to it, its been around so long that people have generally worked out all the kinks and quirks.
-
The problem why Touch OSC does not update values Isadora is sending, is a touch OSC problem. A workaround is to change the automatic generated OSC adresses to manual. You can even use the same as the automatic generated one, but it will work now.
Best Michel
Michel Weber | www.filmprojekt.ch | rMBP (2019) i9, 16gig, AMD 5500M 8 GB, OS X 10.15 | located in Winterthur Switzerland.
-
Somebody wrote to me privately that my setup works fully on High Sierra, so that suspect is off the hook. I am looking at blocked ports using this approach, but am not finding anything blocking my ports yet.
Analysis: http://post.scriptum.ru | Synthesis: http://onewaytheater.us
Twitter: https://twitter.com/eight_io | Flickr: http://www.flickr.com/photos/eight_io/
Github: https://github.com/eighteight | MulchCam: https//mulchcam.com
MulchTune: https://itunes.apple.com/us/app/mulch-tune/id1070973465 | Augmented Theatre: https://augmentedtheatre.com -
First thing to do: trying using a destination port for Isadora other than 1234. Try 8000 for instance. See if that helps.
Best Wishes,
MarkMedia Artist & Creator of Isadora
Macintosh SE-30, 32 Mb RAM, MacOS 7.6, Dual Floppy Drives -
Can you explain the TouchOSC problem you described above in more detail? Are the addresses wrong? Or?
Best Wishes,
MarkMedia Artist & Creator of Isadora
Macintosh SE-30, 32 Mb RAM, MacOS 7.6, Dual Floppy Drives -
@mark I have never used the port 1234. Instead I tried 3000, 3001, 10000 and 10001
and just tried 8000 -- never got the signals on the computer from the phone.
-
In TouchOSC by default the adressing of buttons or "led's" are set to automatic. This works fine if I use touch OSC to control Isadora, but if I send a value from Isadora to touch OSC to the adress that touch OSC generated automatically, touch OSC does not receive the value. If I deselect "automatic" (I then have to type the address again because touch OSC clears the address field) and type exactly the same address as touch OSC did before it finally works. In the picture below the function is that Isadora labels the buttons automatically with the movie, picture or sound file name, depending what one you have selected on the right. And on the right bottom you see a countdown in seconds how long the movie or audio file will play.
Best Michel
-
More results of this investigation (apologies for verbosity level, but I think this maybe useful for somebody else, trying to debug a similar problem):
1. See the state of the udp port 3001 on local machine 192.168.1.34 in question:
eight_io-MacBook-Pro:~ eight_io$ sudo nmap -sU -p 3001 192.168.1.34
Password:
Starting Nmap 7.60 ( https://nmap.org ) at 2017-10-29 19:54 MSK
Nmap scan report for 192.168.1.34
Host is up.
PORT STATE SERVICE
3001/udp open|filtered unknown
Nmap done: 1 IP address (1 host up) scanned in 2.42 seconds
eight_io-MacBook-Pro:~ eight_io$
It seems that 3001 is open, but filtered, perhaps by a firewall -- it's inconclusive message, meaning more digging must be done
Here goes more digging:
On problematic machine, run the following
sudo tcpdump -A 'udp and port 3001'
and then send the osc message to the latter machine. Once the messages start being sent I get the following output of the tcpdump locally:
eight_io-MacBook-Pro:~ eight_io$ sudo tcpdump -A 'udp and port 3001'
tcpdump: data link type PKTAP
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on pktap, link-type PKTAP (Apple DLT_PKTAP), capture size 262144 bytes
19:46:26.404641 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 84
..............E..p....@......$....'....\../location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:27.326753 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 84
..............E..p....@......$....'....\../location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:29.271750 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 84
..............E..pz...@.=....$....'....\../location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:30.297793 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 84
..............E..p'|..@..5...$....'....\../location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:31.217488 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 84
..............E..p....@......$....'....\../location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:32.242078 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 84
..............E..p....@......$....'....\../location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:33.265481 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 84
..............E..p....@.+'...$....'....\../location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:33.982378 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 92
..............E..x....@......$....'....d../devicestate/1..,sss....background..8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:34.187973 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 84
..............E..p:B..@.~o...$....'....\../location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:35.211226 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 84
..............E..p#(..@......$....'....\../location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:36.235224 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 84
..............E..p....@......$....'....\../location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:37.259201 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 84
..............E..p.;..@..u...$....'....\../location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:38.283181 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 84
..............E..p....@......$....'....\../location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:39.307169 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 84
..............E..p....@......$....'....\../location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:40.229788 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 84
..............E..pkr..@.M?...$....'....\../location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:41.256772 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 84
..............E..pL...@.l....$....'....\../location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:42.174611 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 92
..............E..xqq..@.G8...$....'....d../devicestate/1..,sss....foreground..8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:43.301371 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 84
..............E..p.1..@......$....'....\../location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:44.251092 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 84
..............E..p....@..!...$....'....\../location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
19:46:45.348958 IP 192.168.1.36.ndmp > broadcasthost.redwood-broker: UDP, length 84
..............E..p....@......$....'....\../location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36....
^C
20 packets captured
47 packets received by filter
0 packets dropped by kernel
/location/1.,sss....NONE....8508E811-8FC5-4D73-9B73-994EBB74B865....192.168.1.36 corresponds exactly to the OSC message sent by iphone, which contains three values: a string "NONE", a string "8508E811-8FC5-4D73-9B73-994EBB74B865" and device's IP address 192.168.1.36
Analysis: http://post.scriptum.ru | Synthesis: http://onewaytheater.us
Twitter: https://twitter.com/eight_io | Flickr: http://www.flickr.com/photos/eight_io/
Github: https://github.com/eighteight | MulchCam: https//mulchcam.com
MulchTune: https://itunes.apple.com/us/app/mulch-tune/id1070973465 | Augmented Theatre: https://augmentedtheatre.com -
@eight OK, in view of the approaching tech, after trying to set iptables, debugging using different unix tools, I reformatted my macbook pro, and now everything works. Still have no idea what happened.
Analysis: http://post.scriptum.ru | Synthesis: http://onewaytheater.us
Twitter: https://twitter.com/eight_io | Flickr: http://www.flickr.com/photos/eight_io/
Github: https://github.com/eighteight | MulchCam: https//mulchcam.com
MulchTune: https://itunes.apple.com/us/app/mulch-tune/id1070973465 | Augmented Theatre: https://augmentedtheatre.com -
@eight
Glad you got it working. Sometimes you just have to start fresh I guess.
