Mastermind PBC Firmware / Editor 5.3.1 Release

[rjmmusic]

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.

We send MIDI as fast as is physically possible, maybe that's the difference. Other controllers could be putting a few mSec between messages and we wouldn't be able to notice in most cases. Generally speaking, I find faster = better for MIDI purposes, though.

Thanks for the info on the CCs, it's good to know I do actually have it right.

 

[GregBouchard]

I don’t know if this is specifically a firmware upgrade issue or not, but it occurred immediately after upgrading to 5.3.

when powering on, it takes a few seconds after the splash screen reverts to my preset screen for the LEDs to illuminate. My button presses react sluggishly and stop having any effect after 2-3 button presses (same button or random buttons). I downgraded the firmware to 5.21 but could only do so by powering up with1&3 depressed, going directly to the bootloader.

I've had my PBC for several years and have never had an issue. I’m baffled.

 

[rjmmusic]

I don’t know if this is specifically a firmware upgrade issue or not, but it occurred immediately after upgrading to 5.3.

when powering on, it takes a few seconds after the splash screen reverts to my preset screen for the LEDs to illuminate. My button presses react sluggishly and stop having any effect after 2-3 button presses (same button or random buttons). I downgraded the firmware to 5.21 but could only do so by powering up with1&3 depressed, going directly to the bootloader.

I've had my PBC for several years and have never had an issue. I’m baffled.

Is it working correctly after downgrading to 5.2.1?

 

[GregBouchard]

No, but I just downgraded to 5.0 and it seems to be back to normal.

I had previously been running 5.21 with no issues.

 

[GregBouchard]

A further update. I reinstalled the 5.21 firmware and the odd behaviour returned, back to 5.01 and all was normal. I reinstalled 5.30 and the odd behaviour returned. I'm now back on 5.01, no issues.

 

[rjmmusic]

Did this happen after you added the System / Wait action(s)? If there's a lot of them, it could slow things down. When you tell it to wait, it will wait the specified amount of time and nothing will happen during that time period.

 

[GregBouchard]

No, it began as soon as I updated the firmware. The button response was very slow at first and then they stopped responding entirely. No modifications to my setup which has been running for years now.

I was only able to downgrade the firmware by powering up with 1&3 depressed and going straight to the boot loader as the buttons weren’t responding once the controller booted up normally.

 

[GregBouchard]

I read the device for my settings (included) and I'm sharing a screenshot of my editor. Take note of the button groups section.

 

[rjmmusic]

I read the device for my settings (included) and I'm sharing a screenshot of my editor. Take note of the button groups section.

Well, your settings file is definitely corrupted. I'm surprised you could even load it.

The problem seems to be limited to group settings. Attached is a new file that has group settings reset to factory defaults. Load this one up and see if it works for you.

 

[GregBouchard]

Yeah, when I saw that I figured it was a problem. I do have back up settings files on my thumb drive as well. Thanks.

 

[atsounds]

Anyone experiencing problems with Bank switching in Song Mode after updating F/W to 5.30 ?
Haven't made any other changes... bank switching works normal in preset mode... everything else seems to be working as usual after the update.
Bank Up & Bank Down buttons use default buttons & settings.

No prior probs with this... tried deleting bank up/down buttons & then re-assigning them w/o success.
Have not yet downgraded F/W.
Most recent file attached.

Any help much appreciated!

 

[GregBouchard]

Yeah, when I saw that I figured it was a problem. I do have back up settings files on my thumb drive as well. Thanks.

I just tried updating to firmware 5.3 again and again ended up with a corrupted groups section. I don’t know if I’m the only one with this issue. Downgrading to 5.0 and installing backup settings gets me up and going. When I have time, I’ll try upgrading again, converting a backup settings file to 5.3 and installing that. That’s all I can think of.

 

[rjmmusic]

There are no songs in the currently selected setlist, that's why bank up & down don't work. If you add songs to the first setlist, or switch to a setlist that isn't empty, it should work.

 

[atsounds]

There are no songs in the currently selected setlist, that's why bank up & down don't work. If you add songs to the first setlist, or switch to a setlist that isn't empty, it should work.

Yep ... (DOH !)
I didn't catch it til the next day & forgot to delete this post ... man, talk about embarassing... anyhoo, thanks for taking the time.
Sorry to waste yours...

 

[PAPITO]

Now That the kemper player is fully matured , hope we get an update for it

 

[rjmmusic]

Now That the kemper player is fully matured , hope we get an update for it

The main difficulty is that the player doesn't have standard MIDI ports. Has anyone found a solution for connecting to it that works reliably?

 

[PAPITO]

The main difficulty is that the player doesn't have standard MIDI ports. Has anyone found a solution for connecting to it that works reliably?

I have ! I been using the kemper player and the hx one for while with my pbc6x . everything is working fine . I use a MODIFIED fore usb midi adapter ( from amazon )

 

[cfcr]

After I updated the PBC/10 firmware to 5.3.0, the PBC/10 malfunctions in a few interesting ways. It seems to be sending a *lot* of MIDI to the pedals, which are rapidly switching presets and so on. The display shows what looks like multiple screens overlaid (picture attached). And finally, when I restored the firmware to 5.2.1, the problem goes away entirely. I tried updating the 5.3.0 firmware via the Editor, as well as via USB thumb drive. I verified that the md5 checksum is the same between the firmware file on my computer and the firmware file on the USB thumb drive.

I have also uploaded my settings file. Like I said, this works fine with firmware 5.2.1 but something about these settings may be causing these problems with 5.3.0.

I read the settings back from my device into the Editor, and I don't see the corrupt groups in the Editor that were seen by the earlier poster. I am using groups, and it's possible that something I did with my groups/button actions is what's breaking things for me when I try 5.3.0.

 

[cuterigs]

After I updated the PBC/10 firmware to 5.3.0, the PBC/10 malfunctions in a few interesting ways. It seems to be sending a *lot* of MIDI to the pedals, which are rapidly switching presets and so on. The display shows what looks like multiple screens overlaid (picture attached). And finally, when I restored the firmware to 5.2.1, the problem goes away entirely. I tried updating the 5.3.0 firmware via the Editor, as well as via USB thumb drive. I verified that the md5 checksum is the same between the firmware file on my computer and the firmware file on the USB thumb drive.

I have also uploaded my settings file. Like I said, this works fine with firmware 5.2.1 but something about these settings may be causing these problems with 5.3.0.

I read the settings back from my device into the Editor, and I don't see the corrupt groups in the Editor that were seen by the earlier poster. I am using groups, and it's possible that something I did with my groups/button actions is what's breaking things for me when I try 5.3.0.

I could be wrong but I believe this has to do with the new “ignore incoming CC” and PCs features added… if you check those boxes in your devices the problem should go away.

 

[cfcr]

I could be wrong but I believe this has to do with the new “ignore incoming CC” and PCs features added… if you check those boxes in your devices the problem should go away.

Yes, that was the problem. Thanks!