MESSENGER // Feature Request via Firmware Update
MESSENGER // Feature Request via Firmware Update
Please add via firmware update: edit state indication. It’s bad enough you omitted even a small OLED screen (a la Sub37) on a digitally controlled analog with 256 patch memories. But no visual indication of whether a parameter’s saved value has been changed and/or how to return it to its saved value is a big UX fumble. Look to the Novation Bass Station 2 for a clue how this might be implemented. One of the buttons could light up if a patch has been edited and the (already part of the UX design) 16 buttons could indicate new value/return to value.
Last edited by Æsc on Wed Jun 11, 2025 1:21 pm, edited 1 time in total.
Re: MESSENGER // Feature Request via Firmware Update
Suggested implementation: make the [PANEL] button blink/pulse slowly to indicate when patch is in edited state. And then as mentioned above, buttons 1-16 indicate parameter value (as elsewhere in the UX design), center/off indicating return to saved value; lit buttons L/R from center indicate value -/+ away from saved value. Buttons automatically light/indicate when a parameter control is moved/changed. Then return to default state after a second or so. Easy peasy. Thanks!
Last edited by Æsc on Wed Jun 11, 2025 1:24 pm, edited 1 time in total.
Re: MESSENGER // Feature Request via Firmware Update
For parameters which involve state selection (e.g. LFO WAVESHAPE, FILTER MODE, OSC. OCTAVE, MOD DEST., etc.) the saved state could blink while the edited state remains solid. And for parameters which are on/off only, they would simply blink/pulse if their state is edited.
Re: MESSENGER // Feature Request via Firmware Update
i just want to co-sign that this would be a solid addition to the firmware.
At it's minimum, it could be an indication when any control in general have deviated from the save patch. But ideally, an indication when moving a control, whether it is higher or lower than the save patch.
my BS2 and Prophet 5 Rev 4 both have pretty bare bones implementation of this feature, but it's still a big help.
At it's minimum, it could be an indication when any control in general have deviated from the save patch. But ideally, an indication when moving a control, whether it is higher or lower than the save patch.
my BS2 and Prophet 5 Rev 4 both have pretty bare bones implementation of this feature, but it's still a big help.
Re: MESSENGER // Feature Request via Firmware Update
Only had the Messenger for a week, but there's 2 things I'd like to see in an update.
The first would be to be able to assign more than one destination to the performance sources.
For example, assign expression to both filt. cutoff and osc. wav mod amount.
Maybe use one or more of the pages for this.
And while cool, it would be more flexible to be able to disable the hardwired routings of the pitch and mod wheels,
and be able to assign them to one or more different things.
For example, use the mod wheel to control cutoff or resonance directly without activating it through an lfo.
BTW- the Messenger is great. It's exceeded my expectations, so this isn't a complaint, just a wish list.
The first would be to be able to assign more than one destination to the performance sources.
For example, assign expression to both filt. cutoff and osc. wav mod amount.
Maybe use one or more of the pages for this.
And while cool, it would be more flexible to be able to disable the hardwired routings of the pitch and mod wheels,
and be able to assign them to one or more different things.
For example, use the mod wheel to control cutoff or resonance directly without activating it through an lfo.
BTW- the Messenger is great. It's exceeded my expectations, so this isn't a complaint, just a wish list.
Re: MESSENGER // Feature Request via Firmware Update
I'd like to be able to set the modulation amounts for the mod wheel destinations, at the moment there's no way to say fully modulate the volume and the pitch a little
Re: MESSENGER // Feature Request via Firmware Update
I'd like rachets in the sequencer. They're in the Mother-32 and the Matriarch, to name a few, so why not?