+- Conductive Labs Support Forum (https://conductivelabs.com/forum)
+-- Forum: MRCC - MIDI Router Control Center (https://conductivelabs.com/forum/forumdisplay.php?fid=13)
+--- Forum: MRCC Open Beta Firmware (https://conductivelabs.com/forum/forumdisplay.php?fid=26)
+--- Thread: MRCC Firmware Release 1.1.095 (/showthread.php?tid=2107)
RE: MRCC Firmware Beta 1.1.077 - Jesse Johannesen - 01-02-2025
Not easily, you can remove the end cheek and take out the microSD and copy the contents, then send them, then I can load them onto mine, but that only gives me half of the info I need, (the other half being what is connected and where, etc). I recommend you just shoot me an email with your availability for the next couple of business days, your time zone and location and I can set us up a Zoom call. It sounds much simpler. We can talk it over and see what shakes out.
RE: MRCC Firmware Beta 1.1.077 - Darryl - 01-05-2025
(12-31-2024, 09:43 AM)RadekPilich Wrote: OK, I have redone / minimized /"de-bugged" my routing yesterday and will try to slowly expand and save iterations as separate profiles. Will report later if I find some specific cause for freezing.
Thank you for your effort and any issue you can uncover. Typically, the only thing that "hangs" MRCC is a MIDI loop, which will often recover after the loop is removed. The other is much more uncommon, but we've seen some USB MIDI devices cause occasional hard lockup when used with some combination of other USB MIDI devices. The Waldorf Blofeld has been a common denominator in such cases, so best to use that one with 5 pin DIN.
RE: MRCC Firmware Beta 1.1.077 - RadekPilich - 01-06-2025
Yes, that makes sense and confirms my hunches. I was attempting to get transport messages from all sequencers to trigger all other sequencers.
RE: MRCC Firmware Beta 1.1.077 - ekkomouse - 01-23-2025
I just loaded the new firmware, right off the bat the mrcc names for A/B/C/D are not recognized by the computer, so I have downgraded as I can't test my dual mrcc setup with names that can't be recognized, it breaks all of my computer Bome network routings. Ableton projects with saved routings, and the names are not matching settings when viewed inside DAWs. Let me know if you get that sorted and I can try again.
RE: MRCC Firmware Beta 1.1.077 - RadekPilich - 01-24-2025
Jesse / Darryl - would it be possible to add MIDI CCs for the Start / Stop / Continue functions of the MRCC Clock? It's hard to use MRCC Clock as main clock for sequencers without it, it's odd that it's not a part of the current MIDI implementation.
RE: MRCC Firmware Beta 1.1.077 - Darryl - 01-25-2025
(01-23-2025, 06:03 AM)ekkomouse Wrote: I just loaded the new firmware, right off the bat the mrcc names for A/B/C/D are not recognized by the computer, so I have downgraded as I can't test my dual mrcc setup with names that can't be recognized, it breaks all of my computer Bome network routings. Ableton projects with saved routings, and the names are not matching settings when viewed inside DAWs. Let me know if you get that sorted and I can try again.
There are some complexities when it comes to USB device naming. The operating system will cache the USB device names, so you can't just change the name setting and see the change. When the firmware is updated, it might see the MRCC as a new device and that's what messes up the naming. On Windows, there are a couple of ways to clear that cache, then get the OS to learn the new name after a reboot, so the name you select will be learned after a reboot.
I thought I wrote up some instructions for that somewhere but can't find it at the moment. I'll take a look when I'm in the office next week, or write new instructions in an FAQ and post it here. Otherwise, there's nothing in the new firmware that should affect that USB device naming, but we did update the USB device firmware to the latest version, so it could be something unexpected is happening. We'll check it out.
RE: MRCC Firmware Beta 1.1.077 - Darryl - 01-25-2025
(01-24-2025, 02:43 PM)RadekPilich Wrote: Jesse / Darryl - would it be possible to add MIDI CCs for the Start / Stop / Continue functions of the MRCC Clock? It's hard to use MRCC Clock as main clock for sequencers without it, it's odd that it's not a part of the current MIDI implementation.
I think we had another request to add this recently, it's a good idea. I'll make sure it's in the backlog.
RE: MRCC Firmware Beta 1.1.077 - ekkomouse - 01-25-2025
(01-25-2025, 02:23 PM)Darryl Wrote:(01-23-2025, 06:03 AM)ekkomouse Wrote: I just loaded the new firmware, right off the bat the mrcc names for A/B/C/D are not recognized by the computer, so I have downgraded as I can't test my dual mrcc setup with names that can't be recognized, it breaks all of my computer Bome network routings. Ableton projects with saved routings, and the names are not matching settings when viewed inside DAWs. Let me know if you get that sorted and I can try again.
There are some complexities when it comes to USB device naming. The operating system will cache the USB device names, so you can't just change the name setting and see the change. When the firmware is updated, it might see the MRCC as a new device and that's what messes up the naming. On Windows, there are a couple of ways to clear that cache, then get the OS to learn the new name after a reboot, so the name you select will be learned after a reboot.
I thought I wrote up some instructions for that somewhere but can't find it at the moment. I'll take a look when I'm in the office next week, or write new instructions in an FAQ and post it here. Otherwise, there's nothing in the new firmware that should affect that USB device naming, but we did update the USB device firmware to the latest version, so it could be something unexpected is happening. We'll check it out.
ok, thanks for the reply, if you recall, we had this issue before and an update was made to address it. The prior issue was the device name would not match settings and when network or port routings were made, they would have to be redone every power up due to the device name not populating correctly in Mac os
RE: MRCC Firmware Beta 1.1.077 - Darryl - 02-03-2025
(01-25-2025, 04:13 PM)ekkomouse Wrote:(01-25-2025, 02:23 PM)Darryl Wrote:(01-23-2025, 06:03 AM)ekkomouse Wrote: I just loaded the new firmware, right off the bat the mrcc names for A/B/C/D are not recognized by the computer, so I have downgraded as I can't test my dual mrcc setup with names that can't be recognized, it breaks all of my computer Bome network routings. Ableton projects with saved routings, and the names are not matching settings when viewed inside DAWs. Let me know if you get that sorted and I can try again.
There are some complexities when it comes to USB device naming. The operating system will cache the USB device names, so you can't just change the name setting and see the change. When the firmware is updated, it might see the MRCC as a new device and that's what messes up the naming. On Windows, there are a couple of ways to clear that cache, then get the OS to learn the new name after a reboot, so the name you select will be learned after a reboot.
I thought I wrote up some instructions for that somewhere but can't find it at the moment. I'll take a look when I'm in the office next week, or write new instructions in an FAQ and post it here. Otherwise, there's nothing in the new firmware that should affect that USB device naming, but we did update the USB device firmware to the latest version, so it could be something unexpected is happening. We'll check it out.
ok, thanks for the reply, if you recall, we had this issue before and an update was made to address it. The prior issue was the device name would not match settings and when network or port routings were made, they would have to be redone every power up due to the device name not populating correctly in Mac os
We've been looking into the USB device naming some more. We didn't change anything that should have effected it's functionality, however, what we did before was a change to address a race condition. It's possible that the new libraries caused the condition to worsen. We took a deep dive into the USB device code and came up with a better solution for dynamically setting the USB device name which completely eliminates the race condition. We should be ready to post that here later this week.
RE: MRCC Firmware Beta 1.1.077 - ekkomouse - 02-04-2025
OK sounds good. I will test it when it’s posted.
Today I was realizing I’m not able to name remote outputs when using a dual MRCC setup. So I have a few requests related to output naming.
1. There needs to be a global naming configuration, I imagine most users don’t do a lot of swapping where it’s needed per preset, But maybe there’s a few users that do need that. So I suggest a global name pool for inputs/outputs, With a flag in settings per preset to override global names, which then imports the global name pool and allows the user to change per preset like currently. This way when adding a device and assign to an output or name changing outputs/inputs, we don’t have to update each user preset individually, As well as the pool of names.
2. In a dual MRCC set up they Should share their name assignments, So when assigning remotely, you see the name, Currently, it just says none.