Not sure what is causing this, but it has happened to me quite a few times now. Actually, since the second time it happened, I haven't been able to use MO3ENC any at all.
I'm making a program that will take a list of files and run MO3ENC with some specified options on all of them, using LAME. Now of course, the end user may not have LAME calibrated for MO3ENC, so I told my program to calibrate it on startup. Well, that seemed to work okay the first couple times, and I'm not sure what caused everything to stop working (that might not even be relevant), but eventually when I would run MO3ENC.EXE, instead of printing out the module information and encoding it, it would just print out the top two copyright notice lines. It wouldn't even tell me the song name and stuff, as if it couldn't find the file. But I'm sure it would have an error message if it couldn't find the file. My command line and the output is as follows:
C:\Downloads\MuSiC\ModArchive>C:\Downloads\MuSiC\ModArchive\mo3enc.exe -e2 -m7 "
MO3 Encoder 2.1 - IT/XM/S3M/MOD/MTM/UMX to MO3
===== (c) 2002-2005 Ian Luck =========================== www.un4seen.com =====
It has been running for 48 minutes now, and the file is only one meg. So it isn't that the file is too large, or that I'm not giving it enough time either. Also, it constantly uses around 87-99% processor power and I can't figure out what it is doing. I was hoping I could find the source code to the encoder somewhere so that I could figure out what it was doing then, but no such luck.
The very first time this happened, I deleted the registry keys associated with MO3, and that fixed it. Now, though, that isn't helping. I don't know exactly what the problem is, but I'm hoping this is something wrong that I'm doing on my part.
BTW...if anyone is wondering, yes, I have the entire ModArchive and I am trying to compress it using MO3 to allow it to be BitTorrent-ed in a reasonable timeframe.
It is also worth mentioning that my program, after clearing the registry, re-calibrates about 2.5 seconds afterward. Should I be waiting longer, perhaps? I can see Windows having some potential issues with things like that, using cache or something.... Also, dunno if this matters at all, but I am taking "a-imag.it" and saving it as "a-imag.it.mo3". Perhaps MO3ENC sees this as the same thing or something?
EDIT: I think I should mention that it does this on any file, not just the one mentioned above.