husker
I do understand the importance of having a good computer to run the DAW. I build my own computers (don't judge), so that will generally not be an issue.
Unfortunately there's a bit more to building a good Windows PC DAW than sheer speed and processing power. Very often Windows-based wifi and low audio latency don't go hand in hand for example (though ethernet is generally less troublesome). Low latency audio (around 10-12 milliseconds or less between an audio signal going into an interface, the DAW processing it and it emerging as audio again) is asking Windows and the hardware to do things it's designers didn't always pay as much attention to as we might like. Power saving settings that most PC users, including gamers, would never notice at all can bring things to a popping and crackling halt.
Then there's keeping the mechanical noise of the PC down, especially if you need to use microphones anywhere near it.
Despite all that, a good DAW can be built without too much difficulty, I suggest browsing the "computers" part of the forum for some pointers, and we have some good and experienced commercial DAW builders around if you decide to look for a pre-built and configured system.
husker
My current rig is an overclocked Core I7 with 32 GB of RAM. I'll probably build another computer at Christmas, due to my other hobby (Flight Simulations, again, please don't judge). I'm a PC (and Android) guy, so Ipads and Macs do not interest me.
As it happens I'm a *nix/OS X sort of person by inclination and the only PC we have around is the (currently a bit poorly) one that runs Sonar :-) My "other DAW" is Logic Pro. Which at times makes me tear out what's left of my hair at least as much as Sonar ever has. And Sonar is far better documented and, in my opinion, has a better and more useful forum.
husker
What everyone relayed about the Artist, Pro, and Platinum sharing the same basic characterstics makes sense. On that note, perhaps SPLAT is the way to go. I have downloaded and played with all the trials, but again, I don't really know which one would "fit" my workflow. (TBH, I'm not even sure what that means.) I do like the look and feel of the Sonar and Studio One products better than Reaper.
Think of "workflow" like this. On your right is a big Moog Modular. Every function has a dedicated control and every control has a single function. On your left a workstation keyboard with a display and relatively few controls each carrying out many functions depending where you are in the operating system. The person who finds the Moog fits them best might find the workstation impenetrable, while someone else finds the workstation logical and straightforward but the Moog a mess of knobs and wires.
But in the end the Moog and workstation do the same thing - they make music.
husker
I'm more interested in syntheizers and sounds now. I've thought about a Midi controller only, but I do want the flexibility to just turn it on and play, and not need to worry about the computer and DAW. So I have rather limited myself to keyboard workstations.
It still might be worth your while considering adding a small 25 to 37 key controller with a faster synth action and aftertouch as well. But I'm not a pianist, so feel free to disagree.
Or even one of the smaller analogue monosynths like the Arturia Brutes, MS-20 etc.
husker
A note on the interfaces. I posted a similar question on the Homerecording BBS, but got VERY confused on the answers. Both the FA-08 and MOX8 have built in audio interfaces. However, everyone seemed to think that buying an external interface (like the Komplete Audio) was better due to Latency.
There are two different issues, both confusingly called "latency" in DAWs. Audio latency, which is where the interface and its drivers come into play is basically how long it takes audio to get converted to digital 1s and 0s or vice versa. When you play a software synth it's the delay between pressing the key and a sound emerging from the speakers. The delay is caused by the time it takes for the DAW to process the audio. If you want to monitor an audio source you are recording through the DAW (so you hear any applied effects while recording) latency is how long it takes the audio to enter the DAW, get processed and sent out again to the monitors or headphones.
It's the bane of computer audio. To get audio latency acceptably low as possible and keep the DAW working stably what are known as "ASIO drivers" which provide low latency and let you configure it are usually required. Most audio interface manufacturers supply dedicated ASIO drivers for their kit, but it has to be said that not all are created equal. The best way, I think, to shop for interfaces is to work out what inputs and outputs you think you need, add at least a couple more then see what's available and within your budget. And feel free to ask for opinions and suggestions before commiting yourself.
You can only use one interface at a time using ASIO by the way, unless the manufacturer has written their driver specifically to cater for more than one interface from the same manufacturer.
There's a driver that's sometimes recommended or advocated around the internet called ASIO4ALL. It's intended to let you try to use the PC's built-in sound-chip as if it has a dedicated ASIO driver. Sometimes it works, sometimes it doesn't and it can be a beast of a thing to configure. It's particularly useful if you have a laptop PC and need to use the built-in audio rather than a proper interface. Other than that specific use, a proper ASIO driver from the interface manufacturer will 99.99999% of the time do a better job.
The other kind of latency is "delayed procedure calls" when Windows has to stop giving it's attention to the DAW software and give time to another process. Which has bad consequences for audio playback and recording if dpc latency is too high. Some PCs don't suffer much from it, others do and unless the DAW has been built by a capable specialist often it can only be diagnosed and (usually) sorted out once the PC is up and running.
husker
If I have an AI, I assume I connect both the lineouts and midi out of the keyboard into the Audio interface, as well as the monitors. In this configuration, I assume there is no need for a USB connection to the computer?
USB connections can be very useful. Often not so much for audio unless the instrument has very good ASIO drivers for its interface, but for MIDI. Every MIDI device plugged directly into a PC is identified by Windows as a seperate MIDI port (sometimes more than one). Sonar in turn uses those ports and you can set up which instrument (port) controls which MIDI track and vice versa very easily. Much easier than having several instruments connected by 5-pin DIN to a single MIDI interface or daisy-chaining MIDI gear.
Another thing USB is useful for is if a synth has a software editing programme available. If you want to program your own sounds then the instruments's interface becomes crucial and many don't have a particularly user-friendly display, use a few controls for lots of different functions or can involve a lot of "menu diving" to get to functions. Modern software editors can make that job much, much easier.