Very big file size reduction when converting MIDI to mmf

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Carl. - 03 Jan 2004 04:43 GMT

Now and then I find a MIDI that won't play properly on my phone, even when
the number of tracks are reduced to just a few (usually gets stuck on a note
and then speeds up).

To resolve this, I used PSMplay to convert a MIDI to 40 chord .mmf and back
again. I checked and the resulting file had all of the original notes. It
also plays just fine.

But the new file is only 4k, while the original was 13k. What was removed?

Reply to this Message

Jutta - 19 Jan 2004 02:43 GMT

Very Briefly,

Many MIDI files contains a LOT of information
that gets deleted upon conversion to .mmf
For instance, channel aftertouch, pitchbend (very common),
polyphonic aftertouch (less common). And let me tell
you, even the first two can generate amounts of data
that dwarf the note-#-on-and-offs that you're left with.

That's a pretty simply explanation. Rock On!

Jutta

On 02 Jan 2004, you wrote in alt.cellular.ericsson:

> Now and then I find a MIDI that won't play properly on my phone, even
> when the number of tracks are reduced to just a few (usually gets
[quoted text clipped - 6 lines]
> But the new file is only 4k, while the original was 13k. What was
> removed?

Reply to this Message

Carl. - 19 Jan 2004 06:06 GMT

Thanks for the info. I later noticed on other files that the pitch bend
effects were gone.

What is a channel aftertouch?

> Very Briefly,
>
[quoted text clipped - 21 lines]
> > But the new file is only 4k, while the original was 13k. What was
> > removed?

Reply to this Message