This is used so that my cast and crew know who is saying what and when, and in which style. It can be practiced by voice actors before recording so as to make the best use of time in session.
The script is also useful for setting the scene and deciphering which other sounds are required. The 'master' script can be used to create a variety of breakdown scripts including an audio breakdown script. This is where a script is marked up to show where sounds need to be accounted for and added to the Sound Assets list. This in turn makes sure the required sounds are actually recorded.
The tools in YouMeScript helped format the following script. I feel the script could be improved slightly by adding in more parentheticals; (information in brackets that helps the voice actor know how to deliver a line.)
The 'master script' is then used to create various mark ups. Simply hi-lighting characters' dialogue and issuing to each actor respectively can help actors decipher and learn the script quickly. An audio mark-up script, or audio breakdown script, is made and issued to the audio department. This version hi-lights each character with a different colour; this helps the crew pack the right combination of microphones. The producer or Sound Supervisor will then gone through the script to mark up any instances where sound needs consideration. Colour-coding helps separate out different sound elements and help to create a definitive Sound Assets List.
In my Audio Mark-Up Script below I have hi-lighted the different actors - I'm thinking I should have used green for Green Lantern! Doh. I have also pointed out where SFX and Foley need to be recorded.
What would improve this is if I had made more of the outdoor environment in setting the scene, in the original script as this breakdown omits the need for outdoor ambience. I also don't feel that enough has been made of the cavernous metallic properties of Superman's Bunker. In this instance I will deal with it in post-production, artificially creating the reverb required; but I should have given the opportunity fir the sound department to take thus into consideration when choosing ocations for recording.
From the audio breakdown script (To be posted) I was able to create a Sound Assets list. This list is a definitive checklist to make sure everything is recorded. It works much better alongside the audio breakdown script though as not all the sounds in the list may be captured during the same session.
I also created an equipment List. As daft as it sounds; without a comprehensive equipment list there is always the danger that something is left behind for a session; something that stops the session working effectively. Of course the list is only as useful as the person who checks it thoroughly.
It is worth noting as I have made the effort to include spares. You never know when an SD card or set of batteries might fail. Backup power, digital storage and cabling is always a good idea.
Professional movie productions, including the audio is never left to chance. Having an idea about when things might happen, in your head, does not ensure that everyone knows what they are doing and when. Even with smaller projects like this one where the crew may just be you; or perhaps one other person, leaving the process to chance is almost guaranteed to fail; or be less than it could have been.
There are 8 weeks from this assignment being set to it all being 'handed in' on 8th March; with an extra week for half term.
In order to allow enough time to learn, plan and deliver what I need, taking into consideration possible set backs like adverse weather, I have come up with the following schedule. I have decided to do mine day by day so that I can see what availability I have each day for other work and activities. As you will see from the colour key; for the days marked in blue I am expecting to be putting a full days work in; whereas the 'orange days' will leave me significant time to do other work and activities.
You will see that the plan is thorough, covers all the processes and allows me time at the end to check everything.
This schedule should be shared with the full production team along with all the documentation created so far, Pre-Visualisation docs (which you will learn about via Mathew and Kayleigh) and Location Recces/Permissions, so everyone knows where they need to be and when. For more complex projects it would be worth adding in which departments and personnel need to be present for each activity on the schedule.
I discovered through research what can go wrong if Heath and Safety is not sufficiently addressed for a filming or recording activity. Even for small exercises like going out into the carpark to record outdoor ambience comes with it's hazards that presents risk, however unlikely. A Risk Assessment helps to manage any potential hazard and risk of harm.
As discovered in the documentary on Mignight Rider; a Risk Assessment needs to be thorough, realistic and seen by everybody involved. The documentary suggested that in the case of a particular scene being shot for Midnight Rider; cast and crew were filming on a railway; on a tressle bridge with limited escape routes; with no knowledge of train times; no permission to be there and guessing at 60 seconds to escape should a train show up. Such poor Risk Assessment ended up with the death of one of the crew and serious injury of another.
No matter how simple a shoot or recording session may a to be; if it involves other people or could impact on members of the public, it must be Risk Assessed.
My Risk Assessment for recording on location, the sounds of Batman approaching the bunker is below. The session should only take 15 to 20 mins if planned well; but I have considered people, vehicles, equipment, trips and falls, infectious diseases, exposure and ear fatigue. I can't think of anything else, but if I do; I will add to this.
All the hazards identified already have 'controls' in place; such as 5mph speed limit; this does not mean that everyone adheres to these controls. This should also be considered in a Risk Assessment.
Everyone in your cast and crew should have sight of the Risk Assessment; they deserve to know that their safety has been fully considered.
One last point is that the temptaion to include non-risk related items on a Risk Assessment is high! Risk Assessments are not the place to worry about damage or loss of stuff, equipment, property etc. The RA is for Health & Safety or people only.
Finally; a location recce is required before recording for a number of reasons:
Audio Crew and personnel will know where to be
To share access arrangements and facilities such as place for parking etc
to demonstrate you have permission to be there and offer contact details
For personnel to know why they are there; what to look for and what job to do when they get there.
My location recce is for Mynydd Dinas; the landmark mountain that rises above Baglan in Port Talbot. Without a Location Recce no one will know where on this mountain we are recording (it covers a rather large area!) or indeed which access point we are using. Personnel may well find themselves heading to or parking at locations miles apart.
In my Location Recce I have used a digital map reference, but this can only be used if this document is being accessed digitally; so I have provided nearest address, parking options, a map and directions. I have pointed out what we are looking to record there and how to be prepared for working on a mountain side. (This will need expanding upon in another Risk Assessment)
This area is governed by Neath Port Talbot Council and I have added where I sought permission from. This area remote, so you would probably get away with recording without permissions, but it is always wise to seek official permission to be there. There is now a whole site dedicated to supporting film makers in Port Talbot Town area; this is certainly a recent additions and looks like it has lots of potential to be very supportive.
Website: https://beta.npt.gov.uk/leisure-parks-and-culture/our-town-centres/filming-in-npt/
(Photo: Path on Mynydd Dinas by Gareth James, CC BY-SA 2.0 <https://creativecommons.org/licenses/by-sa/2.0>, via Wikimedia Commons)