Yeah... all it does is print a never-ending stream of bytes (which could be interpreted as ASCII text) to standard output. The limit is how fast whatever's reading that text will take it. If you pipe it into aplay or sox at 8000 Hz, you're getting about 8 kilobytes per second. Writing to disk is much faster.95 @Someone Else 37 remember that music generation code?
I decided to give it a try, and after that instead of letting it play the music just letting it write to a file.
I now have a file that is 230.8 MB big that I can't open
good job me >_<
A safer way to do that would've been to just have it output to the console. That's much slower than writing to disk, and as it's scrolling past (or you can ^C it and scroll back up, if your terminal emulator lets you do that (most modern ones do)), you can see some of the structure in the output, and how some parts are long and smooth and how the frequency lines up (or doesn't line up) with the width of your terminal, whereas other parts are more chaotic and broken up by stuff going on at higher frequencies and faster timescales.97 well....I was just curious as to what it would have looked liked. The size doesn't bother me at all, its the fact that I can't open it that annoys the crap out of me