WATCH BOX OFFICE MOVIES FOR FREE
We May Know Why Colin Trevorrow Was Fired From Star Wars: Episode IX
The Star Wars franchise is back up and running, and its showing no signs of slowing anytime soon. With Disney now in charge of the property, fans have been treated to a new addition to the beloved galaxy every year. While movies like The Last Jedi and Rogue One have been critical and financial successes, there has been some behind the scenes drama in the next two installments. Both Solo and Episode IX have lost their original directors, after apparent conflict with Lucasfilm. Jurassic World director Colin Trevorrow was original set to helm Episode IX, before being replaced by J.J. Abrams. And now we haven an idea why.
Ahead of the release of Solo, some more information is coming out about the inner workings of the Star Wars franchise. The most recent report indicates that Colin Trevorrow was let go from Episode IX after producing an unsatisfactory script. This apparently was met with the ire of Lucasfilm president Kathleen Kennedy, who ended the working relationship.
This latest report, which comes to us from The Wall Street Journal, seems to echo some of the conversation revolving around the Star Wars franchise. Because Kathleen Kennedy is running the show over at Lucasfilm, she's got a fair amount of say and power over each new blockbuster. And if directors aren't bringing what they need to, the company is happy to respectfully part ways with their collaborators. I guess that's show business.
While not confirmed by either party, this story seems to echo what happened on the set of Solo: A Star Wars Story. Directors Chris Miller and Phil Lord were famously fired halfway through filming, before Ron Howard stepped in to finish the project. Kathleen Kennedy has maintained that decision was because of how the film was (or wasn't) progressing during production, although she's had nothing but kind words to say about the directors. Colin Trevorrow's departure from Episode IX was luckily a bit earlier in development, allowing J.J Abarams to maintain full ownership over the upcoming threequel.
Because the Star Wars franchise is on such a hot streak right now, the pressure is on for everyone involved in the property to continue producing financial and critical successes. But Solo and Episode IX mark the first time that a director change has happened during a Star Wars project. As such, fans and critics are going to be watching each frame with a magnifying glass.
Up first is Solo: A Star Wars Story, which is set to arrive in just a few weeks time. The standalone movie also had the added pressure of recasting classic characters like Han Solo and Lando Clarissian. And considering Han's fate in The Force Awakens, there will be an extra emotional layer to watching his origin.
Solo: A Star Wars Story will arrive in theaters on May 25th, 2018, and Episode IX will hit May December 20, 2019. In the meantime, check out our 2018 release list to plan your next trip to the movies.
The Star Wars world was left shaken last year when it was announced that director Colin Trevorrow had been fired from Episode IX.That catch-all term of "creative differences" was wheeled out
Here's Why Colin Trevorrow Was Fired from Star Wars 9
Colin Trevorrow's Star Wars 9 will go down as one of the great unknowns of the Star Wars saga. Trevorrow was brought in as director of the film back in August 2015, with the aim of bringing the sequel trilogy to a triumphant close. However, his time with Lucasfilm came to an abrupt end in September 2017, after two years on the project.
Colin Trevorrow 'Episode IX' Departure Is Bad News For Disney
A new article in the Wall Street Journal details the reason behind the firing of Colin Trevorrow from Star Wars: Episode IX. The article goes into the script issues that were happening between
Rumour: Colin Trevorrow fired from Star Wars: Episode IX due
Star Wars 9: Why Colin Trevorrow Was Fired | Collider
collider.com/star-wars-9-why-colin-trevorrow-was-fired/
A new report sheds light on why 'Jurassic World' filmmaker Colin Trevorrow was fired from writing and directing 'Star Wars 9', confirming that Rian Johnson was approached to take over.
Why was Colin Trevorrow Fired from Star Wars? - vulture.com
Turns out, certain white male directors can fail upwards for only so long, and what we have been discovering of late is that the ceiling for directors who lack the requisite talent is apparently Star Wars movies. It's not always that lack of talent catches up to directors; sometimes, simply being an asshole can get you fired.
Colin Trevorrow Fired From Star Wars: Episode IX Because He
Colin Trevorrow was original set to helm Episode IX, before being replaced by J.J. Abrams. And now we haven an idea why. Subscribe To We May Know Why Colin Trevorrow Was Fired From Star Wars
Star Wars 9: Insiders reveal why Colin Treverrow was fired
Sep 05, 2017 · Colin Trevorrow 'Episode IX' Departure Is Bad News For Disney's 'Star Wars' We wish Colin the best and will be sharing more information about the film soon." I don't know why Trevorrow
Rumour: Colin Trevorrow fired from Star Wars: Episode IX due to disagreements over The Last Jedi. You and I both know Luke will be around in Episode IX, and remaining a mentor to Rey and
Star Wars 9: Details On Colin Trevorrow's Canceled Version
That is to say, since the Tuesday announcement of Colin Trevorrow's firing as director of Star Wars: Episode IX (with Lucasfilm reaching the conclusion that his and the company's "visions
We May Know Why Colin Trevorrow Was Fired From Star Wars
With Colin Trevorrow's departure from Star Wars: Episode IX, every Hollywood commentator was working overtime to try and unearth the reasons why.
Now We Know Why Colin Trevorrow Was Fired From 'Star Wars
0 comments:
Post a Comment