I’m thinking about building another app or service based on the music community’s needs and pain points. Here’s some questions I’ve come up with: if anyone would like to chime in, maybe we can solve some problems!

1. If you had a magic wand: What’s the one part of the business side of being a musician that you wish would just disappear?

2. What do you use a spreadsheet or notes app for that you wish was a proper tool?

3. What’s something you do before or after every gig that takes more time than it should?

4. What’s the last thing you Googled that you couldn’t find a good answer to about the business side of gigging?

5. If you had a very organized musician friend you could text anytime, what would you ask them?

I’m hoping to find some unsolved problems to sink my teeth into. Thanks in advance for any input!!

This is *not* a post about MIDI Captain MAX for a change!

Paint Audio has released brand new firmware for the Captains! See here: https://paintaudio.com/pages/surports

I haven’t digested all the info yet, but it’s a capital-M Major release, incompatible with the existing code. I’ve actually talked to them recently and it’s a complete rewrite in a different language: from Python to C.

The new code should be more performant and flexible than the older versions. I haven’t tried it yet, but I’m looking forward to it!

Where does this leave MIDI Captain MAX? For the moment, nothing changes. I’m still pushing hard on it and have many unique new features, and OEM parity features, in development. I don’t plan on stopping. In fact, PA has been very supportive and I’m hoping to work closely with them in the future. The challenges will mostly be technical ones that I’m sure will have positive outcomes.

I’m looking forward to where this goes, stay tuned for more. In the meantime, more new MCM features are on the way!

Hi!

I was thinking of buying the Captain 6, but i came across the Morningstar MC6 with its LFOs, which is something that i would love to have the option to use, because i intend to use it with my HX stomp and i want to be able to control the effects with some oscillation and stuff by holding down the footswitch (low to high delay rate, for example).

I made a little research and i didn't find anything related about this concept with the Paintaudio devices.

Do you know something about this?

Thanks!!

Currently in testing for some big features coming to MCM:

1. Keytimes, Short/Long, Multiple Messages
2. Enhanced MIDI Thru

Parity features (meeting or exceeding OEM functionality)

• Keytimes
• Short & Long Press
• Multiple messages per press

The three parity features are all rolled into the Keytimes functionality. In other words, to utilize short/long press or multiple messages per press, you configure them via the Keytimes setup. It makes sense in the UI.

Existing button modes Toggle, Momentary are not touched, this is purely additive. The exception is if you happened to have Keytimes configured currently, you’ll have to roll it over to the new config. The old Keytimes didn’t really work right anyway.

New feature

• MIDI Thru 2x2 matrix

All permutations of midi-thru are now supported:

5–Pin (DIN) -> 5-pin
DIN -> USB
USB -> USB
USB -> DIN

The GUI Config Editor gets a 2x2 button grid to enable/disable any combination of MIDI Thru you want. All default on except USB->USB which will likely cause feedback, but it’s there if you need it.

Hello, I bought a Midi Duo for the purpose of taking the Duo's Midi Out 5 pin into the Midi In of the MIDI Captain. This way I can have 12 keys. The MIDI Captain, however, is not carrying on the MIDI commands from the Duo to my device.

I am using Supermode on the MIDI Captain and I have set each Page's option to:

# on / off
midithrough = [on]

The Midi Captain is working fine otherwise, and if I plug the Duo's MIDI out direct to the device, it works. Thanks for any help!

I just spent a few hours editing keys for both devices only to find there is no pass thru!

Hi All,

I am having difficulty implementing an independent toggle using long and short press on a single switch in Supermode.

I have attached the code below. The problem is that the long and short actions interact and interfere with the toggling action.

For example:

A short sends cc value 127 (Delay on)

A long sends cc value 127 (Reverb on)

Next Short should send cc 0 to turn off Delay but it sends cc value 127 again.

The same happens with long toggle sequence.

I can see that keytimes might cause this behaviour.

Can anyone tell me how to achieve the desired independent toggle action?
Is is possible in Supermode

"page0 code snippet"

# Short Press: Toggles Sht CC 28 + Lg CC 36(Delay + Reverb)

[key3]

keytimes = [2]

ledmode = [normal]

ledcolor1 = [0x00ff00][0x00ff00][0x00ff00]

ledcolor2 = [0x666666][0x666666][0x666666]

# DELAY1 ON/OFF

short_up1 = [1][CC][28][127]

short_up2 = [1][CC][28][0]

# REVERB ON/OFF

long_up1 = [1][CC][36][127]

long_up2 = [1][CC][36][0]