Search options (Page 14 of 18)

There are FM chips in every old Sound Blaster compatible card - OPL2/3. You just need old enough PC or an old enough notebook with built-in sound card. There are a lot MS-DOS trackers for these chips, they works under Windows 9x as well.

I somehow forgot that YM2612 was actually used in one home computer - FM Towns. It is japanese and not imported anyway.

Developing costs are highly depends from what is required. Is it involves custom hardware (could seriously increase costs), how much features are needed and how complex they are (considering hardware limitations), which interface (generally text-based interface with a lot of hex numbers could be done much faster than something visual with knobs, graphs etc). Then approximation how much time the thing would take should be done, based on previous projects, multiplied to medium programmer's wage (it is $1200-1400/month here, lowest is 500, top are 2000+), and total price negotiated. I think, for this case it should be some certain price for some certain work done, not just payment for time spent, with payments in few parts, per milestones.

How much time it could take. TFM MM in very basic form, which allowed to make music, with simplest instrument editor, with pattern editor, without a lot of service functions including copy/paste, was made in less than a month (don't forget, it is an app for powerful PC, made with RAD tools, and it is FM only). Service functions were added in next three years, in few takes of 1-2 weeks of active work each - 80/20 rule in action. There was half of year between start of work and first public version, although active work was ~2 months, I guess. Considering there are no RAD tools for SMD, and it far less powerful than PC (so you can't do things in dumb or bruteforce way), my estimate, without thinking on details, is that you could expect some very basic thing done in a month, some usable in ~three months, and then everything depends from feature requests.

Also, you could check how much other native console trackers development took. Recent examples: NTRQ took 5 months from start to first public release, and Pulsar about 6 months, these projects were done in part time, but by very experienced man.

Atari ST has absolutely different and much simpler sound chip, which is also used in Amstrad CPC, MSX, ZX Spectrum, and some computers and consoles. Most of these computers has a lot of native trackers for it, there are tens of thousands of songs made for it.

There are no computers or other consoles that has exactly the same sound chip as Genesis. Probably it is actually custom OPN version made by Yamaha for Sega needs (they also made Genesis video chip, which was renumbered to Sega part number by some reason). There are some computers with other OPN chips, which are somewhat compatible (whole NEC PC-88 range has either YM2203 or YM2608), however they are all japanese, never were sold outside Japan, and I haven't ever heard about any musical software for japanese computers other than MML compilers. Never heard about any japanese tracker for any platform as well.

I just inform people that if someone really need the thing (a native tracker for Genesis), he has option to hire me for this work. I'm not going to do project of this scale, which I'm absolutely not need and never will use, for free. If someone thinks it is easy and want to get it for free or cheap - he has options to do it himself, or wait for indefinite time, etc. If someone thinks I could pay his needs, he has option too, guess which one.

Although I'm able to make one, I would never use it by myself, so I would only make it for some serious $, as it is a lot of work.

TmEE also had some plans on something native, but it is unknown when and how, he still haven't released his cross tracker yet (there was an alpha in 2007, and it was used to make music for Pier Solar).

Export a TFD from editor, then use TFMCOM from /replayers/ folder as any other command line utility - tfmcom yourfile.tfd, and you'll get TFC.

Emulator does not work properly for me, even in 128K mode. The sound is high-pitched and jerky, almost complete mess. The same sound in TS2068 mode, so it probably always emulate standart AY ports.