Hardware Troubleshooting
Fix common hardware issues in Spectralite
Hardware Troubleshooting
Solutions for common hardware problems.
Art-Net Issues
Nodes Not Discovered
Symptoms: Art-Net node doesn't appear in Discovered Clients
Solutions:
- Check physical connection - Verify cables are connected and link lights are on
- Verify same subnet - Mac and node must be on same network range
- Check IP configuration - Both should use static IPs in same subnet
- Disable firewall temporarily - macOS firewall may block Art-Net
- Try direct connection - Connect Mac directly to node (no switch)
To check your network:
# In Terminal
ifconfig en0 # or en1 for different interface
ping [node-ip-address]No DMX Output
Symptoms: Node is discovered but fixtures don't respond
Solutions:
- Verify universe configuration - Node and Spectralite must match
- Check fixture addresses - Confirm DMX addresses are correct
- Enable output - Ensure output is enabled in Spectralite
- Test node - Use node's built-in test function
- Check DMX cables - Try known-working cables
- Verify fixture mode - Fixture must be in DMX mode
Flickering or Glitches
Symptoms: Output is unstable, flickering, or random
Solutions:
- Check for IP conflicts - Each device needs unique IP
- Reduce network congestion - Use dedicated lighting network
- Verify cable quality - Use Cat5e or better
- Check node capacity - Some nodes can't handle high refresh rates
- Monitor bandwidth - Large pixel counts need gigabit
MIDI Issues
Controller Not Detected
Symptoms: MIDI device doesn't appear in MIDI Devices panel
Solutions:
- Check USB connection - Try different port
- Power cycle controller - Turn off, wait, turn on
- Check in Audio MIDI Setup - System should see the device
- Try different USB cable - Some cables are charge-only
- Restart Spectralite - Sometimes needed after connecting
Controls Not Responding
Symptoms: Moving controls doesn't affect Spectralite
Solutions:
- Enable the device - Check the enable box in MIDI Devices
- Check MIDI channel - Verify channel settings match
- Verify mapping exists - Check MIDI Map Editor
- Use MIDI monitor - Verify messages are being received
- Check controller mode - Some have multiple modes
Wrong Values
Symptoms: Controls behave unexpectedly (jumping, reversed)
Solutions:
- Check mapping mode - Use Relative for encoders
- Verify range settings - Input and output ranges correct
- Check for duplicate mappings - Same CC mapped twice
- Calibrate controller - Some need calibration
Preview Issues
Black Preview
Symptoms: Preview panel shows nothing
Solutions:
- Check fixture addresses - Fixtures need valid patches
- Verify layer is enabled - Check layer visibility
- Check effect output - Effect must connect to output node
- Enable preview in settings - May be disabled
Slow Preview
Symptoms: Preview is laggy or stuttering
Solutions:
- Reduce preview quality - In Settings > Display
- Simplify effects - Complex node graphs need more power
- Close other applications - Free up GPU resources
- Check GPU capabilities - Older GPUs may struggle
Performance Issues
High CPU Usage
Symptoms: Mac runs hot, fans spin up
Solutions:
- Reduce effect complexity - Fewer nodes = less CPU
- Lower preview quality - Reduce rendering load
- Disable unused features - Turn off what you're not using
- Update Spectralite - Performance improvements in updates
Memory Issues
Symptoms: Spectralite slows down over time
Solutions:
- Restart Spectralite periodically - For long sessions
- Close unused projects - Free up memory
- Reduce history size - In Settings > General
- Check for memory leaks - Report to support if persistent
Network Issues
Packet Loss
Symptoms: Intermittent output, missing updates
Solutions:
- Use wired Ethernet - Never WiFi for Art-Net
- Check cable runs - Max 100m per segment
- Use quality switches - Managed switches recommended
- Reduce universe count - If bandwidth limited
Latency
Symptoms: Noticeable delay between action and output
Solutions:
- Check network path - Minimize hops
- Use gigabit equipment - 100Mbps may bottleneck
- Reduce preview quality - Frees processing
- Check node buffering - Some nodes add latency
Buffer Space Errors (Large Installations)
Symptoms: When using very large pixel counts, you may experience:
- Fixtures not responding or freezing
- Dropped frames causing stuttering or flickering
- Some fixtures working while others don't update
- Output working briefly then stopping
This typically occurs with more than 7,500 universes on macOS. On Linux, the threshold varies by distribution—some have conservative defaults that may cause issues at lower universe counts.
Cause: The operating system's UDP socket buffer may not be large enough to send all Art-Net data at once. Spectralite automatically tries to increase the buffer size, but is limited by OS-level maximums.
Solutions:
macOS
Check current limit:
sysctl kern.ipc.maxsockbufIncrease temporarily (until reboot):
sudo sysctl -w kern.ipc.maxsockbuf=20971520Make permanent by adding to /etc/sysctl.conf:
kern.ipc.maxsockbuf=20971520Linux
Check current limit:
sysctl net.core.wmem_maxIncrease temporarily (until reboot):
sudo sysctl -w net.core.wmem_max=20971520Make permanent by adding to /etc/sysctl.conf:
net.core.wmem_max=20971520Then run sudo sysctl -p to apply.
Recommended buffer sizes:
| Universe Count | Minimum Buffer |
|---|---|
| Up to 2,000 | 1.1 MB |
| Up to 8,000 | 4.3 MB (macOS default is usually sufficient) |
| Up to 32,000 | 17 MB |
The value 20971520 (20 MB) shown above covers up to 32,000 universes.
Still Having Problems?
Gather Information
Before contacting support:
- Note your macOS version
- Note Spectralite version
- Describe hardware in use
- List steps to reproduce
- Include any error messages
Get Help
- Check the community forums
- Contact support
- Include the information gathered above