Actually, I might be able to fudge tempo export, as VST technically allows a plugin to ask the host for the tempo for a particular song position. The problem is locating tempo changes accurately and, perhaps more pertinently, coping with the VST hosts that don't support this particular VST feature. In any case, a default tempo could always be inserted (e.g. 120bpm), to be edited by the user later.

However, there are other problems associated with module export. For example, reViSiT allows you to specify a volume AND panning setting for any note, whereas older formats only allow one OR the other. And this is just one example of the problems of trying to export a reViSiT file in a format that can't encapsulate a reViSiT song - the technology has really moved on since the days of DOS trackers, some of which are over 20 years old! And I find it hard to imagine a large audience seeking this feature - are IT files still in widespread use? In any case, there are numerous forward-looking features that I'm more eager to code.

However, this may not be the last line in IT export support, in reViSiT. Knowing that some people might want to convert reViSiT songs to other formats, I designed reViSiT's file format to be as easily readable (by human and machine) as possible. It's simply an XML file (with samples as WAVs) packaged in a ZIP archive, so it should be relatively simple for a third-party developer to read reViSiT files and code their own IT/XM/MOD convertors. If anyone wants to take a shot at it, I'm happy to answer any technical questions they might have.

Best,
Chris