TL;DR
- Mako spent nearly three years developing Arcane’s music before creating the finale song
- The song’s haunting piano and vocals were present from the earliest demo versions
- Creative challenges included timing issues and structural pacing problems
- Collaboration with Sting exceeded expectations despite initial doubts
- Emotional connections to characters fueled the creative process throughout
Netflix’s acclaimed animated series Arcane, based on the League of Legends universe, received widespread recognition for its exceptional musical score and original compositions. Composer Alex “Mako” Seaver recently provided an intimate look at the development of the ninth episode’s emotionally charged closing track “What Could Have Been,” detailing the extensive creative journey behind its production.
In a comprehensive video shared on his official YouTube platform, Mako deconstructs the intricate and lengthy creative workflow that preceded Arcane’s public debut. The composer reveals that when he started developing preliminary versions for the series’ poignant concluding scenes, he had already been immersed in the Arcane universe and its character development for approximately three years. Seaver explains that after viewing the visual sequences for the dramatic cliffhanger conclusion, the musical composition emerged with surprising natural fluidity.
Seaver describes frequently experiencing emotional reactions when presenting the composition to colleagues, attributing this to the extensive period invested in crafting the entire musical landscape. The composer presents various developmental stages of the track, including the initial complete demonstration of What Could Have Been. The distinctive melancholic piano arrangement paired with subtle vocal elements were identifiable even in this primary iteration of the composition. Subsequently, Mako demonstrates how meticulous refinements progressively enhanced the musical piece’s impact.
Following modifications to an initial verse section, Mako discusses the technical difficulties encountered when the composition approached its emotional climax prematurely. He outlines the audio production team’s methodical approach to realigning with the song’s core artistic intention, alongside the time-sensitive demands to finalize the audio before the complete soundtrack publication. These creative obstacles represent essential components of the artistic development cycle, and he eventually succeeded in producing an exceptional result with What Could Have Been.
Mako additionally addresses the collaborative experience with Sting, who represented Riot Games’ primary selection for featured vocal artist on the What Could Have Been recording. Seaver indicates he never anticipated the iconic musician would consent to participate, but experienced tremendous excitement upon learning he had approved Riot Games’ invitation. This collaboration demonstrates how strategic partnerships in creative projects can yield unexpectedly brilliant outcomes, much like how proper team composition affects overall success in gaming experiences.
Action Checklist
- Analyze visual inspiration sources before composition
- Create multiple song iterations for comparison
- Identify and address structural pacing issues early
- Establish emotional connection points with the material
- Implement strategic collaborations for enhanced outcomes
No reproduction without permission：Games Guides Website » Behind the scenes of the “What Could Have Been” song in Arcane Behind the scenes of Arcane's emotional finale song creation process with composer Mako