Troubleshooting

This page gathers the most frequent problems and the steps to follow for each. The first reflex is always the same: look at the Log panel, where DreamShow notes what it is doing and what is going wrong (AVT lines for warnings, ERR for errors).

The log, your first tool

The Log panel shows DreamShow's messages, with the time and the source (dmx, video, audio, robot, masks, displays…).

• The Info, Warn., Errors and Debug boxes choose which messages are displayed (Debug, very chatty, is unticked by default).
• Clear empties the display.
• Copy: “Copies the displayed journal to the clipboard”. Paste these lines into a request for help: they say exactly what happened.
• Follow scrolls the log to the most recent messages.

See Log, Audio and Clock.

Nothing goes out to the fixtures (DMX)

Check in this order:

1. The LIVE button, at the top right. When on, the selected scene is sent to the interfaces; when off, “no frame goes out any more, only the simulation keeps running”. It has no effect in show mode.
2. Visualiser mode. During DMX > Visualiser mode (Art-Net / sACN in)…, DreamShow stays silent: its output is cut. Stop this mode.
3. The connections. Next to the Connections… button (at the top of the screen), a text summarises the outputs in use; its tooltip lists any errors. Open Venue > DMX connections… and check that each universe in use has an interface (and not “None”). See DMX connections.
4. What DreamShow sends. Open DMX > DMX values…: if the values move when the scene plays, DreamShow is indeed sending; the problem is between the PC and the fixtures.
5. Depending on the interface:
   • Art-Net: the node's IP address must be on the same network as the PC, and the network universe number must match the one set in the node. The Windows firewall must allow DreamShow (see below).
   • sACN: check the universe number (1 to 63,999), and that the network lets multicast through, or give the receiver's IP address.
   • USB DMX PRO: the interface's COM port must appear in the ““Ports COM : …” (COM ports: …)” list of the DMX connections window; otherwise, check the connection and the interface's driver.
   • uDMX: the interface uses the libusbK driver.
6. The fixtures. The DMX address and the mode (number of channels) set on each fixture must be those of Venue > Fixtures, addresses, positions…. Check the cables and the termination at the end of the line.
7. Testing a channel. DMX > DMX faders… forces channels by hand on top of the cue list: raise a fixture's intensity channel to check that it responds. See DMX values and DMX faders.

A fixture is behaving erratically

• Wrong DMX mode: the fixture is set to a different number of channels from the one declared in the venue. Align the two.
• Overlapping addresses: two fixtures share channels. Check the addresses in Venue > Fixtures, addresses, positions….
• Incorrect definition: correct it in Venue > Fixture library…. See The fixture library.
• A moving head aims badly: check its position, orientation and rigging in the venue, or calibrate it. See Moving-head calibration.

The video does not start

Videos on monitors are played by ppvideoplayer, installed with DreamShow. DreamShow starts it by itself, minimised in the taskbar, when the show contains videos. Read the log (source “video”):

• “ppvideoplayer started automatically (the show contains videos)” then “ppvideoplayer ready — media folder and loads sent”: all is well on the launch side.
• “The show has videos but ppvideoplayer cannot be found (…)”: the player is not at the indicated locations; reinstall DreamShow.
• “ppvideoplayer started but its pipe does not answer (15 s) — new attempt in 30 s.”: the player is starting badly; wait for the new attempt, or restart it (see below).
• “ppvideoplayer is running (…) but its pipe is missing — dead instance, it is stopped and restarted.”: DreamShow repaired this by itself.

Also check:

1. That the video file is in the show's media folder (File > Open the show's media folder).
2. That the chosen screen exists: Venue > Screens…, 🔎 Identify the screen button (a test pattern appears on the monitor; a click or a key closes it), then ▶ Test the video.
3. ppvideoplayer only sees the monitors that were connected when it started. If you connect a screen afterwards, click ⟳ Restart ppvideoplayer in Venue > Screens….

See Video screens and Sound and video on the timeline.

No sound

• DreamShow plays the sounds itself, on the Windows default audio output: it has no output setting of its own. Change the default output in Windows' sound settings if needed.
• Look at the levels of the Audio panel (left / right): a Sound level block on the timeline may have lowered them.
• The log (source “audio”) flags a missing file: “File not found: …”. The file must be in the show's media folder.
• 🔇 Mute the sounds (Audio panel, and cue window) immediately stops all sounds in progress.

See Log, Audio and Clock.

DreamShow is slow, the simulation stutters

• Turn the simulation off: the ⏻ button, at the top of the Venue panel (the simulation). When off, “the room is no longer computed or drawn (2D and 3D), which relieves the processor and the graphics card during a show. The DMX output is not affected.” The panel shows “Simulation off — the ⏻ button turns it back on. The DMX output carries on normally.” This setting is kept at the next launch: if the simulation stays black, check this button.
• Lower the 3D quality: in 3D view, the list next to 2D / 3D offers Basic (flat cones), Standard (gradient core and halo, soft impact spots) and Maximal (rendered by the graphics card, volumetric beams). Choose Basic on a modest PC.
• Switch to 2D, which is much lighter than 3D.
• The small line under the simulation shows the refresh rate and the cost of one frame; the bar at the top of the main screen shows the engine's real rate.
• The engine keeps playing the show even if the display is slow: the light is not slowed down by the simulation.

See 2D and 3D simulation.

Windows firewall and network

Several DreamShow functions go over the network: Art-Net, sACN, the web remote, the OSC remote, follow-spot tablets, displays, IP video players, robots, visualiser mode. The first time, Windows may ask whether to allow DreamShow on the network: accept (at least for private networks). If you refused, allow DreamShow in the Windows firewall settings.

Ports used (for a network administrator):

For tablets and displays: the address shown by DreamShow is the PC's first network address. If it has several cards (Wi-Fi and cable, virtual card…), use its address on the devices' network.

Tablets, displays, robots, masks

• A follow-spot tablet does not connect: same network, firewall, address with :8090. See Follow spot on a tablet.
• A display stays empty: check the zone name in the address, and that a Backstage display… block really targets this display. See Backstage displays.
• The robot does not move: is it ARMED (🤖 button)? The log notes “… DISARMED — command ignored: …” otherwise. See Humanoid robots.
• The mask does not respond: switched on, not paired in Windows, mobile app closed, Reconnect button. See LED masks.

After a crash or a power cut

Restart DreamShow. If it stopped during a show or an editing session (within the last 6 hours), it shows the Resume after an interruption window: “DreamShow stopped … (last point: …).” with the show, the scene and the position, and offers to resume exactly at that point (Yes, resume / No). See Recovering after a crash or power cut.

Your files are protected: each save also keeps a dated copy in an autosave subfolder of the data folder.

If the crash happens again, note the version (? > About DreamShow…), what you were doing, and copy the log (Copy button) for support.

The screen layout is lost

The ⟲ UI button, at the top right, restores the default layout of the panels. See Main screen overview.

See also

• DMX connections
• DMX values and DMX faders
• Video screens
• 2D and 3D simulation
• Recovering after a crash or power cut
• Installation, languages and updates