Reflection of both of the works.
Reflection on Team Project
Our team of five collaborated to deliver this project, and I was primarily responsible for post-production compositing. Looking back, I can identify both valuable outcomes and some shortcomings, particularly around project planning and workflow management.
The most significant challenge was time management. We had originally intended to begin production in late April, but in reality the location shoot and early preparatory work were delayed until early June. Although we visited White Cliffs of Dover (East Dean) and carried out on-site filming with both drones and cameras, only a small portion of this footage proved useful in the final edit. In hindsight, this raised the question of how to balance ambition with efficiency. From a pragmatic standpoint, I believe we devoted excessive time to a module that counts for only one-third of forty credits. My personal aim had been to keep the production cycle within two months, which would have allowed us to allocate more energy to other academic or professional commitments.
Technically, the project required careful coordination across multiple software environments. Character modelling, scene design, and animation were all completed in Blender. Houdini was used to simulate the ocean waves and pollution particles, while Nuke was employed for most camera tracking. The remainder of the compositing was executed in After Effects. This cross-platform workflow gave me first-hand experience of how different tools can complement one another, but it also exposed the risk of inefficiency when stylistic decisions are repeatedly revised. The composite underwent several major re-designs during production, which I believe slowed progress more than any other factor. Nonetheless, I was satisfied that the final cut achieved a coherent rhythm and maintained consistent colour grading, suggesting that the additional iterations did improve quality.
One of the most important lessons I drew from this project is the necessity of clear role allocation at the outset. In a group of five, individual contributions will inevitably vary, but disputes and wasted effort can be reduced if each member’s scope of work is agreed upon in advance. This would not only minimise internal conflict but also give everyone a stronger sense of accountability.
From a technical perspective, I also came to appreciate once again the value of EXR render passes in large-scale projects. They enable highly granular compositing, allowing adjustments to be made to individual layers without resorting to crude masks or extensive manual rotoscoping. This reinforced my understanding that robust data management and pipeline discipline are just as critical as creative vision in post-production.
In conclusion, the team project was both demanding and rewarding. While we struggled with delays and occasional inefficiencies, the experience provided me with deeper insight into collaborative workflows, the interplay of different software platforms, and the importance of structured planning. If I were to undertake a similar project in the future, I would prioritise clearer initial planning, more disciplined iteration, and a stronger emphasis on technical pipeline management. These changes would not only improve efficiency but also enhance the creative outcome of the collaboration.
Leave a Reply