9CBADDCB8BABCDAB

8090a0b0c0d0e0f0

(play them on kit 2. #2 I made by starting with the cursor at the left (and the field zeroed out) and typing 123456789abcdef. The program turned it into that, and it doesn't sound half bad!)

As for how it should end...Maybe explain that binary is the only way to represent any number if all you have is two numbers to work with. And that this invention enables all electronic gadgets, from remote controls to satellites. :

]]>And thanx for corrections.

Another One: FAF90088280820C0

]]>90A0C01A1842D182

On the Binary, Decimal and Hexadecimal Numbers page, in the 'Counting' flash window, the white bits on the play button aren't transparent, whereas the pause button is. Purely for looks...

Hexadecimal Numbers wrote:

The Hexadecimal

numberare interesting.

Maybe insert an 's' or rephrase the sentence? That's all. Thanks.

]]>5EC1A1A85E5A81A0

1591121181151210

5EC1A1A85E5A81A0 sounds best on drumkit 3

1591121181151210 sounds best with the volume down

And you are right, explanations of why binary is useful is just so obvious I couldn't think of what to say! How should it end?

]]>"Also, computers love binary (and hexadecimal) because the computer circuits and memory are based on "on/off" (either a signal is there or not). For example, the pictures and sound on a DVD"

It looks chopped short to me.

]]>5EC1A1A85E5A81A0

1591121181151210

At least then I won't have to deal with variations like "-1.1e-5"

]]>When you enter big numbers into the decimal box, then the binary and hex boxes start to not convert accurately anymore. They get the first digits of the number and then it ends with a bunch of zeroes.

Interestingly, converting to and from binary and hex doesn't have this problem.

]]>That 100(Hex) ---> 1(Bin) is part of the original problem. Inbetween Binary and Hex I do a direct "translation", and then clean up any leading and trailing zeros. It was that cleanup that was misbehaving (turning binary "100000000" into "1").

Have a try now, I have uploaded a modified version. You may need to use "refresh".

(Now that I allow "e" to be displayed in the decimal box, people will also be able to enter decimals in standard form. I now need to check all possibilities there.)

]]>Also, if you type a number that ends in 0 into the hex box, then the binary converter ignores the 0.

e.g 100(Hex) ---> 1(Bin)

]]>With the tally, it goes off the screen and eventually stops creating little dots (if I let it go on, and somebody let it go overnight it might eventually create so many little dots that it would use up all the computers memory). Maybe I could get it to create a large dot for every hundred dots or something?

]]>When you type stuff into the hexadecimal box, the other two behave strangely. The decimal one eventually gets a decimal point from nowhere and starts showing numbers far smaller than it should, and the binary one is even odder. If you type only 1 and 0 into the hex box, then it the binary box just copies it and there are other strange things about it too.

The explanation for Binary, Decimal and Hex numbers was very good though. I especally liked the counter that could go up to 10 digits in any base from 2 to 16. I watched it count all the way up to 1111111111 in binary.

The only minor thing I can find with that is that the tally of how many it's done goes off the screen after around 150-ish. I'm not sure how you'd fix that though.

]]>mathsy: adjustable size is pretty difficult, but maybe one day. And the random rhythm could have 1,2,4,8 or 16 spacings, so that one random change could be (for example) to play the snare every 4th beat starting at beat 3.

Another fun idea would be to have a couple of extra drums that could be "hit" with the mouse.

]]>