MIDI-OX User Forum - Print Page


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

        MIDI-OX >> Mapping Questions >> Text included in midiox translation map
        
(Message started by: mortier on Feb 13^th, 2009, 7:42am)

Title: Text included in midiox translation map
Post by mortier on Feb 13^th, 2009, 7:42am

Dear all, I have several translation maps made up for different fairground organ scales.

Is there any way when viewing the translation map window that a means of entering text could be incorporated into that window that tells me which one of my maps I am looking at.

Many thanks for a wonderful piece of software, I use this in conjuction with Hurchalla Maple VMidi Cable v3.56 and all seems very stable and very reliable.

Title: Re: Text included in midiox translation map
Post by babotas on Mar 11^th, 2009, 7:20pm

If I understand your question correctly:

I believe one can not have comments or text annotations in the map itself.

But, a suitable descriptive name for the file to where one saves that map is plenty good, I feel.

Then in the MIDI-Ox window that shows the connections, Right-clicking on the junction point square symbol, in properties, one can read the name of the file, so as to know what map one is using.

Title: Re: Text included in midiox translation map
Post by Jamie OConnell on Mar 29^th, 2009, 9:30pm

If you save the map as an ascii text mapping (*.txm), you can place comments on a row by beginning with a semi-colon: ';' (leave out the quotes). In general, *.txm are supported where ever *.oxm are. The other thing you can do is give your maps descriptive names, or even use the Windows feature of associating a comment with a file (right-click it and go to properties).

Title: Re: Text included in midiox translation map
Post by mekline on Apr 1^st, 2009, 4:20pm

Another quick way to "identify" which Translation Map overlay is the current Map in the Translation Map Window is to use a dummy entry ( I usually make it the first item ) and use the SysEX message to put a number or your own code in the line.

Note: The number or code you use has to be in 2 digit hex - but you can be creative in using numbers and letters that can at least help you identify the current map in the window.

Of course it is not a text message or a nice window label but it is useful.

I have dozens and dozens of maps some with just minor variations in volumes, programs, or effects and when I bring up MIDIOX and click the MIDI Data Mapping Transforms icon button in the tool bar I can quickly determine which map is "on" the current overlay.

This is something that works for me - I don't know if it would help anyone else but thought I'd pass it along :)

Title: Re: Text included in midiox translation map
Post by mortier on Apr 1^st, 2009, 6:24pm

Hi Mekline, Thanks for your reply, it seems you have, like myself, use several maps which you load as required. I find that when I open MidiOx, then click on the red - blue notes to open the Translation Map, I don't know which one of my maps I am looking at. I have to clear it down and then re-load to be sure. I thank you for the info. that by using SysEx, I can enter a 2 digit hex code which serves as my identification.
Ideally, I would love the ability to be able to enter text into the map window so I could identify which map I am looking at but it doesn't seen possible. Jamie replied to me and mentioned to save the map as .txm - not .oxm and then text could be entered by placing a ';' first before the text. I have tried this but without success. I found that I could load the mapping details into Wordpad but all attempts to enter text corrupted the mapping. - Just wanted to thank you for pointing out the SysEx to me, regards, Ken

Title: Re: Text included in midiox translation map
Post by mekline on Apr 1^st, 2009, 7:35pm

You're sure welcome.

I am mostly a novice with MIDIOX and use trial and error to find ways to do things - but can honestly say that it is the most wondrful and useful program I have.

Without MIDIOX I would pack up and sail away. There is nothing ... nothing like it or can substitute for the things it does. The Swiss Army Knife icon says so much.

We all owe Jamie ..... It is an amazing program.

- Mike -

P.S. I had the same problem, when I open MIDIOX I was never sure what MAP I used last - also sometimes while running I wanted to check the MAP file in use and I could never be sure what it was. So I started naming my files "## + description" Then with the dummy line and sysex message as just the ## I was in business - I knew what file was in use. Later I used more digits to indicate other things.

Title: Re: Text included in midiox translation map
Post by Jamie OConnell on Apr 2^nd, 2009, 5:18pm

Here is an example of how to enter comments (this file is in your Program Files MIDI-OX Map folder as Example.txm):

Code:

MOXMAP Version 5

; Any line beginning with a ';' is a comment, and will be ignored.
; If you overwrite a map using MIDI-OX Translation Map [Save...], any
; existing comments will be overwritten and discarded;

; The Header and version# are mandatory.
; Currently the header is: 'MOXMAP Version 4'

; Sections are enclosed in square backets ([]) on a line by themselves.
; Any lines follwing a Section designator belong to that section.
; Currently there are 2 sections: [Map] and [Options].

[Map]
; Each line in the Map section defines a mapping step in the Data Map.
; The only type that is very different is when mapping to a SysEx string.
; See the last line in the [Map] section for an example.

; Basically the format is:
; SrcChan,SrcMsg,SrcV1Min,SrcV1Max,SrcV2Min,SrcV1Max,Clone(Y/N),TrgChan,TrgMsg,TrgV1Min,TrgV1Max,TrgV2Min,TrgV1Max
; In addtion, if the "Use Input Value 1" flag should be set, the line should have ",>" tagged on.
; Similarly, if "Use Input Value 2" flag should be set, the line should have ",<" tagged on.
; Example Mapping steps:

*,NoteOn,36,84,1,127,Y,0,*,NRPN,656,656,0,16383,>
*,NoteOn,36,84,*,*,N,0,*,*,*,*,*,*
*,Ctrl,1,1,0,127,N,0,*,NRPN,160,160,0,16256
*,NoteOn,36,84,1,127,Y,0,*,NRPN,656,656,0,16383,>,<
*,NoteOn,36,84,*,*,N,0,*,*,*,*,*,*
*,Ctrl,1,1,0,127,N,0,*,NRPN,160,160,0,16256
1,Ctrl,64,64,64,127,N,0,*,SysEx,F0 7E 7F 09 01 F7

; The format for mapping to SysEx is:
; SrcChan,SrcMsg,SrcV1Min,SrcV1Max,SrcV2Min,SrcV1Max,Clone(Y/N),*,SysEx,F0 XX XX XX ... F7
; In other words, the SysEx string is tacked on to the end of the message -- directly following "SysEx,".

; NOTES
; Channel: ranges from 1 - 16 (or *)
; Message Names: NoteOff, NoteOn, KeyAft, Ctrl, ProgChg, ChanAft, PitchB, NRPN, SysEx, Discard, or *
; Clone: Y or N
; Use Input Value 1: >
; Use Input Value 2: <
; Most Values: 0 - 127
; NRPN Numbers and Values: 0 - 16383

; Items must be seperated by commas (except the SysEx string). It's OK to insert spaces (example: 1, 2 , 3,4).
; In general, names and characters are case insensitive ('sysex' is the same as 'SysEx').
; If you're ever unsure how something might be specified, try entering it in the MIDI-OX Translation Map
; and then [Save...] it as an MIDIOX ASCII Text File (.txm). Then open it in Notepad to see how it's
; specified.

[Options]
; Options are optional. When specified, they cause the corresponding
; map level flag to be set to the value (0=off or 1=on).

; Following are the currently defined flags:
WaitForFullNRPN=0
MapNRPNDataIncr=1
SendFullNRPN=0
ReverseDataEntry=0

Title: Re: Text included in midiox translation map
Post by sqgl on Jun 16^th, 2009, 3:54pm

Thanks. That is helpful as my maps are getting unwieldly.
Pity we can't put comments in the actual editor :(

A bigger editing window would be cool in a future version.
Resizable perhaps. Sortable by column would be perfect.
I'm sure there are many things on the wish list.

Rock steady is better than buggy features,
and MidiOx sure is rock steady.