[googlemaps https://maps.google.com/maps/embed?pb=!1m18!1m12!1m3!1d4860.36791338718!2d-1.8889401000000292!3d52.47580490000002!2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x4870bc8710d1493f%3A0x3da1221bedd65553!2sDigbeth!5e0!3m2!1sen!2suk!4v1396458788364&w=400&h=450]
A big part of running the maths in our workflow is working out where different filming locations are on the map and where the editors are situated. We have to work out a data ‘flight path’, calculating where the footage is going to be shot and then ferried to the post department, via cloning for insurance, synchronised with the different filming teams so that there aren’t bottlenecks. One area where we’ve failed consistently with the previous projects is the even flow of data into the edit. This time around, we are trying to make it a priority.
Similarly, in the previous 72 projects we had jaunts out to Melbourne and Galway airports on the outskirts of town. We won’t be making a trip out of the city centre for this movie apart from one sequence in a park, which will have to be out of the immediate city centre. This cuts out the need for a huge ‘movement order’, like bussing the entire crew to another part of town in a specialist bus.
These ‘flight paths’ for data and ‘movement orders’ for cast and crew are the most critical part of the 72, and in previous years we’ve simply estimated the times between locations and edits and worked around whatever came our way. This time we must use the home advantage. We must study this map and work out the rat-runs and short cuts. The hope is that the familiarity of these streets will enable us to make the best 72 yet.
James and the 72 team.
