@knievel said:
Cheers BK for that very informative post!
Just a quick question...
Would RAM speed come into the equation at all?? Or is it mainly to do with the CPU calculations?
For instance:
I have 12GB of DDR3 RAM running at 1066Mhz CL7 latency, but still get pops n' crackles with MIR on my i7 920 at 512 samples latency.
If I used the same set up, but instead used faster or overclocked RAM, would I still get the same crackerly results, do you think? As the CPU still has to make exactly the same calculations anyway??
I notice the new 6 core Intel i7 980X only 'officially' supports 1066Mhz RAM anyways... so I'm thinking RAM speed has little bearing on this issue?
knievel
Hi Knievel
For making an "assessment" a of a "music station" you should take each component into account.
12GB DDR3 1066MHz could be a good RAM compared with the rest of the system (GHz, amount of cores etc.) but in another system it would be a weak part.
For us - the average consumer - 12 GB, DDR3, 1066Mhz a good average... even if 1333Mhz would be better...[;)]
But as I said: We have to observe the whole system. Sometimes we have components, programs or settings outside the "Audio-Line" which can disturb a proper handling with the audio datas.
1. Good to know, which part of your PC or MAC is the weakest one. If you know that you can try to fit the part in an adequate way to the rest of the system.
One possibility to get first hints: Use the WN7/Vista "Leistungsbewertung" (Power Assessment?)
Example: I know that my grafic card is too weak compared with the rest. Its job: Showing datas on two screens of 2 x 1650 x 1050 pixels.
A first step could be: Switching off all the nice effects like shadows etc. Nevertheless, I should exchange the component for better results.
There are other programs for getting information and for finding the weakest part of the system: A freeware example is "Sandra Light"
2. But there are other "powerkillers". Try to keep your Computer free from any program which isn't necessary for producing music.
So switch off - if possible - all security programs, sidebare wheather forcasts, connections with ... etc.
A really bad situation could be:
You are working with MIR - and at the same time: The security program downloads and installs the newest antivirus files - in the background.
Such processes can lead to a crash.
Further, try to stop all autostart programs, auto tasks etc. as much as possible.
A lot of words but a short summary: It is not one single part which makes a fast system...[;)]
Best
Beat Kaufmann