LightShark controllers promise a streamlined workflow: browser-based control, compact hardware, and a shorter learning curve than a full-size desk. Yet most setup problems start before a single fixture is patched. A rushed network config, a missing patch backup, or a mismatched DMX profile can turn a quick install into a troubleshooting session.
Get the network right, lock down your patch process, and check compatibility before you walk onto site. These six setup mistakes appear on production sites regularly, and every one is avoidable when you know where the trap is.
Key Takeaways
- Set a static IP before walking onto site - DHCP churn causes intermittent control loss
- Save and export the patch file after every programming session
- Confirm each fixture's exact DMX profile before patching - generic modes drop features
- Put nodes and hubs on dedicated network segments to avoid broadcast storms
- Label each DMX line at the controller and at the fixture end before striking
- Run a fixture check before show time - not during the dress rehearsal
Skipping a Static IP and Hoping DHCP Holds
Dynamic IP assignment works well enough for a laptop at home. On a production network with multiple LightShark devices, DMX nodes, and wireless access points, DHCP lease changes drop control mid-show.
A router reboot, a lease expiry, or another device claiming the same address puts your controller offline. The fix takes seconds during load-in and costs hours during a live event.
Assign a static IP to every LightShark controller, node, and network device. Use a reserved block outside your DHCP pool so no automatic lease collides. Document the IP scheme in your patch notes so the next operator knows what lives where.
When you're controlling across subnets, check that your router forwards multicast traffic. Some consumer-grade routers block it by default, and your LS Node sitting in a different VLAN won't respond.
Patching Fixtures Without Confirming the DMX Profile
Every moving head and LED wash publishes multiple DMX modes: basic channel counts, standard modes, extended with effects, or fuller options with individual pixel control. Pick the wrong one and some of your features disappear.
A common trap: patching a fixture in a simplified mode because it's first in the menu, then wondering why the zoom and prism controls do nothing. The fixture obeys the channels defined by that mode and ignores everything else you send.
Check the fixture's control panel or menu screen before you patch. Write down the exact mode name and channel count. Then match it character-for-character in the LightShark fixture library. If the profile doesn't exist, request it from StageKraft or build a custom personality using the manufacturer's DMX chart.
When you're working with pixel fixtures, double-check whether the profile treats each cell as a separate fixture or maps them as a single multi-channel unit. Get this wrong and your pixel effects will stack on the first segment and leave the rest dark.
Running Every Device on One Flat Network
Small installs work fine with everything on a single switch. Scale up to multiple DMX universes, add wireless control, and mix in video streaming or AV integration, and your network becomes a broadcast storm waiting to happen.
Every Art-Net or sACN packet hits every device on the network. Multiply that by many fixtures refreshing at high rates and you've saturated a network link before the show starts. Control latency climbs, faders lag, and cues miss their mark.
Segment your network. Put DMX nodes and LightShark controllers on a dedicated VLAN or subnet. Keep wireless tablets and control surfaces on a separate segment with QoS priority. Use a managed switch and throttle multicast traffic so your lighting data doesn't compete with file transfers or video streams.
If you're adding wireless DMX into the chain, isolate it from the wired network unless you need both paths live. Running parallel control without proper network discipline creates timing conflicts and ghost commands.
| Network Issue | Symptom | Fix |
|---|---|---|
| Broadcast storm | Sluggish fader response, dropped cues | Segment DMX nodes onto a dedicated VLAN |
| DHCP lease change | Controller offline mid-show | Assign static IPs outside DHCP pool |
| Multicast blocked | Nodes invisible to controller | Enable IGMP snooping on managed switch |
| QoS not set | Control lag when video or file transfer runs | Prioritise DMX traffic in switch QoS settings |
Forgetting to Back Up the Patch File
You spend considerable time patching many fixtures, building groups, and programming focus positions. Then the browser crashes, the tablet runs flat, or a power glitch resets the session. Everything goes back to an empty show file.
LightShark stores show data locally, but it won't survive a factory reset or a corrupted file. The system doesn't auto-save to the cloud, so unless you've exported the file yourself, it's gone.
After every significant programming session, export the show file to a USB stick or network share. Name it with the date and session number so you can roll back if a later change breaks something. Keep at least two backups in separate locations.
When you're touring, carry the show file on multiple devices: your main controller, a backup tablet, and a USB stick in a different case. Gear gets stolen, dropped, or left behind. A show file stored in one place is a single point of failure.
Leaving DMX Cables and Universes Unlabelled
A touring rig with multiple DMX universes, multiple moving head lights, many LED pars, and several atmospheric units generates a nest of identical five-pin cables. Label nothing and you'll spend the first part of every load-in tracing lines with a multimeter.
Label every DMX cable at both ends. Write the universe number and a sequential ID so you know which line feeds which fixture cluster. Use adhesive labels or heat-shrink sleeves that survive being coiled, dragged, and stepped on.
At the controller end, label each output port with the universe and the fixture group it controls. Write it on tape and stick it to the rack or the node casing. When you're troubleshooting a dead universe late at night, you shouldn't need to open the patch file to find out which port goes where.
If you're running nodes at front-of-house and dimmer beach, document the physical path of every data line. A cable map saves hours when a stagehand unplugs the wrong link or a support act brings their own rig and needs to tap into your infrastructure.
Waiting Until Dress Rehearsal to Test Fixtures
You finish the patch, close the controller, and assume everything works because the DMX indicator lights are green. Then the first cue fires during rehearsal and some fixtures sit dark or strobing at full intensity.
Run a full fixture check the moment patching is done. Step through every unit, confirm it responds to intensity, colour, pan, tilt, and any effects channels. If a fixture doesn't respond, check the DMX mode, the start address, and the cable termination before you move on.
For complex rigs, build a test cue that cycles every fixture through a standard sequence: full white, primary colours, slow movement, then blackout. Run it after every programming session and before every show. A fixture that worked yesterday can fail overnight, and you want to know about it before the client arrives.
When you find a fault, isolate whether it's the fixture, the cable, the node, or the patch. Swap the DMX line to a known working fixture. If the problem follows the cable, replace it. If it stays with the fixture, check the address, mode, and power supply. Document every fault and the fix so the next crew doesn't repeat the same diagnostic.
Professional lighting demand continues to grow in Australia as more venues, productions, and installations require reliable control systems. Get the fundamentals right and you'll spend less time fixing avoidable faults and more time programming the show.
How StageKraft Supports Your LightShark Setup
StageKraft supplies the LightShark controller range across Australia, with the LS-1, LS-Core, LS-Core IO, LS-Wing, and LS Nodes for touring, installation, and venue use.
If you're building a system or replacing a desk, get in touch with the sales team at sales@stagekraft.com.au or call +61 2 9982 1494 to confirm compatibility and lead time for your project.
Frequently Asked Questions
Can haze fluid damage a LightShark controller or node?
No, haze doesn't harm the electronics in a controller or node, but glycol residue can build up on cooling vents and reduce airflow. Keep controllers away from direct haze output and clean vents with compressed air after multi-day productions to maintain proper cooling.
How many DMX universes can the LS-1 control at once?
The LS-1 provides 4 DMX universes. You can expand that by adding LS Nodes to your network, with the LS Node 1 contributing 1 universe, the LS Node 2 contributing 2 universes, and the LS Node 4 contributing 4 universes, giving you the capacity to scale your system as the rig grows.
Does LightShark work offline without an internet connection?
Yes, LightShark runs offline. Programming, playback, and control all happen on the local network between your controller and the devices. An internet connection is only needed for software updates or remote access when you choose to enable it.
Can I control LightShark from an iPad during a live show?
Yes, LightShark's browser-based interface works on any tablet or phone connected to the same network as the controller. Make sure the device has a static IP or reserved DHCP lease, and test wireless latency before relying on it for live cues.
What happens if two operators try to control the same LightShark session?
Both devices will send commands to the controller, which can create conflicting cue triggers and parameter changes. LightShark doesn't lock users out, so you need to coordinate who controls what during the show and use separate user accounts or access levels when the system supports them.
Setup discipline separates rigs that run reliably from those that fail under pressure. Lock down your network config, document your patch, and test every fixture before the client walks in. These six mistakes appear on production sites regularly, but none of them survive a methodical load-in process. Get the fundamentals right and the rest of the show takes care of itself.
Kitting out a stage, venue or show?
StageKraft supplies professional lighting, control, atmospherics, rigging and cases across Australia and New Zealand, with an in-house service team behind every brand.
See the range