User Forum    :: Powered by YaBB
  « MIDI-OX User Forum - Patch/Program Change 2 Ctrl/Note »
Welcome, Guest. Please Login or Register.
May 10th, 2025, 9:43pm


Home Home Help Help Search Search Members Members Login Login Register Register


   MIDI-OX User Forum
   MIDI-OX
   Mapping Questions
(Moderator: Jamie OConnell)
   Patch/Program Change 2 Ctrl/Note
« Previous topic | Next topic »
Pages: 1  Reply Reply Notify of replies Notify of replies Send Topic Send Topic Print Print
   Author  Topic: Patch/Program Change 2 Ctrl/Note  (Read 916 times)
the_soul
New Member
*



MIDI-OX Rules!

   


Posts: 1
Patch/Program Change 2 Ctrl/Note
« on: Apr 25th, 2006, 6:37pm »
Quote Quote Modify Modify

Hello. I'm a very new user of Midi Ox. First I installed to use my notebook's touchpad as a midi controller (using Livelab's touchpad2Midi VST application).
 
Now I purchased a Boss FC-50 Footcontroller and a ESI Usb midi port intending to use it in Fruityloops to trigger samples and control some knobs and that.
 
The footcontroller only sends program changes and actually I can see fruityloops receiving the midi data I can't actually use it.
 
Now I would like to convert that data into something more useful to me - controller data and note on/note off messages.
For what I understand this super program called Midi Ox can do this, or cannot?
 
Thank You
IP Logged
Peter L Jones
Expert
*****




Hit it

   
WWW

Gender: male
Posts: 978
Re: Patch/Program Change 2 Ctrl/Note
« Reply #1 on: Apr 26th, 2006, 3:28am »
Quote Quote Modify Modify

You currently have a setup something like this:
Boss FC-50 MIDI Out -> Notebook MIDI In (ESI USB) -> Fruityloops
 
What you want to do is transform the MIDI data between "Notebook MIDI In (ESI USB)" and "Fruityloops":
Boss FC-50 MIDI Out -> Notebook MIDI In (ESI USB) -> (transform data) -> Fruityloops
 
The "(transform data)" will look like this:
MIDI OX -> MIDI Yoke
 
This gives a complete signal chain of:
Boss FC-50 MIDI Out -> Notebook MIDI In (ESI USB) -> MIDI OX -> MIDI Yoke -> Fruityloops
 
Okay, so I added "MIDI OX" and "MIDI Yoke"...  You need MIDI Yoke to route the output of MIDI OX to the input of Fruityloops - it's "virtual MIDI cable".  You need MIDI OX to do the actual message transformation.
 
It's probably worth trying to get a simple setup going before trying anything too adventurous -- i.e. just getting the data being passed through MIDI OX and into Fruityloops.  Once you've done that, you can try adding data mappings in MIDI OX to transform input messages.
IP Logged

"...Playing fast around the drums is one thing. But to play with people for others, to listen to, that's something else. That's a whole other world." -- Tony Williams
Pages: 1  Reply Reply Notify of replies Notify of replies Send Topic Send Topic Print Print

« Previous topic | Next topic »


MIDI-OX User Forum » Powered by YaBB 1 Gold - SP 1.3.1!
YaBB © 2000-2003. All Rights Reserved.