Skip to content

Saving Your Configuration

Configurations save as JSON files with .nipc extension (Nipper Configuration).

.nipc files contain:

  • Configuration name
  • Author name
  • All audio sources (all types)
  • All video destinations
  • Assignment mappings
  • Group definitions (video groups and audio groups)
  • Buzz Out verification results
  • Timestamps (created, modified)
  • Version number (for future compatibility)

Human-readable JSON structure.
Can be opened in text editor for inspection (not recommended for editing).

Creating a configuration:

Menu → File → New

Nipper prompts for configuration name.

Enter descriptive name (e.g., “OB Truck 3 - Tennis Tournament”).
Default author name populates automatically if you’ve set one via Menu → File → Edit Author.

Configuration unsaved until first save operation.

Menu → File → Save
Keyboard shortcut: Cmd+S / Ctrl+S

If file path known:
Saves immediately to existing location.
Status bar updates with “Saved” confirmation.

If new configuration:
File picker opens.
Choose location and confirm filename.
Defaults to configuration name with .nipc extension.

Requires license.

Without license, opens License Manager.

[Screenshot: Save dialog showing file picker with .nipc file type filter]

Menu → File → Save As
Keyboard shortcut: Cmd+Shift+S / Ctrl+Shift+S

Always prompts for new location.

Use when:

  • Creating configuration variant
  • Saving copy for backup
  • Renaming file

Subsequent saves use the new path.

Requires license.

The status bar shows your unsaved state. No indicator means everything’s saved with no changes, while ⚠ Unsaved (amber/orange) means you’ve made changes since the last save.

Quit application with unsaved changes triggers confirmation:

“Configuration has unsaved changes. Save before quitting?”

[Save] [Don’t Save] [Cancel]

Go to Menu → File → Recent Files to see your last 10 opened configurations. Click any filename to open it. Recent files persist across application restarts and are stored in application settings.

Menu → Edit → Rename Configuration changes the configuration name that’s displayed in the UI and exports. Note that this doesn’t rename the file on disk - use Save As if you want to change the filename. Nipper prompts you to save after renaming since the configuration file must update.

Configurations can save anywhere on your filesystem. Typical locations include your user Documents folder, project-specific directories, network shares (for team access), or cloud storage folders (Dropbox, OneDrive, etc.). There’s no restriction on file location, and files are portable across computers since all data is self-contained in the .nipc file.