Portland-based creative engineering for live performance
We design the technical spine of live performances and installations: lighting, audio, show control, custom software, hardware interfaces, and the handoff materials operators need when the room is live.
Approved partner and project contexts showing where the studio has taken responsibility for lighting, audio, technical direction, archive capture, operation, and continuity.
Ongoing concert lighting design
Concert archive capture
Production direction for Queer Tarot
Production direction for Queer Love in the Time of Resistance
For teams that need creative intent translated into cueable, operable, documented systems: lighting, audio, show control, custom tools, hardware interfaces, and the materials that keep the system understandable.
Bring us in when creative intent, crew capacity, budget, vendors, venue limits, and risk need one production plan the team can rehearse and operate.
Leaves: a clearer operating picture, rehearsal priorities, and a path toward continuity.
Bring us in when stage lighting needs to be cued, repeated, and handed off without guesswork. We help with fixture planning, patching, cue structure, DMX/Art-Net/sACN paths, ETC Eos/ETCnomad workflows, and show-file cleanup.
Leaves: a cleaner patch, cue structure, and show file.
Bring us in when capture, playback, routing, or archive paths need to stay steady without adding friction. We work with archival capture, playback prep, QLab and Ableton sessions, interface setup, and signal-flow documentation.
Leaves: clearer routing, prepared sessions, and practical troubleshooting guidance.
Bring us in when off-the-shelf workflows do not connect the way the show actually runs. We build operator dashboards, cue helpers, control surfaces, real-time displays, OSC/MIDI paths, and automations shaped around the team using them.
Leaves: a working tool, operator instructions, and the logic needed to maintain it.
Bring us in when physical devices need to trigger, sense, display, or control something the software cannot reach on its own. We help with microcontroller interfaces, sensors, controller boxes, cabling plans, and device links.
Leaves: a safer bridge between the physical room and the software layer.
Handoff is not an afterthought. We turn readable files, signal paths, cue documentation, labels, setup steps, and operating patterns into material another operator can follow.
Leaves: labeled paths, readable files, setup steps, and an operator packet.
Choose the lightest engagement that reduces the risk. A project can start as a focused consult, become a production role, or close with clean documentation before another person inherits it.
A short, practical review before budget, venue, vendor, or equipment decisions become expensive to change.
Leaves: a short risk map, decision list, and recommended next step.A lead role for a concert, performance, or installation where creative and production decisions need one accountable owner.
Leaves: a production plan, rehearsal priorities, cue/workflow decisions, and one accountable thread.Help with cueing, capture, playback, routing, fixture choices, and operator material when a setup needs to run cleanly.
Leaves: cleaner routing, cue documentation, setup steps, and repeatable operator material.Purpose-built software, dashboards, cue helpers, control surfaces, or device links for a specific workflow.
Leaves: a working tool, operator instructions, and the logic needed to maintain it.Cleanup for labels, signal paths, cue documentation, setup steps, and operating patterns before someone else inherits the system.
Leaves: labeled paths, readable files, setup steps, and an operator packet another person can use.The process stays simple: map what can fail, build the path the production actually needs, rehearse with the people using it, and leave the system readable.
We map goals, constraints, people, schedule, gear, and likely failure points before build decisions harden.
Output: scope record, risk map, and next decisions.
We build or connect the cue path, control logic, show files, tools, labels, and setup patterns the production needs.
Output: working system components and operator-facing structure.
We test the system with the people operating it, then tune timing, controls, instructions, and failure recovery.
Output: cleaner operation and fewer fragile assumptions.
We leave files, labels, cue documentation, setup steps, and system logic in a form another operator can follow.
Output: operator packet, show files, and run material.
dreamsinco.de is led by one accountable technical owner, with collaborators added only when the project needs more hands or a narrower specialty. The goal is not to make the engagement bigger. The goal is to make the system clearer, safer, and easier to operate.
Background: the studio brings software architecture, systems integration, and live-production judgment into one studio practice.
Decisions do not disappear into layers of account management before they reach the person responsible for scope, build, rehearsal, and transfer.
Plans are shaped around the people, constraints, schedule, equipment, and pressure of the real production environment.
The studio can advise, lead, build, clean up, or document without forcing a larger engagement than the situation calls for.
Bring us in before rehearsal pressure turns unclear choices into expensive fixes. If a smaller next step is enough, we will say so.
For productions, we coordinate the moving parts, prepare the people operating the show, and keep the system legible from rehearsal through transfer.
You do not need a perfect spec. Send the shape of the project, the timeline, the location, the people involved, and the part that feels unclear or fragile.
We will respond with the next useful step: a scope conversation, a recommendation, or a clear reason we are not the right fit.