Older Firmware Releases

[Stratblue]

Hi.

I have sent sysex from port 1 to port 4, no USB sources, nothing else was transmitting at the time and the file was slightly smaller (37KB) when compared to the normal way I send it (37.4KB), I'm running the new firmware. I'm guessing that's not right...that's the total of my technical insight.
  2SysexFiles.zip (Size: 3.37 KB / Downloads: 4)

[ekkomouse]

Beta 1.1.068

Issues found:
1. In Port filter sub page doesn't display USB D3 and D4, was like this on official firmware too
2. Out Port filter sub page doesn't display P05-12, was like this on official firmware too.
3. When pressing up/down from the matrix page, the display shows the additional inputs/ouputs of PC and USB, but then activating a new output doesn’t update the screen correctly, it glitches and shows incorrect info. I think when you select a USB or pc input, the matrix should display that sub matrix automatically and pressing the encoder can return you to the normal view.


Feature request:
1. Display Input and output name upon button press from the main routing matrix page
2. When assigning input names inside MRCC allow us to rename inputs in PC and any DAW, pass names to PC/Mac please.
3. Show what inputs are active on the preset with dimly lit LED’s similar to how you show outputs that are active but not currently selected.
4. Midi monitor screen should record more note/event data and be scrollable so we can see what was received, also a clear screen option. Helpful for troubleshooting.
5. On routing screen, it shows incoming data, but there is no way to control which data is shown in such a small space, so if you have lots of data coming in, you dont see it if the MRCC has chosen to show some other data. Can the MRCC display the data associated with the tab stopped icon? Example: So when you are tab stopped on the clock icon, it shows if that input is sending clock, if tab stopped on the note icon, it shows what note was received, if not tab stopped on an icon, it shows the current way it displays but also please provide us with info on how it prioritizes what data its showing, this is helpful with troubleshooting.

[Darryl]

Beta 1.1.068

Issues found:
1. In Port filter sub page doesn't display USB D3 and D4, was like this on official firmware too
2. Out Port filter sub page doesn't display P05-12, was like this on official firmware too.
3. When pressing up/down from the matrix page, the display shows the additional inputs/ouputs of PC and USB, but then activating a new output doesn’t update the screen correctly, it glitches and shows incorrect info. I think when you select a USB or pc input, the matrix should display that sub matrix automatically and pressing the encoder can return you to the normal view.
...

Thanks for the report! The #1 and #2 issues are just something that's a bit confusing... its not that we don't show the D3 and D4 ports or PC ports, we just end the list as that is as many filters that can be set. To change the port, tab to the green port number and turn the encoder to select the port to filter. There you can select any port. We thought it would be better to show something there rather than a blank space.

[Darryl]

Beta 1.1.068

Feature request: ...

Regarding the feature requests, some of these we've discussed in the past.

Really liking #5, to filter what data is shown based on selecting the filter icon. It currently can't show every message because we wouldn't be able to read it fast enough, so it just samples at a rate that us mortals can consume. If we filter by clock for instance, maybe we could show BPM there. It already indicates clock with the red carrot, but I often use The NDLR as a BPM monitor and it would be handy to have a BPM monitor on MRCC. 

Having the MIDI monitor screen capture more data and scrollable was on our original feature list, its just that C string handling is a b*tch   We'll take another look at it though, we'd like to have that.

[User]

Thanks for update and saving preset fix.

1. In Channel Map modifier: added a new Chan Source = "-" (none) in lines 2-4. This enables a bunch of Channel mapping possibilities.
   

Could you tell something more about that?  How to use it?

Could you explain, how to use this mod?

...and also there are some bugs reported in latest version.

[ekkomouse]

I’m using MRCC with Bome Network, to route some usb midi devices through the MRCC PC inputs, it works well except the Bome is reading the PC port name’s incorrectly. Bome support seems to think it’s the device as an issue, they say the Bome software takes the name from Mac OS. It seems Bome Network just sees MRCC and a random numbering applies which doesn’t match port names.

Can you help me get port names correctly labeled?

Does each PC port have an actual name or are they all named MRCC and the MacOS applies the port number?


Is there any chance you can incorporate custom port naming into the firmware?


Red is my note

[ekkomouse]

As a followup, on MacOS 12.6.1 I keep getting multiple MRCC USB devices showing up in Audio/Midi Setup, which causes the MRCC port names to change within that Bome Network. Sometimes I am able to get it to return to the old deactivated midi device by turning off MRCC, deleting the new midi device in MacOS and turning on the MRCC, at that point it may communicate that its the old device. There may be something off with the initial handshake in MacOS.

So requesting user customized port names. And/or better defined port names within MacOS so 3rd party software/MacOS doesn't think they are all named the same and define its own name. And a way not to have multiple MRCC midi devices show up in settings so if the first two requests aren't possible, we dont have to keep troubleshooting 12 PC/DAW ports to find which one the assignments have changed to.

[ekkomouse]

Separately I did just have a lockup on the MRCC doing the following, its not repeatable to lockup though:

1. Save a previously made preset into a new slot.
2. Start to alter the preset, I was switching cables around and going back and forth to recreate settings from the old setup.
3. When I got into the mod matrix, assigning transpose 2 to around 14 outputs, it stopped responding, no clock or notes were playing.
4. Non-responsive so I turned off and on, did not get past firmware load screen.
5. After a couple tries, I unplugged both pc and USB devices and it turned on and worked.

[Darryl]

Separately I did just have a lockup on the MRCC doing the following, its not repeatable to lockup though:

1. Save a previously made preset into a new slot.
2. Start to alter the preset, I was switching cables around and going back and forth to recreate settings from the old setup.
3. When I got into the mod matrix, assigning transpose 2 to around 14 outputs, it stopped responding, no clock or notes were playing.
4. Non-responsive so I turned off and on, did not get past firmware load screen.
5. After a couple tries, I unplugged both pc and USB devices and it turned on and worked.

Making a MIDI loop will do that, especially if there's a clock present. Sometimes if you keep pressing a button you can unloop it and get it back without a power cycle. It would be cool to have a loop detector that would see MIDI buffer overflow and throttle the input causing the issue, and maybe blink its LED. But that would take some processing power to monitor so I don't know if its practical. 

 You might possibly prevent locking up with a MIDI loop by turning off "If X Port Panic" on SETTINGS page 3. Since this is introducing MIDI messages that could feed a loop when trying different things.

[Darryl]

As a followup, on MacOS 12.6.1 I keep getting multiple MRCC USB devices showing up in Audio/Midi Setup, which causes the MRCC port names to change within that Bome Network. Sometimes I am able to get it to return to the old deactivated midi device by turning off MRCC, deleting the new midi device in MacOS and turning on the MRCC, at that point it may communicate that its the old device. There may be something off with the initial handshake in MacOS.

So requesting user customized port names. And/or better defined port names within MacOS so 3rd party software/MacOS doesn't think they are all named the same and define its own name. And a way not to have multiple MRCC midi devices show up in settings so if the first two requests aren't possible, we dont have to keep troubleshooting 12 PC/DAW ports to find which one the assignments have changed to.

We've been selling MRCC for a couple of years now and have a lot of mac users that are not having a problem that we know of, though I remember this being reported once before. There must be something going on different here. Is this a macbook? If you disconnect it without turning off the MRCC, maybe its not automatically removing it from its USB device list? Have you used the MRCC feature to change the name of MRCC? If so, turn off MRCC, delete MRCC from the audio/MIDI settings, then change back to the original name of "MRCC", SETTINGS page 4. Would be curious to see if that has anything to do with this.

Also, beside the BOME software, other programs get the ports numbered correctly. We've contacted BOME and looking into it.