But while I could trigger output from a controller connected to input 1 or 8 and through from each output port, tested one at a time, to my module ... I couldn't patch directly from, for example, input 3 to output 3 with controller in and module out.
Strophoid wrote:If you select midex output 3 in cubase and connect something to midi out 3 on the midex then yes it should receive any data you send to it from Cubase. Question would be if Cubase takes the midex out of standalone mode? If not, then your PC doesn't fully recognise it.But while I could trigger output from a controller connected to input 1 or 8 and through from each output port, tested one at a time, to my module ... I couldn't patch directly from, for example, input 3 to output 3 with controller in and module out.
This is intended behaviour. There are 2 standalone options, you can switch between them using the button on the right. Option 1 is: send all midi data received at input 1 to output 1-8, option 2 is send all midi data received at input 8 to output 1-8. In standalone, inputs 2-7 are inactive. With that in mind, you already tested that input 1, input 8 and outputs 1-8 are all fully functional.
However, when Cubase launches it should take over the Midex, taking it out of standalone mode and disabling all routing until you make the connections in software. To test the other 6 inputs you'l need to use Cubase to do the midi routing. In other words, this observation is normal and no indication of a defective unit. What I mentioned above however about the routing from Cubase should work. If it doesn't to me it sounds like a driver problem and not a hardware problem.
MrSoundman wrote:Is it possible the OP is confusing the Midex with a MIDI router/patchbay? For example, something like the MOTU MIDI Express 128 XT also has patchbay and merger functionality, i.e. you can use a seperate software utility to program patches with any combination of inputs connecting to any combination of outputs, and these will work even when disconnected from the computer, whereas the Midex is "only" a MIDI interface ... the only routing available when not under control of a host computer is as outlined by Strophoid above.
Como Baila wrote:MrSoundman wrote:Wouldn't it be nice if Steinberg developed an 8 port interface with the functionality of the MOTU and LTB?
Just to mention that you can continue to use your Timepiece if you program your patches on an older XP machine using the parallel port (maybe an old laptop which only gets connected when you need to modify an existing patch) -- you can switch patches from the front panel of the Timepiece. You could e.g. take ADAT sync, send it out from the Timepiece as MTC and into the Midex and get Cubase to slave to it, have another patch where you just use it as a merger for convenience, etc.Como Baila wrote:I was successfully using a MOTU MIDI Timepiece Parallel
MrSoundman wrote:Just to mention that you can continue to use your Timepiece if you program your patches on an older XP machine using the parallel port (maybe an old laptop which only gets connected when you need to modify an existing patch) -- you can switch patches from the front panel of the Timepiece. You could e.g. take ADAT sync, send it out from the Timepiece as MTC and into the Midex and get Cubase to slave to it, have another patch where you just use it as a merger for convenience, etc.Como Baila wrote:I was successfully using a MOTU MIDI Timepiece Parallel
Just plug it in and use it ... no sync requirements as they'll both get LTB from CubaseComo Baila wrote:I'm now thinking of a second Midex 8. What is the deal on syncing two of them?
MrSoundman wrote:Just to mention that you can continue to use your Timepiece if you program your patches on an older XP machine using the parallel port (maybe an old laptop which only gets connected when you need to modify an existing patch) -- you can switch patches from the front panel of the Timepiece. You could e.g. take ADAT sync, send it out from the Timepiece as MTC and into the Midex and get Cubase to slave to it, have another patch where you just use it as a merger for convenience, etc.Como Baila wrote:I was successfully using a MOTU MIDI Timepiece Parallel
Reiknir wrote:This is why I keep an old pre-OSX mac around, I can buy old opcode interfaces for only 1 to 5 pounds apice these days on ebay, useless for the most part as MIDI interfaces but superb MIDI processors and mergers but need a MAC to control them to a degree.
MrSoundman wrote:Is it possible the OP is confusing the Midex with a MIDI router/patchbay? For example, something like the MOTU MIDI Express 128 XT also has patchbay and merger functionality, i.e. you can use a seperate software utility to program patches with any combination of inputs connecting to any combination of outputs, and these will work even when disconnected from the computer, whereas the Midex is "only" a MIDI interface ... the only routing available when not under control of a host computer is as outlined by Strophoid above.
Not the Midex itself, but combined with something like MIDI-OX, pretty much anything would be possible.Steve Fogal wrote:I'm not sure that the Midex can have such extensive routing even while connected to a computer...
You can do all of that with the Midex inside Cubase already, without any need for MIDI-OX; however, if you wanted to use, let's say, a standalone synth editing application you could use virtual MIDI ports (using e.g. MIDI Yoke) and route them to any hardware ports using MIDI-OX.Steve Fogal wrote:Are you saying that 'as long as' the Midex 8 is hooked up to a computer, and while using MIDI-OX, any of the Midex 8's 5-pin midi Inputs (incoming midi instrument/module) can be configured to any midi channel/track 'into Cubase'. Likewise, any midi channel/track 'within Cubase' can be routed out to any of the Midex 8's 5-pin midi Outputs to trigger a connected midi instrument/module![]()
Return to Legacy Steinberg Hardware
Users browsing this forum: No registered users and 1 guest