WEBVTT

00:00:00.020 --> 00:00:03.100
PC gaming hardware is expensive, right?

00:00:03.700 --> 00:00:07.900
Core i7 Extreme Edition, $1,600.

00:00:08.660 --> 00:00:13.640
2 terabyte 960 Pro NVMe drive, $1,300.

00:00:14.480 --> 00:00:19.320
Two GTX Titan XPPs, we got $2,400.

00:00:20.020 --> 00:00:24.800
You add 128 gigs of RAM, as well as a top-of-the-line motherboard,

00:00:24.800 --> 00:00:29.500
and yeah, that'll be $6,800, please.

00:00:30.020 --> 00:00:33.310
Now, to be clear, I'm not complaining.

00:00:33.450 --> 00:00:35.870
This is a spectacularly first-world problem.

00:00:36.250 --> 00:00:40.630
But pro video production gear is on a whole freaking other level.

00:00:40.970 --> 00:00:42.250
Let me put it in perspective.

00:00:42.930 --> 00:00:51.770
This one PCI Express card costs as much as all that stuff I just listed combined.

00:00:52.130 --> 00:00:52.910
All of it.

00:00:52.910 --> 00:00:58.230
This is the Red Rocket X, a state-of-the-art creation tool

00:00:58.230 --> 00:00:59.910
and simultaneously a revolutionary...

00:01:00.210 --> 00:01:02.210
...delic of a bygone era.

00:01:02.210 --> 00:01:07.210
A $7,000 co-processor card.

00:01:07.210 --> 00:01:10.210
Welcome to holy sh**.

00:01:10.210 --> 00:01:24.710
Cooler Master's 25th anniversary edition, Cosmos II,

00:01:24.710 --> 00:01:28.710
features a unique dual curved tempered glass side panel.

00:01:28.710 --> 00:01:31.710
Check it out now at the link below.

00:01:33.030 --> 00:01:35.030
Okay, so as many of you are probably aware,

00:01:35.030 --> 00:01:38.030
we moved to RED Digital Cinema cameras earlier this year

00:01:38.030 --> 00:01:40.030
in an effort to bump up our production value.

00:01:40.030 --> 00:01:42.030
And, I mean, let's be honest, we're enthusiasts.

00:01:42.030 --> 00:01:45.030
Give Brandon and Max some new toys to play with.

00:01:45.030 --> 00:01:50.060
But have you ever actually tried to work with RED code RAW footage before?

00:01:50.060 --> 00:01:52.060
As Taren would put it,

00:01:52.060 --> 00:01:54.060
it's a nightmare.

00:01:54.060 --> 00:01:59.060
At full 8K on a 10-core Extreme Edition processor

00:01:59.060 --> 00:02:04.060
with a $5,000 NVIDIA Quadro P6000 graphics card,

00:02:04.060 --> 00:02:08.060
this is what timeline performance looks like.

00:02:08.060 --> 00:02:09.060
You see those delays?

00:02:09.060 --> 00:02:11.060
As I'm scrubbing around?

00:02:11.060 --> 00:02:17.060
And even straight playback performance is abominable.

00:02:17.060 --> 00:02:21.060
It's not like it's our 10 gigabit network connection bottlenecking us either.

00:02:21.060 --> 00:02:24.160
We're nowhere near saturating it.

00:02:24.160 --> 00:02:25.160
No.

00:02:25.160 --> 00:02:27.260
It's the CPU.

00:02:27.260 --> 00:02:32.260
Even though we're scaling across all 20 of our threads,

00:02:32.260 --> 00:02:35.260
we are still running out of processing power.

00:02:35.260 --> 00:02:39.260
And we haven't even added any Lumetri colors.

00:02:39.260 --> 00:02:41.260
Yet, either.

00:02:41.260 --> 00:02:44.260
That's only going to make matters worse.

00:02:44.260 --> 00:02:46.260
Throw that into the picture,

00:02:46.260 --> 00:02:51.260
and now we are dropping about 90% of our frames

00:02:51.260 --> 00:02:56.260
while dealing with a quarter to a third of a second delay

00:02:56.260 --> 00:03:00.290
when we're trying to move the playhead around on the timeline.

00:03:00.290 --> 00:03:01.290
Ridiculous.

00:03:01.290 --> 00:03:05.290
And both our CPU and GPU are basically maxed.

00:03:05.290 --> 00:03:07.290
You actually need to drop your preview quality

00:03:07.290 --> 00:03:09.290
all the way down

00:03:09.290 --> 00:03:10.290
to 1 eighth

00:03:10.290 --> 00:03:13.290
in order to get what I would consider to be

00:03:13.290 --> 00:03:15.290
acceptable performance

00:03:15.290 --> 00:03:17.290
with much lower usage.

00:03:17.290 --> 00:03:19.350
True to form though,

00:03:19.350 --> 00:03:22.350
RED Digital Cinema has a solution for you.

00:03:22.350 --> 00:03:25.350
Are you unhappy with your editing experience

00:03:25.350 --> 00:03:28.350
of the footage from your $50,000 camera?

00:03:28.350 --> 00:03:31.350
Buy this expansion card

00:03:31.350 --> 00:03:32.350
to accelerate it.

00:03:32.350 --> 00:03:35.350
Available now for 7,000 easy payments

00:03:35.350 --> 00:03:37.350
of only $1.

00:03:37.350 --> 00:03:39.350
Call now and we'll throw in this nothing.

00:03:39.350 --> 00:03:42.350
Absolutely free because we're RED

00:03:42.350 --> 00:03:45.350
and your wallet is more than just our job.

00:03:45.350 --> 00:03:46.350
It's our passion.

00:03:46.350 --> 00:03:49.350
But what is this thing?

00:03:49.350 --> 00:03:51.350
What does it even do?

00:03:51.350 --> 00:03:54.350
Well, we can figure out a little bit on our own.

00:03:54.350 --> 00:03:57.350
So there's some kind of processor here

00:03:57.350 --> 00:04:00.350
that's under 150 watts of total power consumption

00:04:00.350 --> 00:04:02.350
based on the single slot cooler

00:04:02.350 --> 00:04:05.350
and the single six pin power connector back here.

00:04:05.350 --> 00:04:07.350
There's some memory on board

00:04:07.350 --> 00:04:08.350
so we can see those things.

00:04:08.350 --> 00:04:11.350
So we can see those chips arranged around the chip here

00:04:11.350 --> 00:04:14.350
and the dual DisplayPort ports

00:04:14.350 --> 00:04:17.350
are so it can actually function as a video output device.

00:04:17.350 --> 00:04:21.350
Though our workload necessitates a powerful GPU anyway

00:04:21.350 --> 00:04:24.350
so we won't be using it that way.

00:04:24.350 --> 00:04:27.350
And the main purpose of this thing anyway

00:04:27.350 --> 00:04:32.350
is to accelerate decoding, scaling, and debayering

00:04:32.350 --> 00:04:34.350
of our 3D files.

00:04:34.350 --> 00:04:36.350
The first two I think are fairly self-explanatory

00:04:36.350 --> 00:04:37.350
but the last one

00:04:37.350 --> 00:04:42.350
is the process of reconstructing a full color image

00:04:42.350 --> 00:04:44.350
from incomplete color samples

00:04:44.350 --> 00:04:46.350
that are captured by the sensor

00:04:46.350 --> 00:04:48.350
in a raw recording format.

00:04:48.350 --> 00:04:53.350
But they give us no actual details about the hardware

00:04:53.350 --> 00:04:58.350
other than some nebulous 5X performance claim

00:04:58.350 --> 00:05:02.350
relative to their own first generation RED rocket.

00:05:02.350 --> 00:05:04.350
But why would this older chip

00:05:04.350 --> 00:05:07.350
based on older process nodes

00:05:07.350 --> 00:05:09.350
be better at decoding technology

00:05:09.350 --> 00:05:12.350
compared to a GPU running CUDA

00:05:12.350 --> 00:05:15.350
be better at any of that stuff?

00:05:15.350 --> 00:05:19.350
I mean RED even supports CUDA acceleration

00:05:19.350 --> 00:05:22.350
in their own Cinex desktop application.

00:05:22.350 --> 00:05:24.350
Is this thing even relevant today?

00:05:24.350 --> 00:05:25.350
So with it installed

00:05:25.350 --> 00:05:27.350
we throw on the latest drivers

00:05:27.350 --> 00:05:29.860
and I don't know

00:05:29.860 --> 00:05:31.860
it's kind of weird.

00:05:31.860 --> 00:05:33.860
There's no configuration utility

00:05:33.860 --> 00:05:34.860
or anything like that

00:05:34.860 --> 00:05:36.860
but if you go into device manager

00:05:36.860 --> 00:05:39.860
it's working properly

00:05:39.860 --> 00:05:41.860
and everything seems fine.

00:05:41.860 --> 00:05:43.860
So all that's left to do then

00:05:43.860 --> 00:05:46.860
is go into our video editing software

00:05:46.860 --> 00:05:48.860
and press enable.

00:05:48.860 --> 00:05:50.860
So this is the same project

00:05:50.860 --> 00:05:52.860
that we were just looking at

00:05:52.860 --> 00:05:53.860
and we're going to change this

00:05:53.860 --> 00:05:57.860
use rocket drop down to all available.

00:05:57.860 --> 00:06:00.120
At full quality

00:06:00.120 --> 00:06:03.120
my CPU is still pinned

00:06:03.120 --> 00:06:06.120
and now I'm seeing 90% GPU usage

00:06:06.120 --> 00:06:11.120
even with lumetri color disabled.

00:06:11.120 --> 00:06:13.310
What?

00:06:13.310 --> 00:06:16.820
Okay, well now

00:06:16.820 --> 00:06:19.910
hold on just a minute here.

00:06:19.910 --> 00:06:22.910
Surely there must be something wrong.

00:06:22.910 --> 00:06:25.910
Let's try disabling the rocket

00:06:25.910 --> 00:06:28.100
just to see if we can get back

00:06:28.100 --> 00:06:30.100
to where we started.

00:06:30.100 --> 00:06:31.100
Now hold on

00:06:31.100 --> 00:06:33.100
this doesn't make sense either.

00:06:33.100 --> 00:06:34.100
With it disabled

00:06:34.100 --> 00:06:36.100
our timeline scrubbing

00:06:36.100 --> 00:06:38.100
looks better than ever.

00:06:38.100 --> 00:06:41.330
Our CPU usage is way down

00:06:41.330 --> 00:06:44.330
and even our GPU usage

00:06:44.330 --> 00:06:47.100
is under control now.

00:06:47.100 --> 00:06:49.100
But we are still dropping some frames

00:06:49.100 --> 00:06:51.100
far fewer though.

00:06:51.100 --> 00:06:53.100
Well RED only advertises

00:06:53.100 --> 00:06:55.100
the Rocket X as being capable

00:06:55.100 --> 00:06:57.100
of handling up to 6K footage.

00:06:57.100 --> 00:06:59.100
So maybe what we're looking at here

00:06:59.100 --> 00:07:00.100
makes sense

00:07:00.100 --> 00:07:02.100
if somehow it's enabled.

00:07:02.100 --> 00:07:04.100
Dropping then down to

00:07:04.100 --> 00:07:07.100
half quality in the preview window

00:07:07.100 --> 00:07:09.100
yields perfect playback

00:07:09.100 --> 00:07:11.100
without lumetri color.

00:07:11.100 --> 00:07:14.660
Let's check that out.

00:07:14.660 --> 00:07:15.660
Okay

00:07:15.660 --> 00:07:16.700
and

00:07:16.700 --> 00:07:17.700
all right

00:07:17.700 --> 00:07:18.700
turning it on

00:07:18.700 --> 00:07:19.700
well

00:07:19.700 --> 00:07:21.700
it looks like we are still dropping

00:07:21.700 --> 00:07:22.700
some frames

00:07:22.700 --> 00:07:25.020
in that case.

00:07:25.020 --> 00:07:27.020
But that's probably caused then

00:07:27.020 --> 00:07:28.020
by a GPU bottleneck

00:07:28.020 --> 00:07:29.020
because you can see

00:07:29.020 --> 00:07:31.020
our Quadro is sitting at around

00:07:31.020 --> 00:07:34.020
80 to 85% usage.

00:07:34.020 --> 00:07:36.020
So then finally as a last step

00:07:36.020 --> 00:07:39.020
we drop down to one quarter quality

00:07:39.020 --> 00:07:40.720
and

00:07:40.720 --> 00:07:42.720
that's looking great.

00:07:42.720 --> 00:07:44.720
Acceptable CPU

00:07:44.720 --> 00:07:46.720
and GPU usage

00:07:46.720 --> 00:07:49.720
and a much nicer looking timeline

00:07:49.720 --> 00:07:51.720
than what we were able to achieve

00:07:51.720 --> 00:07:55.840
without the RED Rocket X.

00:07:55.840 --> 00:07:57.840
But in a lot of ways

00:07:57.840 --> 00:08:01.290
this actually raises

00:08:01.290 --> 00:08:04.290
a lot more questions than it answers.

00:08:04.290 --> 00:08:07.290
Why would disabling our add-in card

00:08:07.290 --> 00:08:10.290
give me the best possible editing experience?

00:08:10.290 --> 00:08:11.290
Is it just

00:08:11.290 --> 00:08:13.290
a snake oil hardware key

00:08:13.290 --> 00:08:14.290
to run an improved

00:08:14.290 --> 00:08:17.640
GPU acceleration algorithm?

00:08:17.640 --> 00:08:18.640
So I actually spent

00:08:18.640 --> 00:08:19.640
a couple of weeks

00:08:19.640 --> 00:08:21.640
investigating this

00:08:21.640 --> 00:08:22.640
because timeline performance

00:08:22.640 --> 00:08:25.640
has genuinely been an issue for us.

00:08:25.640 --> 00:08:27.640
But investing in

00:08:27.640 --> 00:08:28.640
one of these

00:08:28.640 --> 00:08:29.640
for each of our editors

00:08:29.640 --> 00:08:30.640
would be a whopping

00:08:30.640 --> 00:08:33.640
$35,000 total.

00:08:33.640 --> 00:08:35.770
And here's what I found.

00:08:35.770 --> 00:08:36.900
First

00:08:36.900 --> 00:08:37.900
some backup

00:08:37.900 --> 00:08:38.900
for what we already knew.

00:08:38.900 --> 00:08:40.900
Without the RED Rocket X

00:08:40.900 --> 00:08:42.900
REDCODE RAW footage

00:08:42.900 --> 00:08:43.900
loves

00:08:43.900 --> 00:08:44.900
CPU cores.

00:08:44.900 --> 00:08:47.900
Knocking my Extreme Edition down to 6 cores

00:08:47.900 --> 00:08:49.900
yielded dropped frames

00:08:49.900 --> 00:08:52.900
even at only one quarter quality.

00:08:52.900 --> 00:08:55.900
But more cores only carries you so far.

00:08:55.900 --> 00:08:58.900
A 22 core Xeon like this

00:08:58.900 --> 00:08:59.900
costs more

00:08:59.900 --> 00:09:02.900
significantly slashes single core performance

00:09:02.900 --> 00:09:05.900
and doesn't even approach the performance improvement

00:09:05.900 --> 00:09:07.900
from the Rocket X installed

00:09:07.900 --> 00:09:09.900
but disabled in Premiere.

00:09:09.900 --> 00:09:10.900
So then

00:09:10.900 --> 00:09:11.900
the ideal

00:09:11.900 --> 00:09:14.900
8K video editing configuration is

00:09:14.900 --> 00:09:15.900
a 10 core

00:09:15.900 --> 00:09:16.900
with a Quadro

00:09:16.900 --> 00:09:18.900
and a RED Rocket X

00:09:18.900 --> 00:09:19.900
disabled, right?

00:09:19.900 --> 00:09:22.410
Maybe not.

00:09:22.410 --> 00:09:23.410
Is the Quadro

00:09:23.410 --> 00:09:25.410
at over four times the price

00:09:25.410 --> 00:09:27.410
really accelerating this process

00:09:27.410 --> 00:09:28.410
any better

00:09:28.410 --> 00:09:30.410
than a high-end GeForce card would?

00:09:30.410 --> 00:09:33.600
We'll be moving to an HDR workflow

00:09:33.600 --> 00:09:34.600
sometime in Q4.

00:09:34.600 --> 00:09:35.600
Expect an update on that.

00:09:35.600 --> 00:09:37.600
So we need

00:09:37.600 --> 00:09:39.600
10-bit color over DisplayPort.

00:09:39.600 --> 00:09:41.600
A traditional Quadro feature.

00:09:41.600 --> 00:09:44.600
But that was actually added to GeForce

00:09:44.600 --> 00:09:45.600
a while back.

00:09:45.600 --> 00:09:48.790
And the results here are fascinating.

00:09:48.790 --> 00:09:50.790
Our Titan X Pascal

00:09:50.790 --> 00:09:53.790
despite its nearly identical

00:09:53.790 --> 00:09:54.790
on-paper specs

00:09:54.790 --> 00:09:56.790
to our Quadro P6000

00:09:56.790 --> 00:09:59.790
is able to use its sky-high

00:09:59.790 --> 00:10:02.790
nearly 1800 MHz boost clocks

00:10:02.790 --> 00:10:04.790
to reduce GPU usage

00:10:04.790 --> 00:10:06.790
lower our dropped frames

00:10:06.790 --> 00:10:08.790
and even drop CPU usage

00:10:08.790 --> 00:10:09.790
a little bit

00:10:09.790 --> 00:10:10.790
at our target

00:10:10.790 --> 00:10:12.790
one-quarter playback quality.

00:10:12.790 --> 00:10:14.790
It even almost managed

00:10:14.790 --> 00:10:15.790
to pull off

00:10:15.790 --> 00:10:17.790
half playback quality.

00:10:17.790 --> 00:10:19.790
Both GPUs by the way were run

00:10:19.790 --> 00:10:21.790
with their power sliders cranked

00:10:21.790 --> 00:10:23.790
and power saving mode disabled.

00:10:23.790 --> 00:10:25.400
So then

00:10:25.400 --> 00:10:26.400
having finished running

00:10:26.400 --> 00:10:27.400
all of these numbers

00:10:27.400 --> 00:10:28.400
I came to the same conclusion

00:10:28.400 --> 00:10:29.400
that RED support

00:10:29.400 --> 00:10:31.400
did get back and give me.

00:10:31.400 --> 00:10:33.400
Premiere is just being Premiere.

00:10:33.400 --> 00:10:35.400
Disabled is enabled

00:10:35.400 --> 00:10:38.400
and enabled is borked.

00:10:38.400 --> 00:10:39.400
And as for

00:10:39.400 --> 00:10:41.400
an optimal workstation configuration

00:10:41.400 --> 00:10:42.400
well it turns out

00:10:42.400 --> 00:10:45.400
the Rocket X does do something

00:10:45.400 --> 00:10:47.400
for users with 8K footage

00:10:47.400 --> 00:10:49.400
even though it's not rated for it.

00:10:49.400 --> 00:10:51.400
But for the difference that it provides

00:10:51.400 --> 00:10:53.400
I'm not going to invest that much

00:10:53.400 --> 00:10:55.400
just to get a bump

00:10:55.400 --> 00:10:57.400
in preview quality.

00:10:57.400 --> 00:11:00.100
Do you ever find yourself thinking about

00:11:00.100 --> 00:11:02.100
the privacy of your information

00:11:02.100 --> 00:11:04.100
when you're making purchases online?

00:11:04.100 --> 00:11:06.100
Well privacy.com is a great way

00:11:06.100 --> 00:11:07.100
to control and protect

00:11:07.100 --> 00:11:08.100
your online spending.

00:11:08.100 --> 00:11:09.100
They offer the ability

00:11:09.100 --> 00:11:12.100
to set up virtual burner cards

00:11:12.100 --> 00:11:13.100
which allow you to hide

00:11:13.100 --> 00:11:15.100
sensitive information

00:11:15.100 --> 00:11:17.100
and cut off specific points

00:11:17.100 --> 00:11:19.100
of spending immediately

00:11:19.100 --> 00:11:20.100
without interfering with the places

00:11:20.100 --> 00:11:23.100
that you make online purchases.

00:11:23.100 --> 00:11:24.100
Two of the best features

00:11:24.100 --> 00:11:25.100
of privacy.com

00:11:25.100 --> 00:11:27.100
are the ability to set charge limits

00:11:27.100 --> 00:11:31.100
per transaction, per day, and per year

00:11:31.100 --> 00:11:34.100
and you can close any card

00:11:34.100 --> 00:11:36.100
with just a click.

00:11:36.100 --> 00:11:37.100
They've also got their

00:11:37.100 --> 00:11:38.100
private payments feature

00:11:38.100 --> 00:11:39.100
which masks your spending

00:11:39.100 --> 00:11:41.100
because it's nobody's business

00:11:41.100 --> 00:11:42.100
what you're buying

00:11:42.100 --> 00:11:44.100
and their browser extension

00:11:44.100 --> 00:11:45.100
automatically detects

00:11:45.100 --> 00:11:47.100
checkout fields on a webpage

00:11:47.100 --> 00:11:48.100
so with just two clicks

00:11:48.100 --> 00:11:51.100
you can create and autofill

00:11:51.100 --> 00:11:54.100
a dynamic number into the checkout form.

00:11:54.100 --> 00:11:55.100
So head over to

00:11:55.100 --> 00:11:57.100
privacy.com forward slash Linus

00:11:57.100 --> 00:11:58.100
or click the link

00:11:58.100 --> 00:11:59.100
in the video description.

00:11:59.100 --> 00:12:00.100
As a special offer

00:12:00.100 --> 00:12:02.100
privacy will be randomly selecting

00:12:02.100 --> 00:12:04.100
50 of those who sign up

00:12:04.100 --> 00:12:06.100
via privacy.com slash Linus

00:12:06.100 --> 00:12:07.100
and crediting 50 bucks

00:12:07.100 --> 00:12:09.100
to their privacy.com accounts

00:12:09.100 --> 00:12:11.100
to spend whenever.

00:12:11.100 --> 00:12:13.100
That's like a rival 300 mouse

00:12:13.100 --> 00:12:15.100
or a cheap mechanical keyboard

00:12:15.100 --> 00:12:16.100
for nothing.

00:12:16.100 --> 00:12:17.460
So thanks for watching guys

00:12:17.460 --> 00:12:18.460
if you disliked this video

00:12:18.460 --> 00:12:19.460
you can hit that button

00:12:19.460 --> 00:12:20.460
but if you liked it

00:12:20.460 --> 00:12:21.460
hit the like button

00:12:21.460 --> 00:12:22.460
get subscribed

00:12:22.460 --> 00:12:23.460
maybe consider checking out

00:12:23.460 --> 00:12:24.460
where to buy the stuff we featured

00:12:24.460 --> 00:12:27.060
at the link in the video description.

00:12:27.060 --> 00:12:28.060
Also down there

00:12:28.060 --> 00:12:29.060
is our community forum

00:12:29.060 --> 00:12:30.060
which you should totally join

00:12:30.060 --> 00:12:31.060
as well as our merch store

00:12:31.060 --> 00:12:33.060
which has cool shirts like this one.