May be of use to McMillen 12 Step owners

[tauzero]

I went onto the McMillen website for the first time in ages yesterday, and found that there's now an updated 12 Step, the 12 Step2 (as opposed to the 12 Step V2), and an updated editor which caters for both the 12 Step and the 12 Step2, and new firmware, and a new manual. The editor proved a PITA when I installed it on my laptop as it started up well down and to the right on my 1920 x 1080 display. This was extra special PITA as the first run pops up a window which I couldn't read properly (it's about getting your settings from a previous installation) and I had to blindly press Enter, which resulted in not getting the previous settings loaded. With the window positioned fully to the left and top, it was still too tall to see all of it, with no scroll bars and no resizing, so the programmers (for want of a better term) really don't have a f*cking clue.

 

Anyroadup, I did load up the new firmware, and copied my settings across (go into the presets directory in the old installation and copy 12Step.json into C:\Users\<username>\AppData\Roaming\KeithMcMillenInstruments\12 Step Editor). And I've just had a bit of a play on my desktop and it's OK. The "keyboard" display for note selection is still absolutely horrible, it takes me about a minute per note to set note values using it.

 

So: probably worth getting the new editor for the firmware update, but keep the old installation until you're sure you'll be able to use the new one. McMillen  are rebranding as Muse Kinetics following the unfortunate demise of Keith McMillen - new website is https://www.musekinetics.com/. Whether they'll employ better coders than the monkeys who came up with the 12 Step editor remains to be seen.

[tauzero]

PS: I reported the installation issue to McMillen and they've just responded saying that they've identified the bug and will be fixing it shortly. A total rewrite using proper Windows APIs would be a good idea but doesn't look like it'll happen.

[Woodinblack]

Is that new firmware for the 12 step? Any idea what the updates are? I must admit to never actually having an issue with the editor, it always worked fine with me, or is this the new editor? Probably wouldn't update then if that was the case.

[tauzero]

The new firmware is for the 12 Step as well as the 12 Step2. You can install it somewhere that won't overwrite your current editor installation, just specify the installation location when you run the installation.

 

Changes (in Content\CHANGELOG.md on installation):

 

#### 12 Step Editor and Firmware Changelog

### Editor 3.0.5, Firmware 1.0.4 (2024-06-24)
- New Features/Changes:
    - Added global key on/off thresholds to settings tab. 
        - On threshold determines how much pressure is needed to turn a key on
            - A higher on threshold setting requires more pressure to turn a key on and reduces unintended notes
        - Off threshold determines when an active key is turned off.
            - A higher off threshold setting prevents stuck keys and allows more rapid playing
            - A lower off threshold setting prevents double triggering
    - Reduced key-on latency and improved key sensitivity, especially for black/accidental keys
    - Keys pressure now automatically scales/calibrates based on the peak key value received since power on
- Bug Fixes:
    - Fixed an over-indexing error that caused unexpected behavior under very specific conditions 

### Editor 3.0.4, Firmware 1.0.3 (2024-04-08)
- Bug Fixes:
    - Program Changes received from expander port (legacy 12 Step1) now control presets
    - Pitch Bend messages sent to CV interface now properly scale with calibration values
    - Program Change RX channel now correctly updates NRPN messaging for CV calibration
    - Firmware update process throttled to 256 bytes every 4ms, bootloader locked

### Editor 3.0.3 - not released to public

### Editor 3.0.2, Firmware 1.0.2 (2024-03-06)
- Bug Fixes:
    - Added extra steps to bootloader installation process (unplug device, relaunch app) to account for Windows MIDI drivers refusing to let go of device ports during reboot

### Editor 3.0.1, Firmware 1.0.2 (2024-02-29)
Major release update for 12 Step2
- New Features/Changes:
    - 12 Step2 Editor UI additions:
        - Added CV Out routing controls to MIDI Tab
        - Added Backlight Brightness control to Settings Tab
        - Replaced key frames and setlist button PNGs with SVGs (much cleaner)
        - Windows scaling and sizing fixes for combobox widths and fonts 
    - Added Expression Pedal Calibration to the Editor Hardware menu
        - User can define min/max values to scale expression pedal input to output
        - Added table assignment (linear, exponential, log, etc). This is a global setting that will always be applied to the expression pedal before preset modlines.
    - Added CV Calibration to the Editor Hardware Menu
        - User can calibrate Octaves (6 values per CV out for 0/1/2/3/4/5V), or Notes (calibrate every note individually)
    - Complete overhaul of USB MIDI driver. 12 Step now uses the same driver as KMI's latest products.
        - 12 Step2 uses new USB MIDI port names: "12 Step Control Surface", "12 Step TRS MIDI Out", "12 Step CV Out"
        - Legacy hardware (12 Step1) uses old port names "12 Step Port 1" and "12 Step Port 2", this retains backwards compatibility with older editors.
    - Added Bank MSB messages for each voice
        - The previous "Bank" message was for the LSB (CC32), and was always enabled if Program Changes were enabled. Now all three messages can be individually enabled as needed.
        - This feature replaced Pitch Bend Range. 12 Step now sends the full 14bit pitch bend range, so users should configure pitch bend range at the receiving MIDI device.
    - Added Program Change Preset Control dropdown to Settings tab. 
        - This is a global setting for all presets that determines which MIDI channel 12 Step listens to for Program Chance, CC, and NRPN commands. 
    - Presets are now stored in the OS Application Data Directory rathern than the application directory/package. 
        - A README.PDF has been included in the MacOS and Windows installation files that explains how to back up presets from previous editors before upgrading.
        - When loading editor 3.0.0 for the first time, you will be prompted if you want to import your old presets or load factory defaults.
    - Updated Ableton remote script for Live11/python3.
    - Settings tab sliders now display actual values
    - 12 Steps now report serial numbers to the USB Host. 12 Step2 units have unique serials burned into memory at the factory.
- Bug Fixes:
    - All preset data, settings, and calibration information is now preserved even after a firmware update
    - Fixes to UI scaling for both MacOS and Windows
    - Improved analog sensor scanning and removed some crosstalk noise present when pressing multiple keys
    - Increased KeyOn and KeyOff thresholds to clean up false triggers and stuck notes
    - Global Transposition is now preserved when settings updates are sent from the editor
- NOTE FOR MACOS USERS
    - MacOS Sonoma 14.1.1 has a known bug where CoreMIDI misroutes port data to devices with asymetric USB MIDI port configurations (ie 1in 3out). This means that data sent to the 12 Step2 TRS MIDI and CV out ports will fail. This bug has been fixed in the developer 14.4 beta release. 

### Editor 2.1.0, Firmware 0.3.0 (2022-09-30)
- New Features/Changes:
    - Overhauled editor MIDI backend using RtMidi, now builds/runs on modern operating systems.
    - Added a MIDI THRU port to route incomming 12 Step midi to a virtual port, workaround for Windows inability to share MIDI ports with multiple applications
- Bug Fixes:
    - Sensitivity Sliders
        - 12 Step now reacts to slider adjustments in realtime, you no longer have to send the setlist for them to take affect.
        - Renamed the "Select Sensitivity" slider to the more accurate "Select Button Hold Time", and fixed a bug where a 0 value would disable it
    - Replaced old low-res UI images with vector fonts.

### Editor 2.0.0, Firmware 0.2.8 (2014-09-01)
- New Features/Changes:
    - Entirely new UI & design.
    - Support for Windows 8 & Mac OS 10.9 (Mavericks).
    - New preset management features:
        - Copy / Paste preset
        - Import / Export preset
        - Save As & Delete preset
    - Enable and disable cc7 127 on preset change option.
    - Added the ability to control 12 Step LEDs from the MIDI Expander.
    - Note entry is now editable from both the full keyboard and the 12 Step keyboard layout.
    - Clearing all keys at once is now possible for note entry.
    - Presets are now numbered 1-64 instead of 0-63.
    - Added a global velocity override function that turns off velocity response for all presets.  Velocity will be a full 127 value on every note if velocity override is enabled.
- Bug Fixes:
    - USB buffer problem causing MIDI input to crash 12 Step is resolved.
    - Pitch bend can now return to true center when used with tilt source.
    - Connectivity issues between 12 Step and Windows 8 resolved.
    - Preset corrections.

 

[Woodinblack]

Would say they have been busy although it took them almost a decade without doing anything (and I suspect that is the one I have!)

 

I use mine in every gig, but i haven't actually changed the setup on it for many years. I have a few songs that I play chords, and a few songs with just using it as a straight keyboard. I probably should get round to making chords for some other songs now we lost our keyboard player.

[tauzero]

I haven't been using mine, but there's a couple of songs we're just about to start on that it would be useful for, and I may go back over the set and see if there's anything we already do that I can use it for.

[Eric Bateman]

Hi @tauzero, I'm the monkey that you're referring to.

 

Why all the hate? I've spent many hours of my life trying to improve the KMI products and editors. When I started, some of them wouldn't even run on a modern computer without hacks and workarounds.

 

"A total rewrite using proper Windows APIs"

 

That would be another several hundred hours of work, you're talking tens of thousands of dollars in engineering time. 

 

I'm sorry you don't like my work, but believe me when I tell you that the editors and firmware are in a way better state than they were when I took over the project. Check out this screenshot, this is what the old 12 Step 2.0 editor looks like if you try to run it on Windows 11. 

Edited February 7 by Eric Bateman

[tauzero]

And this is what the current version looks like when run on my laptop:

 

 

That is the full screen shot. Can't resize it. So it's unusable on the laptop (1920x1080 screen). Nobody thought to test it on something that size?

 

The "keyboard" along the bottom for note selection is horrible.

 

You do have my sympathy as in the past I've inherited some pretty horrible code and I know what it's like. However, I had an email about the issue with size telling me it would be fixed in a couple of days and I haven't seen a new version turn up yet.

[Woodinblack]

14 minutes ago, tauzero said:

And this is what the current version looks like when run on my laptop:

 

 

 

That is the full screen shot. Can't resize it. So it's unusable on the laptop (1920x1080 screen). Nobody thought to test it on something that size?

 

Seems very much that you have your desktop scaling set to something higher than 100%, windows is a bit shit with that sort of thing. Temporarily put it to 100% in the display control panel, and I guess it will probably work.

[tauzero]

10 hours ago, Woodinblack said:

 

Seems very much that you have your desktop scaling set to something higher than 100%, windows is a bit shit with that sort of thing. Temporarily put it to 100% in the display control panel, and I guess it will probably work.

 

Thanks, that was the solution (scaled to 150%). Completely overlooked that.

[Eric Bateman]

On 07/02/2025 at 18:21, tauzero said:

You do have my sympathy as in the past I've inherited some pretty horrible code and I know what it's like. However, I had an email about the issue with size telling me it would be fixed in a couple of days and I haven't seen a new version turn up yet.

 

We did release an update (3.0.7) a few days ago, but it wouldn't have addressed your scaling being set to 150%.

 

On 08/02/2025 at 05:37, tauzero said:

 

Thanks, that was the solution (scaled to 150%). Completely overlooked that.

 

Right, so again I have to ask - why all the hate? Please re-read your original post from my perspective and think about your condescending (and downright insulting) language and tone. All because you had your scaling cranked up too high.

 

I found your post because I was googling for background info to complete a blog post that I was writing to help legacy customers, in some cases people who bought a $350 product from us 12 years ago, use our software. If I was required to submit a revenue neutral/positive business plan to justify my hours doing this work, I'd be denied. I do it because I love our products and I want our legacy customers to trust us. At times it can be a very thankless job because most of the feedback we get are posts like this, either on forums or social media. Please take more care in the future. 

 

 

[tauzero]

33 minutes ago, Eric Bateman said:

Right, so again I have to ask - why all the hate? Please re-read your original post from my perspective and think about your condescending (and downright insulting) language and tone. All because you had your scaling cranked up too high.

 

 

Yes, sorry about being intemperate but the lack of resizing was a serious frustration. And as far as that lack of resizing goes, I had problems installing a previous version of the editor because it didn't like being inside another folder within Program Files, and also raised the issue of resizing. In an email dated 2023/07/27, part of Tom Ferguson's response (after providing the solution) was

 

"The window resize and screen resolution issues is a known bug that we've addressed in the Mac version of the Editor, and we will be porting that over to the Windows Editor in an update that is scheduled to come out next month."

 

So should I have expected the resizing to be present in a release 18 months after that response?

 

Also, I'm not sure if there is an issue with the latest firmware. Since updating, I keep getting random keypresses (nothing touching the keys, a note just comes on randomly). Happens every few minutes. Didn't happen before the firmware update. I have submitted a ticket.

[tauzero]

PS. If it's any comfort, everyone on Basschat will be pointing at me and laughing.

[tauzero]

And I should add, Eric has answered my ticket, there has been a software and firmware update, and it seems to be behaving - I'm leaving it running for a couple of hours and if there's no random notes in that time, I'll pronounce it cured.

[Eric Bateman]

45 minutes ago, tauzero said:

 

Yes, sorry about being intemperate but the lack of resizing was a serious frustration.

 

I totally understand and have been there myself. I will even admit, in the past I've been "that guy" when it comes to contacting support. 

 

The screen resolution "bug" you referenced with Tom was actually the facelift we did when we released the update for 12 Step 2, mainly switching to vector graphics and increasing the size so that it didn't look like a postage stamp at 100% scaling. I don't remember when that was released, but it was in 2023. 

The scaling issues on Windows are largely to due to the editors being written before HD displays were commonplace, and before the release of Windows 10/11, there wasn't and OS scaling to worry about. 
 

For reference, the QuNexus, 12 Step, SoftStep, QuNeo, and K-Mix editors were all written in Qt with no layouts, no methods to rescale or resize, and ton of explicit code to handle all sorts of UI corner cases. None had been updated since 2016 when I joined the company, and I had zero prior experience with Qt. My priority in bringing them up to date has been backend cleanup and functionality, consolidating snowflake code into shared libraries, and fixing bugs. We did add a lot of features into QuNexus and now the Steps with their re-release, so there's been cleanup and consolidation there as well. All of this work has been largely in my spare time, even with the re-releases these products are not creating enough revenue to justify a ton of engineering time. So with the UI, rewriting things to be re-sizeable was never an option, I had to pick a resolution that would work well on different size screens, but with Windows the scale factor is always going to affect how things look. 

 

 

8 minutes ago, tauzero said:

PS. If it's any comfort, everyone on Basschat will be pointing at me and laughing.

 

...only a little bit :). 

 

6 minutes ago, tauzero said:

And I should add, Eric has answered my ticket, there has been a software and firmware update, and it seems to be behaving - I'm leaving it running for a couple of hours and if there's no random notes in that time, I'll pronounce it cured.

 

The random note issue you found was a bug introduced in fw 1.0.5. I made a longer post in the facebook group, but basically we had some users complaining that the latency on the key action was slow, so we naively put out an update that sped things up. It tested fine on the new hardware (which had many improvements in the PCB), but some legacy users (and from your support ticket it looks like you bought your 12 Step 9 years ago) ended up having phantom notes triggered by electrical noise. 

 

So, lesson learned - never listen to customer feature requests (sarcasm). But we did find a fix (1.0.7) that solved the noise and kept the latency low.

[tauzero]

29 minutes ago, Eric Bateman said:

The random note issue you found was a bug introduced in fw 1.0.5. I made a longer post in the facebook group, but basically we had some users complaining that the latency on the key action was slow, so we naively put out an update that sped things up. It tested fine on the new hardware (which had many improvements in the PCB), but some legacy users (and from your support ticket it looks like you bought your 12 Step 9 years ago) ended up having phantom notes triggered by electrical noise. 

 

So, lesson learned - never listen to customer feature requests (sarcasm). But we did find a fix (1.0.7) that solved the noise and kept the latency low.

 

It's been happily sitting in the corner not generating random notes for about an hour and a half so I'll call it cured.

 

The lack of resizing is a bit of a pain but not insuperable. Is there any chance that the keyboard along the bottom will be changed to better look like a piano keyboard at some future date?

[King Tut]

Thought this post was about alcohol recovery for a moment 🙀

[Woodinblack]

17 hours ago, Eric Bateman said:

All because you had your scaling cranked up too high.

 

I don't think there is any need for hate or arguments, but as someone who also does UIs for a living, I do make a point of ensuring that, within bounds, the user can access all of the user interface functionality whatever the resolution of their screen. If it is too small to display, put a scroll - its an ugly work around but at least it enables functionality on a reduced screen.

The resolution is not 'too high', it goes up way higher than that, and some people have bad eyesight or high res screens (my work laptop is set to 250% but it is a 4k screen) but if it is a problem not being able to see the user interface, it might be worth mentioning in the manual or support documentation that the screen has to show a minimum size to be able to see the current UI, so people aren't asking how to get it to work on a completely unrelated forum.

 

But you say it was made with QT and I have had to work with QT, older QT so I know the issues.

 

As an aside, the UI for the 12 step works for me, but then it is not something I go back to often as the 12 step works pretty well the way I set it up, 

[Beedster]

8 hours ago, King Tut said:

Thought this post was about alcohol recovery for a moment 🙀

 

Same 🤔

[Eric Bateman]

On 10/02/2025 at 15:34, tauzero said:

 

It's been happily sitting in the corner not generating random notes for about an hour and a half so I'll call it cured.

 

The lack of resizing is a bit of a pain but not insuperable. Is there any chance that the keyboard along the bottom will be changed to better look like a piano keyboard at some future date?

 

It's funny that you call out the keyboard, Tom (our support engineer) thinks it's ridiculous to have a 127 key keyboard in the first place. 

 

Unfortunately the keyboard UI is a completely 100% bespoke piece of graphics code that I didn't write. There be dragons there. To change it would be a complete rewrite, and unfortunately I have to focus on fixing some bugs with our other products. Keep in mind we are starting a completely new project this year, several new products, and we have 3 employees (myself included) and a handful of contractors. So I don't think I'm going to get to any UI rewrites for 12 Step in the next 18 months.

 

On 10/02/2025 at 22:33, King Tut said:

Thought this post was about alcohol recovery for a moment 🙀

 

Keith had an interesting sense of humor. For the record, there are 13 keys on the device, and we half/seriously considered calling the updated product the 13 Step.

 

On 11/02/2025 at 07:22, Woodinblack said:

 

I don't think there is any need for hate or arguments, but as someone who also does UIs for a living, I do make a point of ensuring that, within bounds, the user can access all of the user interface functionality whatever the resolution of their screen. If it is too small to display, put a scroll - its an ugly work around but at least it enables functionality on a reduced screen.

The resolution is not 'too high', it goes up way higher than that, and some people have bad eyesight or high res screens (my work laptop is set to 250% but it is a 4k screen) but if it is a problem not being able to see the user interface, it might be worth mentioning in the manual or support documentation that the screen has to show a minimum size to be able to see the current UI, so people aren't asking how to get it to work on a completely unrelated forum.

 

But you say it was made with QT and I have had to work with QT, older QT so I know the issues.

 

As an aside, the UI for the 12 step works for me, but then it is not something I go back to often as the 12 step works pretty well the way I set it up, 

 

I appreciate the feedback, and you're totally correct. The DPI scaling on Windows really broke a lot of older apps, 12 Step was originally written in Qt4 for reference. When I increased the size of the UI I tested on 1080p and 4K monitors of various sizes at 100% scaling, and found that to be a decent compromise. On 13" laptops or 50" displays things might become tricky, but without a full rewrite using QML the current size will have to do. I forget if we've added any info about scaling to the updated manual, but our real metric for any issue is our support ticket system, and when we updated the Editor/UI we ended a long run of regular tickets where people were having issues with the old editor either a) not running at all, or b) having issues with the UI size / fonts etc. This thread is honestly the first time it's come up since then, and we handle thousands of of tickets a year.

Edited February 13 by Eric Bateman