Simulacrum | BRAWL 2019 Entry | Brick à Brack

Become a member and enjoy many benefits, it's fast and free!

InformationViewing

Simulacrum | BRAWL 2019 Entry

An image or representation of someone or something.

-----------------------------------------------------------------------------------------------------------

This was a busy week. For my second BRAWL I wanted to get away from the more comedic tone of 'Flight Plan' and create a visual narrative.

I tried out a LOT of new techniques in this, new supports for masking and new lights. I had to cut a minute and a half out of the script, removing some odd visuals including a ferryman and a metronome. Overall, I would say the hardest part was editing together the final film while Premiere Pro continued to crash, recover files, and then crash those recovered files.

As I said, busy week. I hope you enjoy.
-----------------------------------------------------------------------------------------------------------

Credits:

Foley - MrGasMaskMan
Sound Effects- https://www.freesound.org/


-----------------------------------------------------------------------------------------------------------

Check me out on:
Facebook: https://www.facebook.com/FormalLensProductions/
Twitter: https://twitter.com/FormalLens/
Instagram: https://www.instagram.com/FormalLensProductions/

Thanks for reading this far!

Production team
Formal LensProducer, project's creator

Brick à Brack (2)Youtube (9)

I really like the way you animated this. The effects were well done.
For the story I couldn't really see the difference between Step 1 and Step 2. What was duplicated here?

@AoW-GamerI really like the way you animated this. The effects were well done.
For the story I couldn't really see the difference between Step 1 and Step 2. What was duplicated here?


That was more a flaw in production than anything else. In the script, the 1st Step has the Simulacrum's motions lag behind whereas they are synced in Step 2. The shot that was meant to convey this ate up a lot of time during BRAWL but had, I thought, gone well. It was only once I reached editing that I realized the shot was synced, akin to a shot in Step 2. I did not have time to go back and reshoot it thanks to some poor planning on my part as well as Premiere Pro's sudden decision to crash several times over. This is honestly the biggest problem with not shooting on a capture software (Dragonframe for example) as it means that set bumps, continuity errors, and pacing issues are harder to catch before reaching post-production. Normally, I reshoot these. In this case, as I stated, there was a time-crunch. Thanks for asking!

Last edited by Formal Lens (jul. 28, 2019 (09:43pm)).

Sponsors

Support us

Language

Français - English