Why are my changes to the NDI JSON configuration file not being saved?

NDI settings on a PC are stored to a single JSON file- this file includes information such as Send/Receive groups, multicast settings, and external network devices that are not in the same subnet, including more. This config file is accessed at the when most NDI programs start up. Typically, most of the settings are accessible within Access Manager, but an advanced user can edit the JSON file directly, such as deploying the same settings to multiple users at once. Sometimes, a user can launch NDI Access Manager and seemingly revert the changes that are made. The most likely reason is that Access Manager includes a linter, so if a syntax is incorrect such as a misplaced comma, it will erase the offending lines instead of presenting an error.

Currently, Access Manager will rewrite manually updated config files if they are entered incorrectly. The following is an example of valid JSON in the NDI configuration file:

{
  "ndi": {
    "machinename": "",
    "tcp": {
      "recv": {
        "enable": true
      }
    },
    "rudp": {
      "recv": {
        "enable": true
      }
    },
    "groups": {
      "send": "Public",
      "recv": "Public"
    },
    "unicast": {
      "recv": {
        "enable": true
      }
    },
    "networks": {
      "ips": "192.168.1.92,",
      "discovery": ""
    },
    "adapters": {
      "allowed": []
    },
    "multicast": {
      "send": {
        "ttl": 1,
        "enable": false,
        "netmask": "255.255.0.0",
        "netprefix": "239.255.0.0"
      }
    }
  }
}

Common syntax errors that can invalidate JSON include missing comma delimiters, incorrect string quote delimiters, and unbalanced braces, among others. Consider using a JSON linter to confirm that your proposed JSON changes are valid.

We've recognized in the documentation that this may not clear to everybody, so we're correcting that to make it more apparent that proper syntax is needed.