Sean Oneil
Forum Replies Created
-
[Michael Bloodgood] “Xeon is downright lousy. And when it comes to real overclocking (not this change the system bus with a program BS) it all has to do with the motherboard hardware and the BIOS”
I don’t doubt what you say is true, but typically there’s no difference between chips of the same type – a 2.6ghz Xeon and a 3.2ghz Xeon come from the same assembly line and are essentially the same (except for the clock multiplier and perhaps passing a QC test). My understanding is that the when overclocking any of these newer Intel chips, the memory will clonk out long before the CPU does.
But yeah, the whole idea is a bad one and almost pointless. It won’t let you do things you couldn’t already do. If you get a 12 minute render to take 9 minutes instead – I don’t see any great value in that. If render times are really important one can always setup Qmaster. For serious improvements, this Snow Leopard 10.6 thing looks like it could have a major game-changing impact (that 12 minute render becomes 12 seconds).
Sean
-
You can capture HDV native (and DV) and edit on a ProRes sequence. That’s probably your best bet.
Sean
-
[Arnie Schlissel] “OK, I finally read the article, but it didn’t say anything about internal temperature.”
It’s just prior knowledge I have. The way overclocking works is that you increase the system bus speed to a certain point where your machine becomes unstable. So in order to push it further, you need to increase the voltage going to the CPU which in effect makes it stable again so you can keep increasing the speed. But by increasing the voltage you are increasing the temperature.
The Intel Core 2 series (what the Mac Pro’s Xeon is part of) is known for being able to overclock quite a bit without increasing the voltage. Regardless, this tool doesn’t alter your voltage, so increased heat is not an issue. Even if it did, the Mac Pro already has excessive overkill in regards to CPU cooling.
[Arnie Schlissel] “Anyway, I’d be leery about doing this on a machine used for anything critical without rigorous testing.”
Agreed. The system clock being off would concern me. Also, increasing the system bus causes your PCI cards to run at faster than intended speed. This could cause problems with a Kona, for example.
Sean
-
[Zane Barker] “Exactly, because my friend who works for Apple says doing that would void your warranty.”
I agree you shouldn’t use it, but it won’t void your warranty as long as you don’t tell them.
Sean
-
[Arnie Schlissel] “I’d be very careful about doing this kind of thing. In particular, you should probably keep a close eye on the internal temperature.”
This won’t affect the system temperature. That only happens when you increase the voltage to the CPU (which this program doesn’t do).
Sean
-
[Arnie Schlissel] “It doesn’t effect the system clock, it overcranks the CPU.”
Read the article. It does affect the system clock.
Sean
-
Trash your preferences. This is an issue that a lot of people run into.
Sean
-
Thanks for posting this. But having the system clock going too fast seems like a bad idea. Lots of apps rely on it. Files are always time stamped. It could even cause problems with Time Machine or Final Cut’s autosave.
Sean
-
Are you sure the source contains 3:2:3:2 pulldown? As you jog through it you should see three full progressive frames followed by two frames that have mismatched fields. And then it will repeat.
Sean
-
If it’s 60, then you probably just want to edit all your footage on a 59.94 sequence. FCP6 allows this. The 23.98 footage will just playback with 2:2:2:4 pulldown.
Sean