General techniques

3 minutes read

Choosing the render engine

I initially started the project with EEVEE exclusively, as it is faster than Cycles. I ended up switching to Cycles for certain scenes for the following reasons :

I got very good results with 32 samples and denoising in Cycles, which is fast to render. The default value is 4096 samples, which is excessive here.

Choosing the framerate

The original opening has 23.98 fps, I chose this framerate in Blender (output/format/frame rate) to make it match easily.

Scene and reference videos

I decided to use a different blend file for each shot of video, as it seemed easier to manage.

I cut the original opening to obtain a reference clip for each scene, then imported it with Object mode/Add/Image/Reference. Then, in the object data properties, click match movie length to get the clip length of this scene. Finally, use this value as the end of your timeline, so that the Blender scene duration matches with the reference.

reference image menu in its object data properties
Reference image menu in its object data properties. The match movie length button is circled in red.

Warning

Blender will only take into account the scene frame rate to play the reference video. For example, if your reference is 23.98 fps and your scene is at 60 fps, the reference will be sped up when playing in Blender.

This is why I chose to animate scenes at the framerate of the original video : it avoids complications.

Using a screenshot as a light-emitting background

Although you can use an image as background in the compositor, it can be useful to import your background as a mesh in your scene : it will be compatible with camera shaking, and can even emit secondary lighting to better integrate the characters in the scene.

To add a mesh background : Object mode/Add/Image/Mesh, then customize the material with the following parameters :

Background image material setup
Background image material setup.