WEBVTT

00:00:00.000 --> 00:00:06.899
but Linus YouTube doesn't even support 12K video

00:00:04.380 --> 00:00:12.120
I know there's gonna be some of you out there thinking that exact thing so let's

00:00:09.059 --> 00:00:15.059
get this out of the way we know nobody

00:00:12.120 --> 00:00:20.160
has a 12K display okay the real reason someone might want to shoot in 12K are

00:00:17.880 --> 00:00:25.140
the same reasons that we switched to 8K back in 2017. capturing more detail in

00:00:23.220 --> 00:00:30.180
the first place helps immensely with post-production work and it gives the

00:00:27.599 --> 00:00:35.219
editor more flexibility to reframe shots and of course the sharper The Source

00:00:32.520 --> 00:00:39.120
footage the better the final output and of course there's one other important

00:00:36.840 --> 00:00:45.180
reason we just love playing around with the latest high-tech gizmos and ah

00:00:41.640 --> 00:00:48.840
speaking of which look at this a black

00:00:45.180 --> 00:00:52.079
magic Ursa mini pro 12K got it right

00:00:48.840 --> 00:00:55.860
here oh yeah this puppy makes it super

00:00:52.079 --> 00:00:59.460
easy to shoot 12K video and that is a

00:00:55.860 --> 00:01:02.280
huge deal I mean come on Linus that

00:00:59.460 --> 00:01:12.299
sounds like what maybe 50 more than 8K right right wrong 12K is over double the

00:01:08.280 --> 00:01:13.260
pixel count of 8K 80 million pixels per

00:01:12.299 --> 00:01:20.280
frame so get ready then for the sharpest LTT

00:01:16.080 --> 00:01:23.580
videos you've ever seen right right

00:01:20.280 --> 00:01:25.920
well okay shooting 12K might be pretty

00:01:23.580 --> 00:01:29.220
simple editing it on a mere mortal Workstation

00:01:27.060 --> 00:01:34.200
that's another story like my story about our sponsor origin

00:01:31.680 --> 00:01:38.100
PC origin PC desktops can be customized with NVIDIA RTX 30 series graphics cards

00:01:36.420 --> 00:01:41.400
and if you're in the market for a new PC power buying videos latest graphics

00:01:39.540 --> 00:01:45.920
cards and backed by a 24 7 support team you can check out origin PC at the link

00:01:43.439 --> 00:01:45.920
below

00:01:52.340 --> 00:01:59.100
we realized that it was a pretty bold

00:01:55.439 --> 00:02:00.899
choice to buy Six 12K cameras as soon as

00:01:59.100 --> 00:02:06.060
they were released I know I know don't pre-order right but the thing is the

00:02:03.299 --> 00:02:10.500
Ursa mini pro 12K has a lot of other features aside from the resolution that

00:02:08.280 --> 00:02:14.760
make it perfect for a new set that we're building for ShortCircuit and well

00:02:12.780 --> 00:02:20.160
given blackmagic's typical Supply constraints we felt that we either had

00:02:17.099 --> 00:02:21.599
to go all in or wait months to get

00:02:20.160 --> 00:02:25.620
enough Hardware to finish up our build we knew that we were going to run into

00:02:23.220 --> 00:02:30.540
some roadblocks I mean to say our transition to RED cameras was smooth

00:02:27.420 --> 00:02:32.099
would be a bold-faced lie but actually

00:02:30.540 --> 00:02:36.540
compared to the truckload of early issues we experienced with red hardware

00:02:33.840 --> 00:02:40.379
and software our early 12K workflow testing with the Blackmagic Ursa mini

00:02:38.220 --> 00:02:45.180
was significantly smoother that's partially because our current editing

00:02:42.180 --> 00:02:48.780
stations with ryzen 3960x threadripper

00:02:45.180 --> 00:02:52.019
processors 100 28 gigs of RAM and 8 gig

00:02:48.780 --> 00:02:54.360
RTX 2080 graphics cards seemed to be

00:02:52.019 --> 00:02:59.160
good enough to edit 12K video without any upgrades look at this Premiere

00:02:56.580 --> 00:03:03.239
timeline it's quick and responsive at 1 8 resolution which by the way is still

00:03:01.620 --> 00:03:08.280
pretty sharp at this size when you've got 80 megapixels per frame to start

00:03:05.760 --> 00:03:12.360
with so it looks like we're good on the hardware side

00:03:09.540 --> 00:03:17.400
as it turns out the 12K early adopter tax is collected in software in our

00:03:15.239 --> 00:03:21.360
initial tests with the Ursa mini 12K our Shooters quickly discovered a bug where

00:03:19.620 --> 00:03:25.440
the sensor wouldn't initialize after video playback unless you change the

00:03:23.519 --> 00:03:29.940
settings I mean it's not a game breaker but it's definitely pretty annoying

00:03:27.540 --> 00:03:34.560
however another YouTuber we talked to had a different issue involving their

00:03:31.980 --> 00:03:39.659
Ursa mini 12K where it would just start to record seemingly at random for what

00:03:37.080 --> 00:03:44.459
is supposedly a professional tool that kind of unpredictability is

00:03:41.840 --> 00:03:47.760
disconcerting to say the least and we're just getting started instead of

00:03:45.780 --> 00:03:53.040
recording in a well-supported industry standard format like h.265 or prores

00:03:50.420 --> 00:03:58.739
Blackmagic uses a proprietary codec called Blackmagic raw now the advantage

00:03:55.560 --> 00:04:00.780
is that like other raw or compressed raw

00:03:58.739 --> 00:04:05.519
formats it allows you to retain extra information without the unreasonable

00:04:03.120 --> 00:04:11.879
storage requirements of true raw and change metadata like white balance and

00:04:08.220 --> 00:04:14.700
ISO in post after you've shot it that's

00:04:11.879 --> 00:04:19.799
great the disadvantage and this is where we hit our first major roadblock is that

00:04:16.979 --> 00:04:26.160
the Ursa mini pro 12K only supports shooting video in b-raw and well our

00:04:23.520 --> 00:04:30.479
other applications didn't like that for instance kaino the program we use to

00:04:28.139 --> 00:04:33.900
ingest inspect and backup our footage doesn't currently support b-roth and

00:04:32.460 --> 00:04:38.820
they've been told to hold off on supporting it until Blackmagic software

00:04:35.820 --> 00:04:40.860
comes out of beta so we'll have to wait

00:04:38.820 --> 00:04:46.440
until that happens or completely change our ingest procedure also Adobe Premiere

00:04:43.560 --> 00:04:50.460
our video editing program of choice is able to work with b-raw but there are

00:04:48.600 --> 00:04:54.960
some Hefty software issues to work out which we'll get to in a minute the thing

00:04:51.900 --> 00:04:56.759
is b-raw is really meant to be used in

00:04:54.960 --> 00:05:01.620
blackmagic's own editing software DaVinci Resolve and if you're after a

00:04:59.520 --> 00:05:07.139
completely seamless synergistic experience that can be found using

00:05:03.960 --> 00:05:10.259
resolve on a Mac on both our 5K iMac

00:05:07.139 --> 00:05:13.320
with 16 gigs of vram and our lowly Mac

00:05:10.259 --> 00:05:15.600
Mini with Intel Graphics 12K B raw

00:05:13.320 --> 00:05:20.280
footage plays back just fine when you set the timeline to 4K even when we set

00:05:17.820 --> 00:05:24.660
the timeline to Native 12K resolve could still play back the footage although it

00:05:22.380 --> 00:05:28.440
was choppy enough to be unusable Blackmagic claims that the experience

00:05:26.580 --> 00:05:34.440
Works using a graphics card with as little as 4 gigs of vram though wow

00:05:31.800 --> 00:05:38.820
unfortunately on Windows it's a different story resolve instantly stops

00:05:36.840 --> 00:05:43.680
playback of 12K footage with a warning about insufficient video memory until

00:05:41.039 --> 00:05:50.160
you install a card with 12 gigs of RAM then because get this Blackmagic

00:05:46.020 --> 00:05:51.900
actually recommends 24 gigs of vram are

00:05:50.160 --> 00:05:57.660
they in cahoots with NVIDIA to get us to buy RTX 3090s you can't even buy RTX

00:05:54.840 --> 00:06:01.919
3090s come on this is just cruel okay well then what about Premiere well

00:06:00.240 --> 00:06:06.960
thanks to the latest beta version of blackmagic's b-raw plug-in you can

00:06:04.259 --> 00:06:11.639
import and edit 12K footage from the Ursa mini pro 12K and with GPU

00:06:09.419 --> 00:06:18.000
acceleration playback isn't perfectly smooth at full 12K but it is serviceable

00:06:15.060 --> 00:06:22.979
until the moment you want to apply any color correction using lumetri as soon

00:06:20.759 --> 00:06:27.720
as you open up the panel you instantly lose Hardware acceleration causing about

00:06:25.139 --> 00:06:31.259
90 of your frames to be dropped even if you are running a threadripper and your

00:06:29.520 --> 00:06:36.539
rendering times to absolutely fall off a cliff what here's where it gets crazy the

00:06:34.919 --> 00:06:41.100
quickest way to fix timeline performance in Premiere is to change your timeline

00:06:38.220 --> 00:06:44.819
from 12K down to 4K and then drop the preview window down to one quarter scale

00:06:43.020 --> 00:06:49.139
this does improve timeline responsiveness as we'd expect but it

00:06:47.220 --> 00:06:53.880
doesn't help at all with the color correction problem the solution to that

00:06:51.360 --> 00:07:00.180
was to follow blackmagic's resolve guidance and then install a 24 gig

00:06:56.759 --> 00:07:03.120
graphics card but but premiere's usage

00:07:00.180 --> 00:07:07.680
of vram isn't even that high and the rabbit hole goes even deeper if we drop

00:07:05.220 --> 00:07:14.039
our recording resolution down to 12 288 by 5112 it works fine with just eight

00:07:11.280 --> 00:07:20.160
gigs of vram so why would we need three times as much and get this even if we

00:07:16.979 --> 00:07:22.199
record at full res if we use lumetri on

00:07:20.160 --> 00:07:28.319
an adjustment layer instead of on the clip itself it also works fine damn you

00:07:26.099 --> 00:07:33.539
software bugs the bottom line then is that for whatever reason Blackmagic just

00:07:31.080 --> 00:07:38.460
cannot see seem to get their b-raw plugin to a stable place and it's been

00:07:36.000 --> 00:07:42.300
an ongoing issue one version will work then the next one will introduce bugs

00:07:40.380 --> 00:07:47.400
before being fixed again a couple of months later in a new version as for the

00:07:44.880 --> 00:07:52.319
current version well it's pretty broken for example copying and pasting raw

00:07:50.039 --> 00:07:56.220
settings from one clip to another is a guaranteed way to draw out a bug you

00:07:54.539 --> 00:08:00.479
might lose the ability to edit the raw settings or a clip might take on the

00:07:58.259 --> 00:08:04.500
settings of the clip preceding it or your program might just straight up

00:08:02.340 --> 00:08:08.160
crash some folks get around this by sticking to a version that works until

00:08:06.300 --> 00:08:13.740
the rest of the community finishes beta testing for them but to edit the Ursa

00:08:10.680 --> 00:08:15.660
mini 12ks footage Premiere requires the

00:08:13.740 --> 00:08:20.819
latest version of blackmagic's plugin which is the first to support 12kb raw

00:08:18.539 --> 00:08:24.720
files so unfortunately that's not an option for us which wouldn't be a

00:08:23.280 --> 00:08:30.479
problem if the camera could at least record in prores or dnxhd like its

00:08:27.900 --> 00:08:35.099
predecessors but it can't and whether it's for technical reasons or just

00:08:32.159 --> 00:08:38.880
because they don't want to Blackmagic apparently has no plans to support other

00:08:37.260 --> 00:08:44.219
codecs that they were willing to tell us about so then with a camera that

00:08:41.760 --> 00:08:49.680
requires the use of a janky plug-in to edit its footage what's an aspiring 12K

00:08:47.100 --> 00:08:55.560
content created to do enter autochroma they're a company AKA two guys who have

00:08:53.339 --> 00:09:00.839
been developing their own bra enabling plug-in for Premiere called b-raw studio

00:08:58.080 --> 00:09:06.180
for the last two years and shockingly even though it's a third-party plug-in

00:09:02.700 --> 00:09:07.920
made by two guys our experience is that

00:09:06.180 --> 00:09:12.660
it's more stable offers more functionality and has better support

00:09:10.080 --> 00:09:15.839
because autochroma actually answers emails which is

00:09:14.100 --> 00:09:20.339
they helped us iron out some initial wrinkles and it looks like with their

00:09:17.760 --> 00:09:24.060
plugin editing b-raw in Premiere is stable enough for us to consider making

00:09:22.019 --> 00:09:29.399
it part of our workflow but wait a second I mean isn't that ridiculous why

00:09:26.279 --> 00:09:31.500
is it necessary to buy a 59 third-party

00:09:29.399 --> 00:09:36.120
plug-in to be able to actually edit footage from a brand new ten thousand

00:09:34.140 --> 00:09:40.860
dollar camera we don't know maybe Blackmagic has Apple dreams you

00:09:38.880 --> 00:09:44.519
know where you film on a Blackmagic camera using a Blackmagic codec then

00:09:42.839 --> 00:09:48.540
edit in a Blackmagic program using Blackmagic Hardware which is neat you

00:09:46.620 --> 00:09:51.959
know good for you Blackmagic but if you want my advice

00:09:49.920 --> 00:09:56.940
make sure that your products work both in and out of your ecosystem because

00:09:54.720 --> 00:10:00.360
think about it if I were to dip my toes in the water with a purchase like this

00:09:58.380 --> 00:10:04.980
only to find out that the experience totally sucks unless I give you even

00:10:03.000 --> 00:10:08.459
more of my money to change out all of our other stuff and then maybe it'll be

00:10:07.140 --> 00:10:13.019
great that's not a great first impression is it so while blackmagic's

00:10:10.980 --> 00:10:18.720
Premiere plug-in is free the time and frustration that its instability cost us

00:10:14.940 --> 00:10:21.420
is worth much more than b-raw Studios 60

00:10:18.720 --> 00:10:26.459
price tag so for now we're not going to be shooting

00:10:23.040 --> 00:10:27.959
every video in 12K but with autochromas

00:10:26.459 --> 00:10:31.320
plugin and the adjustment layer workaround we can slowly bring it into

00:10:30.120 --> 00:10:35.220
our workflow while we wait for Blackmagic to fix the bugs and also for

00:10:33.660 --> 00:10:38.760
graphics cards with enough vram to actually be in stock but you know what

00:10:36.720 --> 00:10:43.800
maybe just forget it why don't we just all switch to Mac Brandon oh switch to

00:10:41.459 --> 00:10:46.980
Mac come on just like I'm gonna switch to talking about our sponsor pulseway

00:10:45.660 --> 00:10:52.620
pulseway is a real-time remote monitoring and management software that allows you to manage systems and support

00:10:50.100 --> 00:10:55.980
your users from anywhere it helps you fix problems on the go by sending

00:10:54.120 --> 00:11:00.300
commands from any mobile device it's compatible with Windows Mac and Linux

00:10:58.320 --> 00:11:04.560
pulse ways single app gives you remote desktop functionality so you can check

00:11:02.399 --> 00:11:08.579
real-time status and system resources logged in users monitor Network

00:11:06.300 --> 00:11:12.120
performance manage Windows updates and more and their endpoint protection

00:11:10.380 --> 00:11:16.200
function allows you to install pulse way antivirus across systems and ensure

00:11:14.160 --> 00:11:21.060
they're protected at all times with pulseway you can scan install backup and

00:11:19.079 --> 00:11:25.140
update all your systems on the go from your phone so try it for free today at

00:11:22.980 --> 00:11:29.040
pulseway.com or through our Link in the video description if you guys enjoyed

00:11:26.940 --> 00:11:32.579
this video maybe check out the you know what let's take a trip down memory lane

00:11:30.480 --> 00:11:35.640
and check out the unboxing of our first 8K camera

00:11:34.140 --> 00:11:40.980
ah yes it was enraging so put it in perspective

00:11:38.160 --> 00:11:47.180
guys one of those cameras cost about as much as five of these and it was only at

00:11:44.040 --> 00:11:47.180
8K what a rip