It's really pathetic that we still don't have a fully protracker-compatible program.
Hopefully 8bitBubsy's rewrite will remedy that.

Yeah, now I finally get it. Thanks CMDR

Hi RG, sorry I forgot to reply to your PM ages ago.
I've completely forgotten, and my hdd has been wiped since then, so I can't just slam some files your way
If I get it working again i'll let you know!

It exports as three different MED filetypes (for different versions), standard midi file, an executable or a protracker mod.
Any commands, additional block lines, or tracks that aren't included in protracker just get excluded on save.

Sure don't mind. As far as I know, some OctaMED commands are different than Protracker, and so mod files made in MED could have troubles with some players that were meant to play Protracker mod files.

But in fact I don't know exactly what extra features on OctaMED wouldn't allow it to export the same type of mod file as Protracker would (besides the obvious synth stuff MED has).

Why use octamed, protracker or milky when you can use renoise with a couple of vst's?

Why open them in octamed if they open fine in Milky?

I hope you don't mind me asking, but why open them in protracker if they open fine in octamed anyway?

Yep, I´m already doing that. I´m making some modules saving with different config settings on Milky untill I find one that can be opened with no problems on PT. Thanks a lot for your help!

It's a very loooong shot, but did you check the mod replay routine in milky config? It can be set to either PT2.x or PT3.x.
Not that it should have anything to do with the saved file.

About the sample noises, do they appear at the beginning of samples? If so, perhaps they are some sort of header (non-raw sample format) or other meta-data, so you should double-check anything you did with the instruments. Smartest thing would be to start a new module in milky form scratch and keep fiddling with it until you manage to make it not load in protracker. Using an emu would be simplest for this.

Frankly, whatever this is, it should be treated as a bug and reported. Milky is supposed to let you know if you did anything to break the mod compatibility.
I'll try to load all my milky-modules into protracker, see if it's a common problem.

If you would post the MOD file it would help a damn lot to know what's up.

I guess you're probably right. I only used few instruments on those tracks.

Anyway, let's hope cTrix or someone else reads this thread xD

Maybe the number of instruments has something to do with it? I don't know and wish I could be of some assistance.

We need a .mod guru in here!

I have a couple of .mod tunes I made last year on OctaMED 5.04 -- nothing fancy, no sample loops and only simple commands (I was beginning to learn Amiga trackers). And they work fine on PT2.3 (just tested them). 

What I roughly know about MED's commands is that most of them are pretty much the same as Protrackers commands.

We spent about 3 weeks trying to figure out why dispyz's datarunner .mod wasn't working for use in the tracker hero game. I remember him writing it on octamed soundstudio and throwing a rage when neither winamp or renoise would play the sound file. I asked if it worked in protracker, and when it didn't we knew something was up. I'm sure there's an easy answer but Amiga tracking and beer usually go hand-in-hand.

Anyway, I wish I had documented some of the process, but I do remember having to go into protracker and adjusting various settings which seemed to adhere to the incredibly strict rules of the .mod format. Octamed was certainly a little more lenient and opened files as .mod when others wouldn't.

Whatever it is, I'm personally convinced of there being a difference in how octamed/protracker handle .mods. Correct me if I'm wrong please!

I followed RG's tip and opened the files on OctaMED v5.04. Strangely (but fortunately) they opened fine! I thought I was opening the wrong .mod file on PT2.3, went to it again and it continues opening the file badly. 4mat, I was aware of the C-3/C-5 ranging and was already using it for these test files. Also, I didn't do any sample looping. I open Milkytracker, already subtract some channels so it's only 4-channel, use raw samples, put the config on Amiga linear and resampling, and save it as .mod. But I really have no clue why OctaMED opened it and PT2.3 didn't.

Anyway, it really should be good to know more about this "mod standards" RG put in question.