Marcus Moore
Forum Replies Created
-
Some people like the new workflows and some don’t. The only way you’ll know if it works for you is work with it- REALLY work with it for not just a few days (and get frustrated by how different it is), but for several weeks until you get over the initial workflow shock. Then you can determine if you like it or not. No one else can answer that for you.
-
No, but I’ve been in contact with my Apple business rep a few times.
Did the email come from “Apple” corporate, or from your local contact? I’d imagine business reps are having to juggle a lot of anxious clients who really want their machines.
-
Due to lease signing and the holidays, my order didn’t go in until the 26th. Ugh!
My shipping form still says February. That’s all I’ve got at this point!
-
8-core, otherwise maxed out is what I went with as well.
I’m sure I’ll get it someday…
-
Well, I haven’t seen my ship date slip from February yet. But I also haven’t heard that people who managed to order earlier than me have started to receive theirs yet either.
-
If we’re talking about the same Barefeats article [where the 6-core D500 outpaced the 12-core D700 in some test], the one metric that was missing from those tests was an 8-core D700 machine, and it will be really interesting to see how it measures up. The 8-core processor has a much higher turbo boost than the 12-core, much more in line with the 6-core. But as the Barefeats article suggests, some processes seem to be limited by the number of CPU threads they can physically use- and in those cases the 6-core 3.5GHz (and presumably even more the 4-core 3.7GHz) will always win out.
A really complete matrix of MacPro configs will undeniably prove that no machine is going to be the fastest for every application (or even for every process within an application); and the user really needs to decide what their primary job is, and configure to that. Hopefully that doesn’t mean that your SECOND most important task is too compromised. For example, the best machine for FCPX and the best machine for AE are probably about as polar opposite as you can get- and that’s when the hand-wringing begins…
-
Isn’t that just the universal menu at the bottom of the page, and NOT a list of software used on that video?
-
I’d definitely go with the new enclosure- the nature of my business is that projects and storage is very modular, a lot of separate client drives. So the legacy MacPro’s internal storage would be largely wasted on me.
And all my peripherals (BlackMagic I/O) are Thunderbolt anyway, so I have no stock of PCIe cards I need to worry about replacing.
-
-
This gets even more confusing. I was chatting with Philip Hodgetts, who had a loaner MacPro 12-core D700. And he swears that he saw all 12 cores being used in activity monitor (for whatever he was doing at the time). And since this is all supposed to be handled by Grand Central Dispatch, shouldn’t the maximum number of cores be being put to use whenever possible?
8 cores (or as you suggest down below) in FCPX is not optimal, but 3 in Motion (granted for OpenGL previews) is nutty.
Is it how the plugins were built (in an earlier Motion perhaps), the type of calculations they’re doing?
I think there’s going to be a VERY complicated flow chart somewhere down the line for what types of operations (playback, analysis, rendering, exporting, encoding, etc., etc…) lean on what parts of the hardware (CPU, GPU, RAM, SSD speed).