Building the BEST PC for Movie Edit Pro
I have an ASUS P5N-E SLI motherboard. I think it's about 3 years old. However, I recently found out the guy that sold it to me really did me well because I was still able to install one of the new quad-core processors, the Intel Core 2 Quad Q9650 3.0gHz, giving me a total of 12gHz of cpu power. Also, I've installed two 2-gig PC-2 6400 sticks of memory, for 4 gigs of RAM total, however, since I'm running WinXP 32-bit, it doesn't see any more than 3.5 gigs. Originally I had purchased 8 gigs, but after finding out the 3.5gig limitation, I returned two of the sticks. In my PC currently is a 750 gig SATA300 drive by Seagate. Unfortunately, it is already full. I learned fairly early that IDE hard drives, while functional, are not really ideal for video editing because the transfer speeds can't keep up in the long haul. Actually, SATA drives, even over USB2.0 buses, are faster still than IDE/UDMA600 drives. This isn't really all that noticeable on a regular Windows system to the average user, but once you start working with HD video files, like AVCHD/Blu-Ray or stuff like that, you'll see the difference. For a video card, I bought a PCI-Express16 ATI Radeon 4670 w/1gig of dedicated video RAM. I recommend either the ATI/DIAMOND brand or the eVGA brand. Both will surely give you incredible performance. Anything less than PCI-Express16 in a video card will buy you a serious bottleneck in editing. Virtually all the processing that happens during editing is done by the video card. During render times, it's more the CPU, editing times, it's the GPU. So make sure you have a TON of video ram and a killer GPU. SPEND THIS EXTRA MONEY.
I cannot stress enough how important stability is. If you're looking to overclock, you might do well to rethink your strategy, because there's nothing more frustrating than learning you don't have enough of a cooling setup and your system crashes while you have 4 hours of unsaved work on the screen. In my opinion, I feel it is best to start out with a motherboard that will support FIRST the highest-end CPU's available TODAY AND TOMORROW, and SECOND will also allow you to start out with a lower-end, more affordable CPU right now. This gives you both balance and budget. Then buy a CPU that does the best OUT-OF-THE-BOX performance you can afford. One of the things I learned about Movie Edit Pro is that it doesn't seem to take full advantage of my quad core. I can boost it up by using CTRL-ALT-DEL and right-clicking on the MovieEdit.exe process and jumping the priority up the "Realtime" or "Critical", but it still only uses about 29-33% of my processor power... I don't know what gives with that, as I've set the affinity to use all 4 CPU cores. Still, it runs circles around my old Core 2 Duo 2.4gHz processor. I am told 3 things about this:
1. The i7 processors work better with Movie Edit Pro 15 plus on 32-bit systems
2. Magix Video Pro X handles the Core 2 Quad processors better.
3. Windows 7 solves this problem.
Since I have none of the above, I can't verify this information. I'm also told that MEP doesn't like 64-bit Windows XP and I know it has problems using the 3D Text functions on Vista.
Let me come back to cooling for a minute. We all know fans make noise. If you're going to be doing any filming or recording of audio around the PC, try to make sure you spend a tiny bit of extra money (seriously, it might mean $10 difference) on quieter fans. Also try to use a case that offers MAXIMUM ventilation. This will reduce the need for bigger fans, and make for quicker escape routes for the heat. When it comes to rendering out your final video cut, your CPU fan will be fighting for its life, and you will surely hear it whirring up to full speed. And don't be too cheap to buy a decent fan. If you try to pinch a penny on this, you'll end up kicking yourself when you have to buy a new CPU because you turned it into a cinder chip.
For video cards, I chose the one I have because of expandability. Because I was thinking ahead, I bought the right motherboard, and now I can buy two of these video cards and have twice the rendering power. Many of the newer cards have some sort of built-in pairing ability. You'll need to be sure your motherboard supports it first, but after that, just get the best card you can afford that can take advantage of this feature. Start out buying ONE. In another year, that card will drop easily in half in price, so you should be able to find one cheap to pair it with on ebay or something.... come to think of it, I need to start shopping for that! LOL!
With all this being said, I should probably tell you that NOBODY I know has a system good enough for silky-smooth editing using Movie Edit Pro on a PC. All of us experience choppy video at times while editing. So don't get all bummed out when you spend all this time and money building the PC of your dreams only to find out MEP still "stutters" when you're watching the edits in the preview window. Your end product will still look amazing if you're using the program right.
Also don't be afraid to shop around for individual parts. If you do it right, you can save yourself a thousand dollars or more, especially if you take advantage of rebates that often come around for hard drives, memory, and motherboard/CPU combos. But be aware that price has to come SECOND to practicality. Start out buying the best motherboard you can afford for the job, and go from there.
-Bryce
http://www.newdepthmedia.com
Labels: building, card, cpu, edit, editing, motherboard, movie, pc, perfect, pro

My grandfather was what we would today call a "Mad Scientist." Literally. You know all those movies where you see the guy in his laboratory with the tubes and wires, and sparks flying everywhere? Well, that was pretty much him. Anything that there ever was to know about electronics, or science, or computers, he knew it. He'd be sitting at the kitchen table, making up the layout for a circuit board on this big light board using little strips and circles of electric tape. Then he'd take it down in the basement and etch it onto a silicon board in an acid bath. I'm not really sure how that worked, but I know he had a brain the size of a planet. Grampa had all the social skills of a block of wood, though. He was a very hard man. He taught my sister and I how to write programs for computers at a very early age. We were able to convert decimal to hexidecimal and program in machine code at age 9 and 7, respectively. I even learned how to program on those old punch-cards that you would push into the front of a "Teletype" machine (a sort of glorified wide-carriage typewriter with half a brain). Grampa taught me some stuff about electronics, but he didn't have the patience to teach me very much. He gave me books and told me to study hard. I did for a while, but I didn't live up to his expectations.
ter, a Commodore Vic-20. He bought it for an outrageous price, from one of my friends' dads, who, it just so happens, was also another mad scientist. He'd built some sort of memory expansion board for it from an Odyssey video game console, which boosted the Vic's memory from a meek 3k to a COLOSSA
L 32k! Anyway, with this in my hands, I learned the basics of the Commodore BASIC programming language. Some friends and I learned how to make video games on it, and I even wrote a BBS (Bulletin Board System) program for it -- I think I called it Odyssey, too. It didn't work very well, and it bothered my folks to have people calling the home phone all the time with their modems. I was also intrigued with the sounds that this computer could make, and I would write programs that would mimic music I'd heard in some of my video games.
Commodore 64 computer for me. He was sure that if he bought me a more serious computer, I could do more serious stuff with it, and cease with this silly video game nonsense. He was not a man of recreation. If you did anything, it should be useful. Fun was not useful to him. Again, I went on to do more creative things with this C64 than I could have ever done with my Vic-20. As time went on, I wrote several video games, and got my hands on some great drawing programs. Grampa was so disappointed, he quit trying to teach me anything, since it was obvious to him that I was not going to follow in his utilitarian footsteps.
ere people would bring their entire computer setups, set them up at a table in a pizza parlor, and we'd soon have 200+ C64's around the room, all either playing video games, running demos or copying stuff. This copying busines
s really had me hooked. I couldn't do much of it because I was stuck using a C2N data cassette deck. Everyone else used disk drives. And while they all had nice 1701 or 1702 monitors, I had a 22" color TV that weighed about as much as a Jeep. I was quite an eyesore at some of the parties. But alas, I strugged to fit in, and I still made a few friends. I gradually learned some computer hacking tricks that allowed me to put some of these disk-based games onto tape, and I was copying games with the rest of them, just at a much, much slower pace.
r pictures of musicians, fantasy characters, cartoons, and more. At the same time, there came an emergence of Color 64 BBS's that came up all over Portland. Somehow I got my hands on a terminal program that would load off of tape, and started getting on these bulletin board systems. So here in the early stages of ONLINE activity, Commodore computers were at the forefront. You could use your modem to call out to any bulletin board in town, and post and read messages -- and what's more, on the Color 64 systems (as well as some other BBS software like Ivory and AA BBS) you could post and look at some amazing graphics made entirely with Commodore keyboard graphics.
e couldn't afford to buy a disk drive, and all the graphics programs that were made in that day required one. So I took my programming knowledge and put it to work. After several failed attempts to make a mainstream program that would make those nifty graphics, I had only succeeded in making a program that I could use. I could make my graphics with it, and I could get online with it, but nobody else would use it... ever. I had gone to great lengths to make it work on disk drives, but not having one to test it on, it had many problems. Still, it WAS the only program of its type that supported tape. Maybe some poor soul in Germany (where, by the way, everyone was stuck on tape for a
long, long time!) would use it, right? Well, I wasn't sure what would happen, but I always said if I ever got my hands on a disk drive, I would be able to do much better than the competition.
"Kaleidoscope." My friend Ken helped me bug test it (in fact, we grew to call him Captain Crash), and made some clip art for it, and after 4 versions, we succeeded in making the most downloaded program ever put up on Q-Link (which was the Commodore version of what is now known as AOL). It also became the program of choice worldwide for use in making Commodore keyboard graphics. We distributed it with another cute program, called "Kaleidoscope Animator" which would allow you to make animated messages using recorded cursor movements and such. Together, these two programs were the programs that sysops (or System Operators) used to make all their menus, logon and logoff screens (or splash screens as we'd call them today), and online games.
my program, showing it off to lots of people, and at the same time copying games, utility and office programs, even copy programs themselves, and pretty much everything. I was a software pirate. Big time. I had gotten involved with people who were bringing stuff in from overseas a
nd I was bringing software to these parties that nobody in these parts had ever seen before. It wasn't long before I had amassed a collection of thousands of floppy disks, many of which I would never use. I would just copy stuff so that I would have more than anyone else. It didn't matter what it was. And I was the guy you came to if you needed something. I felt like I ruled the world. And when you're 17, you pretty much wanna rule the world. That was me. I was pretty sure I'd found where I belonged. Deep in the piracy scene.
friends' parents kept them away from the games for the most part. Partly, they must've known that it would grow to be a distraction away from their Christian studies. But I'm sure now that they were aware of the eternal consequences of the path I was following with computers. I was going to class in the day with my friends, and then going to these pirating parties by night, sometimes going to sleepovers with my computer buddies, or working my eyeballs into a salty sweat in the wee hours of the evening downloading games and such from the BBS's. Now I was the Graphics Op (Operator) for several of the bulletin boards around town, and so was my friend Ken (or Captain Kenby back then). Back in this day, I remember I was on "The Cop Shop" "Oregon Eagle," "Crystal Palace," and "The Lord's BBS."
wasn't too long before I was working 40+ hours a week, and became both head box boy and employee of the month for several months running. I worked
my tail off, and for a lot less money than anyone would do it for nowadays. But it supported my computer habits. I was pretty much able to buy any of the toys I'd wanted for so long. I got a RAM Expander, a Super Snapshot cracking cartridge, a bunch of disk drives, a 1702 monitor, and lots of other stuff that littered my desk for almost a decade.
Computers, called "geoMetrix". We built up a library of public domain and shareware software for the GEOS 64 and 128 operating systems, as well as a newsletter that ended up with more than 300 subscribers. At some point, a magazine editor who considered us to be "competition" began selling cheap, shrunk down photocopies of our 20-40 page newsletters overseas. While that didn't go on for very long, it opened up a new market when one of the subscribers to the "pirated" newsletter found our address in one of the screenshots used for a software article.