v1.12.0 Beta

[mcascone]

🧪 Beta Release - Feature complete, undergoing final testing.

What's Changed

• Bundle CP 7.3.1 .uf2 + Reflash CircuitPython GUI flow (Bundle CircuitPython 7.3.1 .uf2 + add "Reflash CircuitPython" GUI flow #134) by @mcascone in Bundle CP 7.3.1 .uf2 + Reflash CircuitPython GUI flow (#134) #135
• Surface reflash button in the no-device empty state (Bundle CircuitPython 7.3.1 .uf2 + add "Reflash CircuitPython" GUI flow #134 follow-up) by @mcascone in Surface reflash button in the no-device empty state (#134 follow-up) #136
• Force sync_all on bootloader copy + Cancel + watchdog (Bundle CircuitPython 7.3.1 .uf2 + add "Reflash CircuitPython" GUI flow #134 hotfix) by @mcascone in Force sync_all on bootloader copy + Cancel + watchdog (#134 hotfix) #137
• Gate reflash button on RPI-RP2 detection (Bundle CircuitPython 7.3.1 .uf2 + add "Reflash CircuitPython" GUI flow #134 polish) by @mcascone in Gate reflash button on RPI-RP2 detection (#134 polish) #138

Full Changelog: v1.12.0-beta.5...v1.12.0-beta.6

First: Backup!

Before doing any of this, if you haven't already, please back up your existing config and firmware to a safe place for recovery or to revert to OEM firmware:

1. Mount the device to your computer. You may have to hold down Button 1 / KEY0 to force it to mount.
2. Copy all contents of the device to a safe place on your computer.

Installation

Once MIDI Captain MAX is installed, manual firmware updates are no longer needed. The GUI Config Editor now includes a Firmware Installation section at the bottom of the window. It shows the currently installed firmware version and the bundled version available to install.

You can download either:

• The appropriate Config Editor installer for your OS: .dmg for macOS, .exe or .msi for Windows. The Config Editor includes the bundled firmware, so you don't need to download it separately, or
• The MIDI-Captain-MAX-v1.10.0-complete.zip package if you want the GUI and the firmware as separate packages.
  For example, if you need to use the deploy script for the first install, or for an unsupported OS, this package includes everything you need. (The GUI still includes the bundled firmware; the zip is just for convenience if you want to use the deploy script instead of the GUI installer.)

Updating an Existing MIDI Captain MAX Install

1. Connect your MIDI Captain via USB and power it on.
   • The device may mount as CIRCUITPY or MIDICAPTAIN.
   • If no drive appears, hold switch 1 / KEY0 while plugging in USB.
2. Install and open the MIDI Captain MAX Config Editor.
3. Scroll to the Firmware Installation section at the bottom of the app window.
4. Click Install Firmware.

By default, the installer preserves your existing config.json. Enable Reset config.json to bundled defaults only if you want to overwrite your current settings with the default template.

The app will copy the firmware, reload the device, and update it in place.

First Run on OEM Firmware

If your MIDI Captain is still running the factory Paint Audio firmware, the Config Editor may show OEM (no VERSION.txt file).

In many cases, the first install still requires a one-time bootstrap because the OEM firmware does not provide a MIDI Captain MAX config.json for device-type detection.

1. Hold Button 1 / KEY0 while plugging in USB to enter the OEM USB settings mode. A MIDICAPTAIN drive should appear.
2. Download and extract MIDI-Captain-MAX-v1.10.0-complete.zip from the Assets section below.
3. Run the included deploy script once with your device type:
   
   NOTE: only enter the desired device type, not the full list of options.
   
   For example, if you have a Nano 4, run ./deploy.sh --device nano4.
   • macOS / Linux: ./deploy.sh --device std10|mini6|nano4|duo2|one1
   • Windows PowerShell: .\deploy.ps1 -Device std10|mini6|nano4|duo2|one1
4. Reconnect the device and open the MIDI Captain MAX Config Editor.
5. From then on, use the Firmware Installation section in the app for future updates.

Recovery

If anything goes wrong, it is fully recoverable:

1. Mount the device.
2. Erase the contents.
3. Restore your backup, or re-run the first-install steps above.

---

This discussion was created from the release v1.12.0-beta.6.

[M1DHB]

Installation Issues:
Midi-Captain 10 Gold - Supermode 4.0 only initially installed - Windows 11

The deploy script won't run because it is unsigned
I get around this by copying the contents to my own deploy script deploy.ps1 this does run but with errors.
see the screenshot below.

Note:
I've usually installed MC-MAX by deleting contents of the mounted MIDICAPTAIN drive and copying all the contents of the
midicaptain-firmware-v1.12.0-beta.6 folder to the empty MIDICAPTAIN, Ejecting the drive and rebooting the MidiCaptain.

[mcascone]

Thanks for this, I'll try to ship it with a fix to require no extra touches.

[mcascone]

logged as #140

[mcascone]

try this fix release: https://github.com/MC-Music-Workshop/midi-captain-max/releases/tag/v1.12.0-beta.8

note: does NOT include the fix in the beta.7 build

[mcascone]

testing on my windows VM, finding some bugs - stand by

[mcascone]

this should be resolved in v1.12.0-beta.11, although the GUI installer is highly preferred

[M1DHB]

MIDI Captain MAX Config Editor v1.12.0-6
Saving changes to the device works OK but "Restart Device" from Config Editor doesn't work cleanly.
The MidiCaptain Screen displays some code which sticks there even if you press buttons. (see attached photo)
Manually rebooting the MidiCaptain clears it ok

[mcascone]

I've only seen this when re-flashing the CircuitPython OS code. It's possible the Windows serial port drivers aren't playing nice with the reset commands. I'll test it better on Windows!

[mcascone]

logged as #141

[mcascone]

i see it intermittently too; #141 open; not a blocker, moving forward with v1.12.0 release

[M1DHB]

Expression Pedal Spurious Outputs:-
With the EXP1 & 2 Enabled but no pedals connected outputs gradually ramp up.
This doesn't happen on the OEM 4.0 FW

[mcascone]

Hm, this is an odd one. I admit i do most of my testing on a NANO4 which doesn't have exp ports. I'll look into it!

[mcascone]

logged as #142

[mcascone]

Plugged in my STD10, no exp pedals in, i see it too, on only one of the ports. I'm seeing a thrashing, not a gradual ramp, although it looks like it is indeed increasing slowly over time. in other words the thrashing happens as it's about to increase to the next digit. Clearly a debounce/noise issue.

==> They're noisy. It's likely Paint Audio has some kind of debouncing/tolerance in their code to mitigate it.

Thinking about it more, I have also seen this with the exp pedals in. Meaning, even with them connected, they were noisy. As a result there are two existing workarounds:

in the Expression Pedals section

1. Set the Threshold to 2.
2. Disable them altogether with the checkboxes.

Neither of which are perfect fixes, but they are workarounds for now. #142 remains open.

[M1DHB]

Keytimes - Label not displaying correctly on small display.

I've attached a config.json that that works OK in regard to the Midi outputs however on Button/Key 5 and 10 the Labels on the small display only show while Short Press is activated. Once Long Press is activated no label is displayed for either Short or Long Presses.

Button/Key 8 has Keytimes with Short and Long and the Labels work ok.

config.json

B5-B10 Short

B5-B10 Long

[mcascone]

My guess here is you have the Long led setting to either Off or DIM. It can be hard to see DIM slots on the screen. Let me know if i'm off base here.

[mcascone]

logged as #143

[M1DHB]

You were correct regarding the Dim & Bright however there is an issue with the display label of Shorts following Long press.
I think this is mentioned in #143. but I've attached a sequence of pictures for clarity.
Initial State

1st Short

2nd Short

1st Long

2nd Long

3rd Short

[mcascone]

@M1DHB Thank you SO MUCH for your input! These are real issues, so i'm glad I put this out there for real-world testing! I'll get to them asap!

[M1DHB]

I just listed issues, a lot of good things just work :)
Thank you for your work.

[mcascone]

@M1DHB Try this fix: https://github.com/MC-Music-Workshop/midi-captain-max/releases/tag/v1.12.0-beta.7

[mcascone]

I've tried both beta7 & beta 8 re the keytimes label issue. I still end up stuck with the Long Press label. It never switches back to the short press.

I really thought I'd tested this one thoroughly. Let me take a closer look. Thanks for your patience.

[mcascone]

for the record it's specifically only beta.7 that has any kind of fix for this, beta.8 is unrelated.

[M1DHB]

I have tried again, upgrading from beta6 to 7 using the config editor but I still get sticky long press labels. I'll try again when I get some time.

[mcascone]

are you updating the firmware too, via the UI?

[M1DHB]

Yes, I even reset the config and recreated the PUP & BUP buttons using the Config Editor.

Ive attached a zip of the MIDICAPTAIN contents and a screenshot of the Config editor Firmware report.
MC-10-b7.zip

[mcascone]

@M1DHB v1.12.0-beta.9 has fixes to test for both the keytimes-dim and the powershell install issue. Please test when you can! THANK YOU SO MUCH IN ADVANCE!!

https://github.com/MC-Music-Workshop/midi-captain-max/releases/tag/v1.12.0-beta.9

[M1DHB]

MCM beta9 test procedure.##

1 install & test OEM FW4.0 - Done
2 uninstall Config Editor - done
3 download & extract MIDI-Captain-MAX-v1.12.0-beta.9-complete
4 Deploy --
ran deploy.bat from
MIDI-Captain-MAX-v1.12.0-beta.9-complete\midicaptain-firmware-v1.12.0-beta.9>deploy.bat -Device std10
Ran clean - Done

4b Eject MC and reboot manually.
##Note When I install using the deploy it leaves some old stuff like the supersetup files intact.
I personally prefer to delete everything and just copy the fresh files. ##

5 Install config editor - Done

6 Use config editor to create PUP & BUP long and short
7 Save to device and eject using Config Editor (not restart)
8 manually reboot
9 test PUP & BUP :( Long label always sticks.

MCM beta9 test procedure Second Try.

(Prelim - copy newly created config.json from first try to firmware folder)
1 Delete MC Contents
2 Empty Recycle Bin
3 Copy midicaptain-firmware-v1.12.0-beta.9 to MC
4 Eject and Reboot
5 test PUP & BUP :( Long label always sticks.

config - Copy.json

[mcascone]

Thanks for this. I'll keep digging. Can you help me understand, why are you choosing to install the fw manually, vs using the GUI? Try downloading the .exe or .msi installer instead of the -complete. The firmware is baked into the app's contents. First install i understand, but subsequent installs should all be doable via the gui. (And i've got a branch going to make even the first install completely doable via the GUI.)

[M1DHB]

I usually prefer the delete and copy process because I'm in control and can be sure the right files are copied.
I'm especially uncomfortable if any of the OEM files are left in case there may be unintended interaction.
When I get a chance I'll install the latest update using the .msi only and GUI. I wasn't sure where it picked up the firmware from.

[mcascone]

ok i think i found it, working on fix

[mcascone]

Ok - try this one: https://github.com/MC-Music-Workshop/midi-captain-max/releases/tag/v1.12.0-beta.9

Use the msi/exe installer, upgrade the firmware with that (make your life easier), then try your config. 🤞

Root cause: long_label or short_label precedence + long_label never cleared once set → first long press stuck the long label/color on every later short press. Order-dependent (long→short), which is why it dodged my testing.

Fix: Last-fired class owns the render (LED + label).

Behavior now: Idle → button label. Short → short label (or button label if none). Long → long label. Long then short → short label (was stuck on long). LED follows same rule.

[M1DHB]

Are you sure? "Ok - try this one: https://github.com/MC-Music-Workshop/midi-captain-max/releases/tag/v1.12.0-beta.9"
We had beta9 before.

I tried it anyway like this "Use the msi/exe installer, upgrade the firmware with that (make your life easier), then try your config. "

Not Good - Long then short → LONG label
long_label never cleared once set
Sorry :(

[mcascone]

madre mia, you're totally right. Git worktree mistake. stand by. beta.10 building now

[M1DHB]

Happy Days

I Used the beta10 msi installer, clicked "Install Firmware" with "Reset json Unchecked)
Ejected using the Config Editor, Rebooted manually and now it works :)

I'll try some more combinations of long & short including Tap/Tuner when I get some time.

Thank you for the Fix

[mcascone]

YES!!! Thank you so much for you patience and testing!

[mcascone]

Two of the above issues are resolved: #143, #140.
Two will remain open in v1.12.0: #141, #142. Thanks @M1DHB for your incredible support!