subtitlecat.com

All language subtitles for Nuke Compositing for 3D Artists week 2 - Classroom - CG Master Academy

Afrikaans

Akan

Albanian

Amharic

Arabic

Armenian

Azerbaijani

Basque

Belarusian

Bemba

Bengali

Bihari

Bosnian

Breton

Bulgarian

Cambodian

Catalan

Cebuano

Cherokee

Chichewa

Chinese (Simplified)

Chinese (Traditional)

Corsican

Croatian

Czech

Danish

Dutch

English

Esperanto

Estonian

Ewe

Faroese

Filipino

Finnish

French Download

Frisian

Galician

Georgian

German

Greek

Guarani

Gujarati

Haitian Creole

Hausa

Hawaiian

Hebrew

Hindi

Hmong

Hungarian

Icelandic

Igbo

Indonesian

Interlingua

Irish

Italian

Japanese

Javanese

Kannada

Kazakh

Kinyarwanda

Kirundi

Kongo

Korean

Krio (Sierra Leone)

Kurdish

Kurdish (Soranî)

Kyrgyz

Laothian

Latin

Latvian

Lingala

Lithuanian

Lozi

Luganda

Luo

Luxembourgish

Macedonian

Malagasy

Malay

Malayalam

Maltese

Maori

Marathi

Mauritian Creole

Moldavian

Mongolian

Myanmar (Burmese)

Montenegrin

Nepali

Nigerian Pidgin

Northern Sotho

Norwegian

Norwegian (Nynorsk)

Occitan

Oriya

Oromo

Pashto

Persian

Polish

Portuguese (Brazil)

Portuguese (Portugal)

Punjabi

Quechua

Romanian

Romansh

Runyakitara

Russian

Samoan

Scots Gaelic

Serbian

Serbo-Croatian

Sesotho

Setswana

Seychellois Creole

Shona

Sindhi

Sinhalese

Slovak

Slovenian

Somali

Spanish

Spanish (Latin American)

Sundanese

Swahili

Swedish

Tajik

Tamil

Tatar

Telugu

Thai

Tigrinya

Tonga

Tshiluba

Tumbuka

Turkish

Turkmen

Twi

Uighur

Ukrainian

Urdu

Uzbek

Vietnamese

Welsh

Wolof

Xhosa

Yiddish

Yoruba

Zulu

Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 00:00:05,166 --> 00:00:06,566 hi welcome to week 2 2 00:00:06,566 --> 00:00:07,300 in this week 3 00:00:07,300 --> 00:00:08,900 we're going to be going over 4 00:00:08,966 --> 00:00:10,333 a couple nodes um 5 00:00:10,333 --> 00:00:11,966 such as the tracker node 6 00:00:11,966 --> 00:00:14,833 and with the tracker node will be able to 7 00:00:14,866 --> 00:00:17,400 track features on any footage 8 00:00:17,466 --> 00:00:19,500 and from there we could use the 9 00:00:19,666 --> 00:00:22,100 transform data to either match 10 00:00:22,100 --> 00:00:25,133 move or stabilize a footage from there 11 00:00:25,133 --> 00:00:28,000 we will be looking at the camera tracker node 12 00:00:28,000 --> 00:00:31,400 which is a powerful node that allows us to solve 13 00:00:31,466 --> 00:00:33,766 for a 3D camera in nuke 14 00:00:33,800 --> 00:00:36,166 and from there we could use the 15 00:00:36,300 --> 00:00:38,066 3D camera to 16 00:00:38,533 --> 00:00:40,300 project elements 17 00:00:40,333 --> 00:00:41,333 using that camera 18 00:00:41,333 --> 00:00:44,466 or we could generate point clouds off of the 19 00:00:44,900 --> 00:00:45,900 camera solve 20 00:00:45,900 --> 00:00:48,966 which will allow us control to output 21 00:00:49,466 --> 00:00:51,366 access nodes off of it 22 00:00:51,733 --> 00:00:55,100 from there we will move on to the Motion Blur 2D 23 00:00:55,266 --> 00:00:59,066 which allows us to take 2D transform datas 24 00:00:59,133 --> 00:01:01,800 from a tracker and apply 25 00:01:01,933 --> 00:01:02,700 vector blur 26 00:01:02,700 --> 00:01:06,266 and motion blur to an image based on the 2D transforms 27 00:01:06,533 --> 00:01:07,400 and from there 28 00:01:07,400 --> 00:01:10,000 we will move on to Motion Blur 3D 29 00:01:10,066 --> 00:01:12,600 which similar to the Motion Blur 2D node 30 00:01:12,900 --> 00:01:14,533 it allows us to take 31 00:01:14,533 --> 00:01:15,966 um camera data 32 00:01:15,966 --> 00:01:18,833 translations and apply motion blur 33 00:01:18,866 --> 00:01:20,500 based on that camera data 34 00:01:20,866 --> 00:01:22,533 from there we will go into 35 00:01:22,533 --> 00:01:24,333 the use of the Vector Blur Node 36 00:01:24,333 --> 00:01:26,600 which works with the 37 00:01:26,666 --> 00:01:27,366 Motion Blur 38 00:01:27,366 --> 00:01:29,300 3D and Motion Blur 2D 39 00:01:29,466 --> 00:01:32,466 along with 3D rendered velocity data 40 00:01:32,466 --> 00:01:35,000 that we could use to apply Motion Blur to 41 00:01:35,000 --> 00:01:36,566 our 3D renders 42 00:01:36,766 --> 00:01:38,566 which is great 43 00:01:38,566 --> 00:01:39,566 efficient use 44 00:01:39,566 --> 00:01:42,533 of render time on the 3D side and allows us 45 00:01:42,533 --> 00:01:45,000 to do post motion blur in comp 46 00:01:45,000 --> 00:01:48,566 and control how much motion blur we output from there 47 00:01:48,566 --> 00:01:53,133 we will finish things off by using the reconsaw 3D node 48 00:01:53,133 --> 00:01:55,500 which allows us to take x 49 00:01:55,500 --> 00:01:57,433 y z coordinates 50 00:01:57,466 --> 00:02:00,500 and transform and translate those to 51 00:02:00,566 --> 00:02:02,400 2D coordinates in X and y 52 00:02:02,733 --> 00:02:03,966 which allows us 53 00:02:04,000 --> 00:02:06,233 great control over using 54 00:02:06,533 --> 00:02:08,400 the 2D coordinates to 55 00:02:08,600 --> 00:02:10,766 apply volume rays and 56 00:02:10,766 --> 00:02:12,466 lens flares and 57 00:02:12,466 --> 00:02:14,566 anything that pretty much uses 2D coordinates 58 00:02:14,566 --> 00:02:16,466 we could actually even use the 59 00:02:16,900 --> 00:02:19,633 2D coordinates that we get from the reconcile 3D 60 00:02:19,733 --> 00:02:22,466 to help help our trackers out 61 00:02:22,466 --> 00:02:23,833 or even apply 62 00:02:24,166 --> 00:02:25,500 to a tracker for match 63 00:02:25,500 --> 00:02:27,266 move and stabilization 64 00:02:27,266 --> 00:02:29,333 so that is just a broad overview 65 00:02:29,333 --> 00:02:31,766 of the notes we will be covering this week 66 00:02:31,766 --> 00:02:35,266 um I hope you find them informative and um 67 00:02:35,366 --> 00:02:37,033 you get good use out of them 68 00:02:37,100 --> 00:02:38,266 in the coming weeks 69 00:02:38,300 --> 00:02:39,533 look forward to 70 00:02:39,533 --> 00:02:42,100 going over these with you guys in Week 2 71 00:02:42,200 --> 00:02:43,466 thank you so much 4745