Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

mavericks+titan = faster than red rocket

Zakaree Sandberg

Well-known member
Joined
Dec 28, 2006
Messages
4,260
Reaction score
1
Points
38
Age
43
Location
Los Angeles, CA
no joke.. my titan with mavericks.. and plus my juicy system.. is spitting out transcodes faster than my red rocket..

playing back full res with almost no jitter


amazing


btw.. hackintosh hexacore system
 
Last edited:
Do not think they look better going GPU probably a bit softer. Atleast if you go 1:1 resolution I'm pretty sure rocket holds up better but if you downsample then it might be so that the GPU benefits from being softer. Atleast thats how it is if you transfer with CPU.
 
anyone tested R3D playback on Mavericks with rMBP latest one? (16GB Ram 2.6Ghz i7 2GB GT 750M)

I just ran some Epic 3:1 5K FF (23.98fps) R3D's through the Macbook Pro and get real time playback with no stutter or slowdown at 1/4 resolution. I think the next release of RCx might better include the new graphics card as well as the next Mavericks update.

EDIT: I should have mentioned the footage is going through a USB 3 drive and that is most likely a bit of a bottleneck. I'm sure Thunderbolt would speed things up..

Anyone using a Rocket in an enclosure with the new rMBP? I'd love to know your feedback as I'm looking into an enclosure but only if I get real time transcodes. Playback is fine at 1/2 res...
 
I feel I notice a significant difference in the quality...

GPU & CPU are exactly the same. CPU/GPU are not exactly the same as rendered with Red Rocket.

And of course ... "quality" very quickly starts to become a subjective choice / preference - like choosing a lens or filter. And theres a pretty big difference IMO when it comes to 4K finish for 4K viewing vs. oversample to 1080 for 1080 viewing.
 
Last edited:
GPU & CPU are exactly the same. CPU/GPU are not exactly the same as rendered with Red Rocket.

And of course ... "quality" very quickly starts to become a subjective choice / preference - like choosing a lens or filter. And theres a pretty big difference IMO when it comes to 4K finish for 4K viewing vs. oversample to 1080 for 1080 viewing.


I meant difference between gpu and rocket.. never did the cpu transcode.. took too damn long
 
Matt, what the hell kind of drive are you testing in that Aja screenshot? That's quite a disparity between read and write speeds. 6000MBps?!

Pretty sure something was wrong with the test. Might be a Mavericks driver thing. I just tested again and now the numbers are almost the same for read and write.
 
What about using the lanczos3 debayer algorithm.

Isn't that supposed to be the sharpest debayer?

lanczos3 is a downscaling algorithm - it's not a debayer algorithm. After the R3D is debayered - IF you want to downscale to 2K or HD, etc. - many applications let you can choose which algorithm you want to use for the downscale. Lanczos is one such option many apps give you - and there are many hybrid, custom versions of these algorithms as well. But downscale is not debayer.
 
Last edited:
OH snap… Are there any more tidbits like that? I've just been going by what RCXp says for each "algorithm" (smoother, smoothest, sharper, sharpest, etc.)… I didn't realized different strokes (algorithms) were better for different folks (outputs).
 
Last edited:
Back
Top