Tips & Best Practices

Organization Strategies

Use consistent naming conventions:

• Video sources: Function-based naming works well (EVS 1, Camera ISO 3, Graphics Feed)
• Audio sources: Source-based naming (Desk Mic 1, Ambient L/R, Commentary Feed)

Future you will thank present you for clear naming.

Group things logically:

• Video groups by equipment type or purpose
• Audio groups by location or function

Add descriptions liberally:

• Document signal paths: “Rack 3 → Patchbay A12”
• Note special requirements: “Requires phantom power”
• Identify talent: “Lavalier on Host B”

Descriptions show up everywhere - tooltips, exports, verification screens. They’re worth the effort.

Common Workflows

Standard project setup sequence:

1. Add all audio sources (bulk operations for full MADI/Dante groups)
2. Add video destinations (specify correct embedded capacity)
3. Create video groups for organization
4. Assign audio to video (drag and drop)
5. Run Routing Check to verify
6. Add descriptions to ambiguous channels
7. Save configuration
8. Perform Buzz Out verification on site
9. Export HTML documentation for crew
10. Save final verified configuration

Template workflow:

Create base configuration with standard routing.
Export as CSV.
Modify CSV for project-specific variations.
Import CSV into new configuration.
Adjust unique elements.

Saves time on recurring event types.

Configuration Examples

Live sports production:

• Audio: Commentary, ambient mics, referee mics, effects
• Video: ISO cameras, EVS slow-motion, program feed, graphics
• Groups: Cameras, EVS machines, talent audio, effects audio
• Buzz Out critical: Verify all commentary feeds before event

Multi-camera recording:

• Audio: Camera-mounted shotguns, boom mics, wireless lavs, room tone
• Video: Camera ISO feeds (one per camera)
• Groups: Camera audio, wireless mics, atmosphere
• Matrix View helpful: See all cameras receiving correct audio at a glance

Studio recording session:

• Audio: Multitrack from mixing desk (MADI or Dante)
• Video: Multiple recorders for redundancy, program monitor feed
• Groups: Instruments, vocals, ambience
• Descriptions essential: Document which audio channel represents which instrument/performer

Naming Conventions

Video sources:

Format: [Equipment Type] [Number] [Variant]

Examples:

• SDI 1, SDI 2, …, SDI 16
• EVS 1 Left, EVS 1 Right
• Camera ISO 3
• Graphics Out A

Audio sources:

Format: [Source Type] [Location/Talent] [Detail]

Examples:

• MADI 1.01 L (if channel function unknown)
• Desk Mic Host A (if function known)
• Camera 3 Shotgun
• Ambient L/R

Groups:

Format: [Function] [Number if multiple]

Examples:

• EVS Machines
• Camera Audio
• Talent Wireless 1
• Effects Sends

Backup Strategy

Save often:

Use Save As to create timestamped variants throughout the day:

• Project Name 2026-02-15.nipc
• Project Name 2026-02-15 v2.nipc

Hard drives fail. This is not paranoia.

Version control:

If you’re working with a team, store .nipc files in version control (Git works great).
The JSON format diffs cleanly, so you can see exactly what changed.

Export as backup:

Export a JSON copy alongside your .nipc file.
If the .nipc file gets corrupted somehow, the JSON preserves all your data.

Documentation Workflow

For crew distribution:

1. Complete configuration
2. Perform Buzz Out verification
3. Export HTML
4. Open in browser, print to PDF
5. Distribute PDF to all crew members

Single file contains all routing information.
No software required to view.

For archival:

Save .nipc file plus HTML export.
.nipc allows future editing if routing changes.
HTML provides human-readable record even if Nipper unavailable in future.

---