MIDI-OX User Forum (http://www.midiox.com/cgi-bin/yabb/YaBB.pl)
General >> General Board >> Help with MF2T file
(Message started by: mr4chnt on Jul 10th, 2009, 7:28pm)

Title: Help with MF2T file
Post by mr4chnt on Jul 10th, 2009, 7:28pm
Hi (first post)

I have converted a few midi files to text using MF2T and back again (after editing) using T2MF.

I recognize the "note on" commands and the "change program" commands but what does a line like "24 Par ch=1 c=1 v=0" mean?

Ideally there is some documentaion for MF2T that would answer this and other questions. (?)

Thanks in advance.

Doug

Title: Re: Help with MF2T file
Post by Jamie OConnell on Aug 2nd, 2009, 10:25am
There is a readme.txt in the mft.zip that explains the various text formatting.  For your benefit, I will reproduce the relevant part here:

Format of the textfile:
-----------------------

The following representation of the midievents is generated (between
[] the form when -v is used:

File header:            Mfile <format> <ntrks> <division>
Start of track:            MTrk
End of track:            TrkEnd

Note On:            On <ch> <note> <vol>
Note Off:            Off <ch> <note> <vol>
Poly Pressure:            PoPr[PolyPr] <ch> <note> <val>
Channel Pressure:      ChPr[ChanPr] <ch> <val>
Controller parameter:      Par[Param] <ch> <con> <val>
Pitch bend:            Pb <ch> <val>
Program change:            PrCh[ProgCh] <ch> <prog>
Sysex message:            SysEx <hex>
Arbutrary midi bytes:      Arb <hex>

Sequence nr:            Seqnr <num>
Key signature:            KeySig <num> <manor>
Tempo:                  Tempo <num>
Time signature:            TimeSig <num>/<num> <num> <num>
SMPTE event:            SMPTE <num> <num> <num> <num> <num>

Meta text events:      Meta <texttype> <string>
Meta end of track:      Meta TrkEnd
Sequencer specific:      SeqSpec <type> <hex>
Misc meta events:      Meta <type> <hex>

The <> have the following meaning:

<ch>            ch=<num>
<note>            n=<noteval>  [note=<noteval>]
<vol>            v=<num> [vol=<num>]
<val>            v=<num> [val=<num>]
<con>            c=<num> [con=<num>]
<prog>            p=<num> [prog=<num>]
<manor>            minor or major
<noteval>      either a <num> or A-G optionally followed by #,
           followed by <num> without intermediate spaces.

<texttype>      Text Copyright SeqName TrkName InstrName Lyric Marker Cue
           or <type>
<type>            a hex number of the form 0xab
<hex>            a sequence of 2-digit hex numbers (without 0x)
           separated by space
<string>      a string between double quotes (like "text").

Channel numbers are 1-based, all other numbers are as they appear in
the midifile.
<division> is either a positive number (giving the time resolution in
clicks per quarter note) or a negative number followed by a positive
number (giving SMPTE timing).
<format> <ntrks> <num> are decimal numbers.
The <num> in the Pb is the real value (two midibytes combined)
In Tempo it is a long (32 bits) value. Others are in the interval 0-127
The SysEx sequence contains the leading F0 and the trailing F7.

Title: Re: Help with MF2T file
Post by mr4chnt on Aug 2nd, 2009, 8:33pm
Hi Jamie,

Thanks for your assistance.  

I did eventually figure out that I had the readme.txt file so was able to find the answer, but do appreciate your reply.

Doug



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