So I caddy during the summer, which meant that today I had 4+ hours of just thinking. And here is the result.

I have made a program that will play sound on the 84+'s with the bad ram. I just started it a few hours ago, so I'm still working on it. But I have gotten near perfect sound quality from my calculator. It uses pulse width modulation (turning the link port on and off really fast) to get the amount of voltage it needs to play a note. I currently have it set up for 44.1khz, because I wanted to keep this on off above the human level of hearing. But then shortly after I made it I realized that it is playing a 44khz note and not a 22khz note. So I'll be working on 22khz because 44kb/s really eats up calculator memory.

I also have proven to myself that my speed program was right when it said my calculator runs at 15.8 mhz and not 14.9 mhz like the first speed test program said. I figured this out because I have the song set to play at 15.5 mhz and on my calculator and it runs too fast.

I'll put a video on youtube once I get 22khz working. If you are going to test this, don't use wabbitemu. Your sound card doesn't know what to do with a 44khz note and it will sound awful. So make sure you test it on a real calculator. It is currently set up in an app and a program, the app is the music, and the program is the program. This is so I don't have to resend it every time I change it.

If you want to make your own song. You have to put it in 44,100 hz, mono, 8bit. Then use a hex editor to cut off the header, replace all zeros with ones, and put a zero at the end. (Song starts 4 bytes after "DATA"). Then you have to find a way to convert it to an app and send it to your calculator. I used brandonW's new binTo8xk and then used wappsign.

I have also included the little demo I made for myself. It's only 5 seconds long but it's 340,000 bytes on calculator. Oh, and someone please laugh at the source, the technique I used has max sound quality at the cost of the programmer. (255 subroutines each 1 t-state different from each other.

That's awesome!

I need to either: 1) Find my cable converter 2) Buy another one

that's epic.  Someone should convert a rickroll. 

Those 25 seconds take 15 minutes to send to calc. But I guess that makes it even more funny if someone does it.

Oh well, 22khz coming soon. I just did the preliminary copying and pasting for my routines. The source is over 8,000 lines long now.

oh, wow
But yes, it'd be totally worth it
I agree, this'd deserve a POTY award, especially if you get some compression in there.

cool, can't wait to see what you come up with!

It should work for the 83+SE AFAICT.
Unless he gets compression, though, any song more than a few seconds will be SE-only due to the storage space required.

That'd give you access to all 64KB of address space, but it might not be worth it.
You'd have to do two or three erases every time you wanted to play a file, which makes it slow to start up and puts wear and tear on the flash.
But if you must, I suggest you make it optional
Ignore my skepticism and continue. Keep up the good work!
Edit: 700^th post!