Posts: 4
Threads: 1
Joined: Apr 2025
Reputation:
0
0
Hello all. I have been using the MRCC for a while now in a Dawless setup, and I have a firm grasp on how to route everything, including PC ports. I was always eventually going to start using Studio one, and I like I can switch between dawlees and PC via the user profiles. The problem I am having is the way studio one lists the ports when adding a new instrument. It lists the ports with a number that doesn'r correspond to the mrcc numbers, and none of the 12 PC ports show up either on the initial setup screen, or within the program on a track by track basis. I does have on MRCC port with no number, and I think that is the PC port, as I do get midi activity to my mono-timbrel synths, but it doesn't have any option to select any of the 12 PC ports. For my mono-timbrel synths that's fine, omly need one midi channel per, but for my multi-timbrel synths I was going to use a single port each for them so they can use all 16 channels of that port. I have read other posts about a FW update that changed the way the MRCC does this, but I was thinking it could also be a Studio One thing. Perfect world, the labels I gave each port on the MRCC would show up in Studio One for ease of use, but if Studio One isn't seeing multiple PC ports it would defeat the purpose. Hoping for any advice on this especially from Studio One users using the MRCC. I use a combi of din and usb just for clarity. I could also be missing something obvious lol. I do have another midi router I could use but I really like the MRCC and would hate to have to switch routers when I want to switch from dawless to PC. Cheers, TBrett.
Posts: 1,325
Threads: 7
Joined: Jan 2020
Reputation:
67
7
If I remember correctly, we had been doing something which was problematic with the way things enumerated a while back which mostly caused problems with Apple, but mainly when using 2 devices. Are you on the latest beta firmware? As you may have seen we recently took a good deep look at our USB enumeration and port naming and I think we're pretty confident that naming issues are fixed on our end. It's always possible that I'm wrong, but I don't think there is anything we're doing that would prevent the ports from showing up in normal (correctly implemented) use cases. You my reach out to the Studio one devs and ask them to get in touch with us (support@conductivelabs.com) and we can see if there's anything we can do to steer them in the right direction.
Posts: 4
Threads: 1
Joined: Apr 2025
Reputation:
0
0
(04-11-2025, 01:02 PM)Jesse Johannesen Wrote: If I remember correctly, we had been doing something which was problematic with the way things enumerated a while back which mostly caused problems with Apple, but mainly when using 2 devices. Are you on the latest beta firmware? As you may have seen we recently took a good deep look at our USB enumeration and port naming and I think we're pretty confident that naming issues are fixed on our end. It's always possible that I'm wrong, but I don't think there is anything we're doing that would prevent the ports from showing up in normal (correctly implemented) use cases. You my reach out to the Studio one devs and ask them to get in touch with us (support@conductivelabs.com) and we can see if there's anything we can do to steer them in the right direction.
Thanks for the reply. I slept on it and realized my mistake. I was confusing the ports listed on studio one between the PC ports and the din/usb inputs ( it had been a long day). Woke up and it was clear what I had been thinking. MRCC is port 1, and then MRCC2 is port 2 etc. Set it all up on the MRCC and is working now, although when I put my 4 mono-timbre synths all on port 1 (even with different midi channel assignments) Studio One warned of conflicts. Are the PC ports on the MRCC supposed to be for one unit or is it fine to run multiples on 1 port? Even though it all set up in S1 with labels now, I will look at the beta FW, I normally avoid betas, but I will check it out.
Posts: 1,325
Threads: 7
Joined: Jan 2020
Reputation:
67
7
Great news.
As for ports, they can support any number of devices as long as they're routed. The limit is 16 channels per port, but even with 1 channel, you can send that port to the mrcc and route it to 12 other ports on channel 1 and they will all play if devices are listening on that channel. The other limit is only one software can utilize a port at a time, so studio one can use port 1 but then if you were also running Reason, it could not access port 1 until you disconnected studio one. Does that make sense?
Posts: 4
Threads: 1
Joined: Apr 2025
Reputation:
0
0
(04-11-2025, 11:09 PM)Jesse Johannesen Wrote: Great news.
As for ports, they can support any number of devices as long as they're routed. The limit is 16 channels per port, but even with 1 channel, you can send that port to the mrcc and route it to 12 other ports on channel 1 and they will all play if devices are listening on that channel. The other limit is only one software can utilize a port at a time, so studio one can use port 1 but then if you were also running Reason, it could not access port 1 until you disconnected studio one. Does that make sense?
Yep, and I assume the same for Software editors for my synths. Haven't tried them yet, but I have plenty of prts to work with. Thanks a heap.
Posts: 1,325
Threads: 7
Joined: Jan 2020
Reputation:
67
7
(04-12-2025, 12:13 AM)TBrett Wrote: (04-11-2025, 11:09 PM)Jesse Johannesen Wrote: Great news.
As for ports, they can support any number of devices as long as they're routed. The limit is 16 channels per port, but even with 1 channel, you can send that port to the mrcc and route it to 12 other ports on channel 1 and they will all play if devices are listening on that channel. The other limit is only one software can utilize a port at a time, so studio one can use port 1 but then if you were also running Reason, it could not access port 1 until you disconnected studio one. Does that make sense?
Yep, and I assume the same for Software editors for my synths. Haven't tried them yet, but I have plenty of prts to work with. Thanks a heap.
It depends on whether the software editors use MIDI or direct USB connections. If they require USB connection, MRCC will not provide that as it's not a USB hub, but MIDI connections should work. I think the most recent beta fw has a bug we're still ironing out which may be a problem for sending Sysex over some ports. I hope to have a solution soon, but for now if you plan on using editors sending Sysex and run into trouble try loading the previous released FW and see if that fixes any issues.
Posts: 4
Threads: 1
Joined: Apr 2025
Reputation:
0
0
04-18-2025, 02:17 PM
(This post was last modified: 04-18-2025, 02:20 PM by TBrett.)
Hi Jesse. I was using some software editors yersterday and thought I would give some feedback. I found that I could send midi out to a module but not back to the pc. For instance, using Edisyn for my E-Mu P2500, I could sned a test tone, and change presets, but I couldn't download the iibrary from the P2500. Both were on PC port 4 in and out, sys ex id correct. Same for my JV 2080, could change patcges and play notes, but couldn't get info back. Also I noticed I couldn't run an editor and use Studio one at the same time, do I need to use a seperate port for editors so I can? I also change my config on the mrcc and just dedicated 1 port for each synth, but I notice some difference in the port numbering. For instance. My deepmind 6 is set to port 6 in and out on the mrcc, but Studio one I had to set it port 7. Some were different, some, like the E-Mu were the same, port 4.The JV 2080 same, port 5. all the others were different. Through trial and error I set it all up and it's functional, and not sure if it's operator error, but though you might like the feed back. I installed the beta hex 1.1.089. Cheers.
|
