• Kewl
  • ADAT user
  • Offline
  • From: Montreal, Canada
  • Registered: 2007-11-26
  • Posts: 10

Topic: MIDI problems with ADI-642 & Micstasy

PowerMac G5 4*2.4 GHz, Mac OS X 10.5.8, M-Audio MIDISPORT 2x2, RME ADI-642, RME Micstasy, RME MIDI Remote 1.5

When I only connect the ADI-642, the MIDI Remote controls it. When I only connect the Micstasy, the MIDI Remote controls it.

When I connect both of them

Midisport -> ADI-642 -> Micstasy -> Midisport
or
Midisport -> Micstasy -> ADI-642 -> Midisport

the MIDI doest not see the Micstasy, only the ADI.

ADI-642 ID is set to 0, Micstasy to 1.

Any ideas?

- Daniel

Kewl's Website

2 Reply by MC

  • MC
  • MC
  • Administrator
  • Offline
  • From: Germany/Thailand
  • Registered: 2007-04-06
  • Posts: 25,670

Re: MIDI problems with ADI-642 & Micstasy

The MIDI input is not passed through to the MIDI output with the 642 - as shown in the manual. So you need to split its output and merge both outputs for all remote request feedback to be present at the Midisport.

Regards
Matthias Carstens
RME

MC's Website

  • Kewl
  • ADAT user
  • Offline
  • From: Montreal, Canada
  • Registered: 2007-11-26
  • Posts: 10

Re: MIDI problems with ADI-642 & Micstasy

MC wrote:

So you need to split its output and merge both outputs for all remote request feedback to be present at the Midisport.

Split "its" output: I guess you're referring to the MIDI interface output? Merge "both" outputs: I guess you're referring to the 642 and Micstasy outputs?

Thanks,

Daniel

Kewl's Website

4 Reply by MC

  • MC
  • MC
  • Administrator
  • Offline
  • From: Germany/Thailand
  • Registered: 2007-04-06
  • Posts: 25,670

Re: MIDI problems with ADI-642 & Micstasy

You can split the MIDI interface output, or the output from the Micstasy when used as first device. Then merge the Micstasy's and the 642's MIDI outputs back into one input of the MIDISport.

Regards
Matthias Carstens
RME

MC's Website