Feature Requests

Posted 5 days ago by Jens Klopp

Post a topic

Topic is Locked
Merged Topic

Jens Klopp

Hi MaestroDMX Team,

I am a user of MaestroDMX, running the latest software version. While I really love the autonomous music analysis capabilities, I am currently facing two major roadblocks in my live workflow that I highly request to be fixed or added in the upcoming v1.6 update.

1. Feature Request: Touch-Friendly XY-Pad for Moving Heads (Live Intervention)
Currently, manually overriding moving heads via the tablet interface using separate sliders for Pan and Tilt is very counterintuitive and difficult during a live show.

The Problem: If a speaker enters the stage or a specific spot needs to be highlighted manually, using sliders feels clunky.
The Solution: Please implement a native XY-Pad (Touch Field) within the web interface. This would allow users to smoothly drag a pointer on their tablet to guide moving heads to a specific position in real-time.

2. Bug Report / Improvement: Issues with Combined Shutter/Strobe Channels (e.g., Showtec Phantom Series & others)
The fixture profile creator is currently too rigid for fixtures that share Shutter, Dimmer, or Strobe functions on a single DMX channel. This is a generic issue affecting almost all fixtures with multi-function/combined channels.

The Problem: For fixtures like the Showtec Phantom series, values from 0–15 might control the Shutter (Open/Closed), while higher values control the Strobe speed. Because MaestroDMX flags this entire channel purely as a dynamic "Strobe" channel, the AI constantly overwrites manual overrides or Snapshots. It is impossible to reliably save a static "Shutter Open" state (e.g., for a white stage spot) without the AI blacking out or flashing the fixture.
The Solution: Please implement a "Range-Splitter" feature in the Fixture Profile Editor, allowing users to define specific value ranges for a single channel (e.g., 0–15 = Shutter Open/Closed, 16–255 = Strobe). This ensures that static Snapshots can hold a specific channel value without being overridden by the AI's strobe engine.

These additions would immensely help DJs and light technicians who need a hybrid workflow (reliable AI music automation mixed with fast, intuitive manual live interventions).

Looking forward to your reply and future updates!

0 Votes

1 Comments

Technical Support posted 4 days ago Admin

Hi Jens!

Thank you for your support and feedback.

1. This feature is complete and will be included in our next software release (v1.6), along with more fixture groups (now called zones), more effect buttons, among other changes. You can expect this release within 2-3 months.

2. The Strobe feature does need work. Currently our software "strobes" the RGB channels, rather than updating the Shutter. This section definitely needs some improvement. It does sounds like there might be something else going on here too, any channel that had value ranges like you're describing should probably not be set to a dynamic range, especiall a range that spans across different discrete behaviours. You may want to reach out to our support team, we offer office hours where they can work with you to pinpoint the issue you're having. Hopefully for the time being there is a way to use snapshots to get the desired effect. I'm going to merge this feature request into other requests for improved strobe support, so that it's upvoted. We do use feedback here to help plan our roadmap and prioritize feature development.

Thanks again

Gabby

0 Votes