Quantcast
Channel: Mac Pro
Viewing all articles
Browse latest Browse all 30307

Please help me with upgrade dilemma

$
0
0
Brief back story & Info:

Usage - Pro Audio recording / programming system, Logic pro/Pro Tools.

I bought a second user 2008 Mac Pro 3,1 in January 2010 which was a Quad core.
I bought and fitted a second quad CPU so it became an 8 Core 2.8ghz one month later.
There's 8gb of Ram installed, though running at 32 bit Logic can only access
4gb of that, maximum.

I moved a Quad core system on at the time, so it cost me only £300 in real
terms.
Original graphics card went south so it has a basic - but fine for my needs
GT120 card right now.
Also has a sonnet FW800 card and a UAD 2 card fitted.

It's beginning to show it's age and is sometimes a little "strained" at what I am
asking it to do, otherwise it's a FAB machine and has no issues.

I am not a fan of the new "bog brush holder" Mac Pro, though I understand that it's
a radical design and super powerful, I wouldn't buy the first incarnation anyway.

Is it worth spending approx £2500 on a decent spec 2012 Mac Pro, at least 8 cores
possibly 12 to come up to speed ?

OR- I could stick a new system drive in mine ( SSD perhaps ) and get more memory, though
DDR800 is for some reason VERY expensive !!

See, I like the options to swop drives out, upgrade memory and even processors
and that"s just a NO NO on the new Mac Pro - I don't need a studio full of drives
and cables hanging out the back of the computer !


I'm thinking that the increase in processor power wont be HUGE but the system
buss will be much faster and memory also ( 800 Vs 1,333 )

Pulling my hair out somewhat about buying into tech that's essentially from 2010
anyway.

Good advice / similar experiences are MOST welcome :-)

Caveat - the cost is not an issue though "bang for buck" is always in my mind.
Mac abuser since Quadra 700 in 1993.

Regards,
Martin.

Viewing all articles
Browse latest Browse all 30307

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>