PlanetZ forums - scopeusers.com

I got a deal on a used Axiom 25 I have tried everything for a week but can not get it to send midi to scope 4.5. The Axiom is connected with a midi cable and I can control Scope from Reaper but not directly like my old keyboard ?

the midi out on the axiom is connected to the midi in cable on the whip?

if you connect a midi monitor to the pulsar/scope/luna/ps midi source, are there messages in the monitor window when you play the axiom?

Just hit the ADVANCED button and after that the middle B (German h) to activate the midi out.
There are little white notes about the function of the key and that middle B is for switching between
two modes.

1. Your Axiom sends midi only over USB but you can use the midi out from your sequencer (little MidiDIN symbol)
2. Your Axiom send midi via USB and parallel also to the midi out (no symbol)

You just have to switch to that 2nd mode...
Hope that helps...

Janni wrote:Just hit the ADVANCED button and after that the middle B (German h) to activate the midi out.
...
You just have to switch to that 2nd mode...

does it remember the mode setting between power cycles?

I have activated the midi out on the Axiom It actully starts in midi you have to enable usb on the Axiom. I will try the midi monitor today thanks Gary

So I tried midi monitor and no activity I connected the Axiom to my NI Maschine with midi out to Scope and the midi monitor displayed note on and off. I would like to control scope with the Axiom ? Could I use some virtual cable any ideas

I have mine connected via usb, and have a sequencer running. the sequencer recieves the notes from usb, and sends them to the scope enviroment thru "sequencer midi SOURCE", so i can hook that module up to whatever device i want to control.

rolo wrote:Could I use some virtual cable any ideas

If you don't want to use a sequencer, you could use MusicLab's MIDI Connection Center 1.1 (Freeware!)
and connect the Axiom Mididriver with Scope's driver... The only disadvantage is you have to hit
the connect button after every computer restart.

http://www.musiclab.com/downloads/free/

kylie wrote:does it remember the mode setting between power cycles?

Just tried it out and: YES!

I personally have my Axiom midi out connected to the Scope midi in via an old MOTU micro express (parallel port).
A really nice stand alone patchbay with many cool features (like filtering out active sensing).
But afaik the Axiom doesn't send active senseing, so this should't be the problem...

Thanks I will try Midi Tools. Would be interesting to see If your Axiom would work directly in to Scope.

Janni wrote:

kylie wrote:does it remember the mode setting between power cycles?

Just tried it out and: YES!

yeah, yesterday I had time to figure out myself (got a used one 2 days ago)
mine came with din midi out disabled, but with your hint it was done in a split seconds

I personally have my Axiom midi out connected to the Scope midi in via an old MOTU micro express (parallel port).

I intend to hook it to a motu express xt (yes, parallel, too ) I must have somewhere. since you have a similar setup I expect it to work fine.
did you try to configure it with enigma? I didn't have time yet, and the machine I hooked it up to first was a win2k that ended up with nasty bluescreen after the axiom was plugged into it and the "new hardware found" process started...
(with XP it was all fine)

I have my Axiom connected via USB to my MacBook (sequencers, Enigma (no probs with MacOsX)) and
the DIN midi goes to the MOTU micro express which is connected via parallel port to my PC (Scope machine).
Since the MOTU has a pretty routing window (clockworks console on PC) I can now switch on midi out
on my Axiom and can play my Plugiator (also connected to MOTU) or any scope synth without starting a sequencer.
If I want to do sequencer work, I just switch off midi out on my Axiom and can use this midi out from my sequencer...
I love this setup!

But there are two VERY SMALL minus points.... When I switch on my Axiom, it produces only once a little midi loop which screws
the MOTU... I just switch the MOTU off and on again an everything is fine again.... meanwhile even the pc dosn't loose the parallel interface
(if it does, just hit refresh on MOTU's clockworks console and it's back again).
The looping prob could be solved but since I'm already used to switch the motu on after the axiom I leave it like this...
The other point is, you have to check the internal battery of the motu... If it's too old, you gonna have driver problems and finally
the unit looses all settings...

sounds great. thanks for the battery hint, I'll check whether it's easy or not to change it. don't like the idea of unracking the unit for that procedure, though...

If you don't want to use a sequencer, you could use MusicLab's MIDI Connection Center 1.1 (Freeware!)
and connect the Axiom Mididriver with Scope's driver... The only disadvantage is you have to hit
the connect button after every computer restart.

http://www.musiclab.com/downloads/free/

Thanks this worked great Janni

rolo wrote:

janni wrote:If you don't want to use a sequencer, you could use MusicLab's MIDI Connection Center 1.1 (Freeware!)
and connect the Axiom Mididriver with Scope's driver... The only disadvantage is you have to hit
the connect button after every computer restart.

http://www.musiclab.com/downloads/free/

Thanks this worked great Janni

nice to know. would placing the "connect" button (or maybe a scripted call, if possible) in the autostart group an option?

rolo wrote:Thanks this worked great Janni

perfect!

kylie wrote:would placing the "connect" button (or maybe a scripted call, if possible) in the autostart group an option?

afaik the problem is that your scope startup project has to be loaded completly before mcc is starting... Else the mididrivers are not ready....
If you could program some kind of delay I think it might work.

Janni wrote:

kylie wrote:would placing the "connect" button (or maybe a scripted call, if possible) in the autostart group an option?

afaik the problem is that your scope startup project has to be loaded completly before mcc is starting... Else the mididrivers are not ready....
If you could program some kind of delay I think it might work.

mh, I see...
for now it seems to be safe to just hit the button