WEBVTT 00:00.390 --> 00:03.760 Welcome to blender camera tracking footage. 00:04.600 --> 00:11.140 So getting the right footage is important just like getting the right picture was important with a with 00:11.140 --> 00:17.120 our CGI in it in the right footage for a moving scene is equally as important. 00:17.150 --> 00:24.400 And initially I would recommend using a low resolution video high resolution video will require more 00:24.400 --> 00:27.310 memory and will be more taxing on your system. 00:27.310 --> 00:33.910 Now there is an argument to be said that higher resolution video will have more opportunities for high 00:33.910 --> 00:36.030 contrast areas in them. 00:36.070 --> 00:40.260 That's also important but we'll get to that in a bit. 00:40.270 --> 00:47.470 I'll be showing you how to allocate some more memory to the sequence or clip editor so that you can 00:47.470 --> 00:55.750 utilize more of your system's memory then Blender's default one gigabyte areas of high contrast in your 00:55.750 --> 00:58.920 footage are essential for auto tracking. 00:58.930 --> 01:04.080 Sure you can go ahead and place markers manually but that's going to be no fun. 01:04.080 --> 01:06.290 Well want to avoid that if possible. 01:07.220 --> 01:09.150 So what else about the footage. 01:09.230 --> 01:17.880 Short video is better if you have a look at any production film or even acg a short CGI animation. 01:17.910 --> 01:22.040 You can see that the scenes themselves they flick very quickly. 01:22.040 --> 01:23.960 There are only a few seconds long. 01:23.970 --> 01:32.040 I'll probably say don't try to go for any longer than 10 seconds unless the scene really requires it. 01:32.060 --> 01:37.460 Now if you've got several videos that you're joining together remember if they're part of the same scene 01:37.460 --> 01:40.360 same time frame consistent lighting does hap. 01:40.370 --> 01:41.710 That really really help. 01:41.870 --> 01:45.790 So have you shot one video at the beginning of the day one at noon and one at the end of the day and 01:45.790 --> 01:47.170 are suppose to be at the same time. 01:47.270 --> 01:52.070 The lighting is going to look dramatically different in the morning in the evening shadows are a lot 01:52.070 --> 01:57.930 lot longer so something to bear in mind and that can ruin the illusion that you're trying to put together. 01:58.280 --> 02:03.500 Now you will need the same camera and lens information that we did with the still image. 02:03.500 --> 02:05.750 And this can be problematic. 02:05.780 --> 02:08.450 The more you know about the scene the better. 02:08.450 --> 02:14.240 So this is one of these instances where you better even know the camera person who took the video and 02:14.240 --> 02:18.520 they know the details about the video or it's one you've taken yourself. 02:18.530 --> 02:25.100 Otherwise it can be very difficult because the video does not have the same metter data that a picture 02:25.100 --> 02:25.600 has. 02:25.610 --> 02:33.140 Very rarely have I ever seen the information for a video contain anything other than its resolution 02:33.410 --> 02:37.730 and maybe its frame rate as well as its size and all that lot. 02:37.820 --> 02:40.150 So that's going to leave us a bit in the dark. 02:40.190 --> 02:46.020 If you don't have that information now some tips when recording your own footage. 02:46.040 --> 02:51.710 Now you may have seen in the movies that people in cars and buildings and other bits and bobs sometimes 02:51.710 --> 02:54.780 end up with stickers stuck on them called markers. 02:54.800 --> 03:02.120 Well if the scene is green screened which often happens in production a character that is moving and 03:02.130 --> 03:08.660 is then to be replaced with a CGI character or indeed there is a lack of high contrast. 03:08.660 --> 03:14.840 You can place markers in the scene so there's nothing distinguishable and you can obviously control 03:14.840 --> 03:16.610 this if you're shooting the footage. 03:16.760 --> 03:23.060 If there's no high contrast areas you may need markers in the scene itself in order to. 03:23.060 --> 03:25.470 Camera track properly. 03:25.790 --> 03:29.120 Now are they going to be covered up by CGI. 03:29.120 --> 03:33.030 If not then you're going to have to remove them afterwards. 03:33.050 --> 03:38.350 So try and avoid actually putting markers where they're not going to be covered up. 03:39.110 --> 03:42.440 And finally keep a log of your cameras set up. 03:42.440 --> 03:45.250 Remember that some cameras a difference a don't. 03:45.260 --> 03:46.950 I've got an iPhone in front of me. 03:46.970 --> 03:48.550 Don't just write down iPhone right. 03:48.560 --> 03:55.040 The version of the iPhone it is otherwise you may get confused when you put in the details for an iPhone 03:55.040 --> 03:58.120 5 and it's an iPhone 6 for its iPhone 7 or whatever. 03:58.190 --> 04:01.350 You know these things can make a difference. 04:01.370 --> 04:05.620 So let's go import some footage now and hop on over into a blender. 04:07.100 --> 04:07.400 Right. 04:07.400 --> 04:12.160 So now they were over in blender The first thing I'm going to do is switch myself across. 04:12.180 --> 04:14.870 So the video editing window. 04:15.980 --> 04:19.430 Now we're over here we've got a breakout of everything. 04:19.490 --> 04:23.510 Now this is going to seem quite cramped again because I'm running at a lower resolution. 04:23.510 --> 04:29.390 Feel free by the way if you've got multiple monitors to start using your multiple monitors. 04:29.390 --> 04:30.430 It's a great idea. 04:30.440 --> 04:31.780 In this instance. 04:32.270 --> 04:40.250 So we need to import something into a blender and we'd can do that on the video sequence editor. 04:41.090 --> 04:46.040 And this particular view we can see we can switch between fuse. 04:46.690 --> 04:50.180 With these three toggles that move quite violently. 04:50.290 --> 04:52.600 This is the sequence of. 04:52.600 --> 05:00.580 The next one along is the image preview and then after that we have the secrets and the image preview 05:01.130 --> 05:05.770 so the image preview is the one in the top right hand corner and we're not actually going to use the 05:05.770 --> 05:11.440 curb's in this particular lecture so I'm going to make that disappear. 05:11.770 --> 05:17.440 So we've literally got one on top of the other and there's a time line underneath so we can play rewind 05:17.510 --> 05:18.350 etc.. 05:19.330 --> 05:24.300 Let's go ahead now and add a movie into our scene. 05:24.330 --> 05:30.280 Now I'm going to pick the high resolution so I'm going to go into my assets drone footage. 05:30.280 --> 05:36.160 I'm going to go to the for cave footage because really going to show the problems that you can have 05:36.160 --> 05:39.090 when it comes to large files. 05:39.100 --> 05:41.110 So I'm going to have this movie strip in now. 05:41.110 --> 05:48.230 Incidentally it will add the movie wherever your timeline was positioned so if it was at frame 135 would 05:48.250 --> 05:49.320 it popped in there. 05:49.480 --> 05:52.370 Fortunately it was at frame one. 05:52.400 --> 05:57.440 Now if I go ahead and hit play we can see in the video. 05:57.490 --> 06:01.250 Well with that she got the clip itself the image preview going. 06:01.300 --> 06:03.900 It's running about 10 frames per second. 06:03.910 --> 06:10.240 Now we're up to about frame 130 I'm going to stop that and go back to the beginning and play and we 06:10.240 --> 06:16.210 can see that it's now running at 30 frames per second and nice and smoothly and then it drops back down 06:16.210 --> 06:16.870 again. 06:16.870 --> 06:21.100 So it's start cashing that information is starting to store that information. 06:21.310 --> 06:27.280 Now if you're working on a larger project you may find you run out of buffer to do that on and it will 06:27.280 --> 06:30.610 depend again on your systems specifications. 06:30.610 --> 06:35.430 Now this is all to do with the system memory not your graphics card memory. 06:35.560 --> 06:43.180 So if you've got enough memory what we can do is go to file user preferences and go to the system tab. 06:43.410 --> 06:50.500 Once you're on the system tab you may have to scroll down or expand this out but on the second this 06:50.500 --> 06:57.130 middle column here sequencer and clip editor at the bottom there's a memory cash limit and this is measured 06:57.130 --> 06:58.530 in megabytes. 06:58.540 --> 07:04.010 If we hover over it's like most things it gives us a little tip says the memri cash limit in megabytes. 07:04.210 --> 07:08.180 Now you don't want to set this any higher than your system's value that's for sure. 07:08.320 --> 07:11.140 And you don't want a seller at your system's value either. 07:11.440 --> 07:16.750 But because I'm going to be working with this for a file and I have had a bit of practice putting together 07:16.750 --> 07:22.540 of his lectures I know that this fall k file is not going to be able to the entire thing is not going 07:22.540 --> 07:26.710 to be able to fit in to one gigabyte. 07:26.710 --> 07:31.330 So there are a couple of things we can do we can chop up the file to just the specific area we need. 07:31.330 --> 07:32.890 But we might not be able to do that. 07:32.890 --> 07:34.800 We may need more memory to work with. 07:34.960 --> 07:37.630 And again this does depend on your system memory as well. 07:37.720 --> 07:45.670 My computer that I'm on at the moment has 16 gigabytes of RAM so I'm going to give myself eight gigabytes 07:45.700 --> 07:48.850 using about half the capacity it needs to. 07:48.850 --> 07:50.660 It won't suddenly consume 8. 07:50.680 --> 07:57.770 It will just use up to 8 to cache video anything that's in the sequencing clip. 07:57.780 --> 08:02.020 Ed I'm going to save my user settings and close down user preferences. 08:02.020 --> 08:07.570 Now if I left this to play out it would go through and it would remember the whole thing. 08:07.570 --> 08:11.650 Incidentally I can also scrub backwards and forwards nice and quickly. 08:11.650 --> 08:18.240 If I go outside the range that have already gone so it starts jerking about which is less than I deal. 08:18.350 --> 08:22.290 It's nice and smooth here all jerky if we go further on. 08:22.360 --> 08:29.020 Now this is a 30 second clip so if I let that play out it would take roughly three times longer it would 08:29.020 --> 08:33.640 take about a minute and a half to play through and then the entire thing will be cached and you can 08:33.640 --> 08:39.850 see how much memory is currently using If I just set this playing a wizard at 30 frames per second on 08:39.850 --> 08:42.160 the info header bar at the very top here. 08:42.160 --> 08:48.640 We got the version of blender etc etc and then we have the memory utilization and we can see that if 08:48.640 --> 08:53.330 I just leave the mouse over it does nothing but if I keep revisiting it its will. 08:53.360 --> 08:55.270 Updates we've currently got. 08:55.270 --> 08:57.370 Five hundred ninety megabytes. 08:57.640 --> 08:59.150 And it's not going up anymore. 08:59.170 --> 09:06.070 Well it's not going up because our start and end frame who got a start frame at 1 and an end at 250. 09:06.170 --> 09:13.180 If we look at the time line the sorry not the time line sequencer just here where we have the name of 09:13.180 --> 09:19.170 the file and its location on the hard drive and then at the very end there is a vertical slash. 09:19.180 --> 09:25.510 I'm not quite sure those are called but then we've got 9 0 8 6 9 hundred eight frames long so if I update 09:25.510 --> 09:30.340 that to nine hundred eight frames and leave it to play it will actually buffer all the rest and we can 09:30.340 --> 09:35.410 see the frames per second in the top left has dropped down and I'm going to use my mouse wheel here 09:35.410 --> 09:39.470 just to move that back along so we can see the rest of the info head. 09:39.640 --> 09:47.230 And this as you can see if I got using mouse will in the right place is now at 800 900 So that's climbing 09:47.230 --> 09:49.540 up that's using the memory on the computer. 09:49.990 --> 09:55.270 Now when it comes to editing this file itself being able to scrub through just left clicking here and 09:55.270 --> 10:01.450 going backwards and forwards is quite useful and very powerful because it allows us to see our scene 10:01.510 --> 10:02.650 really easily. 10:02.650 --> 10:08.200 But we can also chop up our scene so we can place the play head at any particular point we could do 10:08.200 --> 10:09.580 that manually down at the bottom. 10:09.580 --> 10:14.110 Here we see what the counts are going up at the moment so you can position it exactly using this. 10:14.110 --> 10:18.250 Or we can just do a rough cuts by clicking and dragging them out. 10:18.260 --> 10:18.620 Do that. 10:18.700 --> 10:21.270 In a few moments after this is finished counting up. 10:21.310 --> 10:21.790 Excellent. 10:21.790 --> 10:28.200 So that's now all done and we can see it's using nearly two gigabytes worth of memory and that's a lot. 10:28.210 --> 10:31.480 If you think about it just a short clip. 10:31.510 --> 10:37.330 Now this is one of the reasons why I'd recommend perhaps not working with for K footage but maybe 720 10:37.370 --> 10:43.840 P Also the 720 footage is there for you guys that don't have really quick broadband's. 10:43.840 --> 10:46.970 It's as simple as that you can get going much quicker. 10:47.270 --> 10:47.480 OK. 10:47.500 --> 10:53.290 So now we've got this bufford and we can scrub between it we can start to pick where to make cuts. 10:53.410 --> 10:56.380 And there are a couple of types of cuts that we can make. 10:56.500 --> 11:03.940 So if I position the cursor just that say Here where the air field starts to come into view in the lower 11:03.940 --> 11:07.260 corner there you can go to the strip. 11:07.420 --> 11:10.080 And we've got a load of options. 11:10.170 --> 11:16.180 And at this particular point I'm talking about cutting and there are two types of cutting cut soft and 11:16.180 --> 11:18.270 cuts hard. 11:18.280 --> 11:25.660 The main difference between cuts soft and cut hard is the cut soft allows you to stretch and adjust 11:25.690 --> 11:27.390 the timing of the clip. 11:27.520 --> 11:29.370 Cut hard does not. 11:29.530 --> 11:35.210 So I once I've cut hard at this particular point it may take a few seconds to do. 11:35.380 --> 11:37.800 I can't extend this backwards and forwards. 11:37.810 --> 11:43.410 I can move these clips about using the right mouse but in fact most of the controls you'll come across 11:43.420 --> 11:45.690 a very similar compress X to delete. 11:45.700 --> 11:51.070 If I wanted to but because I have them a soft cut there is no way of extending this back again in recovering 11:51.070 --> 11:52.220 the early footage. 11:52.270 --> 11:55.400 If I'd done the soft cuts I would be able to. 11:55.630 --> 12:01.300 So I can use that to cut up parts of my image and I can hopefully undo those changes. 12:01.300 --> 12:03.030 There we go we're back again. 12:03.160 --> 12:11.620 Now can I undo a cuts that's been made who are in the right place and again something that I'm not used 12:11.620 --> 12:17.950 to doing is waiting because the computer is relatively quick my computer when doing most things however 12:18.190 --> 12:19.680 waiting for things to happen. 12:19.690 --> 12:23.570 The video editor can be time consuming as you sat there. 12:23.680 --> 12:27.900 Now as you see I faff the bout with that and it's jerky again. 12:28.000 --> 12:32.710 Now if I keep moving the cursor backwards and forwards eventually it will start storing those frames 12:32.880 --> 12:34.180 if at as undoing this. 12:34.180 --> 12:40.300 If you take a cursory glance up at the memory at the top it's storing each of these frames as it jumps 12:40.300 --> 12:43.690 over it and eventually it will start to get smooth again. 12:43.690 --> 12:47.510 So when you're doing editing like that it can clear some of your buffer. 12:47.520 --> 12:51.160 If you're not careful to just bear that in mind. 12:51.370 --> 12:57.320 So now we can get a movie clip on to our sequencer and we can cut it up. 12:57.520 --> 12:59.710 I think it's time for a challenge. 13:00.070 --> 13:05.670 Okay so a quick challenge for you guys are likely to go ahead and import your footage. 13:05.800 --> 13:11.830 So cut down your chosen footage to a suitable length I dare recommend leaving it minutes long perhaps 13:11.920 --> 13:14.580 10 seconds or less. 13:14.620 --> 13:20.740 Set up your camera accordingly so we haven't done that just yet and if you're following along with my 13:20.740 --> 13:27.700 particular videos then the supplied footage was shot on a deejay I Phantom for drone So you have to 13:27.700 --> 13:32.170 go and have a look and find the camera settings for that particular model. 13:32.260 --> 13:34.200 As always remember to save your work. 13:34.210 --> 13:39.550 That is quite important but when saving your work remember that your footage is not stored in the blend 13:39.550 --> 13:40.810 file itself. 13:40.810 --> 13:48.760 So I'd recommend putting it in its appropriate place now and then don't move it rename it from its location 13:48.790 --> 13:49.990 on your computer. 13:49.990 --> 13:50.840 Very important. 13:50.890 --> 13:54.090 Otherwise you'll open up your file again and it will just be blank. 13:54.100 --> 13:55.730 Which would be no good. 13:55.730 --> 13:58.480 Suppose a video now and give that a go. 14:00.060 --> 14:00.830 Okay guys. 14:00.840 --> 14:01.910 Welcome back. 14:02.040 --> 14:03.900 So now I've got my footage in. 14:03.900 --> 14:07.790 I just need to cut it to a suitable length and set up the camera settings. 14:08.040 --> 14:11.630 So let's go ahead and hop back on over in a blender. 14:12.770 --> 14:19.010 So I've got two things to do here I need to pick the right length and I also need to set up the camera. 14:19.010 --> 14:25.760 I'm going to do the length first so I really want it coming in around heavy airport where we can see 14:25.760 --> 14:29.340 the runway over there and that looks to be around here. 14:29.620 --> 14:32.060 Round the five second Mark. 14:32.480 --> 14:36.290 I'm going to use the shortcut key shift in K for that hard cuts. 14:37.810 --> 14:38.370 There we go. 14:38.370 --> 14:40.990 And I'm going to get rid of this beginning footage. 14:40.990 --> 14:48.850 A raise and then the footage here we can see on V in the properties panel over here the start frame 14:48.850 --> 14:49.840 angle is going to set that back. 14:49.840 --> 14:54.810 At one it stops me having to drag things about that can be a bit well. 14:54.850 --> 14:55.760 I'll show you here. 14:55.780 --> 15:02.020 If I start dragging about it's really jerky simply because it's not buffered all of that stuff yet I 15:02.020 --> 15:04.750 don't want to deal with that so that's that done. 15:04.780 --> 15:11.580 Now I want about 8 seconds or so so that that'll be all the way up to where it says 8. 15:11.590 --> 15:14.410 Which is where you saw and it looks like. 15:15.150 --> 15:16.740 Yes that's pretty good. 15:16.740 --> 15:21.570 It looks like the airport itself or the runway there disappears about that. 15:21.620 --> 15:24.210 But point as well sir it appears and disappears there. 15:24.210 --> 15:25.820 So I'm going to set that eight. 15:26.070 --> 15:28.140 And again do a number of hard cuts. 15:28.140 --> 15:31.180 Would the Thai be footage selected here. 15:31.320 --> 15:34.070 And I'm going to get rid of that extra bit. 15:34.230 --> 15:36.730 So I got my eight seconds of footage here. 15:37.320 --> 15:42.090 And how many frames is that that's going to be always eight times 24 25. 15:42.090 --> 15:43.330 I can't remember what I've got. 15:43.330 --> 15:44.420 It's set up to be. 15:44.610 --> 15:48.060 Either way are find out in a moment when you get to the end of it. 15:48.800 --> 15:52.880 To 40 something like that's all very close very very close. 15:53.000 --> 15:55.120 I'll leave it at 240 for the moment. 15:55.220 --> 16:02.720 And once that's bufford which now is Perfect's in it will play back we can see that's the air strip 16:02.720 --> 16:03.760 here is in view. 16:03.770 --> 16:05.480 And then it comes out again. 16:05.480 --> 16:06.180 Perfect. 16:06.380 --> 16:07.790 That's a good time. 16:07.790 --> 16:10.710 Any In fact here we can see it cuts out. 16:11.000 --> 16:13.130 And then there's an extra frame. 16:13.640 --> 16:15.160 So looks like it's 2 3 9. 16:16.710 --> 16:17.090 Okay. 16:17.110 --> 16:22.230 So now that we've got all of this lots in place we need to sort out the camera details. 16:22.300 --> 16:29.850 Now this is where it starts to get a bit interesting looking at the specifications for the deejay I 16:29.920 --> 16:36.700 Phantom for I literally went to Google and type in on another screen if you're wondering what's going 16:36.730 --> 16:37.370 on. 16:37.420 --> 16:39.850 And we have V. 16:41.060 --> 16:42.540 Details here. 16:42.580 --> 16:45.680 Now we've got a camera sensor size and there there's 19 more. 16:45.790 --> 16:49.260 Well let's go to the official dji website. 16:49.280 --> 16:55.310 And if we scroll down here we we have the sensor size how we got the field of view and here it says 16:55.310 --> 17:04.150 it's a 20 millimetre 35 format equivalent now 35 millimetre format equivalent means full frame camera 17:04.670 --> 17:10.650 so we can use that to our advantage and not having to worry too much about this extra information. 17:10.650 --> 17:18.250 And I will go and show you that right away because if we go ahead let's make sure I save my file. 17:19.810 --> 17:21.340 Movie that's fine. 17:21.340 --> 17:24.060 And let's go ahead and go new. 17:24.100 --> 17:29.620 So we have a sense let's go to our camera properties a look through that camera. 17:29.800 --> 17:34.540 This is a certain camera set up and I don't know what is at the moment so I'm going to go to the camera 17:34.540 --> 17:37.480 propertys and go full frame camera. 17:37.480 --> 17:38.680 That's fine. 17:38.920 --> 17:41.000 And focal length of 20. 17:41.080 --> 17:46.760 So that's what's a 20 millimetre equivalent will look like when it's looking at that cube. 17:46.990 --> 17:53.920 Now if we go ahead and add a nother camera into our scene so I'll just duplicated that and door and 17:53.920 --> 17:57.460 let's call it phantom So we just know what's going on. 17:57.460 --> 18:02.830 We've got the cube there we've got the phantom camera now the phantom camera. 18:02.830 --> 18:08.710 According to their spiel is two and a third a cross. 18:09.810 --> 18:20.310 Two point three inches so we can go to our sensor size here and go to Point three times two point five 18:20.310 --> 18:20.950 four. 18:20.970 --> 18:26.150 And that should convert inches into millimetres. 18:26.190 --> 18:27.780 And there we go. 18:28.170 --> 18:29.950 We've got two point. 18:29.990 --> 18:35.790 So five point four eight millimetres that sounds about right for a tiny tiny camera. 18:36.030 --> 18:41.760 And then we can adjust the focal length accordingly so it roughly matches I mean if you needed to be 18:41.820 --> 18:49.500 really really precise you could actually go ahead and do it with mathematics to get you to the right 18:49.500 --> 18:50.180 points. 18:50.190 --> 18:57.720 However there is a nother thing that needs to be taken into account which is quite tricky. 18:57.750 --> 19:03.120 Each sensor can record video not across the whole sensor. 19:03.150 --> 19:09.600 It could record it only on part of the sensor effectively changing the sensor size when it comes to 19:09.780 --> 19:16.030 actually recording and that will completely change the actual angle of the camera etc.. 19:16.350 --> 19:23.880 Now because de provided us with the thirty five mil equivalent I am lit she can stick to that's a full 19:23.880 --> 19:25.070 frame camera. 19:25.190 --> 19:30.200 I've adjusted these settings now which is a bit silly that was 32 before and 20. 19:30.380 --> 19:37.050 So I'm going to have my camera set up with a focal length for 20 at full frame camera for Frankfurt 19:37.080 --> 19:42.480 final camera so I'm going to go head now demonstrate that back to this which is the file I'm working 19:42.480 --> 19:49.230 on go back to the default view go to our camera and I'm going to make sure the camera is named appropriately 19:49.560 --> 19:53.030 so I'm going to call it's D.J eye camera. 19:55.650 --> 20:02.440 And I'm going to call it 20 mil a meter thirty five m e equiv. 20:04.070 --> 20:04.970 Should be enough. 20:04.970 --> 20:10.550 So I know what's going on there suffern go to my camera settings and is currently set at 35. 20:10.550 --> 20:17.400 If we set that 20 there we go that should now have the right field of view for whatever scene we set 20:17.400 --> 20:17.810 up. 20:17.810 --> 20:20.350 Now our footage is quite distant footage. 20:20.360 --> 20:25.370 So we're going to have at the camera itself is going to be positioned quite a way back from this ground 20:25.370 --> 20:30.890 plane etc. So there's a good chance we'll have to play with some clipping distances again but we'll 20:30.890 --> 20:32.160 deal with that in a bit. 20:32.150 --> 20:33.400 So we've got the clipping here. 20:33.440 --> 20:36.750 In fact whilst we're here be silly not to set that too a bit higher. 20:36.780 --> 20:39.780 Let's set it to 1000 meters or a kilometre. 20:39.950 --> 20:43.900 Again with the height of where that drone was that might not be enough. 20:43.990 --> 20:48.420 Will leave a thousand for the moment and tinker with it if necessary. 20:48.470 --> 20:52.980 So now we got all that sorted we can save our file and we're ready to go. 20:53.870 --> 20:55.340 How did you guys get on. 20:55.340 --> 21:01.750 Are you using the footage that I'm using or are you using your own footage I'd love to see your work. 21:01.760 --> 21:06.640 Remember to share on the forums and I will see you guys in the next lecture.