I hope you understand why MIDI & MOD importing's very difficult.
MIDI has simplistic audio, but it can have multiple channels (even more than the current & beta releases of FamiTracker can support). If the MIDI file has more sound channels than what you need, it will glitch out. That said, most MIDI files have more channels than FamiTracker can support because many MIDI composers don't take enough care to remove unused sound channels.
MOD is also difficult because MOD files can not only contain more sound channels than FamiTracker can support, but each instrument you create in a MOD tracker requires its own audio sample to be imported. In other words, MOD formatted music is like a FamiTracker project where every sound channel is a DPCM channel.
No no, I was meaning Midi exporting not Midi importing.
I'll be honest though, I don't understand the exact structure of Midi files and how you write to them (Otherwise I would've made my own music maker by now). But I have composed quite a few midi covers years ago so I know what it's capable of. (Pitch bending seems to be a little weird sometimes though... Some computers handle it differently than others...)
MIDI is industry standart, and thus it is much less limited than the trackers. The MIDI files are nothing like trackers, they are simply recorded stream of the events (like note on, off, program change, etc). The problem with MIDI importing is not number of the channels, but lack of similar structure (no patterns, no order list), and much higher time resolution than the trackers capable of (no rows at all, at least 1/250s quantize).
Regarding MIDI export, it is doable, though I personally see not much point in this. Need to make MIDI? Use proper tools. You never can get nice export anyway, and will have to edit it using MIDI editors (you will have to reassign instruments and redo all the drums, at least).
MIDI has simplistic audio, but it can have multiple channels (even more than the current & beta releases of FamiTracker can support). If the MIDI file has more sound channels than what you need, it will glitch out. That said, most MIDI files have more channels than FamiTracker can support because many MIDI composers don't take enough care to remove unused sound channels.
wow. please don't reply if you don't know what you're talking about.
MIDI has as simplistic or as complex audio as the units it communicates with. it's not really even an audio format per se, just instructions sent to a device that produces audio. as for why famitracker will never support MIDI import well, it's nothing to do with MIDI creators being lazy and not removing superfluous sound channels. even with three midi channels in use, since they can be polyphonic it's likely there'd be more notes than famitracker could successfully import anyway. midis probably have an average of about 7 or 8 layers/tracks. it's just an entirely different format that works in a totally different way.
as for all MOD formatted music having channels like the DPCM channel.. yeah, just don't talk about things you don't understand, period.
Er, I guess I was tired yesterday. I have no idea why I sugested mod exporting...
But as for Midis, that's how I was guessing they where set up, I just don't know about the exporting process from a programing point of view. I hope it's not too difficult...
I don't really see what the beef with MIDI import is. Just have the import function say "error" if the MIDI uses channels other than 1-4, or if it has more than one note playing simultaneously in any channel at any time. If you limit the MIDI import to just notes, and you're very strict about what MIDI data the file can contain (as described above), it should be very possible to make a fully working MIDI import function without too much effort, even if there are other features I would like jsr to prioritize.
That said, I'd appreciate if people would try to resist from posting anything but actual requests in this thread. If you request something and someone else tells you it's a pointless request (or whatever), start a new thread for the request where you can discuss the reasons why or why not to make the request.
I don't really see what the beef with MIDI import is. Just have the import function say "error" if the MIDI uses channels other than 1-4, or if it has more than one note playing simultaneously in any channel at any time. If you limit the MIDI import to just notes, and you're very strict about what MIDI data the file can contain (as described above), it should be very possible to make a fully working MIDI import function without too much effort, even if there are other features I would like jsr to prioritize.
That said, I'd appreciate if people would try to resist from posting anything but actual requests in this thread. If you request something and someone else tells you it's a pointless request (or whatever), start a new thread for the request where you can discuss the reasons why or why not to make the request.
I'd use MODplug to track songs because I'm more used to it, then follow the limitations of the MIDI import. Also, NSF importing would be awesome.
... MIDI has as simplistic or as complex audio as the units it communicates with. it's not really even an audio format per se, just instructions sent to a device that produces audio. as for why famitracker will never support MIDI import well, it's nothing to do with MIDI creators being lazy and not removing superfluous sound channels...
Thanks for correcting me on the MIDI portion of the problem. As for the MOD part, I just looked into it further & realized that it's nothing like what I've said (MODs come with their own audio samples for each instrument).
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
)