Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:14,000 --> 00:00:14,933
in this lesson
2
00:00:14,933 --> 00:00:17,233
we're going to learn how to use PG bouquet
3
00:00:17,333 --> 00:00:19,499
to create realistic depth field
4
00:00:21,000 --> 00:00:25,700
some of you may be aware of PG Bouquet and what it is
5
00:00:26,000 --> 00:00:31,633
is it's a plug in that does depth the field or to focus
6
00:00:33,000 --> 00:00:35,200
and it's real claim to fame
7
00:00:35,200 --> 00:00:37,966
and why it's popular with studios
8
00:00:37,966 --> 00:00:41,399
is that it supports deep
9
00:00:41,533 --> 00:00:43,366
and as far as I'm aware
10
00:00:43,366 --> 00:00:45,366
it's still the only
11
00:00:46,266 --> 00:00:49,499
depth of field plug in that supports deep
12
00:00:50,566 --> 00:00:54,399
and it's also extremely physically accurate
13
00:00:54,700 --> 00:00:57,700
unlike most tools
14
00:00:57,700 --> 00:00:59,166
things like defocus
15
00:01:00,533 --> 00:01:02,899
or Z defocus
16
00:01:02,900 --> 00:01:06,000
or any of the other techniques you can use
17
00:01:06,000 --> 00:01:08,366
to basically just blur an image
18
00:01:09,466 --> 00:01:13,333
it uses algorithms that are designed to actually
19
00:01:13,333 --> 00:01:17,966
simulate the way that light travels through a lens
20
00:01:17,966 --> 00:01:19,466
and the kind of optical artifacts
21
00:01:19,466 --> 00:01:21,099
that you would actually produce
22
00:01:21,100 --> 00:01:24,133
so that you end up with a result that's very
23
00:01:24,133 --> 00:01:25,199
photographic
24
00:01:26,000 --> 00:01:27,666
very optically realistic
25
00:01:28,933 --> 00:01:31,666
it tends to be a little slow and in certain cases
26
00:01:31,666 --> 00:01:33,966
it can actually be a little bit unstable
27
00:01:34,566 --> 00:01:38,066
but if you're looking for accuracy and quality
28
00:01:38,400 --> 00:01:41,766
especially if you can take the time to use it
29
00:01:42,166 --> 00:01:43,266
afford the uh
30
00:01:43,400 --> 00:01:44,800
the computation time
31
00:01:45,200 --> 00:01:46,266
the results can be really
32
00:01:46,266 --> 00:01:47,199
really beautiful
33
00:01:49,066 --> 00:01:51,466
so let's dive into it
34
00:01:54,200 --> 00:01:55,600
alright so we've got our
35
00:01:57,333 --> 00:01:58,466
our shot again
36
00:01:59,566 --> 00:02:03,633
so let's start with making the PG Boken node
37
00:02:04,533 --> 00:02:06,066
so we've got a bunch of inputs
38
00:02:07,300 --> 00:02:08,366
we'll take a look
39
00:02:12,333 --> 00:02:18,499
input kernel camera and deep input
40
00:02:20,966 --> 00:02:22,866
then here additionally we have mats
41
00:02:22,866 --> 00:02:24,666
if you wanted to start putting mats in
42
00:02:25,600 --> 00:02:28,400
mats would be just the same thing as masks
43
00:02:28,600 --> 00:02:30,300
in a normal nuke note
44
00:02:30,900 --> 00:02:32,100
so I kind of walk you through this
45
00:02:32,100 --> 00:02:34,600
input is going to be your regular input
46
00:02:35,800 --> 00:02:36,266
your beauty
47
00:02:36,266 --> 00:02:37,733
you know your beauty pass
48
00:02:37,733 --> 00:02:40,033
your primary image uh
49
00:02:40,166 --> 00:02:42,266
something that is important to note is that
50
00:02:42,266 --> 00:02:46,266
if your deep data is also in your primary input pipe
51
00:02:46,566 --> 00:02:48,599
it can accept it through this just fine
52
00:02:48,800 --> 00:02:52,166
uh otherwise you'd have to plug it into the deep input
53
00:02:52,500 --> 00:02:54,500
if there was just deep by itself
54
00:02:55,166 --> 00:02:56,366
uh the camera
55
00:02:57,066 --> 00:02:59,299
the camera is something that the uh
56
00:02:59,566 --> 00:03:01,666
the camera simulation aspect
57
00:03:02,466 --> 00:03:05,566
of this plugin is really driven by a nuke camera
58
00:03:07,366 --> 00:03:09,166
and I'll I'll explain how that works
59
00:03:09,166 --> 00:03:10,433
and then the kernel
60
00:03:10,733 --> 00:03:14,199
if you're not familiar with how image kernels work
61
00:03:14,533 --> 00:03:16,366
basically when you think about
62
00:03:16,700 --> 00:03:18,333
uh bouquet the
63
00:03:18,333 --> 00:03:19,866
the actual optical effect
64
00:03:19,966 --> 00:03:21,999
you'll get things like um
65
00:03:22,900 --> 00:03:27,433
uh the shape of the Iris in a defocused photograph
66
00:03:28,500 --> 00:03:31,533
well the shape of that Iris is what's referred to
67
00:03:31,533 --> 00:03:33,866
in image processing terms as the kernel
68
00:03:34,366 --> 00:03:36,433
and to be more technical
69
00:03:36,666 --> 00:03:37,633
it would be
70
00:03:37,766 --> 00:03:41,466
if you were to try to recreate that in image processing
71
00:03:41,800 --> 00:03:42,933
which we are
72
00:03:42,933 --> 00:03:43,799
in this case
73
00:03:44,266 --> 00:03:47,633
it would be referred to as a convolution kernel
74
00:03:48,600 --> 00:03:52,633
because convolution is the type of
75
00:03:53,100 --> 00:03:54,800
blurring that we're doing
76
00:03:54,800 --> 00:03:56,733
we're actually blurring it based on
77
00:03:56,733 --> 00:03:57,999
the shape of an image
78
00:03:58,000 --> 00:04:01,366
not just averaging pixels together
79
00:04:01,366 --> 00:04:04,366
based on how a normal blur node
80
00:04:04,366 --> 00:04:05,866
like a gaustian blur
81
00:04:06,800 --> 00:04:09,133
just takes neighboring pixels
82
00:04:09,133 --> 00:04:10,766
and that averages them together
83
00:04:11,466 --> 00:04:14,699
in the case of a convolusion operation
84
00:04:14,700 --> 00:04:18,500
you're actually blurring the image based on a shape
85
00:04:18,733 --> 00:04:21,466
and that shape would be the kernel input
86
00:04:21,533 --> 00:04:23,366
we're not going to use a kernel in this case
87
00:04:23,366 --> 00:04:24,599
but I just thought I'd explain it
88
00:04:24,600 --> 00:04:26,333
in case you wanted to try and match something
89
00:04:26,333 --> 00:04:28,566
cause if you have a very specific look
90
00:04:28,566 --> 00:04:29,999
in a project that you're working on
91
00:04:30,000 --> 00:04:33,200
and you can see very clearly as a certain shape
92
00:04:33,333 --> 00:04:36,366
when you have the focused image and
93
00:04:36,366 --> 00:04:37,766
and you want uh
94
00:04:37,766 --> 00:04:40,099
the focused areas of your visual effect shots
95
00:04:40,100 --> 00:04:41,666
to match that exactly
96
00:04:41,666 --> 00:04:46,633
then you would definitely try to use a kernel shape
97
00:04:46,900 --> 00:04:49,100
based on a reference image from a
98
00:04:49,800 --> 00:04:51,900
actual out of focus area
99
00:04:51,900 --> 00:04:53,266
from the real lens
100
00:04:55,933 --> 00:04:59,833
let's start off by plugging this guy in
101
00:05:02,933 --> 00:05:07,433
input actually set this to
102
00:05:09,166 --> 00:05:10,833
if we take a quick look
103
00:05:11,166 --> 00:05:13,666
to which we still have deep data
104
00:05:15,066 --> 00:05:16,233
yes we do
105
00:05:20,000 --> 00:05:22,700
the problem here is I am not merging to deep data
106
00:05:22,700 --> 00:05:24,600
so let's do all
107
00:05:27,366 --> 00:05:28,499
quick tip is
108
00:05:30,066 --> 00:05:36,299
if you do two brackets in the label value space
109
00:05:36,300 --> 00:05:38,833
and then the name of any knob
110
00:05:38,900 --> 00:05:39,933
any knob at all
111
00:05:39,933 --> 00:05:42,233
in this case we want also merge
112
00:05:44,466 --> 00:05:46,166
so let's just grab the deep
113
00:05:46,166 --> 00:05:48,666
so it'll be more specific in the label just deep
114
00:05:48,766 --> 00:05:50,099
if you just hover the
115
00:05:50,100 --> 00:05:53,933
the cursor over any knob it will give you the name
116
00:05:53,933 --> 00:05:57,199
B box meta input
117
00:05:57,733 --> 00:06:00,566
and this one is also underscore merge
118
00:06:01,933 --> 00:06:05,399
so also underscore merge
119
00:06:05,733 --> 00:06:08,266
so inside a brackets value space
120
00:06:08,266 --> 00:06:09,666
also underscore merge
121
00:06:10,166 --> 00:06:12,299
and the result of course
122
00:06:12,300 --> 00:06:17,000
as we get deep in the label here automatically
123
00:06:18,000 --> 00:06:20,000
and if we change this it changes
124
00:06:21,100 --> 00:06:22,600
so this is a little bit of a
125
00:06:24,166 --> 00:06:27,066
nuke TCL or tickle expression that I
126
00:06:27,066 --> 00:06:29,799
I use all the time because I like to label things
127
00:06:29,800 --> 00:06:31,600
because now I know that at a glance
128
00:06:31,600 --> 00:06:32,733
this is not just RGBA
129
00:06:32,733 --> 00:06:34,199
it's also RGBA deep
130
00:06:35,200 --> 00:06:36,400
so that I can plug in the input here
131
00:06:36,400 --> 00:06:39,833
because as deep data requires deep input
132
00:06:42,900 --> 00:06:46,400
and we need to now make the camera
133
00:06:48,500 --> 00:06:50,600
go ahead and load in just like last time
134
00:06:50,600 --> 00:06:54,900
read in our Olympic camera yes
135
00:06:56,100 --> 00:06:59,600
okay so one thing that we're gonna do
136
00:06:59,866 --> 00:07:01,299
after we hook up this camera
137
00:07:01,500 --> 00:07:03,466
is that we've read in these values
138
00:07:04,466 --> 00:07:06,666
actually gonna uncheck read from file
139
00:07:06,666 --> 00:07:08,299
so now we're not reading from file anymore
140
00:07:08,333 --> 00:07:10,099
cause we have read from file checked
141
00:07:11,533 --> 00:07:13,299
you can see that these knobs are grayed out
142
00:07:13,300 --> 00:07:15,500
we can't adjust these at all
143
00:07:17,100 --> 00:07:17,933
and we're gonna want to
144
00:07:17,933 --> 00:07:19,466
is we're gonna want to manipulate things
145
00:07:19,466 --> 00:07:20,866
in order to control the plug in
146
00:07:24,666 --> 00:07:27,599
let's take a look at the result the plugin is giving us
147
00:07:30,666 --> 00:07:34,799
okay so this case these default settings
148
00:07:35,066 --> 00:07:38,466
not really seeing anything happening
149
00:07:42,766 --> 00:07:44,833
the first reason why is depth channel
150
00:07:45,066 --> 00:07:47,166
the fault is depth dot Z
151
00:07:48,000 --> 00:07:48,966
we don't wanna use the depth channel
152
00:07:48,966 --> 00:07:51,699
we're gonna use deep so choose deep dot front
153
00:07:52,966 --> 00:07:55,933
okay so now it's starting to render this frame
154
00:07:55,933 --> 00:07:58,466
we still don't see much of an issue happening
155
00:07:58,466 --> 00:07:59,899
so let's switch this up
156
00:08:00,666 --> 00:08:02,199
integrate front pack separately
157
00:08:02,200 --> 00:08:04,300
Wanna check this for accuracy
158
00:08:06,166 --> 00:08:07,666
let's go to lens
159
00:08:08,366 --> 00:08:10,433
okay first things first
160
00:08:11,066 --> 00:08:13,799
so now you can see it's still in the default mode
161
00:08:13,800 --> 00:08:15,766
where it's basically just faking it
162
00:08:16,866 --> 00:08:20,633
what we wanna do is check real world lens simulation
163
00:08:21,566 --> 00:08:22,699
we run to the frame
164
00:08:22,700 --> 00:08:26,466
immediately we see a huge difference
165
00:08:29,066 --> 00:08:31,099
so the camera film back
166
00:08:31,133 --> 00:08:33,999
that we're rendering with here is full frame
167
00:08:34,000 --> 00:08:38,600
full frame still just 36 millimeters
168
00:08:39,000 --> 00:08:41,566
horizontal by 24 millimeters vertical
169
00:08:42,166 --> 00:08:43,233
so let's go ahead
170
00:08:43,866 --> 00:08:45,399
set this to custom
171
00:08:48,100 --> 00:08:52,733
36 24 to match the camera
172
00:08:52,733 --> 00:08:54,999
these aren't linked unfortunately
173
00:08:56,933 --> 00:08:57,899
so now what we're getting
174
00:08:57,900 --> 00:09:00,600
with an f stop value of 1.4 is really
175
00:09:00,600 --> 00:09:02,700
really extreme depth of field
176
00:09:06,533 --> 00:09:09,799
this is not something that I would normally pick
177
00:09:09,800 --> 00:09:14,433
let's back off a little bit to something like maybe F4
178
00:09:16,533 --> 00:09:18,599
that's a little bit more manageable
179
00:09:18,600 --> 00:09:21,633
let's take a look at what maybe F8 looks like
180
00:09:22,000 --> 00:09:23,966
okay and then F16
181
00:09:23,966 --> 00:09:25,566
so if you're familiar with photography
182
00:09:25,566 --> 00:09:26,866
have you ever done any photography
183
00:09:26,866 --> 00:09:30,699
you'll know that if you are using a real camera
184
00:09:30,800 --> 00:09:33,666
this is the result you'd expect to get
185
00:09:33,666 --> 00:09:36,199
this is how a real lens would behave
186
00:09:36,800 --> 00:09:39,266
and that's really one of my favorite parts about Peachy
187
00:09:39,266 --> 00:09:42,233
Bouquet is that you can get very
188
00:09:43,066 --> 00:09:47,233
realistic results using realistic methods
189
00:09:48,100 --> 00:09:51,233
so you can apply what you know about photography
190
00:09:52,200 --> 00:09:54,600
directly to what you know about compositing
191
00:09:55,700 --> 00:09:58,366
let's just go back down to F4
192
00:09:59,966 --> 00:10:01,666
what I was doing there in case
193
00:10:02,700 --> 00:10:03,933
case you didn't know
194
00:10:03,933 --> 00:10:07,499
is that you can do little operations division
195
00:10:07,666 --> 00:10:09,833
multiplication right in a knob
196
00:10:10,566 --> 00:10:13,866
and when you press enter it will do the math
197
00:10:13,866 --> 00:10:16,499
and the result will actually become the new value
198
00:10:18,266 --> 00:10:20,433
we have now reached the end of the lesson
199
00:10:20,900 --> 00:10:23,700
we Learned how to use Peragon Labs Bouquet plugin
200
00:10:23,700 --> 00:10:25,700
to create a realistic depth of field
201
00:10:26,533 --> 00:10:27,899
in the next lesson
202
00:10:28,100 --> 00:10:31,433
we will learn how to set the focal point in PG bouquet
14668
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.