Sei sulla pagina 1di 3

The LOGIC PRO X User Guide

Since the last User Guide update you have now used Logic for a
number of different projects. Previously you had recorded a
podcast and made some tunes for a short movie clip. Now you
have used microphones for a number of different applications.
You have mixed different instruments. You have worked with
clients. You have considered sound effects for the radio
play and have composed music specifically for this.

The User Guide must allow the reader to know what you know
your skills in this area. You will have used EQ more often.
You may have imported samples or other tracks and edited these
to fit your project. You will have experimented with the vast
library of sounds on offer, and will no doubt have used many
more tools to help you shape or fix the dynamics of the track.

On top of this, the guide should allow you to reflect on the


process. Self-reflection and analysis are important to gain
the highest grades.

So the guide should include:

Context what were your projects and why do you think they
were important?

Research what theoretical or practical knowledge have you


personally sought after to help you with the tasks?

Problem solving give examples of how youve solved


problems (see notes below)

Planning and Production what might be a typical session


plan, and why is this essential to the production? (see notes
below)

Practical skills what can you do now that you couldnt do


before the process? What are your strengths? What do you think
you can improve?

The highest grades are available only to those who can show a
professional and perceptive critique, and where presentation
is clear and shows a confidence in your understanding.
Session Plan

What might be a typical session plan for a recording session,


particularly one with a client (musician)?

- Getting ready for a session: equipment required (block


diagram?); checking what works; knowing the instruments you
may be recording; setting up the software (number of
tracks/labelling tracks); importing/loading previous
recording; microphone type/pop - shield.

- Getting the musician ready for recording: tuning the


instrument; microphone stand positioning (can they
comfortably play/sing); levels for the musician in
headphones; input levels (is the sound too loud/too
quiet?); ensuring no background sounds; set the correct
BPM; have practice runs.
- Recording: making sure the audio does not peak; dont press
stop too early; record back up versions/double tracking.

- Listening back: does it sound OK; any musical/sonic


problems; any over-dubs required.
- Mixing: fixing any problems fade outs, adding noise gate,
EQ; panning; adding effects; getting correct levels;
labelling/colouring audio files.

- Saving and bouncing: all files labelled and saved


appropriately; final master level correct; bounced in
correct format; back up on external drive/USB.
- Power down: returning the room so ready for next session;
returning equipment; cable tidying.
Problem Solving

What problems might arise, and what can we do/use to solve


them?

Problems may involve:

Finding the correct software instrument/sonics; the tempo or


BPM of a track; signal levels; background sounds or unwanted
clicks; distortion; equipment not working (speakers/cables
etc); feedback; no sound from microphone or headphones;
sibilance or low frequency rumble on an audio track; missing
audio files on a Logic arrange page; confusing multitude of
audio tracks; muddy sounding instruments; sound levels too
low/high.

These may help you solve problems:

EQ (Low cut filter/ shelving EQ/ Bell EQ /Q Factor);


colouring/labelling audio files; saving a project with audio
files ticked; using the BPM counter; panning to separate
instruments in the mix; checking equipment works before use;
tuning up of instruments; finding the correct key for
performers; using the correct microphone (position); adjusting
the gain and checking input levels.

THESE NOTES ARE GUIDELINES THAT COULD HELP


YOU COMPLETE THE USER GUIDE.

REMEMBER:

USE THE HEADER/FOOTER TO PUT YOUR NAME


AND A TITLE FOR THIS WORK (E.G. LOGIC USER
GUIDE).

NUMBER THE PAGES.

Potrebbero piacerti anche