Originally Posted by masstronaut
The ear is incredibly sensitive to rhythm, that's how pitch is perceived for one thing.
Check what's in 'startup' with run/msconfig.
If you know a bit check 'hkey_local_machine/software/microsoft/windows/run' in the registry using run/regedit.
There's lots of services in Windows that are running by default that most people don't need at all especially if the machine is used as a dedicated DAW.
Turn the internet off. Make sure you have a MIDI interface with good drivers.
first off you forgot to look under the user's section too in regedit.
HKEY_USERS WITH individual user listings that are listed as weird number letter string combos.
secondly do not disable services, most times you end up slowing the machine down by disabling services. they are not running until called upon and disabling them means simply not preloading them into ram or onto the faster section of the hard drive's swap area in some cases and preventing apps from functioning fully or as quickly as possible in other instances. if you have enough ram and any recent processor there is no reason to disable a service unless it is a rogue service installed by some form of malware. services are idle until called by the kernal or an app requesting access through the kernal. they aren't little programs sitting there running 24/7, they are programs of a special system level type that are run dynamically and only when needed.
shutting off an internet connection only helps speed up the machine if you have a malware infection that is trying to phone home a lot. it's another one of those "tips" that makes no sense. the amount of time a processor uses for a time get or keep alive ping is so minimal it isn't worth disabling an internet connection for. also when you do need to activate the network again for backup or other useful purposes like research that time spent enabling the internet / network connection is far more of a penalty than simply leaving it on would have been. let alone the time wasted going to another machine and turning it on simply to browse the internet...
if you find yourself getting viri and malware constantly you are the problem not the machine. your surfing habits are the cause of the viral infections and you need to re-analyze what is important enough to look at on the internet vs. how much of a risk you put your machine at by going to questionable links. for instance...
in an office where i did IT a worker stated she had to open that email attachment as it said "important" in the heading. i just looked right at her and asked "were you expecting any documents from this person?" to which she replied "no, but it could have been important". to which i replied "if it were don't you think the body of the email would have stated what the attachemnt was about?". this is the part where i got a blank look, and then her co-worker came to her defense with "but it's your job to make sure this doesn't happen" to which i replied "and i am making sure she doesn't do this again which is my job, i can't think for you all day, somewhere along the way you have to start doing that for yourself, stop looking for a magic bullet to stop virus attacks, it's mostly up to you to figure out what's legit and what's not."
this is the problem most have...
"this anti-virus is worthless, i got a trojan anyway"
an anti virus software package and built in browser security measures are there to scan for a virus before you run the app or execute the script on a webpage. it can't do anything for you if you don't actually enable it to do it's job, and when it recommends you don't continue, if you decide that you must absolutely see what's on that internet site or you absolutely need this app installed anyway it can't protect you from doing dumb things.
anyway back to midi 101
midi is a serial protocol and it's a slow protocol.
it's more than adequate for note on, note number, note off and velocity messages. toss in any continous pitch or mod wheel motion info and it gets choked very fast with only one channel of data. this means your daw has to prioritize note info or wheel update info per frame of midi communication data. cc knob and sysex and nrpn data have the same effect. midi is slow, however for simple note on off and velocity playing info it's more than capable. when you start sending continous state change data it pretty much is more data than midi can handle at once so a daw needs to start quantizing resolution steps and skipping some to make sure note on off and number and velocity info has priority. which isn't so big a deal until you do daisy chaining and /or multiple knob/pitch/mod wheel data to multiple synths. this is where the midi interface standard fals flat on it's face and causes some synths even to lock up or get stuck notes because they can't filter and pass on the required data properly.
best practices are ...
multi port midi interfaces
avoid chaining if at all possible
realise when you start your knob tweaking sessions what's going to get tossed when you start doing cutoff and res and lfo knob movement recording/playback at the same time.
stack mod source amount to the mod wheel as much as possible in your synths for multi parts where you need to adjust things in relation to each other (for example cutoff + amount and resonance - amount to mod wheel)