Conductive Labs Support Forum
Older Firmware Releases - Printable Version

+- 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: Older Firmware Releases (/showthread.php?tid=1583)

Pages: 1 2 3 4 5

Older Firmware Releases - Darryl - 06-22-2021


.zip   MRCC_v1.1.068_12-07-2022.zip (Size: 284.41 KB / Downloads: 89)
MRCC_v1.1.068
This beta has not had extensive testing, but we would appreciate any feedback specific to the below changes if you are willing to give it a try! Please keep discussion of the beta release in the MRCC Open Beta Forum. Thank you!

Features:
  1. Added current Preset Name on Load/Save screen
  2. Added screen idle timeout to prevent OLED burn-in. The "Screen Off" time can be set on Settings page 2. The screen will sleep when MRCC is "idle" (no MIDI notes). However, the idle timeout reset ignores Clock, ActiveSensing or TimeCodeQuarterFrame MIDI messages and will timeout despite those messages being present. Tap the green button or any other button to turn the screen back on.
  3. In Channel Map modifier: added a new Chan Source = "-" (none) in lines 2-4. This enables a bunch of Channel mapping possibilities.
  4. Removed the SHIFT+ required in SAVE / LOAD 'ing presets (no safety on the preset overwrite!!!). 

BUG FIXES:
  1. Major overhaul of System Exclusive (SysEx) message handling. MRCC should be able to handle any length data to all possible out ports including MRCC to MRCC & MRCC to Remote 7. Please note: It is possible to overrun the MRCC's internal buffers when sending large SysEx files from very fast USB to very slow 5 pin DIN outputs. The sending software should throttle the speed it sends SysEx. Also note, if sending large SysEx files, be sure to temporarily turn off any other MIDI data sources. Once the internal buffers are full, MRCC will block MIDI data on merged inputs, but better chance of success if its not having to handle clock and other messages while the large transfer is happening.
  2. The last selectable preset name was 128 (F25) - should have been 127 (F24)
  3. Fix some Preset save issues. If you experienced an issue where after saving a patch, it changed back to Red from Green, this should fix it.
  4. Activity Screen always shows the correct Preset Label
  5. When routing remotely and holding the "Y" 5-Pin #1 is not showing MIDI activity
  6. Fixed some User Label Save/Delete/Assign issues. 



.zip   MRCC_v1.1.052_04-04-2022.hex.zip (Size: 250.84 KB / Downloads: 56)
MRCC_v1.1.052_04-04-2022

BUG FIX:
Program Change messages fail to route when on same port as MRCC MIDI Cntrl, despite being on a different channel.


MRCC_v1.1.051_03-28-2022

FEATURE:

1) Fixed some USB Host compatibility, specifically the OXI MIDI sequencer, but this fix may extend to other previously incompatible devices. Please lets us know with a post on the MRCC beta forum if you get devices to work that did not previously work.

2) MIDI SysEx message size has been increased to a 512 byte buffer size 

3) MIDI SysEx messages can now pass to ports 7-12 and remote ports 1-5 (to the R7).






MRCC_v1.1.044_12-23-2021




FEATURE:

  1) Another update for enabling unique MRCC "USB PC Name" for when you have more than one MRCC attached to your computer. See  SETTING Menu page 4 to set the name.

      We think we've got it (mostly) working as designed. Please give it a try and leave your feedback in this forum. We really appreciate your help!



On a Windows 10 PC, it may be helpful to remove legacy USB cache entries using Device Manager, or the tool USBDeview. At a minimum, after changing the name you will need to reboot for the OS to correctly identify the new USB device names and associated MIDI port numbers. There might still be a race condition where the name could come up as MRCC_?. This shouldn't happen if MRCC is turned on before booting the computer. We're working on it.





[attachment=212]

MRCC_v1.1.041_11-12-2021



FEATURE:

  1) MRCC "USB PC Name" can be augmented to MRCC-A to MRCC-Z, or orig MRCC (see Setting Menu 4).

       This is useful when more than one MRCC is connected to your PC.



  We have NOT been able to get Win10 to correctly identify the unique USB Friendly Names and USB Serial Numbers when cold booting

  with two MRCCs connected. We can clearly see the unique info in Device Manager.  NOTE: If you turn on the MRCCs after booting

  then everything seems to be clearly identified as unique.  






MRCC_v1.1.039_11-05-2021



BUG FIX:

   1) FIXED - Showing 16 USB MIDI virtual ports instead of 12. (only 12 show now, you might have to reboot your PC for the USB cache to be cleared)



FEATURE:

  1) Work-in-Progress! MRCC "USB PC Name" can be augmented to MRCC-A to MRCC-Z, or orig MRCC (see Setting Menu 4).

       This is useful when more than one MRCC is connected to your PC.




MRCC_v1.1.037_10-19-2021



New Features:

   1) The Stop & Start buttons will auto toggle the highlight. So pressing the Enter button repeatedly will toggle Stop & Start states and send the Stop & Start MIDI message each time it is toggled.

   2) New MRCC "CCs" are added for Stop, Start & Continue.  Remember to send CCs to the "MRCC MIDI Control" port and channel (configurable in Settings 1/4). 

        CC#27 - send STOP message, sent if cc = 127

           TIP: set your controller button behavior to MOMENTARY

           NOTE: if "TIC-ON-STOP" is set to "No" then cc=127 will also Stop the MRCC clock

        CC#28 - send START message, sent if cc = 127

           TIP: set your controller button behavior to MOMENTARY

           NOTE: if "TIC-ON-STOP" is set to "No" then cc=127 will also Start the MRCC clock

        CC#29 - send CONTINUE message, sent if cc = 127 

           TIP: set your controller button behavior to MOMENTARY

           NOTE: if "TIC-ON-STOP" is set to "No" then cc=127 will also Start the MRCC clock



        CC#26 - sends STOP, sent if cc = 0 or START/CONTINUE, sent if cc = 127 messages

            TIP: set your controller button behavior to TOGGLE

            NOTE: if "TIC-ON-STOP" is set to "No" then

                  STOP also Stops the MRCC clock

                  START/CONTINUE also Starts the MRCC clock



Known issue:

Showing 16 USB MIDI virtual ports instead of 12. This will be fixed in the next release. In the meantime, please ignore the extra ports.





MRCC_v1.1.035_09-20-2021

Fixed BUGS:
   MRCC can save a corrupt file that can't be read - FIXED (will read corrupted files  AND  will NOT write corrupt files)
   The Load/Save messages don't always fit on the screen correctly - FIXED

New Features:
   Display the current preset on the Activity screen banner
   Display outlined red triangle if Clock is filtered



v1.1.032 08/19/2021
Fixed BUGS:
   MRCC user port Labels can go 'missing' after adding several - FIXED
   Green button 'System Refresh' will erase the serial number - FIXED



This MRCC firmware version is available on the MRCC FW Update Page. Everybody should update their MRCC with this version.
v1.1.030 08/04/2021
Fixed BUGS:
   MRCC intermittently writes extra routings to saved preset file with "-1" - FIXED



v1.1.029 08/03/2021
Fixed BUGS:
   1) BUG: Last 3 MIDI OUT LEDs sometimes turn/flicker red - FIXED
   2) BUG: If preset file has "-1" will hang MRCC (root cause still under investigation) - FIXED
   3) BUG: Can't "load" preset FACTORY - FIXED



v1.1.025 07/20/2021
This MRCC firmware version is available on the Conductivelabs.com/download page.

Changes: Added additional bootup LED indicators. Specifically, when the boot process reaches Output LED 7, Input LEDs 1, 2 and 3 will light to indicate where MRCC is in the Preset load process.
We added this because there have been some reports of trouble at bootup loading the most recent preset, typically after a firmware update. We've been unable to replicate this, and the additional LED indicators will help us identify where in the code to look for issues.
If you experience an issue booting and the process stops at Output LED 7, please let us know on the forum how many Input LEDs lit up when that happened; 1, 2 or 3.



v1.1.024  07/01/21
      FIXED BUGS: 
  • Modifier Ch Map "Exclusive mode" blocks clock (and likely all 1 byte msgs)
  • Fixed some "if" logic issues for System Common & System Real Time messages so as not to be blocked
                happened in 3 places: CHANNEL_MAP, CHAN_TO_PORT & NOTE_MAP
  • 5-Pin MIDI now able to send SongPosition, TimeCodeQuarterFrame, SongSelect, & TuneRequest
  • [i]SysEx now passes thru the Host ports![/i]
Other changes: 
       Capped the LED brightness to 6, down from 10
         Added (4) new and tweaked a few of the Light Shows!
         MRCC MIDI Monitor screen now specifies: ActiveSensing "..?", SongPosition "Sp", TimeCodeQuarterFrame "Qt", SongSelect "Ss", & TuneRequest "@"
    
Known issue: TuneRequest msg type - blocked on USB Host ports



We've posted a new MRCC firmware 1.0.020 and updated User Manual, linked on the conductivelabs.com/download page. 


Changes in summary:

1. New setting in the SETTINGS menu for changing Remote 7 from "copied" ports, to remotely routable ports using the Y remote routing button. Be sure to enable Remote 7 in the settings menu, as MRCC only detects Remote 7 on bootup or when you toggle the Enable Remote 7 on SETTINGS page 2.
2. MRCC to MRCC routing (experimental), with remote output routing using the Y remote routing button. Just connect 2 MRCCs together with the RJ45 port. The 2nd MRCC is auto-detected when its attached and turned on.

A symbol that looks like [i]=Y  lights up in the top right corner of the screen when MRCC recognizes a remote device is attached.

To route to a remote, select an Input on the local MRCC, then press and hold the Y button, if a remote device is attached (Remote 7 or MRCC) you can select outputs on the remote device. For Remote 7 you can select output ports 1-5, or for another MRCC output ports 1-12. 

Press and hold the Y remote button to see remote routed outputs, and activity on the Activity screen. Indicators for remote routes are yellow.

The MRCC to MRCC code is not completely tested and might need some dialing in, but we tested MRCC to MRCC routing in both directions (simultaneously) and it works great. Even works over a 10 meter CAT6a cable. However, complex configurations could break it.

3. A new MOD called Channel to Port Mapping (C-P1) will map the channels of an input to individual channels on separate outputs. See the new manual for details.
4. A new MOD call Note Map (NMp) will let you select notes to transpose to. A Note Map Type setting defines rules for how notes will be transposed.

Bugs fixed:
A problem routing SysEx data from a PC port to a PC port.

Known issues:
FIXED in 1.1.024!  Using Exclusive mode on the Channel Map MOD blocks MIDI real-time data, such as clock.

In the works... a custom RJ45 splitter so you can remote route to a 2nd MRCC, and still use the Remote 7 as "copied" outputs.
If you can't wait for our splitter, I'll post the diagram in this thread.[/i]

RE: New Firmware Release 1.0.020 - oldgearguy - 06-23-2021

BTW - the "Quote -" button option on the forum still seems to quote the source message

Nice!  Our youngest daughter has a birthday and a high school graduation party this week and weekend, but after that I'll fire up the pair of MRCCs and do some cross pollination testing.  It would be extremely helpful having just a single CAT cable running to the other side of my space versus the dozen 25' + MIDI cables currently there.

re - Sysex routing bug -- does this also still apply when trying to get Sysex between a USB port and the PC port?

Looking at the manual only (not in front of the MRCC yet), If you add the C-P1 MOD and then do a Channel Map MOD to re-channel 1 to whatever the port number is, that will give you the ability to have a multi-track sequencer spit out all 16 channels  and then you can take that single input and send the individual channels to different destinations on their own MIDI channels, right?

So if you had 4 synths on ports 1-4 and each synth was set to receive on a single MIDI channel (channel happens to equal their assigned port number), then a multi-track sequence coming in port 5 can be routed to each synth so that each synth only sees the track data assigned to it on its assigned MIDI channel.

Does the C-P1 setting filter clock/realtime or anything else or does it just filter any/all data that is channel based?

RE: New Firmware Release 1.0.020 - Jesse Johannesen - 06-23-2021

Hey,
The Sysex routing bug appears to be on all routings, but only in the specific scenario where you Midi Map to the 4 channels and block all others (exclusive mode). It should be an easy fix, but isn't port dependent.

The C-P1 mod should work like this:
If I route port 3 to port 5 and place the C-P1 mod in the routing, then channel 5 of Port 3 will output at channel 1 of port 5. It's useful if you have each device set to a different port so that you can easily route to the correct device without needing many many channel map mod configurations (since there are only 6 available). This way you can set each device to channel 1 and plug them in and reliably route a single source to any of them without much complication.

(06-23-2021, 02:24 AM)oldgearguy Wrote: So if you had 4 synths on ports 1-4 and each synth was set to receive on a single MIDI channel (channel happens to equal their assigned port number), then a multi-track sequence coming in port 5 can be routed to each synth so that each synth only sees the track data assigned to it on its assigned MIDI channel.

So basically this, but the output channel is 1 instead of the port number.

(06-23-2021, 02:24 AM)oldgearguy Wrote: Does the C-P1 setting filter clock/realtime or anything else or does it just filter any/all data that is channel based?
It shouldn't block clock as far as I know, but it hasn't been tested by the beta team so this may need some further experimentation to confirm. If it does, let me know and I'll make a bug report and get it sorted.

Jesse

RE: New Firmware Release 1.0.029 - Darryl - 08-03-2021

[quote pid="4399" dateline="1624457062"]
(06-23-2021, 02:24 AM)oldgearguy Wrote: Does the C-P1 setting filter clock/realtime or anything else or does it just filter any/all data that is channel based?
It shouldn't block clock as far as I know, but it hasn't been tested by the beta team so this may need some further experimentation to confirm. If it does, let me know and I'll make a bug report and get it sorted.

Jesse
[/quote]

For anybody wondering, this was blocking clock and RT messages, and was fixed as of fw v1.1.024.

RE: New Firmware Release v1.0.041 - Darryl - 11-12-2021

Regarding the MRCC USB name experimental feature... We are not too optimistic that this will work in Windows. However, it may work in OSX. Hopefully someone will give it a try.

"While Audio MIDI Setup is launched but the USB MIDI device is disconnected, locate the cached device in the MIDI Studio window and delete it. Then re-attach the device. CoreMIDI will re-read the configuration descriptor and retrieve the string at the specified descriptor index in order to create a new cached device."

The MRCC has a unique USB serial number (as of v1.1.041 fw), and a unique name that Windows is recognizing. We can see MRCC-A and MRCC-Z in device manager. However, MIDI apps are still assigning the first read name to all of the MRCC ports.

RE: New Firmware Release v1.0.041 - Dark Waves - 11-15-2021

(06-22-2021, 07:46 PM)Darryl Wrote:
MRCC_v1.1.041_11-12-2021

FEATURE:
  1) Completed! (MAYBE!?!?!) MRCC "USB PC Name" can be augmented to MRCC-A to MRCC-Z, or orig MRCC (see Setting Menu 4).
       This is useful when more than one MRCC is connected to your PC.

  We have NOT been able to get Win10 to correctly identify the unique USB Friendly Names and USB Serial Numbers when cold booting
  with two MRCCs connected. We can clearly see the unique info in Device Manager.  NOTE: If you turn on the MRCCs after booting
  then everything seems to be clearly identified as unique.  Any feedback on why would be awesome!


Feedback: Having updated to this latest version, the behavior I'm getting is slightly different from before.

My experience with two routers: so I went from 1.1.035 to the current beta, 1.1.041, and named my #1 unit MRCC-A, and the #2 MRCC-B.  My procedure is typically to turn on the PC, then start the MRCCs in order, and then start the DAW, Studio One on Win 10.  Before now, the selections in the DAW dropdowns for routing were along the lines of MIDIIN1 MRCC and MIDIIN1 MRCC (2), up to MIDIIN12 (MRCC (1) or (2)).  Now they show from MIDIIN1 (MRCC-B) to MIDIIN24 (MRCC-B).  Essentially, B 1-12 are my unit 1 / A, and B 13-24 are for unit 2 / B.  Example, port 3 on my second unit is selected using port 15 in the list

However, if I power on the routers prior to the PC, the assignments in the DAW are reversed, reading MIDIIN1 (MRCC-A) to MIDIIN24 (MRCC-A), and what was 1-12 in the prior scenario is now 13-24 and vice versa.  I don't know if the exact combination stays consistent all the time, but at least so far this has been the result

RE: New Firmware Release v1.0.041 - Darryl - 11-18-2021

We're still working on this. We've found, based on a hot tip from a forum member, that changing the USB PID is likely enough to get MIDI apps to differentiate each MRCC. We didn't write the USB client stack, but we think we can modify it to dynamically read a PID that we create and store in the EEPROM, rather than reading it from the normal configuration file.

More to come next week.

RE: New Firmware Release v1.0.041 - oldgearguy - 12-06-2021

I'm running a Mac Mini (High Sierra) and the Ports are showing up in Waveform (formerly known as Tracktion) as

MRCC Port 1 - Port 12 and the second MRCC shows up as
MRCC  Port 1 - Port 12

the only difference is the extra space between 'C' and 'P'

I am running the latest OS and set the names to MRCC-A and MRCC-B

RE: New Firmware Release v1.0.041 - Jesse Johannesen - 12-07-2021

Thanks for the feedback Tom, I'll let Steve know we may have some kinks to work out.
Jesse

RE: New Firmware Release v1.0.041 - oldgearguy - 12-07-2021

(12-07-2021, 07:51 AM)Jesse Johannesen Wrote: Thanks for the feedback Tom, I'll let Steve know we may have some kinks to work out.
Jesse

Appreciate it.  I have a few cycles for testing potential fixes this week if necessary.

Also - updated my post to use Courier font so what I said can actually be seen.  lol