I have seen a recent ish product called a ScribbleStrip that is interesting, yet the marketing does not convey clearly its use cases.
In either case, it brought to mind whether I can use the MC6Pro to read the CC output from a given pedal. Because the ACS1 operates with switches etc…and they have no functional preset manager it becomes a a challenge to set parameters precisely especially when running 2 different amps in Stereo.
If a person knew what value they are setting things at, then they could easily create a preset without a preset manager. Point being, I am asking if anyone knows how to set up a MC6Pro preset or bank to read a pedal’s output? If this isn’t possible it might be something worthwhile. @james
Many Walrus pedals have 128 preset options but zero way to manage them or name them.
For whatever its worth. I asked Gemeni and here was it’s response:
How to use the MC6 Pro as your “Screen”
Even though the ACS1 won’t send the data to the MC6 Pro, you can set up the MC6 Pro to be the master controller for your Gain. This effectively gives you the visual feedback you’re looking for:
Expression Pedal: Connect an expression pedal to the MC6 Pro and map it to CC# 21 (Gain) for the ACS1. As you move the expression pedal, the MC6 Pro can display the position/value on its screen, giving you a real-time visual of your gain level.2
MC6 Pro MIDI Monitor: The MC6 Pro does have a MIDI Monitor feature (usually accessed via the menu or the desktop editor), but it only shows messages arriving at its MIDI In port. Since the ACS1 doesn’t send CC data, this screen will remain blank when you turn the ACS1’s knobs.
Quick Reference: ACS1 MIDI CC Map
If you decide to control the ACS1 from the MC6 Pro to get that visual feedback, here are the primary CC numbers you will need:
Parameter
MIDI CC #
Range
Volume
20
0-127
Gain
21
0-127
Bass
3
0-127
Mid
14
0-127
Treble
15
0-127
Room
22
0-127
A Note on the ACS1 MKII
If you ever upgrade to the ACS1 MKII, that version includes a built-in OLED screen.3 While it still won’t send MIDI CC data back to your Morningstar, the screen on the pedal itself will show you the exact parameter values as you turn the knobs, solving the “blind adjustment” issue.
This is somewhat interesting, as I could feasibly get a knob midi controller, and just bypass the knobs on the pedal.
Would be really nice for the midi converter feature to trigger any preset. That triggered preswet could use the “Preset Rename” feature to display text (or an enhanced version that can change text in other areas of the Pro’s display).
Alternatively, the Pro could add support for a scripting language (e.g., Lua) and people could go wild with this and other custom features.
Interesting, anyone who buys midi pedals without screens is either fine with just a few presets or they have a midi controller. If the midi controller can be the brain for those pedals then that changes the game, although a dedicated UI for editing patches is ideal for those of us who dial in sounds at a computer, using the MC products is definitely second best. Honestly with AI it is super easy to write apps and such. I could make an app with knobs and bypass the expression hardware altogether.
I agree the MC Pro’s can do a lot more and be the brain for your pedalboard.
Dare I digress….
Coincidentally the last three midi devices I’ve purchased have more advanced capability to script, map/filter messages, or customize/roll your own firmware.
Electra One Mini (knobs and display with Lua script)
Retrokits Retrovision (niche Kemper display with script file to convert messages)
Midi Captain Nano (4 button and tiny display with PySwitch Python firmware that is very hackable but runs out of memory too easily).
I’d really like a Kemper Player display mode for my MC Pro that’s customizable. It would be pretty easy to script (which is my plan for the Electra One .. buy that device serves a different use case for me).
So, the unfortunate thing with the acs1 and similar pedals is they do not transmit midi.
I don’t use a midi foot controller as I do primarily studio work and so use midi designer on an iPad to manage my pedals and their presets but the philosophy would generally be the same.
What you need are presets that will set CC values without transmitting them on recall while still sending the required pc change, then transmit ccs when changed, and use the midi controller as “preset management”-storing all your dummy values and names for presets. You’ll want to make all your changes from the controller if at all possible or use a potentiomer style midi controller that can transmit to both the acs1 and foot controller (I assume there must be a setting on the pedal controller to not send on receive so you avoid loop issues).
Hope this helps in some way and I apologize I can’t help in this specific environment.
Once a preset is dialed in it is easy to save to the PC slot using the Morningstar. I was just looking for visual feedback on the midi# parameters 0-127. It seems like software is an easy choice, I don’t need any physical pedals or whatnot.
I’ll probably make an app that keeps track of the information for me. I’ll look into the MIdi Designer you mentioned.
I definitely need to look into that. Was that easy to put together? I’m actually more concerned with my M1 than my ACS1 because I need a relevant organizational system for Effect type, then I can refer to it when I’m setting up my pedalboard presets on the Morningstar.
It included a bit of trial and error to get it to recall without transmitting midi. Definitely dig through tutorials on the forum and look at examples. It’s not resource hungry but is only limited to 16 channels of midi so even with multiple ports you are a little stuck (I use filtering on my cme hubs/midi USB cables connected to morningstar midi boxes to circumnavigate this).
I am building an app that does exactly what is needed with minimal fuss. It’s too big of a problem in the pedal world to leave it unsolved in a direct way. I’ll let you know when it’s ready. Thanks for sharing your solution with MIDI Designer.
