06-15-2022, 04:31 PM
Rapidly failing detail memory will keep me from getting too specific on a similar situation involving an E-mu XL-7 Command Station and its legacy editor, E-loader, which I managed to install in Win 10 "compatibility mode' as it was made for Win XP (the USB drivers for the module wouldn't install no matter what I tried, being outdated, apparently).
Anyway, I needed the editor to install a way overdue OS update to the XL-7, which I did, and found it has other functions, like a MIDI monitor window, editor, etc. that I thought I'd try out. To summarize (it's been a few weeks) when looking to connect the program to the device through the MRCC, I found that some ports would successfully load (regardless of the module being connected there or not) but most wouldn't. If my DAW, Studio One, was loaded on the PC and was using the ports already, it seemed to take priority, so that none of the ports would connect, even though they all showed up as choices in the editor's dropdown selection list.
While it's something that would be nice to hammer out to work more consistently, it's not anything urgent. Having wanted to get to the bottom of the problem, I wasn't even sure whether to start looking for help in this community, or with the DAW or E-mu communities, so that's why I'm just piggy backing on this thread, since it's already going, and seems like the common factor is the MRCC, which if correct, would still be good to know and resolve. Updating the OS was one of. if not the, first SysEx operation through my MRCCs, or even at all, so as a non-power user I was mainly pleased it worked period. As an aside, given my lack of experience (and confidence) with SysEx, I initially opted to connect the module to the MIDI ports of my Focusrite audio interface, for simplicity, but the cables wouldn't reach, so I daisy chained the Focusrite through other MRCC ports and routed to the E-mu on two others, and that all worked like a charm. It was only later that the experimenting with various ports started. As I said, there are more details I can't quite recall, but this covers the gist of the situation.
Anyway, I needed the editor to install a way overdue OS update to the XL-7, which I did, and found it has other functions, like a MIDI monitor window, editor, etc. that I thought I'd try out. To summarize (it's been a few weeks) when looking to connect the program to the device through the MRCC, I found that some ports would successfully load (regardless of the module being connected there or not) but most wouldn't. If my DAW, Studio One, was loaded on the PC and was using the ports already, it seemed to take priority, so that none of the ports would connect, even though they all showed up as choices in the editor's dropdown selection list.
While it's something that would be nice to hammer out to work more consistently, it's not anything urgent. Having wanted to get to the bottom of the problem, I wasn't even sure whether to start looking for help in this community, or with the DAW or E-mu communities, so that's why I'm just piggy backing on this thread, since it's already going, and seems like the common factor is the MRCC, which if correct, would still be good to know and resolve. Updating the OS was one of. if not the, first SysEx operation through my MRCCs, or even at all, so as a non-power user I was mainly pleased it worked period. As an aside, given my lack of experience (and confidence) with SysEx, I initially opted to connect the module to the MIDI ports of my Focusrite audio interface, for simplicity, but the cables wouldn't reach, so I daisy chained the Focusrite through other MRCC ports and routed to the E-mu on two others, and that all worked like a charm. It was only later that the experimenting with various ports started. As I said, there are more details I can't quite recall, but this covers the gist of the situation.