User Forum :: Powered by YaBB
« MIDI-OX User Forum - Recent Posts »
Welcome, Guest. Please Login or Register.
Dec 10th, 2023, 2:51am


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


 1   MIDI-OX / Mapping Questions / Re: Data Mapping, Port Routing, Port Objects  Dec 1st, 2023, 9:35pm 
Started by jamos | Last post by jamos
Thanks for the suggestions, Royce.  
 
Neither instrument has a patch mapping facility, and the sampler is actually a 16 channel multi-timbral instrument, which is why I need MIDI-OX to filter that for me. Fortunately I figured this out: just delete the unwanted channels from the associated port object.
 
Good to know about the multiple data maps, that was not at all clear from the docs. As it happens I have set everything up with a set of general data maps, one per song, along with appropriate port configs.  
 
I have a fully working system now (!). I spent some time on a detour when I tried to use customized port names, the bugs in that feature and the strangeness of the file locations took a while to sort out. The system now loads my custom profile on power up, and everything follows my patch changes.
  Reply Reply Quote Quote Notify of replies Notify of replies

 2   MIDI-OX / Questions and Discussion / Re: convert .txm map file to .oxm for older versio  Nov 29th, 2023, 3:15pm 
Started by stanwebber | Last post by stanwebber
ok, i figured it out on my own. the only difference between moxmap version 4 and 5 is that 5 adds a delay value after the clone entry. in my case simply doing a replace all of 'N,0' with 'N' converted it to the older format.
 
the reason for doing this is that midiox v7 is simply incompatible with win98se. it seems to work with some stuff, but crashes the system hard with some combinations. midiox v6 works solid and i think v6.5.1 was the last release (and it supports .tmx v4). the author actually hosts all the previous versions on his website, but doesn't provide links. if you look at the version history and alter the filename in the url you can get it.
 
btw, the map i pasted is a simple mt32 to gm instrument conversion that someone copied from scummvm.
  Reply Reply Quote Quote Notify of replies Notify of replies

 3   MIDI-OX / Mapping Questions / Re: Sending signal back to Behringer X-Touch  Nov 28th, 2023, 6:46pm 
Started by beastdg18 | Last post by Breath
Momentary to Toggle.
To do this you need to remember what the state of the switch is.
 'Is it off - yes - OK I'll turn it on'
Similarly 'is it on - yes - OK I'll turn it off'
Both together is 'Is it off - Yes - OK I'll turn it on - No - OK I'll turn it off'
Better 'Is it off - Yes - OK I'll turn it on - else I'll turn it off'
 
When you code you simply use 'State = Not State' (off goes to on and on goes to off)
 
As before, the trouble is MidiOx doesn't remember the state of the switch. So you need to use a script. Sorry.
 
I have an example of how to to this with a script here http://www.midiox.com/cgi-bin/yabb/YaBB.pl?board=MOXScript;action=displa y;num=1657511134
 
I hope this is a good starting point for you.
 
I would have a good look at the Behringer manual as the BCR2k and the BCF2k can change the mode of all the switches - Toggle <=> Momentary
 
All the best
Royce
  Reply Reply Quote Quote Notify of replies Notify of replies

 4   MIDI-OX / Questions and Discussion / Re: Reaper 7 and Vepro midi bus issue  Nov 20th, 2023, 6:45pm 
Started by GeneralMidi | Last post by Breath
Hi Luke
 
You can see the Midi output of an application by using a Midi driver like MidiYoke (from theMidiOx website) or loopMidi which might be better for you in this case.
All loopMidi is is a software that creates Midi Cables to patch to applications and / or hardware.  
But the output is Multiclient so you can connect to more than one software application or hardware Midi device.
 
So you connect things together by  
Application (Reaper7) -> Midi out to a loopMidi port, let's say the first one 'loopMidi'  -> Into MidiOx by going to Options/Midi Devices... and adding loopMidi as an input port
 
also  ->   VEPRO Midi input =  loopMidi (with the data coming from Reaper 7)  
 
Now you should be able to see the data Reaper is sending in the MidiOx Input Monitor window.
VEPRO should also be playing as normal.
 
Hope that helps
 
All the best
Royce
  Reply Reply Quote Quote Notify of replies Notify of replies

 5   MIDI-OX / Mapping Questions / Re: 2 USB to Midi- One Roland XP80, One Korg NX5r  Nov 10th, 2023, 5:18pm 
Started by RaiBeck | Last post by Breath
Hi
You don't say what MidiSport device you are using, but if it is the 2x2 it has a 'Direct Thru' button. Is this what you are talking about or is it a UNO or a different MidiSport (4x4 or 8XCool?
 
I'll assume it is a UNO and you have used the In, Out and Thru On the XP-80
 
PC-> USB-> UNO Out -> XP-80 In
 XP-80 Thru -> NS5r In
 
Either:  
XP-80 Out -> UNO In -> USB-> PC
or
NS5r Out -> UNO In -> USB-> PC
 
If you want both synths connected youw ill need either a MidiSport 2x2 (or greater)
or
A hardware Midi merger like Midi Solutions Merger https://midisolutions.com/prodmrg.htm
Xp-80 Out -> Merger In 1
NX5r Out -> Merger In 2
and
Merger Out (either one) -> UNO In
 
If you are sending or receiving Sysex the header will separate the data.
The M-Audio driver is MultiClient so you can have the two editors running t the same time.
 
Hope the helps
Royce
 
 
  Reply Reply Quote Quote Notify of replies Notify of replies

 6   MIDI-OX / Questions and Discussion / Re: CAN`T SCROLL DOWN PORTS PAGE  Nov 4th, 2023, 9:17pm 
Started by Gestalt_Miner | Last post by Breath
HI
I don't think Jamie ever imagined 85 ports (I assume this means roughly 45 lines with ins and outs).
 
He has vertical scroll bars for the data windows, but I can't seem to get my 20 plus a side ports to bring vertical scroll bars up on the Port Routing window.
 
Your best fit might be by having MidiOx full screen height and using the menu Window/Tile Vertically or CTRL +F5 as this will compress the space between the DIN plug pics.
 
You can see all your connections in the Options/Midi Devices : Port Mapping window.
You can also make connections here by dragging from the 'Port Map Objects' (inputs) to an output in the 'Port Mapping' listbox as you would on the Port Routing window.
You can also drag an oxm file (located in the Port Map Objects below the input ports ) can be dragged to the connection you just made to  have a datamap just for this connection.
 
Not very satisfactory, but I hope it is a usable work around.
 
An alternative might be to split your devices across two or more instances (of MidiOxs running at the save time).
The layout and devices selected (and connection assigned datamaps) are saved separately for each instance of MidiOx so starting the multiple instances of MidiOx will restore the correct setup in each.
You can use different display features - colour, font size etc - to distinguish one instance of MidiOx from earlier one as this configuration is also saved against that particular instance.
 
 
There is a catch though.  
If some your midi devices have only a single client Midi driver (older Win versions default driver, for example) you will get a memory error when you try to use them in two or more instances of MidiOx.
You will need to either install a MultiClient driver from the device maker or use an earlier instance of Midiox to connect to a MidiYoke or loopMidi software cables (these are MultiClient drivers) and use this as your input in later instances.
eg
Keyboard -> MS Midi driver Single Client -> MidiOx1: Port Routing -> loopMidi1 out - now your keyboard input has a MultiClient loopMidi driver
Start MidiOx2
  loopMidi1 in -> MidiOx2 -> : Port Routing -> synth A
Start MidiOx3
  loopMidi1 in -> MidiOx3 -> : Port Routing -> synth B
etc
 
The other catch is that you can't start just MidiOx2 and MidiOx5, for example, to run by themselves.  
If you you want to just see MidiOx2 and MidiOx5 you have to start MidiOx1 through to MidiOx5, and once they are started you can kill off MidiOx1, MidiOx3 and MidiOx4.
 
 
All the best
Royce
  Reply Reply Quote Quote Notify of replies Notify of replies

 7   MIDI-OX / Questions and Discussion / Re: standalone  Nov 3rd, 2023, 8:57am 
Started by jackkcaj | Last post by mollyyang2106
on Dec 10th, 2013, 1:49pm, jackkcaj wrote:
This review of seo reporting tool for seo companies is a lifesaver for marketers. It's like having a trusted compass in the sea of analytics and data. The in-depth examination of the top 10 options, complete with pros and cons, simplifies the decision-making process. This guide is an indispensable tool in our SEO arsenal.
 
Thanks in advance,
 
jack

 
To set up your virtual DJ software to record your performance in Sonar, you'll need to establish a connection between the two applications using MIDI-OX and a virtual MIDI cable like MIDI Yoke. Here's a step-by-step guide on how to do this:
 
Download and Install MIDI-OX and MIDI Yoke:
 
Make sure you've already installed MIDI-OX and MIDI Yoke, which you mentioned you have.
Open MIDI-OX:
 
Launch MIDI-OX on your Windows XP computer.
Configure Virtual DJ:
 
Open your virtual DJ software (e.g., Virtual DJ) and go to the settings or preferences.
Look for the MIDI settings within the virtual DJ software.
Map MIDI Output to MIDI Yoke:
 
In the virtual DJ settings, find the option to map MIDI output or MIDI controller.
Set the MIDI output of your virtual DJ software to MIDI Yoke (e.g., MIDI Yoke 1 or any available port). This step allows Virtual DJ to send MIDI data to MIDI Yoke.
Configure MIDI-OX:
 
In MIDI-OX, go to the "Options" menu and select "MIDI Devices."
In the "MIDI Inputs" section, make sure your controller (if you're using one) is selected as an input device.
In the "MIDI Outputs" section, make sure MIDI Yoke (the same port you selected in Virtual DJ) is selected as an output device.
MIDI Routing:
 
MIDI Yoke acts as a virtual MIDI cable that connects your virtual DJ software to MIDI-OX.
Any MIDI messages sent by Virtual DJ should now be received by MIDI-OX via MIDI Yoke.
Record in Sonar:
 
In Sonar, set up a new audio or MIDI track to record your performance.
Set the input of the track to receive MIDI from MIDI Yoke (or the port you selected).
Arm the track for recording.
Start Recording:
 
Start recording in Sonar.
Perform in your virtual DJ software, and the MIDI data will be recorded in Sonar.
Playback and Edit:
 
After recording, you can play back and edit your performance in Sonar as needed.
This setup allows you to capture your virtual DJ performance in Sonar using MIDI data. Keep in mind that you may need to configure specific MIDI mappings or controls in both Virtual DJ and Sonar to ensure that your performance is accurately recorded.
 
Remember that Windows XP is an older operating system, and driver support for modern hardware can be limited. If you encounter any issues with your sound card or MIDI setup, it could be due to compatibility problems. Ensure you have the latest drivers for your PreSonus Firewire sound card.
  Reply Reply Quote Quote Notify of replies Notify of replies

 8   MIDI-OX / Questions and Discussion / Re: Korg Pa700 and VSTi  Oct 4th, 2023, 10:21pm 
Started by cobanoti | Last post by Breath
Hi
Sorry this has taken so long,  
 
I'm not too sure I understand your question.
 
"My plan is to use Bank Select command to activate midi channels where the VST instruments are on."
 
Do you want to change the Midi Channel on the messages that are coming out of the keyboard (perhaps channel 1) to the one matching the VST?
 
If so, there are three parts to set up .... the first is creating the data maps
 
You need three DataMaps so go to Menu Options / Data Mapping... bring up the the Translation Map dialog.
 
Map1 from Channel 1 to Channel 2 -  
Press 'insert' a line and the 'Define Mapping dialog' pops up.
 
Input :
Channel 1 , Any, -1 , -1, -1, -1  (-1 = any value)
Output :
Channel 2,Match Input, -1, -1, -1, -1
 
Press Ok to go back to the Translation Map dialog.
Save as "Chan1To2.oxm"
 
Map2 from Channel 1 to Channel 3 -  
Press 'Edit" to go back to the 'Define Mapping dialog' that should still have the map you just created.
Change the Output line from 'Channel 2' to  'Channel 3' and leave everything else the same.
 
Press Ok to go back to the Translation Map dialog.
Save as "Chan1To3.oxm"
 
 
If the Keyboard is outputting on channel 1 and Kontakt is on channel 1 then we need a map to get back to 'No changing channel'
 
Map3 from Channel 1 to channel 1 - Really 'Do Nothing'
Press 'Edit' again.
 
For the input line you could use 'Channel 1' as before, but the real 'do nothing' setting is Channel = 'Any'
 
Input :
Any, Any, -1 , -1, -1, -1  
Output :
Match Input, Match Input, -1, -1, -1, -1
 
Press Ok to go back to the Translation Map dialog.
Save as "DoNothing.oxm"
 
 
Make sure 'Turn Map On' is not checked
Press OK
 
***************************************
 
Now you are ready to to create a Patch Map (menu Options / Patch Map...) so you can use patch change messages to swap the maps in and out.
 
To make sure MidiOx will only act on your keyboards Patch change messages, select '1' (or what ever your keyboard's output channel is) only on 'Map On These Input Channels'
 
There is a list table that has a label ...
'Num' - this is the patch number that MidiOx will respond to
'Map Location' - this is where you select the Data Maps that turns on when that Patch Change (PC) message is sent.
 
That is, press PC on your keyboard and MidiOx will load in the new data map.
So we will use rows 'Num' = 0 or 1 or 2  (which is Patch 1 or 2 or 3)
Highlight row Num=0 and press the button 'Assign' and select the file "DoNothing.oxm"
Highlight row Num=1 and press the button 'Assign' and select the file "Chan1To2.oxm"
Highlight row Num=2 and press the button 'Assign' and select the file "Chan1To3.oxm"
 
Check the box  "Turn Map On (after OK)".
You should save this Patch Map with the save button.
Press OK.
 
Now when you send PC 2 from your keyboard to the computer, MidiOx will load in the data Map to change the keyboards output from Channel 1 to Channel 2.
Send PC 3 from your keyboard to the computer to change the keyboards output from Channel 1 to Channel 3.
Send PC 0 from your keyboard to the computer to leave the keyboards output alone.
 
**************************************
 
The last little bit is to route the  changed Midi messages out of MidiOx and into the program that has you VST's.
The Korg uses USB to bring in the Midi -> MidiOx to change it -> MidiOx to route it out to a Midi port -> Your VST program's Midi Input.
 
If you have a separate Midi interface you could route it from MidiOx and send it out of this.  
Then you could use a Midi cable to bring it back in and use this interface as your Midi input in the VST program.
 
The alternative is to use a free program that does this in software - like loopMidi
 
Post again if you are still having trouble.
 
Hope this helps
 
Royce
 
  Reply Reply Quote Quote Notify of replies Notify of replies

 9   MIDI-OX / Questions and Discussion / Re: cant dump presets off therapsid synth into mid  Sep 19th, 2023, 8:51pm 
Started by sumerzy | Last post by Breath
Hi
I'll assume that ...
 you have connected a Midi interface,  
 you have set it up in MidiOx Options / Midi Device... with Input and Output selected.  
 you have View / Port Routings selected and can see the Midi interface connections in this window.
 you have the Synth Midi Out  connected to the Midi In of the interface
 the synth is currently powered OFF
 Make sure that MidiOx is not filtering out Sysex by opening Options/Midi Filter...  
     and having a look to see what is filtered and that the bottom option 'Display Sysex...' is checked.
 
To set up MidiOx to receive sysex...
1. select menu View/Sysex... to open a new dialog
2. select the menu on the new dialog Sysex /Manual Dump...
A 'Save As' window will pop up.
Move to the directory you want  to save to .
Name  the file (".syx" will be added to the end )
Press 'Save' the save dialog will close and a new small ''waiting" dialog will open .
 
3. Power up the synth with the 'Preset Down' pressed.
If the synth outputs Midi you will see the Number in the Waiting window going up.
 
When the number stops going up (the synth has finished dumping the sysex) press OK.
Now you have saved the sysex.
 
When loading sysex into the synth, the file data is sent from the MIDI-OX Event Port on the bottom left of the Midi Port Routing window.
 
Hope that helps
 
All the best
Royce
 
 
  Reply Reply Quote Quote Notify of replies Notify of replies

 10   MIDI-OX / MIDI-OX Bug List / Re: Midi Ox seems to crash my Win11 desktop/Focusr  Sep 16th, 2023, 1:35am 
Started by bravedog | Last post by Breath
Hi
You are most welcome to ask any questions that are Midi or MidiOx related.
 
I have a Focusrite 2i4 2nd gen and a 8i6 3rd gen and both have Midi in and out and work perfectly.
 
I don't use the Microsoft Midi drivers that came with the Windows version that I use because they have led to a few problems.
So I always download the Focusrite drivers from their website and they work perfectly.
 
What version of Win11 do you use? (Home, Pro , Education, Enterprise, SE etc)
I though that a lot of the Midi problems were supposed to be fixed in Win 11 (but I would still download the drivers from Focusrite).
 
Let me know how you get on
 
All the best
Royce
 
 
  Reply Reply Quote Quote Notify of replies Notify of replies

Return to the board index.


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