MIDI-OX User Forum - Print Page


    
      
        MIDI-OX User Forum
        (http://www.midiox.com/cgi-bin/yabb/YaBB.pl)
      

        General >> General Board >> basic questions from a newbie
        
(Message started by: unca_d on Aug 29^th, 2013, 6:57am)

Title: basic questions from a newbie
Post by unca_d on Aug 29^th, 2013, 6:57am

hi, everyone,
some really basic questions from a newbie to this forum.
most questions have to do with compatibility.
My equipment is PC Win 7 64 bit, DAW - Reaper, Roland A800Pro Midi keyboard controller, Yamaha WX5 wind controller, Native Instruments Komplete 8, Kontakt 5, the 3 MusicLab guitars, etc.
I thought I was reasonably intelligent until I encountered MIDI in dealing with digital music. I'm initially concerned about Midi-Ox and Midi-Yoke and their compatibility with Win7 64 bit.
Perhaps some knowledgeable forumer can either inform me or direct me to forum posts before I open either one of the Midi-Ox software products. Thanks

Title: Re: basic questions from a newbie
Post by Breath on Aug 31^st, 2013, 11:11pm

Although I don't use Win 7 there are others who seemed to have got it working OK.
I was waiting for others to comment before I replied.
That is why you question had remained unanswered for so long.

Perhaps if you give a few more details of what you are trying to do we could help you further.

All the best
Royce

Title: Re: basic questions from a newbie
Post by unca_d on Sep 4^th, 2013, 4:19pm

to Breath,
responding to your query, re: what I am intending to use
midi ox for.
My impression is that midi ox can be used as a "viewer" so to speak, which sits in the "transmission" line of midi data, and a person new to midi can "see" better what's happening. That's
one impression.
The other reasons have to do with the use of a Yamaha wind controller, WX5. My understanding is that midi ox is needed in loading sound patches from a sound generator (Roland SonicCell or Yamaha vx m11 (I think is the model number)) to the WX5.
Another reason has to do with loading drum patches from Native Instruments and my DAW to the Roland A800Pro drum pads on the keyboard.
Another possible use is the LoopB30 which I recently purchased, but haven't used yet.
I've decided to sell my DX7 because getting DX Manager's 1600-odd patches to work with my DAW seemed way over my head. But that would have been another possible use for the midi ox.
I'm basically wanting to know if there are any issues in Window 7 64-bit with midi ox. Forget it or install it?
Thanks, Breath.

Title: Re: basic questions from a newbie
Post by Breath on Sep 4^th, 2013, 8:24pm

Hi,
your last point first. MidiOx is a fairly clean install and so I would say try it and see if it works for you.
MidiOx is indeed a Midi data viewer and very useful to see what your gear is putting into the computer.

Roland's SonicCell (SC) has a great Editor and a separate Library program. You can get them for free from any of the Roland sites.
The patches are transmitted by a type of Midi message called System Exclusive (sysex for short). MidiOx can easily transmit and receive sysex files.
The library program for the SC can load and write Standard Midi Files (SMF) which is just the sysex message wrapped up inside some other data.
It is quite easy to convert from sysex to SMF and back to sysex.

I'm not sure what a Yamaha VX M11 is.

The WX5 doesn't have patches loaded into it.
It is just a controller that sends out Note on and off messages along with breath controller messages, patch change messages and modulation messages.
Basically, it just plays the synth and the synth makes the sound.

The A800 Pro is also a Midi controller like the WX5.
It can't generate any sounds, but unlike the WX5 you can change what messages it outputs when, for example, the drum pads are hit or the knobs are moved.

On the WX5 you use physical switches to change the setup, but in the A800 Pro it stores the setup in memory and so uses sysex to save and load setups. There is a free editor for the A800 Pro that you can also get from Roland.

MidiOx can only 'see' what is coming into the computer. That is, when the DAW sends a message you can't display it in MidiOx.
You could connect your Out to the In on you Midi interface hardware with a cable. That way when the DAW sent out a message to the Midi Hardware it would come back in and could be read by MidiOx.

What LoopBE30 (and MidiYoke available here) does is act like an Output -> Cable -> Input in software. You get your DAW to output to a LoopBE30 output as if it is Midi hardware and then get MidiOx to look at the other end of the LoopBE30 'cable'.

MidiOx can do a lot more, like filter out certain messages or change output from channel 2 to channel 5 and lots of other things.

I use it a lot to send my WX5 Midi messages to two sounds on different channels in my SC. One sound gets all the Midi information the other sound is just used for the start of the note and so I have MidiOx filter out the breath information as it is not needed.

It is a bit of a Midi Swiss army knife.

All this stuff is a bit daunting when you first start, but it is really worth persevering despite the frustration.
Feel free to ask anything you like here and we'll see if we can help.

All the best
Royce

Title: Re: basic questions from a newbie
Post by Jamie OConnell on Nov 1^st, 2016, 11:56pm

Although MIDI-OX is a 32 bit binary, it works fine under Win 7, 8, 10 x64. MIDI Yoke, however can only operate between 32 bit MIDI apps. LOOPBE30 is a good alternative than can operate between Win32 and x64 applications.