Mastermind PBC Firmware / Editor 5.3.1 Release

rjmmusic

rjmmusic

Administrator
Staff member
Firmware and editor version 5.3.0 are now available!

FEATURES:
  • New device support:
    • Chase Bliss Mood mk II (fixed previous attempt) and Onward
    • GFI Duophony
    • Morningstar ML10X
    • Strymon Big Sky MX
    • Quad Cortex: Added individual scene CCs (Scene A, Scene B, etc.)
    • Kemper: Added looper buttons (for real this time, had some wires crossed last release...)
  • All devices can now be set to respond to incoming PCs. For example, let's say you have a device on channel 5. If Ignore Incoming PCs is turned off, incoming PCs on channel 5 will cause preset changes on the Mastermind. And, specifically, an incoming PC on channel 5 will never result in the Mastermind sending a PC on channel 5. This prevents MIDI PC feedback loops.
  • The above feature is probably not needed or desired in most cases. As a result, Ignore Incoming PC and Ignore Incoming CC are now the default setting for most devices.
  • The Set Preset PCs to 0 and Set Preset PCs Sequential buttons in the editor now ask for a preset and bank number. This will set all preset PCs for a device to a specific bank and preset (in the case of the Set Preset PCs to Value button) or it will assign sequential PCs starting at the given PC and bank (in the case of Set Preset PCs to Sequential)
BUG FIXES:
  • It's once again possible to recall presets that are not in the active setlist.
  • Fixed fuzz mode for PBC/10 again. This time, it should work.
  • Fixed an issue that could cause buttons to incorrectly send their messages more than once when using Set IA.
  • Fixed expression pedal issues when in Remote Mode.
  • It's now possible to show both preset numbers and scene numbers at the same time on the main screen
  • Fixed an issue where drag and drop in the editor, followed by Send Changes To Device, didn't result in all data being updated correctly.
  • Fixed an editor issue that caused Audio Feature Names to not be carried over correctly when sending to and reading back from the device.
You can also read the full change log if you like.

UPDATE 12/17/2024 - Version 5.3.1

Version 5.3.1 adds support for the following devices:
  • BluGuitar Amp1
  • Chase Bliss Clean, Habit and Lossy
  • Diezel VH-X
  • EHX POG3
  • Friedman IR-C, IR-J, IR-X
  • GFI Enieqma, Solus Ventis
  • Kemper Player (still needs a USB host adapter to connect)
  • Radial Engineering JX-44 v2
  • Two Notes Opus
  • Walrus Meraki
and fixes the following bugs:
  • BPM changes made using System / BPM actions can now be stored using IA Store buttons and actions
  • Fixed a bug where the tuner wouldn't work if a fuzz mode loop was on when turning on the tuner
TO UPDATE FIRMWARE:

PLEASE DON'T DO A MAJOR FIRMWARE UPDATE RIGHT BEFORE YOUR BIG GIG!

- First, back up your settings to a flash drive or computer! If you go back to 4.7 or earlier, your Mastermind will factory reset.
- Download and unzip the firmware file.
- Copy the file to a USB flash drive, and remove any other .rjf files from the flash drive.
- Eject the drive from your computer.
- Power on the Mastermind while holding the 1 and 3 buttons.
- Keep holding until you see "Mastermind Bootloader" appear on the screen.
- Now plug the flash drive into your Mastermind. The update should begin and will take a few minutes to complete.

-OR-

- First, back up your settings to a flash drive or computer! If you go back to 4.7 or earlier, your Mastermind will factory reset.
- Download and unzip the firmware file.
- Use the editor's Transfer / Update Firmware menu option to update the Mastermind. This works with the PBC/6X and PBC/10s made after March 2019.

Firmware: https://www.rjmmusic.com/download-content/PBC/MM531.zip

Mac Editor: https://www.rjmmusic.com/download-content/PBC/MastermindEditor-5.3.1.dmg
PC Editor: https://www.rjmmusic.com/download-content/PBC/MastermindEditor-5.3.1.zip

PBC/6X Manual: https://www.rjmmusic.com/download-content/PBC6X/PBC6X Manual-4.3.pdf
PBC/10 Manual: https://www.rjmmusic.com/download-content/PBC/PBC Manual-4.2.pdf
 
Last edited:
Thanks so much! Excited to see that you fixed the duplicate message issue, I’m sure it will make my life easier at the very least.
 
rjmmusic said:
Hopefully it'll help with the message dropping issue you were seeing.
Click to expand...

So far, I haven't seen the issues I was experiencing with pedals (particularly my HX Stomp) getting tripped up by multiple messages. Thanks so much for your work on this, I'm certain it'll make my preset changes more reliable!
 
Hello ever since I updated my bigsky MX is not responding correctly to bypass commands. I have an IA on a button that per preset will either activate or bypass it. If i push the button alone it bypasses and engages the pedal but when i save the preset and recall the pedal does not bypass it just stays on the whole time. I will add that i have 5 other midi pedals on my board that i use this same method and the bigsky MX is the only one giving problems right now.
 
Last edited:
steveme said:
Hello ever since I updated my bigsky MX is not responding correctly to bypass commands. I have an IA on a button that per preset will either activate or bypass it. If i push the button alone it bypasses and engages the pedal but when i save the preset and recall the pedal does not bypass it just stays on the whole time. I will add that i have 5 other midi pedals on my board that i use this same method and the bigsky MX is the only one giving problems right now.
Click to expand...
I just ran into what I think is the same thing. It seems that the BigSky MX bypass status is saved on the BigSky MX's presets.

I would setup a bypass/active button for the BigSky MX on a dedicated PBC page. Set to OFF and saved the PBC Preset. it kept recalling the BigSky's preset correctly but in the ON state. Then I could turn it off with the IA button and back on. So I tried again and same thing. if I bypass the pedal by pressing the foot switch on the BigSky MX and save that preset with the button OFF, it would recall correctly.

it seems that the bypass status is saved onto the BigSky MX preset but I'm not sure why the CC wouldn't bypass it. maybe if the bigsky preset and the PBC presets are changing at the same time, the CC doesn't get to the BigSky at the right moment. Perhaps a Wait command of a few milliseconds on that PBC preset will allow the BigSky to load its preset first and then the PBC will send the CC? I didn't think of this until after I delivered the pedalboard to the customer.
 
cuterigs said:
I just ran into what I think is the same thing. It seems that the BigSky MX bypass status is saved on the BigSky MX's presets.

I would setup a bypass/active button for the BigSky MX on a dedicated PBC page. Set to OFF and saved the PBC Preset. it kept recalling the BigSky's preset correctly but in the ON state. Then I could turn it off with the IA button and back on. So I tried again and same thing. if I bypass the pedal by pressing the foot switch on the BigSky MX and save that preset with the button OFF, it would recall correctly.

it seems that the bypass status is saved onto the BigSky MX preset but I'm not sure why the CC wouldn't bypass it. maybe if the bigsky preset and the PBC presets are changing at the same time, the CC doesn't get to the BigSky at the right moment. Perhaps a Wait command of a few milliseconds on that PBC preset will allow the BigSky to load its preset first and then the PBC will send the CC? I didn't think of this until after I delivered the pedalboard to the customer.
Click to expand...
Thanks for this I’m going to try this later today. it still doesn’t solve the problem but may be a temporary workaround. For my gigs today I basically changed the midi channel on the big sky and am operating it manually.
 
steveme said:
Thanks for this I’m going to try this later today. it still doesn’t solve the problem but may be a temporary workaround. For my gigs today I basically changed the midi channel on the big sky and am operating it manually.
Click to expand...
Tested this out and you are indeed correct the BigSky Mx ignores bypass of the midi controller when recalling a preset. I have reached out to support to see if intended. Is there an IA I can setup in the meantime as a workaround?
 
steveme said:
Tested this out and you are indeed correct the BigSky Mx ignores bypass of the midi controller when recalling a preset. I have reached out to support to see if intended. Is there an IA I can setup in the meantime as a workaround?
Click to expand...
Yeah I’m under the impression the bypass state of a patch is saved into a patch on the MX.

So I wonder if first turning on “Direct Send PCs/CCs” might help. I’m not sure what the priority order of messages is but I’m assuming it would send the PC first followed by the CC assigned to your bypass IA button. The way I’m thinking of it is it first sends the PC, and regardless of the saved state on the MX, RJM will then send the IA CC so override that.

If that alone doesn’t do it, then try a System/Wait command in the preset actions for your RJM preset, just a few milliseconds at first. I believe this will let the RJM call up the MX patch, wait a few mS, then send the IA CC. It might take experimenting to see how many mS will work and you’ll have to balance that with what seems less noticeable in practice.

I might be unclear on how exactly some of these functions work but I’m sure Ron or someone else will chime in if I’m off!
 
cuterigs said:
Yeah I’m under the impression the bypass state of a patch is saved into a patch on the MX.

So I wonder if first turning on “Direct Send PCs/CCs” might help. I’m not sure what the priority order of messages is but I’m assuming it would send the PC first followed by the CC assigned to your bypass IA button. The way I’m thinking of it is it first sends the PC, and regardless of the saved state on the MX, RJM will then send the IA CC so override that.

If that alone doesn’t do it, then try a System/Wait command in the preset actions for your RJM preset, just a few milliseconds at first. I believe this will let the RJM call up the MX patch, wait a few mS, then send the IA CC. It might take experimenting to see how many mS will work and you’ll have to balance that with what seems less noticeable in practice.

I might be unclear on how exactly some of these functions work but I’m sure Ron or someone else will chime in if I’m off!
Click to expand...
Thank you again! Will give this a go tomorrow. I also have a support ticket out to Strymon regarding this.
 
steveme said:
Thank you again! Will give this a go tomorrow. I also have a support ticket out to Strymon regarding this.
Click to expand...
Strymons response "This does seem to be an issue with certain MIDI switchers, although we're not really sure why. I use an MC6 Pro and I am able to send these messages without any problems whatsoever on two different BigSky MX's, so it does not seem to be an issue with the pedals."

So he recognized it as an issue but they don't know why and it works with the MC6 Pro lol.
 
steveme said:
Strymons response "This does seem to be an issue with certain MIDI switchers, although we're not really sure why. I use an MC6 Pro and I am able to send these messages without any problems whatsoever on two different BigSky MX's, so it does not seem to be an issue with the pedals."

So he recognized it as an issue but they don't know why and it works with the MC6 Pro lol.
Click to expand...

It’s obviously suboptimal but if your MX isn’t inside a loop (and therefore you can’t control bypass using audio settings), you might consider doing what I do with my DD-500; have a patch with 100% dry and 0% wet mix and treat it as a “bypass” state. The MX, surely, has robust preset spillover so switching to a “Bypass Preset” wouldn’t drop your verb signal.

Conversely, you could put your MX inside a looper that features spillover like the Morningstar ML10X, and control that loop via MIDI.
 
The guys above have some good points and some things to try. If you want, you can send your settings and I can see if there's something that needs to be fixed in your settings.
 
rjmmusic said:
The guys above have some good points and some things to try. If you want, you can send your settings and I can see if there's something that needs to be fixed in your settings.
Click to expand...
Here ya go. Im only using the 1st three pages. Page 2 is my loop page page 3 is my midi page. Thanks for checking do you have a video somewhere explaining how to do a delay command. i might try to do that first putting a delay on the bypass command.
 

Attachments

  • newest bs+.rjs.zip
    48.9 KB · Views: 2
steveme said:
Here ya go. Im only using the 1st three pages. Page 2 is my loop page page 3 is my midi page. Thanks for checking do you have a video somewhere explaining how to do a delay command. i might try to do that first putting a delay on the bypass command.
Click to expand...
I found something that is possibly the cause. Edit your BigSky bypass buttons and flip the values so that the off value is 0 and the on value is 127. I may have had them inverted in the database.
 
rjmmusic said:
I found something that is possibly the cause. Edit your BigSky bypass buttons and flip the values so that the off value is 0 and the on value is 127. I may have had them inverted in the database.
Click to expand...
I had tried this previously and it still did not affect the preset being recalled.
So this is the command that i had to do in order for it to bypass which is unfortunate because the reverb does engage momentarily. this along with enabling direct send pc/cc in the device menu.
 

Attachments

  • Screenshot 2024-09-04 at 5.01.22 PM.png
    Screenshot 2024-09-04 at 5.01.22 PM.png
    772.8 KB · Views: 7
Last edited:
steveme said:
I had tried this previously and it still did not affect the preset being recalled.
Click to expand...
Weird. I don't have a BigSky MX to test with, so I'm going to have to guess for now. Inserting a System / Wait action above the Bypass CC action is worth a try. Set it to 100 to 200 mSec. Also turn on Direct Send PC/CC for the BigSky MX in the Devices tab.
 
rjmmusic said:
Weird. I don't have a BigSky MX to test with, so I'm going to have to guess for now. Inserting a System / Wait action above the Bypass CC action is worth a try. Set it to 100 to 200 mSec. Also turn on Direct Send PC/CC for the BigSky MX in the Devices tab.
Click to expand...
yes this worked for me i had it at 6ms and it was working but i just increased just because its not gonna make a big difference. I guess this will do for now. Thank you for all the help everyone and Ron!

Also your values are correct its the manual of the bigsky MX that are incorrect.
bypass 102
on: 0
off: 127

Last thing just wanted to post here what strymon support sent me back with.
Support:
Like I mentioned, it's something to do with certain MIDI switchers and how the messages are sent out, not so much how the pedal receives them. I'm able to send these same MIDI messages using my DAW and my Morningstar MC6 Pro without any issues, and I know the other support folks have tested other MIDI controllers that don't exhibit the behavior you're seeing as well.
 
You must log in or register to reply here.
Back
Top