Chris Kenny
Forum Replies Created
-
My understanding is, it’s just converting to 8-bit for output via the Decklink card, regardless of input format. 10-bit footage still comes in as 10-bit and is processed in Resolve’s 32-bit YRGB float space.
Basically, switching to 8-bit output is just reducing the bandwidth necessary to move the processed frames across the system bus from the GTX285 or FX4800 to the Decklink by 20%.
-
The issue on the 2008 Mac Pros is memory and system bus bandwidth rather than raw CPU power, I think. (Most processing happens on the GPU anyway.) The 2008 models are right on the cusp of being able to do real-time 1080p — we’re seeing something like 21-22 fps on ours. Going 8-bit means there’s 20% less data to push around, which should do the trick. (And does do the trick, in my testing to far.)
-
I don’t know about on other models, but on the 2008 models there’s only a very small space to sneak cables up into the optical bays, and it’s mostly occupied by an existing bundle of cables going up there. Getting SATA cables up there for extra hard drives was bad enough; trying to get an HDMI cable with a head attached probably borders on impossible.
We have a couple of old dead G5 towers around that have doors that fit on the Mac Pro, so we’ll probably just drill some holes in one of those to run out HD-SDI cables from the Rocket and HDMI from the Decklink.
-
Hmm… 17 fps with software-based R3D decoding makes me think I should be able to get away with using a 2008 Mac Pro with a Red Rocket with no problem. With color grades on several indie features lined up, we’ll run out and buy a new tower if we have to, but I’d really like to hold off for Light Peak and/or USB 3 on next year’s models.
-
If you’re primarily working with Red footage, it’s worth noting that the $2500 price difference between the 6 core and 12 core Mac Pro models will pay for most of a refurbished Red Rocket, which will likely do more to speed up R3D decoding than the extra cores.