Maybe I am just doing this wrong. I have built the floppy tunes project and it works great! I actually made my own ide header on a perf board and expanded to using two drives for extra noise! I have noticed that the assembly in the fclocks song is much different than what I am getting back from the online converter. I have used multiple and single track type 1 AND 0 type midis and they all sound horrible! Some dont even act like they are the same song when playing on the drive. The included mario sounds like mario, however is very quiete. Would I be correct to assume I am either missing something or that fclocks is different since it is the only one that the newer floppy tunes recognizes? I would really appreciate any tips on how I can get good loud clear sounding results out of other songs. Also I am using the supplied 8xp compiler, works great!

Somet01, welcome to Cemetech! Would you care to Introduce Yourself when you get a chance? I'm glad to hear that you followed my FloppyTunes instructions and found them understandable. Yes, you have correctly deduced that the signal-generator module in mobileTunes is much different than the signal-generator in floppyTunes. The one in mobileTunes uses the two different channels for two musical channels each, for a total of four channels. By contrast, floppyTunes uses a single musical channel, which it pulses over one data line, and uses the other data line to control the floppy drive's (drives', in this case) head direction to keep the head centered along the stepper spindle. I'm glad you're able to use the Doors CS SDK to compile the songs properly. Here's the note file that you need in order to create proper floppyTunes songs; I'm sorry to say that there's not really an automated tool for it:


Code:


In the NOTES GO HERE section, you need to fill in pairs of the form:

Code:


Note is one of the values from the fourth column of the following table (the column starting with 1761 for an octave-0 C note). The duration value should be the number of beats for the note times the value in the fifth column (the one starting 131). The first column is the octave of each note, and the second column is the note name. The third column is the frequency of the given note in Hz, just for reference.


Code:

Actually, I see I have a sort of vague Javascript tool for this, which I'd be happy to pass along, but it seems semi-broken.

Hey! Thanks for the info! It definitely seems like the floppy tunes coding is the way to go since I could easily tweak the frequency and duration of notes. I would certainly appreciate the chance at checking out your java tool if you want to send that my way. I am wondering though, to streamline things, if there are any other tools out there to read a type 0 midi as note/duration and output frequency... Sounds like an opportunity! Did you end up writing the code for clocks from scratch? I want to show this to some guys at our upcoming e-week and was hoping I could figure out how to code some ACDC or something similar. Thanks again!

Will do. I believe you can grab it in the mobileTunes 1.0 zip at ticalc.org. Indeed! The mobileTunes 3 converter that I wrote does that, but the notes then get further post-processed extensively. If you could manage to make the mobileTunes 3 converter spit out info for a one-track MIDI, you could definitely convert that output to work with floppyTunes; you'd strip off three of the five columns to remove three of the channels, then adjust the duration value. Sounds great, and if you do it, I'd love to see/hear the results. Yes, I wrote it from scratch for the original mobileTunes 1.0 player, which was monophonic, so I was able to re-use it with minimal work.