On OSX using Compannion and Streamdeck to send OSC to GP. Works great but I have issues where the Gig Performer IP address changes. This has happened within an evening while having GP open the entire time.
Is also goes missing sometimes, where OSC stops working and there is no GP IP address in OSC.
Can this not be statically assigned?
Gig Performer uses the IP address that your system provides.
Did you assign a static IP address on your system?
here in lies the problem… If I am performing in a show ready situation, I am not connected to any network, I just want to run locally. with no network connected, OSX does not seem to be able to park itself at any address because there is no adapter active… unless I am overlooking something.
I have lots of configured adapters that are not connected that have static IPs. My WIFI network changes if I am at home, reharsal or gig (where it’s off) so it’s dynamic as a requirement.
Companion always references the local host IP, so 127.0.0.1:8000. It doesn’t need an active network.
Thoughts?
Please create a screenshot of your GP OSC options.
I’m curious what addresses Gig Performer takes. (Can you list a couple of recent IP addresses)
Gig Performer IP address is blank? Is it always blank?
yes, if I have no network connected, it is blank
compannion always has an IP regardless.
How could it have an IP allocated if you have no adapter?
On Windows you can install a dummy loopback adapter so there’s always something there. I’m sure something like that exists on OSX as well.
A possible idea:
–
macOS supports virtual interfaces that never disappear.
You can create a permanent loopback alias.
Example:
sudo ifconfig lo0 alias 10.10.10.1
Then point GP and Companion to:
10.10.10.1
This survives with:
because lo0 is always active.
Maybe you can experiment with this.
on windows I can have a nic that just isn’t plugged into something and it’s still a network the computer can see. On OSX this doesn’t seem to be the case.
Could GP reference 127.0.0.1?
I’ll look into that thanks
Take a small wlan Router, configure dhcp reservation for your devices. And if possible do not provide a Gateway adress, then These devices do not have Internet Access and always the get the same ip adresses…
Setting the alias in command line did create the conditions for a ‘staticly’ assigned IP address sans-network adapter present. However if a network is connected, this stops being the IP selected and it shifts to another randonly assigned IP address from the new host network (well… random if that is DHCP).
AI tips.
When you assign an IP alias to an interface (like en0) via the command line using ifconfig, it works fine while disconnected. But the moment you plug in a cable or connect to Wi-Fi, the macOS network subsystem (managed by configd) kicks in, runs a DHCP request, and overrides or suppresses that alias in favor of the new lease.
To make a static IP truly “stick” on macOS—whether you are connected to a network or not—you have two main approaches.
[1] Method 1: The GUI Way (Create a Dedicated “Location”)
The cleanest way to handle this without fighting the macOS network daemon is to create a specific network Location. This allows you to switch between your “Isolated Static IP” setup and “Normal DHCP” setup with two clicks.
Go to System Settings > Network.
Click the Action menu (three dots icon at the bottom) and select Locations > Edit Locations….
Click the + icon, name it something like Static IP Solo, and click Done.
Select your network adapter (e.g., Wi-Fi or Ethernet), click Details…, and go to the TCP/IP tab.
Change Configure IPv4 from “Using DHCP” to Manually.
Enter your desired IP address and Subnet Mask (you can leave the Router blank if you aren’t connecting to the internet). Click OK and then Apply.
Why this works: When you need your static IP environment, just switch to the Static IP Sololocation. When you plug into a live network and want standard internet access, switch back to your Automatic location.
[2] Method 2: The Loopback Adapter (Best for “Sans-Network”)
If your goal is to have a permanent, static IP address that is always available on the machine—even if every network adapter is turned off or plugged into DHCP—you shouldn’t bind it to a physical adapter like en0 or en1. You should bind it to the loopback interface (lo0).
The loopback interface is entirely virtual and never goes down.
Bash
sudo ifconfig lo0 alias 192.168.99.99 netmask 255.255.255.255
(Note: Using a 255.255.255.255 subnet mask for a loopback alias prevents it from interfering with physical networks).
launchd:Because macOS clears ifconfig aliases on reboot, you can create a lightweight persistent daemon to apply it at boot.
Create a file named org.custom.staticip.plist in /Library/LaunchDaemons/:
XML
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Aple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>org.custom.staticip</string>
<key>ProgramArguments</key>
<array>
<string>/sbin/ifconfig</string>
<string>lo0</string>
<string>alias</string>
<string>192.168.99.99</string>
<string>netmask</string>
<string>255.255.255.255</string>
</array>
<key>RunAtLoad</key>
<true/>
</dict>
</plist>
(Replace 192.168.99.99 with your desired IP).
Then, set the correct permissions and load it:
Bash
sudo chown root:wheel /Library/LaunchDaemons/org.custom.staticip.plist
sudo launchctl load /Library/LaunchDaemons/org.custom.staticip.plist
Now, that IP address will live permanently on your Mac. It will respond to local services regardless of whether you are on Wi-Fi, Ethernet, or completely offline.