VCE Vet Music Sound Production common mistakes
VCE Vet Music Sound Production · Understand the traps and how to avoid them.
When asked to identify a workplace hazard in a described scenario (e.g. a stage with unsecured cable runs, a band using an unfamiliar amp, a PA powered from a single overloaded circuit), the candidate names a hazard in general terms such as 'electrical danger' or 'tripping' without stating the specific hazard, who is exposed and how the harm would occur.
Candidates memorise hazard categories from a checklist and then pattern-match the scenario to a heading, rather than reading the details of the scenario and reasoning about the actual source of harm. They also confuse a hazard (the source) with a risk (the likelihood and consequence), so their answer never gets specific.
What to do instead
Practise a fixed three-part sentence for every scenario: 'The hazard is X, it is created by Y, and it could cause Z to person P.' Then add the control using the hierarchy of control in order (eliminate, substitute, engineer, administrate, PPE) and say why that control sits where it does. Drill this on five different scenarios until the structure is automatic.
On signal-flow questions the candidate lists the correct pieces of equipment but gets the order wrong, for example placing the effects unit after the power amplifier, running the DI output into an instrument amp, or putting the compressor before the preamp in a described chain.
Candidates learn equipment as a vocabulary list rather than as a chain, and they have often only seen a signal path on a diagram, not traced it physically. The weak link is usually the boundary between low-level (mic/line) and high-level (speaker) signal, and where gain stages sit relative to processing.
What to do instead
Draw the chain from memory on blank paper every study session, labelling each stage with its nominal level and connector type (mic level XLR, line level TRS/XLR, speaker level speakON/jack). Say out loud what happens to the signal at each stage. Then take a written scenario and annotate it left to right, marking where gain is added and where it is only shaped.
When asked to set gain structure, the candidate describes turning up the channel fader or master to fix a weak or distorted signal without mentioning the input gain or trim, and does not distinguish clipping at the preamp from clipping at the power amplifier.
In hands-on practice, students often mix with faders only and never learn to set the head amplifier first, so their mental model of 'louder' is 'fader up'. They also cannot hear the difference between a clipped input and an overloaded speaker, so the concept stays abstract.
What to do instead
Learn and rehearse a gain-staging routine: set the fader to unity (or its marked position), bring up input gain until the meter sits in the target zone with headroom, then use the fader for balance. Practise deliberately overdriving the input on a quiet source and listening for the change, then correcting it with the input gain, so the cause and effect is learned by ear as well as on paper.
In a maintenance or fault-finding question, the candidate jumps straight to replacing a cable or a piece of gear, or proposes opening equipment, without first following a systematic process: confirm the fault, isolate the section, substitute a known-good item, and check the simplest causes first.
Candidates answer from remembered anecdotes ('it was probably the cable') rather than a method, and they underestimate how often simple causes (muted channel, phantom power off, wrong input selected, flat battery) explain the symptom. Some also do not know the boundary of what a student may legally and safely service.
What to do instead
Use a written fault-finding template: symptom, what still works, what changed recently, then halve the signal path and test each half. Always list the simple checks first. Add a line to every answer stating what must not be attempted (mains wiring, internal repairs) and who should do it. Practise the template on three described faults.
When asked about microphone choice and placement, the candidate gives a single generic answer ('use a condenser close to the source') instead of matching the transducer type, polar pattern and distance to the specific instrument, room and desired result, and does not mention the trade-offs.
Candidates learn microphone types as definitions rather than as tools chosen for a purpose, so they cannot connect the physics (polar pattern, proximity effect, off-axis response) to a musical outcome. They also fear giving a 'wrong' answer and default to the safest generic one.
What to do instead
Build a table of common sources (drum kit pieces, guitar cab, acoustic guitar, voice, piano) with two viable microphone choices each, the pattern and distance, and one advantage and one disadvantage of each. In answers, always state the choice, the placement, and the reason it suits this source and room, plus one alternative.
In recording questions, the candidate describes only the equipment setup and omits the process decisions: how many takes, how the musicians will be monitored, how to manage spill between instruments, how to keep a record of what was recorded, and how the session will be backed up.
Candidates treat recording as a gear question because gear is easy to revise, while session workflow requires imagining a real day in a studio. Backup and documentation in particular are invisible in normal use, so they are forgotten under exam pressure.
What to do instead
For every recording scenario, answer in four blocks: preparation (session plan, input list, headphone mixes), capture (order of recording, isolation and spill control), documentation (track sheet, naming convention, notes on takes), and protection (duplicate copies in two locations, verified before the session ends). Rehearse this on a full-band scenario and a solo-overdub scenario.
When describing a mix, the candidate lists processing moves ('add EQ, add compression, add reverb') without stating the goal, the order of operations or how they would judge whether the move improved the mix, and does not mention reference listening or checking the mix on more than one system.
Candidates learn plug-ins as a list of effects rather than as solutions to problems, and they have often only mixed on one set of speakers or headphones, so the idea of translation between systems is unfamiliar.
What to do instead
Write mix decisions as 'problem, tool, setting, check': what is wrong (muddy low mids, uneven vocal level), which tool addresses it, roughly how it is set, and how the result is verified. Always include monitoring the mix on at least two systems and against a commercial reference at matched loudness, and leave headroom on the master.
In live sound questions, the candidate plans the front-of-house mix and forgets the stage: no monitor mix or foldback plan, no consideration of feedback control from microphone and speaker placement, no line check or soundcheck sequence, and no plan for what happens if something fails mid-show.
Candidates picture the audience experience and the console, not the performers' needs or the physical acoustics of the room. Feedback and mid-show failure are stressful live events that are hard to revise from a book, so they are avoided.
What to do instead
Answer live sound questions with a fixed checklist: room and rig (speaker placement relative to microphones, coverage), stage (monitor sends, what each performer needs to hear), soundcheck (line check order, then individual then full band), show (who has authority, spare cables and DI, mute-all procedure), pack-down. Practise explaining how microphone and speaker placement and gain-before-feedback interact.
On copyright and industry-practice questions, the candidate confuses the different rights and roles: who owns the sound recording versus the composition, what a licence actually permits, what a mechanical or synchronisation licence covers, and what a producer or session musician is entitled to.
The terminology is overlapping and abstract, and candidates revise definitions without applying them to a concrete example, so the distinctions collapse under pressure. There is also a tendency to answer what feels fair rather than what the law and standard practice provide.
What to do instead
Learn through worked examples: take one song, identify the writer, publisher, performer, recording owner and each licence needed for a stated use (streaming, film sync, cover version, live performance). Write the answer as a chain from creation to use. Keep a one-page glossary of roles and rights and test yourself by classifying new scenarios, not by reciting definitions.
In teamwork and planning questions, the candidate gives a vague answer ('communicate well and be organised') without naming a concrete method: a call sheet or running sheet with times and responsibilities, a named decision-maker, a briefing and debrief, and a way to raise and resolve a problem during a session.
Candidates treat these questions as common sense and do not realise they are being assessed on industry-specific professional behaviours. They also lack experience of a real production, so they have no concrete artefact to describe.
What to do instead
Prepare and memorise one realistic production document (call sheet with times, roles, contacts, equipment list, contingencies) and describe how it is used before, during and after a session. For every teamwork answer, name the roles, the communication channel, the escalation path for problems, and how the team reviews the work afterwards.