The first of two articles about our first steps in producing truly object-based visual media.
Jasmine's Kitchen in the edit - Testing methods for creating objects
To help us understand potential experiences we could create using object-based methods, we ran a guerilla-style experiment. We planned and filmed a very rough cooking show (with an entirely unqualified chef at the helm!) where we captured objects for a lasagne recipe.
We were then able to rearrange these objects into step-based instructions for cooking other things, such as a spaghetti bolognese, bechamel sauce, and also for knife skills. This quick experiment informed our approaches to planning the steps and shooting schedule for capturing objects in the cook-along kitchen.
The most critical component of the project, and the driver for the whole process, is of course the data - remember, when dealing with object-based media, everything is data. As this is the first time weβve covered production right through to output, this consideration is even more important.
Taking this into account, we designed our production so that a single consistent source of information about all of the elements within it runs through the whole thing. From pulling apart the first recipe and scripting, to planning the shoot and powering how the user experiences the programme, this model of all the data in the production is at the core of all our work.
Itβs worth noting that βdata modelβ doesnβt necessarily mean code, or even digital data. Initially our data model was a large whiteboard covered in cards and coloured lines (shown below), which then became a spreadsheet, which we then enhanced with more information, which then became code, and so on. At each stage the data will become more complex, richer - even when itβs being used to control the finished piece of work, the data will constantly be in flux as it learns and adapts to an audience member's needs.
Bella's Chocolate & Orange Pots - Original recipe
The first step was of course to create our data starting point - the recipe structure itself. We worked closely with our chef and presenter, Bella Wright, to create a series of delicious complimentary recipes: a red mullet main course, a cannellini bean mash, a kale side dish, and a chocolate pot dessert. These recipes were chosen as they allowed us a high degree of flexibility in terms of preparation types and ingredient swaps, and of course they work together as a whole meal or as stand alone dishes.
The next phase was to take Bellaβs linear suggested recipes, and really pull them apart into a data representation. This was surprisingly challenging, and required a really deep analysis of exactly what the makeup of a cooking process really looks like. The recipe was broken up into logical sub-sections, any one of which could function on its own or as part of a wider recipe - for example, the fish de-scaling and preparation was planned and scripted so it could be used as a guide on its own, or within a larger recipe flow. Timings and the way that each of the separate elements in the production depended/linked/referred to each other become extremely important too: our fish dish was prepared in three different ways, which took three different lengths of time, meaning the rest of the recipe objects had to be reconfigured depending on which one was being used.
CAKE whiteboard map with possible combinations of recipes
The first pass at this representation took the form of a logical map. This visual representation was then adapted into a more formalised script model - retaining the categorisations, links and organisational conventions, but presented as a traditional script. This was the first real data based representation of the audio and video we needed to shoot, and was then directly used to plan, organise and carry out the shoot on the day of production. This was laid out in a spreadsheet, not code - itβs better to think of the model as a representation of all of the media elements in the production, and a way of conceptualising it, and not as a computer program or similar. The decision to work like this meant that we were able to annotate and enhance the script itself as the shoot was carried out: adding notes, changes, points of interest and various other things to the data model as it was being used in the real world. Following the shoot, the exact same data model was used while editing the footage - allowing us to map footage precisely onto the model, establishing a link between footage and data.
in our production studio, and explain where weβre heading next.
- Our new blog about our first steps in true object-based production - CAKE: the Cook-Along Kitchen Experience β ΒιΆΉΤΌΕΔ R&D (@ΒιΆΉΤΌΕΔRD)