Navigating the technosphere with Ø [Phase]: a pre-Movement discussion

An enigmatic persona exists deep within the techno rabbit hole. Using the moniker Ø [Phase] (né Ashley Burchett), the stalwart DJ and producer has made his mark on things dark, atmospheric, and downright technical. His productions are as hypnotic and diverse as his sets, covering a mélange of stylings that range from subdued and almost tribal, to acidic, to deep, to sinister and driving. He refuses to be boxed into any one category, which is why he’s remained firmly at the cutting edge of his arena.

Ashley’s expertise has been cultivated over quite an extended period of time; over two decades, to be exact. As a mastering professional and a budding musician inspired by the new, innovative sounds imported from Detroit, he soon found his way onto Steve Bicknell’s Cosmic Records imprint before moving onto his primary home label of Token. Techno, with its wide range and malleable structure, was particularly appealing to his sound engineer’s ear, and he has certainly taken this notion in stride with his production MO.

The word “techno” stretches beyond a mere genre, however. It’s built to be paired with the right setting, atmosphere, and mindset. Nuances within it demand appreciating subtle musical details, and an environment that allows for full focus on these aspects.

Who better to dive into the nitty gritty of techno than Ø [Phase]? Given his imminent arrival to Los Angeles, and later, to Detroit’s iconic Movement Festival (where he will be making his debut), we nabbed him for a chat on the sound and the scene. Additionally, Ashley shares his excitement for Movement, and offers a little taste of what to expect from his set at the Underground stage.


How do you think your career would develop/be if you started out today rather than two decades ago? Do you agree with ...

Continue Reading at https://dancingastronaut.com


Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 53 bytes) in /home/content/93/6869993/html/wp-includes/wp-db.php on line 1906