I really don't care what makes me different, I make music for me.  For a real long time, nobody, not even myself, liked my work... but I'm not in it to please, or to sell... I'm in it to learn.  To learn something I've always loved.


If along the way, I make a song that I like, then that's awesome.  If others like it, that's pretty awesome too, but honestly, I care more about learning enough to produce music that I don't hate.

I learned Sax first, about 35 years ago, then keyboards about 30 years ago, started composing around then, started what would be called producing around 20 years ago.  Started to get to where I'm good at making music about 20 minutes from now.

It varies widly, but ultimately, I just don't care... it takes how long it takes.  Sometimes, the track flows like butter, and I'm mostly done in an afternoon.  Other times, I fight with it for 3 weeks.  So long as I'm happy with the end result, it's all good - though the three week tracks are a bit expensive in terms of effort, I tend to learn a lot more from making them, so it's all good.

This is not quite correct either. The floating point parts of the 32 bit CPUs have been handling 64 (and 80) bit floats for quite some time, I think as far back as the 386DX and beyond (i.e. back in the 80's).

True, but I didn't state the number of bits of FP your CPU will support, just that 64 bit will support twice as wide FP on-board - a 64 bit CPU is going to be doing 64 bit FP in a single register, but it really doesn't matter much since that extra accuracy is just going to get thrown into the bit bucket anyway.

Math plays a huge role in music, but through physics. Each note pertains to certain frequencies in which musical scales were built off of. This is very vague but I can't remember much of what I learned in physics class.

Actually, math applies to a lot more in music than just the physics of it.  Pretty much all of theory can be expressed mathematically.  If you dig deep enough, quite a lot of it still has some tangential (or sometimes not so tangential) relationship to the physics of sound, but tempos, intervals, keys, and so on and so forth all have mathematical basis and formulae.

For Christmas, my mom got me an Akai APC 25 key... I highly recommend it as a cheap production tool that will get you by on a budget.  It was $75 at the time, though the full price is higher - it was on sale... the price has now gone back up.

My piece of advice is to find out what your computer is running on (32 or 64 bit) Before installing your DAW of choice, because if you have per-say 32 Bit FL loaded on a 64 bit computer, your computer is going to have to work much harder to bridge the gap as opposed to if it was running 64 bit which is just right for it. Just some advice for beginners ^.^

That's not accurate.  32 bit software on a 64 bit OS/CPU is not going to make more work for your CPU, and 64 bit software isn't even going to run on a 32 bit OS/CPU.  (Not that you can find a 32 bit CPU any more, and haven't been able to for a good decade or so.) 


At the level where software actually executes, the machine language, the 64 bit CPUs still have full support for the 32 bit operands... they don't have to do any translation or anything like that.  The difference between the 32 bit and 64 bit operands is the size of the registers that it uses - essentially, how wide a "word" is.


However, 32 bit software running on a 64 bit CPU will mean that your CPU isn't being fully utilized - when a 64 bit CPU does a math operation, it is capable of twice as much accuracy as a 32 bit CPU (assuming you're working in floating point, which most internal audio production is these days - if your DAW is NOT internally floating point, it's probably time to retire it).  That accuracy is nice, but not terribly important... especially since your FP mixing is 32 bit... the CPU will have the extra width for accuracy while it's doing the math, but once it stores the result into memory, it's going to chop most of that accuracy off.


Now, if you're not doing FP math, then a 64 bit CPU can work with much larger numbers, but this is not something that means anything in audio production.


The biggest hard difference between 32 bit and 64 bit, as it related to audio production, is how much memory you can address.  At a hardware level, there's bus speed and some other things as well, but you aren't using a 32 bit CPU, even if you're running a 32 bit OS on top of it... 32 bit CPUs are soooo last millenium.   

If your software is 64 bit, then it will take better advantage of a modern CPU and can address a lot more memory.  However, 32 bit VSTs won't work in a 64 bit host.  So, you either gotta use somethin' like jBridge to wrap your 32 bit VSTs (which is a bit flakey, we're discussing this in another thread), or you just don't use the VST.


32 bit is dying tech, so it's only a matter of time... and chances are, we're not going to bother with 128 bit for a real long time, so we're going to be on 64 bit for a long while.