Luminite Graviton M1 MIDI Controller

[laxu]

With Momentary Enabled, the current behaviour is: LED is on while holding / off on release (in MIDI Editor / Preset Library / Devices Screens) as it should be (?) for me which screen are you looking at ?

I was using the Devices -> Footswitch view. Now that I rebooted my device to try this again, the momentary seems to actually work where it defaulted to "LED off" and holding it turned the LED on and then back off. For some reason this didn't work yesterday at all.

I don't understand this. With Toggling Enabled, the current behaviour is: LED on = normal CC sent, LED off = CC with value 0 sent (or Toggling CC/PC if added). So it matches the Effect On/Off statuses on the screen of the target device.

When I start the M1, all toggles in every bank default to LED on, even when you have never used that preset. This makes it look like those presets are active when they are not. They should default to LED off until you activate the preset, and then track with the behavior you mention above.

---

I don't know how easy it is to do, but I think for bank changes via double tap or hold functions, it should not highlight any block because it can misleadingly look like it is active. For example, my layout for Strymon Deco presets look like this for the F6W in Devices -> Footswitch:

(O) = toggle
(X) = active preset

[ Deco 4 ] [ Deco 5 ] [ Deco A.F (O) ]
[ Deco 1 ] [ Deco 2 ] [ Deco 3   (X) ]

Hold tap mapping:

[ None   ] [ None   ] [ None ]
[ Bank - ] [ Bank + ] [ None ]

Current behavior:

1. Hold "Deco 1" -> Bank decrement.
2. "Deco 1" (bottom left) is highlighted.
3. Show "Bank -" on bottom left.
4. Switch to previous bank.
5. Bottom left block is still highlighted, which makes it seem like it's the active preset.

I can see from the top that "Deco 3" is still active, but at a glance my brain says the slot for "Deco 1" in the previous bank is active.

The flow should be something like this instead:

1. Hold "Deco 1" -> Bank decrement.
2. Highlight bottom left block.
3. Show "Bank -" on bottom left.
4. Switch to previous bank.
5. Show bottom left slot preset, but keep it unhighlighted.

Now going back to Deco's bank:

1. Hold "Deco 2" -> Bank increment.
2. Highlight bottom center block.
3. Show "Bank +" on bottom center.
4. Switch to next bank.
5. Show bottom right slot ("Deco 3") as highlighted because it's the current active preset.

I don't know if this causes some conflict I am not thinking about right now, but I think that would keep it clearer what is currently active.

 

[Luminite]

I was using the Devices -> Footswitch view. Now that I rebooted my device to try this again, the momentary seems to actually work where it defaulted to "LED off" and holding it turned the LED on and then back off. For some reason this didn't work yesterday at all.

I think I found the bug. If you enabled Momentary, and use touchscreen on that Preset, it will get stuck on the 'On' state. Fixing now.

When I start the M1, all toggles in every bank default to LED on, even when you have never used that preset. This makes it look like those presets are active when they are not. They should default to LED off until you activate the preset, and then track with the behavior you mention above.

I understand now. The On/Off state of each preset is supposed to be retained (saved to flash memory) even after rebooting. However, the saving process is only triggered when you edit that preset, not while playing / toggling them (to avoid unnecessary flash wearing).

So it may appear that all LEDs are defaulted to 'On.' This is because no saving event occurred before powering the M1 off, rather than an intentional default setting. The saving doesn't really work in cases like this anyway, so maybe ignoring the last states and default everything to 'Off' on reboot is better than being stuck with "On".

---

I don't know how easy it is to do, but I think for bank changes via double tap or hold functions, it should not highlight any block because it can misleadingly look like it is active. For example, my layout for Strymon Deco presets look like this for the F6W in Devices -> Footswitch:

(O) = toggle
(X) = active preset

[ Deco 4 ] [ Deco 5 ] [ Deco A.F (O) ]
[ Deco 1 ] [ Deco 2 ] [ Deco 3   (X) ]

Hold tap mapping:

[ None   ] [ None   ] [ None ]
[ Bank - ] [ Bank + ] [ None ]

Current behavior:

1. Hold "Deco 1" -> Bank decrement.
2. "Deco 1" (bottom left) is highlighted.
3. Show "Bank -" on bottom left.
4. Switch to previous bank.
5. Bottom left block is still highlighted, which makes it seem like it's the active preset.

I can see from the top that "Deco 3" is still active, but at a glance my brain says the slot for "Deco 1" in the previous bank is active.

The flow should be something like this instead:

1. Hold "Deco 1" -> Bank decrement.
2. Highlight bottom left block.
3. Show "Bank -" on bottom left.
4. Switch to previous bank.
5. Show bottom left slot preset, but keep it unhighlighted.

Now going back to Deco's bank:

1. Hold "Deco 2" -> Bank increment.
2. Highlight bottom center block.
3. Show "Bank +" on bottom center.
4. Switch to next bank.
5. Show bottom right slot ("Deco 3") as highlighted because it's the current active preset.

I don't know if this causes some conflict I am not thinking about right now, but I think that would keep it clearer what is currently active.

There will be UI conflicts with highlighting the current active preset (as the Preset Library view is for) instead of highlighting the triggered Actions in the Devices view.

Example: If you go back by a normal 'Bank -' or 'Bank Toggle' instead of 'Holding Deco 2', highlighting 'Deco 3' instead mean the 'Bank -' or 'Bank Toggle' action won't have any visual feedback to shown it was triggered. This can be confusing or inconsistent for users.

Maybe the Preset underneath a Hold / Double Action can stay unhighlighted, but keep the white border to show Hold / Double Action was triggered successfully ?

In overall, all Hold / Double / Release Actions should only retain its white border after being triggered, while the primary action underneath stay unhighlighted. That is my suggestion, but I'm open to ideas :)

 

[laxu]

I understand now. The On/Off state of each preset is supposed to be retained (saved to flash memory) even after rebooting. However, the saving process is only triggered when you edit that preset, not while playing / toggling them (to avoid unnecessary flash wearing).

So it may appear that all LEDs are defaulted to 'On.' This is because no saving event occurred before powering the M1 off, rather than an intentional default setting. The saving doesn't really work in cases like this anyway, so maybe ignoring the last states and default everything to 'Off' on reboot is better than being stuck with "On".

Yeah I think keeping track of the states while the pedal is on is enough, considering MIDI pedals aren't consistent in how they behave after power on. Some will default to the first preset and some default bypass state, some will remember their last state. For example my Strymons remember their last state but my BluGuitar does not.

There will be UI conflicts with highlighting the current active preset (as the Preset Library view is for) instead of highlighting the triggered Actions in the Devices view.

Example: If you go back by a normal 'Bank -' or 'Bank Toggle' instead of 'Holding Deco 2', highlighting 'Deco 3' instead mean the 'Bank -' or 'Bank Toggle' action won't have any visual feedback to shown it was triggered. This can be confusing or inconsistent for users.

Maybe the Preset underneath a Hold / Double Action should be transparent when not activated, but keeping the white border after Hold / Double Action was triggered successfully ? In overall, all Hold / Double / Release Actions should only retain its white border after triggered. That is my suggestion, but I'm open to ideas :)

You mean by "normal", using 1st tap for bank changes?

Maybe there could be say a dotted border for activated action "location" and a solid border for active presets or something?

 

[Luminite]

Yeah I think keeping track of the states while the pedal is on is enough, considering MIDI pedals aren't consistent in how they behave after power on. Some will default to the first preset and some default bypass state, some will remember their last state. For example my Strymons remember their last state but my BluGuitar does not.

Yes thats true, I’ll fix it.

You mean by "normal", using 1st tap for bank changes?

Yeah 1st tap

Maybe there could be say a dotted border for activated action "location" and a solid border for active presets or something?

Dotted border is a bit tricky to code. I tried blue borders for activated actions quite a while ago. Will try again, it may work

 

[Luminite]

Graviton M1 / M2 Software Update 4.3.5 (Beta)

• New feature: Silent Mode for Presets: send Presets without updating the screen (MIDI Editor / Live).
• New feature: Setlist Mode: Switch to the next / previous Song after scrolling past the last / first Song Preset.
• Improved: Triggered Hold / Double / Release Action won’t highlight the Action underneath after.
• Improved: Hold Action behaviour.
• Bug Fixes.

How to Update / Rollback:

• Go to Settings > Update / Rollback > Follow the on-screen instructions.
• You can switch between Beta and the last Stable Release anytime without loosing programmed data.
• It's recommended to stay on the Stable Release for gigging.

 

[Luminite]

Graviton M1 / M2 Software Update 4.3.6 (Beta)

• New Feature: USB Keyboard Mode: Control your Computer / DAW / iOS devices over USB.
• New Message: Keystroke with full special keys sets and up to 4 modifiers at once (Shift, Control, Alt/Option, Windows/Command).
• New Feature: TRS Jack Mode: Switch Out: For switching low voltage pedals (5V or less) over AUX Jacks.
• New Feature: Playing Song Screen: Block and List layout, Toggle LEDs and current Setlist number added.
• New Feature: Song +/- Action: Jump to the next Setlist after the last Song was reached.
• New Feature: Bluetooth Settings: Advertising On/Off and Custom Name.
• Bug Fixed: Crashing when loading Backups files.
• Bug Fixed: Universal Footswitches learning doesn’t work in some cases.
• Improved: Settings are saved immediately once changed.
• Improved: MIDI Editor: Toggle Value/Slider and Grayscale display mode directly in the menu.

How to Update / Rollback:

• Go to Settings > Update / Rollback > Follow the on-screen instructions.
• You can switch between Beta and the last Stable Release anytime without loosing programmed data.
• It's recommended to stay on the Stable Release for gigging.

Enjoy and please report bugs here :)

 

[Luminite]

Relay + Control Voltage Adapter

• Relay Port: Control two individual Amp Channels Switching or Pedal’s Footswitch Inputs (Tip and Ring). Normal, Toggling or Momentary Mode. Eliminate ground loop completely with up to 400V of isolation. Silent solid state relays (no clicking). No external power needed.
  
  
• Control Voltage Port: Control two individual Expression or Control Voltage Inputs (Tip and Ring). Selectable range of 0-5V or 0-3.3V DC. Compatible with EC Controllers for wireless expression control. Requires 9VDC Input.
  
  
• Ultra Compact Size: Can be hidden under pedalboards.
  
  
• Stainless Steel Enclosure: Heavy duty construction.

Relay + Control Voltage Adapter

Luminite Effect Pedals, MIDI Controllers, Loopswitchers

luminitefx.com

 

[AFKAEjay]

Relay + Control Voltage Adapter

• Relay Port: Control two individual Amp Channels Switching or Pedal’s Footswitch Inputs (Tip and Ring). Normal, Toggling or Momentary Mode. Eliminate ground loop completely with up to 400V of isolation. Silent solid state relays (no clicking). No external power needed.
  
  
• Control Voltage Port: Control two individual Expression or Control Voltage Inputs (Tip and Ring). Selectable range of 0-5V or 0-3.3V DC. Compatible with EC Controllers for wireless expression control. Requires 9VDC Input.
  
  
• Ultra Compact Size: Can be hidden under pedalboards.
  
  
• Stainless Steel Enclosure: Heavy duty construction.

Relay + Control Voltage Adapter

Luminite Effect Pedals, MIDI Controllers, Loopswitchers

luminitefx.com

View attachment 22608

It says “add expr and cv” to an M2 unit on the website….how does that work of it needs a exp and cv as an input?
If it doesn’t need power…why is there 9v input?

 

[Mike Oliphant]

Very cool suite of devices!

Any chance of a little USB receiver dongle for the EC Controller for those of us who already have a MIDI hub solution?

 

[quadgear]

Very cool suite of devices!

Any chance of a little USB receiver dongle for the EC Controller for those of us who already have a MIDI hub solution?

I'd prefer a midi dongle. ;-)

Or an a battery powered M1 type device with push encoders in place of foot switches? (I'd leave the cables and footswitches on the floor.)

 

[Luminite]

It says “add expr and cv” to an M2 unit on the website….how does that work of it needs a exp and cv as an input?
If it doesn’t need power…why is there 9v input?

The connections are: TRS Jacks (on the M1/M2) > Relay In / CV In Jack (on the Adapter) > Relay Out / CV Out.

The 9V input is for the CV Port only. No power needed if you only use the Relay Port.

 

[Luminite]

Very cool suite of devices!

Any chance of a little USB receiver dongle for the EC Controller for those of us who already have a MIDI hub solution?

It's possible, but programming can be quite difficult, or very limited. And the M1 is not that much bigger.

I'd prefer a midi dongle. ;-)

Or an a battery powered M1 type device with push encoders in place of foot switches? (I'd leave the cables and footswitches on the floor.)

Yes, built-in batteries would be amazing, but shipping anything with a substantial battery size is very challenging due to flight regulations. However you can easily attach an external battery to the M1 (sticky pads or Velcro), and stick the EC controller on the side.

 

[laxu]

Yes, built-in batteries would be amazing, but shipping anything with a substantial battery size is very challenging due to flight regulations. However you can easily attach an external battery to the M1 (sticky pads or Velcro), and stick the EC controller on the side.

I've been using a slim USB powerbank with the M1 for ages now and it has worked just great. Mine (a branded gift from a client so no idea about the model) happens to be a good size that I can transport it in the packing box of the M1 too.

Some sort of mount to fit a couple of EC controllers together with the M1 might be cool. Don't know what that would look like or how it would be most practical but you could always just take a slim piece of wood and put the EC controllers and M1 on that.

I need to order some of those ECs, now that I think of it...

 

[Mike Oliphant]

It's possible, but programming can be quite difficult, or very limited. And the M1 is not that much bigger.

The assumption would be that whatever device the USB receiver is plugged into would be doing the MIDI controlling. The device itself would just be acting as a MIDI peripheral - it could just send fixed MIDI for EC Controller actions. Bonus points if the MIDI behavior could be configured over USB.

As an example, the USB dongle could be plugged directly into a computer (desktop/laptop/SBC/etc.)

 

[laxu]

As an example, the USB dongle could be plugged directly into a computer (desktop/laptop/SBC/etc.)

If this is your usecase, even something like an Elgato Stream Deck Plus can be used as 4 knobs that can send MIDI commands.

 

[Mike Oliphant]

If this is your usecase, even something like an Elgato Stream Deck Plus can be used as 4 knobs that can send MIDI commands.

My use case is a SBC-based pedalboard - specifically this:



I've got stomps covered with an Ampero Control (which is perfect for my needs), but I'd like a few rotary encoder knobs.

 

[Luminite]

Graviton M1 / M2 Software Update 4.4.0 (Stable)

New Features: ​

In comparison to version 4.2.2 (Last stable):

• New Feature: Programmable 1st Tap, 2nd Tap, 3rd Tap, Double Tap, Hold Tap Action for every XY switches, footswitches and EC push buttons (can be used at the same time for 5 Actions per switch).
• New Feature: USB Keyboard Mode: Control your Computer / DAW / iOS devices over USB.
• New Message: Keystroke with full special keys sets and up to 4 modifiers at once (Shift, Control, Alt/Option, Windows/Command).
• New Feature: TRS Jack Mode: Switch Out: For switching low voltage pedals (5V or less) over AUX Jacks.
• New feature: Silent Mode for Presets: send Presets without updating the screen (MIDI Editor / Live).
• Playing Song Screen: Block and List layout, Toggle LEDs and current Setlist number added.
• Song +/- Action: Jump to the next Setlist after the last Song was reached.
• Bluetooth Settings: Advertising On/Off and Custom Name
• Virtual LEDs for Presets On / Off state: Improved visual feedback.
• Live View: Customize display information, additional BPM, Song, Setlist options.
• Live View: EC Controllers and Expression Pedals real time value feedback.
• MIDI Editor: Toggle Value/Slider and Grayscale display mode directly in the menu.
• New Action: Encoder Click: XY Switches and Footswitch presses can function as clicks from EC Controllers.
• New Action: Bank Toggle: Jump between the current bank and a Bank of your choice
• New Action: Bank A/B: Jump betwen two Banks of your choice.
• New Action: Shortcut > Live / Preset Library: Switch to Live and Preset Library with one button press.
• New Action: Change LCD Brightness: With button presses.
• New Message: Clock + and Clock -: nudge BPM up and down by a set amount.
• New Message: Set Toggle: Set the On / Off State of a target Preset.
• New Message: Counter CC and Counter PC Send: Send the current counter value only
• EC Controller Knobs: Set Increase / Decrease Adjustment independent from the rotating direction.
• Encoder Message: Can change Counter CC and Counter PC.
• Encoder Message: Can change MIDI Clock.
• Keyboard: Improved layout with a full set of special characters.
• Footswitch: Sensivity setting from within Footswitch Pedals Screen.
• MIDI In: Incoming USB MIDI Messages can be used to trigger Preset / Action.
• Software Update: Update to Beta and Stable Channel
• Slightly faster UI speed.

Bug Fixes​

• Fixed: Tap Tempo: always start from 40 BPM.
• Fixed: Preset Mode / Setlist Mode: less confusing.
• Fixed: # (sharp) display for Note messages.
• Decpreciated: Last Sent messages. Use MIDI Tracking instead.
• Decpreciated: Toggling Auto-Reset. Use Set Toggle Message instead.
• Name Change: Scrolling CC/PC to Counter CC/PC.
• Numerous bug fixes and UI improvements.

How to Update / Rollback:​

• Go to Settings > Update / Rollback > Follow the on-screen instructions.
• You can switch between Beta and the last Stable Release anytime without loosing programmed data.
• It's recommended to stay on the Stable Release for gigging.

User Manual:​

Luminite Graviton M1 / M2 User Manual 4.4.0

Changes from 4.3.6 Beta​

• Updated: Built-in User Manual (Settings > Manual).
• Fixed: Display of the # (sharp) character for Note messages.
• Fixed: Crashing when changing from Keystroke to CC.
• Fixed: Live screen top center stuck with 3 dots.
• Fixed: Full Keystroke menu in List view.
• Fixed: Hanging up while scrolling long User Manual pages.
• Improved: Relay + CV Adapter: CV output accuracy.
• Added: Restart prompt when switching USB Keystroke Mode.
• Encoder Message: Works with CC/PC Counter Update and Send.
• Numerous stability and UI bug fixes.

 

[laxu]

Upgrading to 4.4.0, the updater still says you are updating to a beta even though the new release is a stable one, so it seems it can't discern between beta and stable releases. I'd use generic texts here (instead of "update to latest beta") and just use the beta label in the versioning somehow so you see say "4.4.1 (beta)" and can determine if you want to install that or wait for stable.

Didn't have any major issues with 4.3.6 in my use but I haven't had time to dive deep into it again.

 

[DrewMan]

Hi Luminite,

You guys have created an awesome range of pedals!

I have a question about functionality and a potential future feature request. I don't think this feature exists yet (correct me if I’m wrong! ), so it's a new concept I believe.

The M2 pedal has 6 foot switches. Let's call each foot switch a “mode”.

Here's how it would work:

1. When you press and hold a foot switch mode.
2. You can then navigate through options using the XY controller (X1, X2, X3, X4, Y1, Y2, Y3, Y4).
3. The screen will show the available options and the current selection.
4. The selection is ONLY confirmed when you release the foot switch.
5. Neutral position is needed as a way to abort the mode without making a selection.
6. Since X and Y switches are independent, you might also need to block X if Y is being rotated (ie x5 and y5 position) and vice versa, to ensure only one selection is made within the mode.

For the user interface:

• On pressing a foot switch, the XY options in that mode are displayed.
• As you navigate with the XY controller, the current selection is shown.
• When you release the foot switch, the last selection should be confirmed and displayed for a second or two for visual confirmation.
• The UI shows the function of each foot switch when no foot switches are pressed, as a visual reminder of what each switch does.

With 6 modes and 8 x XY options per mode (forgetting neutral), you would have 48 options accessible with a foot press and a controller click. If you had 2 x XY controllers, you could have 6 modes and 16 XY options, totalling 96 options! Etc.

I hope this makes sense! I know you’re busy guys, but something to think about