Cutouts Brief Guide

The Image Size consists of the width and height of an image. Usually, these values are given in pixels and the following format:

3000x2250

In this example for the image size, it tells us the following about the image:
The image width is 3000 pixels
The image height is 2250pixels

Higher size/resolution require more time for rendering

Image file formats are standardized means of organizing and storing digital images.

Image files are composed of digital data in one of these formats so that the data can be rasterized for use on a computer display or printer.

Usually, we deliver images in jpg, png or tiff formats.

Raster vs. Vector – What's the difference?

In Cutouts we always render the images on a transparent background and add a solid background in compositing.

We usually deliver tiff or png on a transparent background and jpg with white background

With or without shadows it's all up to the client.

Just keep in mind that shadows require a huge amount of rendering time.

Path to the product 3d model/s

Path to the Shader/s which needs to be used in the project

SKU is an exclusive identification code assigned to merchandise for inventory tracking.
Although SKUs are mainly used by clients we want to have consistency and easy tracking of the delivered images for that reason we require the client to provide SKU or naming convention for all requested images.

Color correction is an important stage of our process that's why it's crucial to have a reference. Some clients prefer requested images to be color corrected to their old images others sent us samples as reference. 

LINK TO CUTOUTS BRIEF TEMPLATE

Every client and every project is unique and may required different information or outcomes. For that reason the template can be adapted and customisable for each client needs and requirements.

The Cutout Brief template must be used as a guide not only to make the brief easier to understand but to promote consistency. A standardised way of briefing the team will make it easier and faster to read, action the work required and subsequently increase capacity.

Core information such as product and shaders paths should live in Ftrack. We should refrain to copy and paste paths into the template and guide/direct the team to existent paths already in Ftrack. Avoiding multiplication of the content will avoid confusion when coming across the same products in multiple locations.