Possible Bug on Big Sur

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • (@)

    I spent this morning unsuccessfully attempting to connect to a student running the Big Sur OS on a 2017 Intel Macbook. Even with port forwarding configured, the stage was having difficulty recognizing the Soundjack program running on her laptop. Her local firewall was disabled, and there did not seem to be anything on her router that would block communication. On the few occasions that the program was recognized, Soundjack would crash upon attempting to send her a connection invite.

    Has anyone else experienced a similar issue? Could this be a compatibility issue with Big Sur, or is there something else I am missing? Any insight would be greatly appreciated.

    Anonymous
    (@)

    I have had no problems running Soundjack (using Firefox) on a 2017 iMac with Big Sur (11.2). My understanding is that you cannot use Safari, though I have no idea what the symptoms/problems are.

    Not much help …

    (@)

    Alex needed to use a HTML feature that is not supported by Safari, so Safari is no longer a useable web browser for SoundJack. Use Firefox, Chrome, (ungoogled) Chromium, Edge or some other current browser that is based on Firefox or Chrom(ium).

    (@)

    Apologies, I should have mentioned that she was using Chrome.

    (@)

    OK, so it’s not the browser (unless it is rather old and not updated).
    Why are you sure that the port forwarding works?
    The only thing where you can see that it works is the three digit code in parentheses after the UDP2 value when pointing on your own or your partners name. Please check and post the numbers of you and your student here.

    Please note that if you have WLAN enabled and a LAN cable connected, the preselected IP-address at the stage is always the smallest. If this is the WLAN-address, the port forwarding might be correctly set at the router, but usually for the LAN-IP-address which is not used then. In that case the three digit number will show that the port forwarding does not work (middle digit is 8 then).

    A second reason why it might not work is when the computer’s IP-address is not fixed to the port forwarding IP-address.
    The fixing could be done at the router (binding the IP-address to the computer’s network interface MAC-address, which is usually represented by the computer name as given to the operating system) or by using a static IP-address (usually leads to problems in other networks, so use only on LAN-interface and be sure this number is outside the DHCP address range (which is usually defined at your router). DHCP usually gives a new IP-address after a while of not using the interface (happens mostly on the less used LAN-interface), so it might work in the beginning but not later. But the three digit number tell you if it works or not.

    If it is a two participants communication only, only one needs to have full connectivity with a port forwarding. So one of you (preferably you as you are the teacher and it only needs to be done once), should have a 1 or 2 as the second digit. If not, you should check your port forwarding and correct it. In that case all students regardless of any port forwarding on their side should be able to connect to you. So, what is your 3-digit number?

    You might also try to check what happens if you accept all incoming connections (for a short while during the student connecting). Does a connection get established then? If it works then, you can go back to the asking for a connection attempt setting.

    Anonymous
    (@)

    I got a new MBP with Big Sur.

    My problem is that the PreSonus interface is not recognized by OSX.
    That’s probably because it is going thru a Satechi port box.
    (The port box works pretty well otherwise.)
    The Satechi is necessary because Apple in its infinite wisdom
    took away each and every port in the MBP and replaced them all
    by not 1 not 2 not 3 but 4 USB-C ports; no card reader no hdmi
    no thunderbolt and certainly no USB-A.

    Not specifically a Soundjack problem, and probably not Big Sur- caused,
    but might affect other Big Sur users.
    Meanwhile, I’m keeping the old MBP for now.

    (@)

    I hope someone else can help you with that. My personal experience ends with MacOS 10.14 on intel-based Macs.

    Since it might not be Big-Sur-related, you might better open a new topic ponting to the use of your Satechi port box.
    In your problem description you should mention that you use Big Sur with that box and you need it.

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.