Well, it was quite an eventful morning for me today. I woke up to having Hayden make his version of the sequence and having us review it and we find that it is not exactly the best with many pacing errors and just a clunky feel to it overall. So we were considering scrapping everything, getting a new actor, and reshooting it. However, I still had to do my version of the sequence and from there we would see what path to take going forward. So, picked off right where I left off yesterday, with all the clips in a folder labeled to what they are supposed to be, and I am going to order them into the initial sequence and get my group's feedback.
First Sequence Done
So, after about 30 minutes I was able to make a coherent version of the event for the opening sequence. I had to cut a lot of clips short, slow some down to fit the pacing, and I had to mesh some clips together to give them a flow of movement, especially for the chase scene. Overall, after doing the initial edit I was proud of how it turned out. It seemed like something we could work with going forward and maybe this would be enough to not scrap everything.
Finished the sequence with all the clips. I will be adding effects to them later, and Hayden will be doing the color correction later as well. The audio also still needs to be done, most of the audio we originally recorded will likely be cut and replaced with foley, vo, and copyright-free sound effects.
Error
Although I was able to get this done I then had to render the sequence in to out to ensure all the clips were properly inputted and flowed properly. When I went to do this I faced an error though.
This was the error I was faced with. I had never seen this before and I had no idea how to fix it. However, I did remember that I faced another error when I was opening up Premiere.
This was the error that I had when I was opening up Premiere and I thought that this may be the reason that I was facing the issue while trying to render the sequence.
To solve the issue I decided that it might work if I updated the drivers on my PC because that is what the error when opening Premiere told me was wrong.
With the drivers now installed I went to check if the error was still occurring.
Premiere opened up properly this time without a pop-up error so things were looking up.
However, when I went to render the sequence against the error still was popping up. I then took it to the place with all the answers (Google) to see if someone had the same error I was having and if they knew how to fix it.
I found this amazing Youtube video that was able to help me fix it.
With the solution, he gave I was able to render my sequence finally, so shoutout to him, I would not be able to proceed without his solution.
Group Feedback
With that out of the way there was only 1 thing left to do: show my group what I had done and talk about whether or not we should scrap everything. To do this we got onto calls on discord and screen shared in order to show the video easily without having to deal with the hassle of sending it. I first called Hayden and he said what I did looked great and I salvaged what he thought was a lost cause. He said after I showed Miguel then I should give him the file so he could do the color correction for the video. Next, I showed it to Miguela and he also said that what I did worked and looked great so we will not be reshooting everything and we will be going forward with my version.
Conclusion
Despite the downs that today had we were able to stay on track for this week and we will hopefully go on to finish this component in a great way that shows off our technique and ourselves. I have sent the files to Hayden to color correct it and when I get back the footage I will add some effects to it as the final touches along with some sound effects. So, stay tuned for that!
No comments:
Post a Comment