• Products
    • Isadora
    • Get It
    • ADD-ONS
    • IzzyCast
    • Get It
  • Forum
  • Help
  • Werkstatt
  • Newsletter
  • Impressum
  • Dsgvo
  • Press
  • Isadora
  • Get It
  • ADD-ONS
  • IzzyCast
  • Get It
  • Press
  • Dsgvo
  • Impressum

Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Popular
    • Tags

    OSC listener trouble on high Sierra

    Troubleshooting and Bug Reports
    6
    15
    4157
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • bonemap
      bonemap Izzy Guru @Woland last edited by bonemap

      Hi @eight,

      @Woland said:

      @bonemap might be able to help

      Sorry, I have not installed High Sierra on any of my machines yet. I have always used the default port number for OSC into Isadora ‘1234’ and TouchOSC port number ‘9000’ - these are defaults and I have had no reason to change them.I would be checking the network settings and checking the IP addresses of each device to confirm that they are sending to the correct network ID, host and receiver IP details. The only other thing that has caught me out is the obligatory “/“ required by Isadora and any character spaces in the address strings that need to be deleted from the beginning or end of lines.

      @eight, I know you will be all over this, so you have now got me worried about moving to High Sierra!

      Regards

      Bonemap 

      http://bonemap.com | Australia
      Izzy STD 4.2 | USB 3.6 | + Beta
      MBP 16” 2019 2.4 GHz Intel i9 64GB AMD Radeon Pro 5500 8 GB 4TB SSD | 14.5 Sonoma
      Mac Studio 2023 M2 Ultra 128GB | OSX 15.3 Sequoia
      A range of deployable older Macs

      Woland 1 Reply Last reply Reply Quote 0
      • Woland
        Woland Tech Staff @bonemap last edited by

        @bonemap said:

        @eight, I know you will be all over this, so you have now got me worried about moving to High Sierra!
        Regards
        Bonemap 

        Personally, 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.

        TroikaTronix Technical Support
        New Support Ticket: https://support.troikatronix.com/support/tickets/new
        Support Policy: https://support.troikatronix.com/support/solutions/articles/13000064762
        Add-Ons: https://troikatronix.com/add-ons/ & https://troikatronix.com/add-ons/?u=woland
        Professional Services: https://support.troikatronix.com/support/solutions/articles/13000109444

        | Isadora Version: all of them | Mac Pro (Late 2013), macOS 10.14.6, 3.5GHz 6-core, 1TB SSD, 64GB RAM, Dual AMD FirePro D700s |

        1 Reply Last reply Reply Quote 0
        • Michel
          Michel Izzy Guru @Woland last edited by

          @Woland

          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.

          mark 1 Reply Last reply Reply Quote 1
          • eight
            eight last edited by eight

            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

            mark 1 Reply Last reply Reply Quote 0
            • mark
              mark @eight last edited by

              @eight

              First thing to do: trying using a destination port for Isadora other than 1234. Try 8000 for instance. See if that helps.

              Best Wishes,
              Mark

              Media Artist & Creator of Isadora
              Macintosh SE-30, 32 Mb RAM, MacOS 7.6, Dual Floppy Drives

              eight 1 Reply Last reply Reply Quote 0
              • mark
                mark @Michel last edited by

                @Michel

                Can you explain the TouchOSC problem you described above in more detail? Are the addresses wrong? Or?

                Best Wishes,
                Mark

                Media Artist & Creator of Isadora
                Macintosh SE-30, 32 Mb RAM, MacOS 7.6, Dual Floppy Drives

                Michel 1 Reply Last reply Reply Quote 0
                • eight
                  eight @mark last edited by

                  @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.

                  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

                  1 Reply Last reply Reply Quote 0
                  • Michel
                    Michel Izzy Guru @mark last edited by Michel

                    @mark

                    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

                    Michel Weber | www.filmprojekt.ch | rMBP (2019) i9, 16gig, AMD 5500M 8 GB, OS X 10.15 | located in Winterthur Switzerland.

                    1 Reply Last reply Reply Quote 0
                    • eight
                      eight last edited by

                      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 1 Reply Last reply Reply Quote 1
                      • eight
                        eight @eight last edited by

                        @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

                        DusX 1 Reply Last reply Reply Quote 1
                        • DusX
                          DusX Tech Staff @eight last edited by

                          @eight
                          Glad you got it working. Sometimes you just have to start fresh I guess.

                          Troikatronix Technical Support

                          • New Support Ticket Link: https://support.troikatronix.com/support/tickets/new
                          • My Add-ons: https://troikatronix.com/add-ons/?u=dusx
                          • Profession Services: https://support.troikatronix.com/support/solutions/articles/13000109444-professional-services

                          Running: Win 11 64bit, i7, M.2 PCIe SSD's, 32gb DDR4, nVidia GTX 4070 | located in Ontario Canada.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post