Posted 2003-12-05 22:07:40 by
Today, I had the occasion to write a program, in Python, to rip samples out of .mod files and store them in the .wav format. Here is it, the real mod sample ripping program from real mod sample rippers.
The needs this program fills that the competition doesn't are two: it runs as a batch process, and it tries to guess the intended playback rate of the samples by analyzing the note information in the patterns. Every other program I tried required two or three keystrokes per sample and set the sample rate in the output to 8363hz.
Despite these killer features, I realize that the cross-section of people who need to rip samples out of a directoryful of mods and people who have Python installed is very small. Consider this code a gift to the archaeologists of future civilizations.
And since I can't leave out my contemporaries, here's a summary of the information I gleaned from the experience:
- .wav file format: horrendous.
- .mod file format: utterly horrendous.
- binary file I/O in Python: surprisingly pleasant.
|python is great|
| Posted by Jim Crawford
on 2004-08-17 17:35:21 |
I love this. I look at rip.py again, almost a year after writing it, and it's perfectly understandable and, quite frankly, looks like poetry. I know this is not my doing, because none of my C or Perl code has ever looked this good a year later. Hooray for Python!
... I do seem to have forgotten what that star on line 80 does, though.