Luminite Graviton M1 MIDI Controller

[Luminite]

@Luminite , what would be the best way to do this?

As a preface, the Strymon Nightsky's Pre-delay is accessible only with a cumbersome "hold a tiny button and turn the Reverb knob" secondary function, so moving that to be adjustable and trackable from the Graviton would be great.

1. I want to track the Strymon Nightsky Pre-delay value across preset changes. Just show the value when the MIDI CC #17 is received.
2. I want to be able to adjust the Pre-delay value from the UI, preferably from the same place where it shows it.
3. I don't really care about adjusting this value via preset changes, but might want to tweak it on the fly.

I can of course just add sending this MIDI CC to the preset and I think adding a MIDI PC command to change Nightsky preset after that should override it, right?

MIDI out from Graviton works like a charm. Can't get MIDI in to work.

EDIT: Seems my roundtrip wireless MIDI hookup was not setup. But I tried connecting the Nightsky MIDI out directly via cable to the Graviton and can't seem to get MIDI input to work in any way. I tried having it send values from the pedals connected via TRS to Conduit and also the pedals connected via MIDI 5-pin since my Conduit ran out of TRS jacks.

My MIDI chain is basically:

Graviton
   wireless
     |
CME WIDI Master
   MIDI out
     |           .---> MIDI in Volante, MIDI out -> MIDI in Nightsky, MIDI Out -> Graviton
     |           |
   MIDI in   MIDI out
 Strymon Conduit
TRS1  TRS2  TRS3 TRS4
|        |    |   |
Compadre |    |   |
    Riverside |   |
           Zelzah |
               Iridium

[/ICODE]

1. Right now MIDI In is for triggering Actions only. And Tracking Blocks keep track of all Outgoing MIDI Messages.
I'll add Incoming MIDI Messages update to Tracking Blocks in the next update.

2. 3. This is a function Ive been thinking about too, aka Global Blocks, where you can "pin" a block to its current position and it would stay that way even when you change presets. For now you need to add this block to all Presets you use.

Yeah if you send PC messages to your NightSky, its current Pre-Delay value will be overridden. The only way to keep track of this value is by filtering the incoming MIDI from the NightSky to the Tracking Blocks. 1st thing in the next update :)

 

[laxu]

Initially the "Shortcut" option (jumping between MIDI and Banks screen) was enabled by default as its the quickest way to select / edit presets, before "tap to rename" became the default.
I think I'll add a system wide "long press" option: tap for shortcut / long press for renaming as it seems the most intuitive ?

Yeah I think that would work, or maybe some pen icon after the name if that fits. But tap for shortcut, hold for rename sounds good.

The shortcut menu option is nice. Goes between the relevant views so easily.

A few more small things:

• I noticed the "clear" icon seems a bit offset from the name and back arrow. Looks like the X icon needs a bit more padding at the top.
• When adding a name for a CC or PC, it should not add the default "Name" title you have to clear every time but instead just leave it empty so you can just start typing your custom name. If left empty it should just not have a name (same as the remove name).
• Keyboard could always default to a version with borders on the keys. I think it is more user friendly than the "letters" only version you see editing e.g CC names.
• In Blocks view, the "Move Down/Up" functions in Type -> Edit should probably be "Move Left/Right." In the Grid view (should that be called List view instead?) Up/Down makes sense.

On another note, the power cable on the included power supply is pretty short. I don't know if you have any control over this since it's probably a pretty standard part, just pointing it out. I'm just powering it with my old 1Spot instead because that allows me to have a bit better placement.

PS. The USB-A to USB-C cable that comes with the unit might be the fanciest USB cable I've seen!

 

[Luminite]

A few more small things:

• I noticed the "clear" icon seems a bit offset from the name and back arrow. Looks like the X icon needs a bit more padding at the top.
• When adding a name for a CC or PC, it should not add the default "Name" title you have to clear every time but instead just leave it empty so you can just start typing your custom name. If left empty it should just not have a name (same as the remove name).
• Keyboard could always default to a version with borders on the keys. I think it is more user friendly than the "letters" only version you see editing e.g CC names.
• In Blocks view, the "Move Down/Up" functions in Type -> Edit should probably be "Move Left/Right." In the Grid view (should that be called List view instead?) Up/Down makes sense.

Yeah makes sense ! Added

PS. The USB-A to USB-C cable that comes with the unit might be the fanciest USB cable I've seen!

Half of the budget goes to these cables but very hard to not include them

 

[laxu]

1. Right now MIDI In is for triggering Actions only. And Tracking Blocks keep track of all Outgoing MIDI Messages.
I'll add Incoming MIDI Messages update to Tracking Blocks in the next update.

Oh ok, I guess I misunderstood the capabilities of the 2.0 update a bit. That's fine, for now the current features do plenty for my needs.

2. 3. This is a function Ive been thinking about too, aka Global Blocks, where you can "pin" a block to its current position and it would stay that way even when you change presets. For now you need to add this block to all Presets you use.

Global blocks sounds like a neat idea. I'm not quite sure how it work out in practice.

I have a different idea for this:

"Param control"​

What: A further set of views/banks. Visually it's identical to the MIDI blocks view and Preset X/Y list (group of 10 "Param control" views).

Usecases:

1. Realtime control of any param values via sliders on Graviton.
2. Realtime visual of param values otherwise hidden, e.g when presets change on a MIDI controllable pedal.
3. Easier control over secondary params.
4. Visualization of param values regardless of where they are set (Graviton UI slider, MIDI CC from pedal or external MIDI controller).
5. Combined control of your most important parameters of all pedals. E.g reverb mix/decay, delay time/feedback/mix, overdrive gain/tone.

As an example, in a view like this I could build blocks to represent parameters on one of my pedals. When changing presets, I can't see where those knobs are pointing, but if the Graviton receives all the MIDI CCs representing them and can show them on screen, then that's no longer an issue.

Or I could build blocks represent a subset of most important params on any of my pedals so I can quickly adjust e.g the mix on delay and reverb from one place, while tracking those values in the same blocks across pedal preset changes.

I could then use either the pedal controls (which can send matching MIDI CCs), an external MIDI knob controller or the slider on the Graviton UI to adjust these params. Last received value = UI value.

Example scenario:

I have "Param control" view with block "Ch 3 CC 14". On my setup this controls the Bass knob on the Strymon Riverside overdrive.

1. I press XY controller to swap to Preset "Rhythm". "Rhytm" sets Riverside to pedal preset 2 where Bass is 5.
2. Riverside outputs MIDI CC 14 value 64 from preset change.
3. Param control view now shows CC 14 slider at 64.
4. I adjust Bass control down on the pedal itself.
5. Riverside again sends MIDI CC 14 value.
6. Param control view CC 14 now reflects this value.
7. I use an external MIDI knob controller to send CC 14 value 78.
8. Riverside Bass is now at whatever 78 value represents.
9. Param control view CC 14 is now 78 too.

You could easily use the XY controller to swap between views of each pedal or these combination views. I'd probably configure something like "X = 4 presets" and "Y = 4 param views."

In terms of implementing I think it should require nothing more than blocks that don't have a stored value and having them react to received MIDI CC.

I've tested this out with my Strymon pedals and the Elgato Streamdeck MIDI plugin and was able to track values on it in a similar system I'm proposing.

 

[Whizzinby]

@laxu needs to get added to the payroll beta tester pool.

 

[Enchilada Jones]

Yea! At this point I’m following him and Luminite!

 

[Luminite]

Oh ok, I guess I misunderstood the capabilities of the 2.0 update a bit. That's fine, for now the current features do plenty for my needs.



Global blocks sounds like a neat idea. I'm not quite sure how it work out in practice.

I have a different idea for this:

"Param control"​

What: A further set of views/banks. Visually it's identical to the MIDI blocks view and Preset X/Y list (group of 10 "Param control" views).

Usecases:

1. Realtime control of any param values via sliders on Graviton.
2. Realtime visual of param values otherwise hidden, e.g when presets change on a MIDI controllable pedal.
3. Easier control over secondary params.
4. Visualization of param values regardless of where they are set (Graviton UI slider, MIDI CC from pedal or external MIDI controller).
5. Combined control of your most important parameters of all pedals. E.g reverb mix/decay, delay time/feedback/mix, overdrive gain/tone.

As an example, in a view like this I could build blocks to represent parameters on one of my pedals. When changing presets, I can't see where those knobs are pointing, but if the Graviton receives all the MIDI CCs representing them and can show them on screen, then that's no longer an issue.

Or I could build blocks represent a subset of most important params on any of my pedals so I can quickly adjust e.g the mix on delay and reverb from one place, while tracking those values in the same blocks across pedal preset changes.

I could then use either the pedal controls (which can send matching MIDI CCs), an external MIDI knob controller or the slider on the Graviton UI to adjust these params. Last received value = UI value.

Example scenario:

I have "Param control" view with block "Ch 3 CC 14". On my setup this controls the Bass knob on the Strymon Riverside overdrive.

1. I press XY controller to swap to Preset "Rhythm". "Rhytm" sets Riverside to pedal preset 2 where Bass is 5.
2. Riverside outputs MIDI CC 14 value 64 from preset change.
3. Param control view now shows CC 14 slider at 64.
4. I adjust Bass control down on the pedal itself.
5. Riverside again sends MIDI CC 14 value.
6. Param control view CC 14 now reflects this value.
7. I use an external MIDI knob controller to send CC 14 value 78.
8. Riverside Bass is now at whatever 78 value represents.
9. Param control view CC 14 is now 78 too.

You could easily use the XY controller to swap between views of each pedal or these combination views. I'd probably configure something like "X = 4 presets" and "Y = 4 param views."

In terms of implementing I think it should require nothing more than blocks that don't have a stored value and having them react to received MIDI CC.

I've tested this out with my Strymon pedals and the Elgato Streamdeck MIDI plugin and was able to track values on it in a similar system I'm proposing.

Very cool idea. I was thinking about something like that too (Scene screen ?), letting you build your own custom control surface, separated from the Presets system. Let me rephrase how I understand you idea ?

There are two ways to keep track of all these parameters (both are needed to adapt to the widest range of gears)

• For pedals that can only receive MIDI messages: already implemented in this 2.0 update in the form of Tracking Blocks (by tracking outgoing MIDI messages across Presets changes). The M1 needs to be the master MIDI hub and all patches / parameters changes need to come from the M1.
• For pedals that can also send their status / parameters changes back over MIDI, like Strymon pedals: the same as above but with incoming status update MIDI messages. You can either control these pedals with the M1, or you can twist knobs, change patches on these pedals themselves (or external controllers) and these changes will be updated on the M1 screen (two way synchronization)

These are easy enough, but implementing the UI is the harder bit (so its not too cluttered or intimidating for new users). Options are:

1. All within one screen (MIDI Screen):

In the current 2.0 Software:

• Preset Blocks: MIDI Messages from the current Preset
• Tracking Blocks: MIDI Messages that was sent out across previous Presets changes, filtered to show the latest status / parameters from each pedals.

Next update:

• Receive incoming status updates over MIDI from pedals that have it. If any of these status / parameters update matches with the same status / parameters that already exist in the Tracking Blocks above (ie: Reverb Mix Level, Drive level etc ) > "overwrite" these status / parameters.
• You can tap on any of these Tracking Blocks and edit these parameters on the fly.

2. A separated set of Screens (Param Control) like your suggestion:

• Build you own set of pedals and their parameters to keep track of.
• Switching back and forth from the MIDI Screen by the XY Controller.

3. Or maybe both 1 & 2 ?

 

[laxu]

Very cool idea. I was thinking about something like that too (Scene screen ?), letting you build your own custom control surface, separated from the Presets system. Let me rephrase how I understand you idea ?

There are two ways to keep track of all these parameters (both are needed to adapt to the widest range of gears)

• For pedals that can only receive MIDI messages: already implemented in this 2.0 update in the form of Tracking Blocks (by tracking outgoing MIDI messages across Presets changes). The M1 needs to be the master MIDI hub and all patches / parameters changes need to come from the M1.
• For pedals that can also send their status / parameters changes back over MIDI, like Strymon pedals: the same as above but with incoming status update MIDI messages. You can either control these pedals with the M1, or you can twist knobs, change patches on these pedals themselves (or external controllers) and these changes will be updated on the M1 screen (two way synchronization)

Nailed it!

I hadn't actually thought about that first scenario and it's definitely something to factor in. I am already out of TRS jacks on my Strymon Conduit, but if I wanted to add another one, then I'd have to go for the "split one TRS MIDI in/out to two MIDI out only with Y cable" feature, where e.g my Riverside and Compadre could share the TRS jack but can't report their status back. Having the Graviton as "source of truth" for this is definitely useful, or with devices that can't report their status (like most complex modelers).

I had a hard time understanding the tracking blocks before reading the manual, I thought I had encountered a bug where a "ghost block" was hanging in my preset but it was just the tracking block for one of the pedals. Maybe adding some little icon or something to the corner might help differentiate them?

I guess the idea with tracking blocks is that if you do no changes to that block in another preset, you can still see what was done to it last?

These are easy enough, but implementing the UI is the harder bit (so its not too cluttered or intimidating for new users). Options are:

1. All within one screen (MIDI Screen):

In the current 2.0 Software:

• Preset Blocks: MIDI Messages from the current Preset
• Tracking Blocks: MIDI Messages that was sent out across previous Presets changes, filtered to show the latest status / parameters from each pedals.

Next update:

• Receive incoming status updates over MIDI from pedals that have it. If any of these status / parameters update matches with the same status / parameters that already exist in the Tracking Blocks above (ie: Reverb Mix Level, Drive level etc ) > "overwrite" these status / parameters.
• You can tap on any of these Tracking Blocks and edit these parameters on the fly.

2. A separated set of Screens (Param Control) like your suggestion:

• Build you own set of pedals and their parameters to keep track of.
• Switching back and forth from the MIDI Screen by the XY Controller.

3. Or maybe both 1 & 2 ?

I think #2 should be significantly easier to program when the current value can be based on incoming MIDI or whatever Graviton set last. Then the user doesn't need to care a who lot about where it comes from as long as their adjustment goes through and responds predictably. Pedal returns CC value, or another MIDI controller sends CC -> Graviton (update screen value) -> pass through to pedals, or slider on Graviton).

In #2 you are also more in control over the exact set of parameters with no tracking blocks popping up. For my uses I'd probably build a preset of each of my pedals, where it shows all the main controls and secondary ones. I think the 16 messages supported is enough to cover for most pedals.

Then I'd build some sort of "just the important stuff" control surface with multiple pedals all in one preset/view.

 

[laxu]

As another feature, being able to define min/max values of a block could be useful.

Now the slider is always 0-127, but there can be e.g toggle type parameters with values that are just 0, 1, 2. Or maybe 0-9. Those will always show up as a tiny sliver in the small slider because the scale is up to 127. If min/max was set, you could use the full slider and step function to adjust them and the slider would show e.g "empty, half full and full" for 0-2.

 

[Luminite]

Nailed it!

I hadn't actually thought about that first scenario and it's definitely something to factor in. I am already out of TRS jacks on my Strymon Conduit, but if I wanted to add another one, then I'd have to go for the "split one TRS MIDI in/out to two MIDI out only with Y cable" feature, where e.g my Riverside and Compadre could share the TRS jack but can't report their status back. Having the Graviton as "source of truth" for this is definitely useful, or with devices that can't report their status (like most complex modelers).

I had a hard time understanding the tracking blocks before reading the manual, I thought I had encountered a bug where a "ghost block" was hanging in my preset but it was just the tracking block for one of the pedals. Maybe adding some little icon or something to the corner might help differentiate them?

I guess the idea with tracking blocks is that if you do no changes to that block in another preset, you can still see what was done to it last?

Yes the Tracking Blocks feature kinda works like browser history . When the Graviton M1 is the command center it can track up to 16 pedals, without being limited by the number of MIDI inputs, and doesn't need setting up MIDI loop back.

Also my idea is the XY Controller can also be setup as CC Value + / - control, so it can function as knobs on your pedals, but a bit more convenient since its wireless and you dont need bending down twisting the knobs all the time.

Of course pedals that can their report status back are ideal, as the next update will have that. But if you need to track more than one pedal then you need some kind of MIDI merger box (Upcoming Graviton M2 will have double number of inputs outputs)

I think #2 should be significantly easier to program when the current value can be based on incoming MIDI or whatever Graviton set last. Then the user doesn't need to care a who lot about where it comes from as long as their adjustment goes through and responds predictably. Pedal returns CC value, or another MIDI controller sends CC -> Graviton (update screen value) -> pass through to pedals, or slider on Graviton).

In #2 you are also more in control over the exact set of parameters with no tracking blocks popping up. For my uses I'd probably build a preset of each of my pedals, where it shows all the main controls and secondary ones. I think the 16 messages supported is enough to cover for most pedals.

Then I'd build some sort of "just the important stuff" control surface with multiple pedals all in one preset/view.

Yeah makes sense, a separated Control Surface is more intuitive for that kind of workflow. Next update will have that

As another feature, being able to define min/max values of a block could be useful.

Now the slider is always 0-127, but there can be e.g toggle type parameters with values that are just 0, 1, 2. Or maybe 0-9. Those will always show up as a tiny sliver in the small slider because the scale is up to 127. If min/max was set, you could use the full slider and step function to adjust them and the slider would show e.g "empty, half full and full" for 0-2.

True, many CC parameters are just toggling between a few modes, so a min max scaling is helpful. Added to the list.

 

[Luminite]

Software Update 3.0.0 Beta

Features:

• Big UI overhaul with much faster and easier-to-tap colorful block-style buttons on most screens.
• Intuitive one-tap to select/edit and long tap for a context menu.
• “What You See Is What You Get" XY Controller / Footswitch Pedals visual mapping.

MIDI Editor Screen:

• Long tap on a MIDI Block to Move / Delete / Disable / Send Block.
• Long tap on a Tracking Block to Clear / Clear All.
• Program Change Block now displayed both number and assigned name.

New: Preset Library Screen (Replacing the Bank screen):

• Block-style preset buttons.
• Added Preset colors with 16 selectable colors.
• One tap for direct Preset editing.
• Long tap for Rename / Copy / Swap / Delete / Change Color menu.

New: XY Controller Screen:

• Block-style buttons arranged in the XY Controller layout.
• One tap for direct Preset editing.
• Long tap for Assign Actions menu.
• Reset all to the default button.
• Individual programming for every XY Controller (up to 10).

New: Footswitch Pedals Screen:

• Block-style buttons arranged in the Footswitch Pedals layout.
• 10-switch and 6-switch layout for Luminite F10/W and F6/W pedals.
• One tap for direct Preset editing.
• Long tap for Assign Actions / Learn menu.
• Reset all to the default button.
• Individual programming for each pedal (2 TRS and 10 wireless).

New: Expression Pedals Screen:

• Block-style preset buttons.
• Added Expression Preset colors with 16 selectable colors.
• One tap for Assign / direct Expression Preset editing.
• Long tap for Rename / Copy / Swap / Delete / Change Color menu.

New: MIDI In Screen:

• Block-style MIDI In action buttons.
• One tap for direct Preset editing.
• Long tap for Assign Actions / Trigger menu.
• Reset all to the default button.

Live Screen:

• Added Preset background color on the live screen.

Setlist Library Screen:

• Merged from 3 individual screens into Setlist Library > Setlist > Song menu for more intuitive navigation.
• Block-style song presets buttons.
• One tap on Songs / Setlists for entering.
• Long tap on Songs / Setlists for Rename / Copy / Swap / Delete.
• One tap on Presets for Direct Editing.
• Long tap on Presets for Add / Change / Remove Preset.

Settings:

• Reorganized Settings > TRS menu.
• Added Wireless section for pairing / managing XY Controller and Wireless Footswitch Pedals
• Added TRS Footswitch sensitivity setting.

New Hardware Support:

• Luminite F10W and F6W wireless footswitch pedals.
• Up to 10 can be paired and programmed individually.

User Interface Improvements:

• Improved keyboard with borders and a new special characters set.
• Added a keyboard cursor, which flashes red when the maximum text length is reached.
• Reset to the default name when no text is entered.
• Added the total number of banks / page numbers.
• The clear text button requires a long tap to prevent accidental touches.
• No default name when adding a new parameter name.
• General bugs fixes and performance improvement.

Upcoming Features:

• New Control Surfaces Screen.
• New Status Monitor Screen.
• Parameter Names Filtering.
• Sliders Scaling.

How to Update:

• Go to Settings > Update > Follow the on-screen instructions > Done.
• The update process typically takes 1-2 minutes. If the Graviton M1 hangs up or becomes unresponsive during the update, simply power cycle the device and try again.

User Manual:

• Will be updated in the final 3.0.0 update.

@laxu some of the new features you requested are pushed to the next update due to limited time, but they’re coming for sure

 

[laxu]

Wow, you're a machine! I will give this a spin soon.

 

[quadgear]

• Luminite F10W and F6W wireless footswitch pedals.

How's the latency in wired and wireless modes? For the wired mode, how does the latency compare to an open/close switch (versus some sensing of the resistance/voltage)? Mostly thinking from a looper perspective where the lag between release and press of a mechanical switch can be an issue.

What are the dimension of the footswitches? Are these laid out in two rows or linear (or given your level of innovation, reconfigurable to either via hinge or magnetic coupler )?

 

[laxu]

@Luminite

Some bugs in 3.00 beta:

• My XY controller no longer works. I tried unpairing and pairing it again and it pairs, but nothing works otherwise.
• Clear button when renaming anything does nothing.
• If a PC/CC has a long name, for some reason it shows an overlapping text from the next command.
• In PC/CC "Kpad" view, it renders the number "10" or "0" with a cursor in between if you haven't typed anything. Should not render cursor.
• When using the copy/swap preset functionality, the Cancel and Confirm texts might be cut off a tiny bit outside the screen, at least the Confirm "f" is clipped.

Usability:

• There seems to be no way to activate a preset from the touchscreen in the Preset library or XY controllers view, unless it activates every time you tap on it which also opens the edit view. Being able to edit vs activate was a nice feature in the older list view. Not sure what would be a good way to have both with quick access. I find that once my preset is built, I mostly want to activate it rather than edit it and sometimes I'm a bit lazy to pick up the XY controller for that and would rather tap on screen.
• It's not clear which XY direction is mapped to which preset in the Preset Library view.
• Being able to revert to an older firmware would be a great addition in case problems arise. Maybe ability to select firmware version in the Update screen?

I liked the old list view for presets, it was easier to read than the block type grid where the preset name tends to run a bit weirdly if it's long. So I hope you offer an option to toggle between block vs list style.

I like the new XY Controllers view.

The new hold functionality is good.

 

[yek]

curious, can the X/Y with M1 act as a wireless expression pedal?

 

[Luminite]

How's the latency in wired and wireless modes? For the wired mode, how does the latency compare to an open/close switch (versus some sensing of the resistance/voltage)? Mostly thinking from a looper perspective where the lag between release and press of a mechanical switch can be an issue.

What are the dimension of the footswitches? Are these laid out in two rows or linear (or given your level of innovation, reconfigurable to either via hinge or magnetic coupler )?

Latency in wired mode with the default sensitivity setting is 20ms, adjustable from 3ms - 80ms. (20-50ms is the normal range for most footswitch pedals as debouncing time is needed to prevent jittering)
In wireless mode the latency is 70ms. There is a low latency wireless mode if you keep it plugged into a power source (like a power bank), then the latency is the same with wired mode .

Some specs:

• F10/W dimension: 280 x 85 x 42mm ( 11 x 3.3 x 1.65 inches)
• F6/W dimension: 150mm x 85mm x 42mm ( 5.9 x 3.3 x 1.65 inches)
• 2.55 inches (65mm) footswitch spacing.
• Staggered footswitch height (tall on the back, low on the front).
• Soft touch momentary footswitches.
• Ultra slim profile.
• Premium brushed stainless steel finish w/ laser engraved text.

There are some supply chain problems but they're solved now. Both will be on available to purchase on luminitefx.com soon

 

[Luminite]

My XY controller no longer works. I tried unpairing and pairing it again and it pairs, but nothing works otherwise.

Hmm tested fine on my multiple XY controllers. Im haven’t managed to reproduce this bug. Can you check and unpair everything in the Settings > Wireless Footswitches as well ? If its a hardware bug I’ll send you a replacement.

Clear button when renaming anything does nothing.

Clear button needs a long touch to active (to prevent accidental touch). But I’m thinking about making long touch on the backspace button to clear text instead, if its more intuitive and looks cleaner?

• If a PC/CC has a long name, for some reason it shows an overlapping text from the next command.

I cant reproduce this. You mind taking a pic of your screen ?

• In PC/CC "Kpad" view, it renders the number "10" or "0" with a cursor in between if you haven't typed anything. Should not render cursor.
• When using the copy/swap preset functionality, the Cancel and Confirm texts might be cut off a tiny bit outside the screen, at least the Confirm "f" is clipped.

Noted ! Should be easy to fix

There seems to be no way to activate a preset from the touchscreen in the Preset library or XY controllers view, unless it activates every time you tap on it which also opens the edit view. Being able to edit vs activate was a nice feature in the older list view. Not sure what would be a good way to have both with quick access. I find that once my preset is built, I mostly want to activate it rather than edit it and sometimes I'm a bit lazy to pick up the XY controller for that and would rather tap on screen.

There is a way to implement all 3 functions: one tap to select / second tap (if already selected) to edit / long tap for menu. What do you think ?

It's not clear which XY direction is mapped to which preset in the Preset Library view.

In this update, the Preset Library became the place for editing / managing the shared pool of presets, as it show presets only, not other actions (bank + / - etc) like in 2.0. This change is to make all footswitch pedals and XY controllers being operated completely independent from each other.

I feel the XY Controllers Screen is easier for programming / performing with XY Controllers (and Footswitch Pedals Screen is easier for footswitch stuffs etc) as their actions / preset blocks are arranged to the physical layout. Does it make sense ? But sure I can add arrows to Preset Library as an option.

Being able to revert to an older firmware would be a great addition in case problems arise. Maybe ability to select firmware version in the Update screen?

Good idea! Switchable firmware should be easy to implement.

I liked the old list view for presets, it was easier to read than the block type grid where the preset name tends to run a bit weirdly if it's long. So I hope you offer an option to toggle between block vs list style.

Also good idea. Should be an switchable option just like the MIDI Editor screen.

 

[Luminite]

curious, can the X/Y with M1 act as a wireless expression pedal?

It can work that way with the CC Scroll function, using the XY switches like a joystick ie: up to increase / down to decrease programmed MIDI CC values and send them over Bluetooth.
You can even have coarser / finer scrolling for the same MIDI parameter on each “joystick” if you want

 

[yek]

It can work that way with the CC Scroll function, using the XY switches like a joystick ie: up to increase / down to decrease programmed MIDI CC values and send them over Bluetooth.
You can even have coarser / finer scrolling for the same MIDI parameter on each “joystick” if you want

That's cool. So, with properly configured effects, it should be possible to use the XY switches for typical guitar manipulation stuff, like simulated pitch dives, vibrato, sustain, feedback.

 

[laxu]

Hmm tested fine on my multiple XY controllers. Im haven’t managed to reproduce this bug. Can you check and unpair everything in the Settings > Wireless Footswitches as well ? If its a hardware bug I’ll send you a replacement.

I've tried unpairing/pairing this multiple times now and it pairs just fine after maybe 5-10 seconds, but after that the controller refuses to do anything. I even tried putting it in another slot in the XY controllers settings in case that matters, but no effect.

I don't think it's a hardware problem because I had zero issues with this controller on fw 2.0. Being able to roll back to that version would probably tell.

The Graviton M1 does connect to my pedalboard and tapping on presets does activate them. I also tried powering it via USB vs 9V and that makes no difference either.

I could try a backup and reset and see if it starts working.

Clear button needs a long touch to active (to prevent accidental touch). But I’m thinking about making long touch on the backspace button to clear text instead, if its more intuitive and looks cleaner?

I think a confirmation functionality like "Do you want to clear name? Y/N" would be better, if the name is not empty or default name. Long touch to clear is not very intuitively discoverable functionality.

I cant reproduce this. You mind taking a pic of your screen ?

Picture below. The conditions to make this happen:

1. Add a name for a PC or CC command. The name needs to be max length allowed.
2. Add this PC/CC command to preset.
3. Add a second command to preset, any command.
4. Now the first command with the long name will show part of the name of the 2nd command.

There is a way to implement all 3 functions: one tap to select / second tap (if already selected) to edit / long tap for menu. What do you think ?

I think adding Edit to long tap menu would be good. Then you can edit any preset, not just what is activated.

But I'm not sure about "second tap to edit if already selected". I think that should be for "replay preset", just load it again. Usecase for this would be that I have preset 1 set mostly to my liking, I tweak something and want to just return it back to where it was without first running preset 2, then back to preset 1. On the other hand I can do that from the XY controller instead...

I don't know if your system supports double tap, but that might work. Single tap to activate, double tap to edit?

In this update, the Preset Library became the place for editing / managing the shared pool of presets, as it show presets only, not other actions (bank + / - etc) like in 2.0. This change is to make all footswitch pedals and XY controllers being operated completely independent from each other.

I feel the XY Controllers Screen is easier for programming / performing with XY Controllers (and Footswitch Pedals Screen is easier for footswitch stuffs etc) as their actions / preset blocks are arranged to the physical layout. Does it make sense ? But sure I can add arrows to Preset Library as an option.

Makes sense. My general use after configuration with fw 2.0 was having it in Preset list and then picking a preset with XY or by tapping one of the X1 etc labels. I think that was pretty quick to work with. The new block view does make it easier to tap on something because the touch target is larger, at the expense of label legibility. Having some indicator for which XY direction is mapped in that list would be good.

The XY Controllers view is a good visual aid for remembering what does what, but once you have those memorized, the block or the old list view is clearer for me because it's just a list, rather than having the presets all over the screen. Arrows in the block view would be a good way to support whichever format users prefer.

Good idea! Switchable firmware should be easy to implement.

CME's WIDI firmware updater just gives you a dropdown list of firmwares, with latest on top and pre-selected. That's really all it needs.

Also good idea. Should be an switchable option just like the MIDI Editor screen.

I think this would be best if it can be toggled really quickly somewhere on a case by case basis. Maybe hold function on the bank select when in Preset library?

Btw, being able to name banks would be a good feature. I have enough banks now that I forget which had which presets. I have mine split so that the first two banks are for "control everything at once" stuff, and subsequent banks are for switching between presets on 1 or 2 different pedals.