Punjab PSEB Sr. Sec. NSQF Media (Roto Artist) common mistakes
Punjab PSEB Sr. Sec. NSQF Media (Roto Artist) · Understand the traps and how to avoid them.
Calculating final image file size or render time by multiplying width by height only, ignoring bit depth and channel count (e.g. answering for an 8-bit RGB frame when the question specifies 16-bit RGBA).
Candidates memorise 'megapixels = resolution' and treat resolution and file size as the same idea, so they skip the bit-depth and channel arithmetic under time pressure.
What to do instead
Before answering any size or data-rate question, write the full formula on scratch paper: pixels × channels × bits per channel ÷ 8 = bytes per frame. Practise with 1920×1080 at 8-bit RGB, 10-bit RGB, and 16-bit RGBA until the channel multiplier becomes automatic.
Describing a roto spline as 'one shape per object' and never adding internal or subtractive shapes, so answers on complex mattes (a person holding a mug, a hand over the face) are marked wrong.
Beginners learn roto as silhouette tracing and do not connect shape modes (add, subtract, intersect) to real occlusion problems.
What to do instead
Study three worked cases: a figure with a gap between arm and torso, an object passing behind a foreground element, and a semi-transparent edge. For each, state which shape mode and which separate matte you would use, and why a single outline fails.
Confusing keyframe interpolation types - answering that linear keys give ease-in/ease-out, or that holding a key produces smooth motion - when asked about natural motion arcs on a tracking or roto animation.
The terms sound interchangeable in casual use, and candidates have clicked the buttons in software without learning what each curve does mathematically.
What to do instead
Build a one-line reference: linear = constant speed, ease/bezier = accelerated start and stop, hold/constant = value jumps at the next key with no in-between. Match each to a shot example (a falling object, a head turn, a light switching on).
Treating the roto artist's deliverable as a finished composite, and answering pipeline questions as if roto happens after grading and comp finalisation.
Candidates see the final shot on screen and assume everyone works on the finished image, rather than understanding mattes feed downstream departments.
What to do instead
Draw the shot order from plate ingest to delivery and mark where roto sits: plate prep, tracking, roto/matte extraction, then comp, grade, and review. Learn what a roto artist hands over - mattes, alpha channels, naming conventions, frame ranges - and who consumes them.
Naming the wrong file format for a given job - proposing JPEG for a matte with soft edges, or MP4 for an intermediate in a comp pipeline - instead of matching format to alpha support, bit depth, and compression type.
Format knowledge is learned from web usage (JPEG for photos, MP4 for video) rather than from post-production requirements, so candidates default to familiar consumer formats.
What to do instead
Memorise a small decision table: formats that carry alpha (PNG, TIFF, OpenEXR, ProRes 4444), formats that are lossy and unsuitable for mattes (JPEG, H.264 MP4), and formats for high dynamic range and multi-channel data (OpenEXR). Attach one reason to each row.
Answering workplace safety questions with generic 'be careful' statements instead of naming the specific hazard control - e.g. not specifying 20-20-20 breaks and monitor distance for eye strain, correct chair and monitor height for posture, or cable management and equipment earthing for electrical risk.
Safety content feels like common sense, so candidates do not revise it and answer in vague language that misses the markable control measure.
What to do instead
For each hazard category - ergonomic, electrical, fire, e-waste and disposal, data security - write one control measure with a number or a named practice attached (20 minutes, 20 feet, 20 seconds; monitor top at or just below eye level; e-waste to authorised recyclers).
Describing colour concepts loosely - using 'resolution' for bit depth, 'hue' for saturation, or claiming sRGB and Rec.709 are the same thing - when asked about colour space, gamma, or bit depth in digital imaging.
Everyday language blurs these terms, and candidates have adjusted sliders in software without learning the underlying definitions.
What to do instead
Write strict one-sentence definitions for resolution, bit depth, hue, saturation, value, gamut, gamma, and colour space, then state where sRGB, Rec.709, and linear/ACES are used. Test yourself by explaining why an 8-bit gradient bands and a 16-bit one does not.
Ignoring the brief and technical spec in shot-management scenarios, delivering answers that describe a good-looking result but skip frame range, naming convention, handles, and delivery format.
Candidates focus on the artistic outcome and treat administrative details as unimportant, even though exam scenarios test exactly those details.
What to do instead
For any delivery scenario, run a fixed checklist: frame range and handles, resolution and aspect ratio, colour space, file format and bit depth, alpha requirement, naming and version convention, and deadline. Practise applying it to a two-line scenario until it is reflex.
Answering teamwork and ethics questions by describing the technically correct fix only, without addressing communication - e.g. silently redoing a colleague's roto or missing a deadline without informing the supervisor.
Candidates treat soft-skills domains as filler and answer as if every problem were purely technical.
What to do instead
Use a three-part answer pattern for scenario questions: state the professional action, state how and when you communicate it (raise it early, with specifics, to the right person), and state the record you leave (notes, version log, ticket). Apply it to late-delivery, conflicting-feedback, and credit/asset-use scenarios.
Confusing entrepreneurship and employability terms - mixing up a business plan with a quotation, or a portfolio with a showreel - and giving generic career answers with no named role, skill, or next step.
These domains are revised last or skipped, so candidates rely on vague impressions rather than defined terms.
What to do instead
Build a definitions list (business plan, quotation, invoice, break-even, showreel, portfolio, freelance vs studio employment, scope of work) and pair each with a one-line example from a VFX or roto freelance context. For career-pathway questions, always name the role, the core skill it needs, and one realistic progression step.