Posts Tagged ‘nelson nunez’
Introducing the newly revamped NelsonNunez.com!
Monday, September 26th, 2011Welcome to my new website!
This is the result of over four months of hard thought, research, and work. I met with Methanie of Methanie Design and after a couple meetings, we were able to narrow down the goals of my website:
1. to showcase my video work in a clean and polished way
2. to make navigation simple, fast and intuitive
3. to have each video section stand on it’s own so users have all the info they need on one page, but can easily access more info and see more videos if desired
4. to make it easy to contact me and locate me on social networks
5. to have a Content Management System (CMS) that would allow me to easily update my site with new content
This site has been a long time coming, as ideas for it really began from the original launch of my site several years ago. I’m happy to have a site that tackles all of the goals listed above, and in style!
Please feel free to browse through each of my pages as you’ll see some new content as well. I hope you enjoy the site as I enjoyed being a part of creating it. Much props to Methanie for the cool design, hand-coding, and patience! Also, thank you to my colleagues at BAPVA who helped immensely not only in my transition to the DSLR workflow but also by generously sharing their knowledge and experience to help me structure the business properly.
Part of my goal in re-launching the site is to commit myself to creating new content on a regular basis. So in the coming weeks and beyond, I’ll be posting new videos and blogs… including my latest wedding concept video. Stay tuned… this one’s gonna be BIG!
Project Arbiter – New Trailer Released!
Friday, July 22nd, 2011Great news about the progress of the short film I edited, Project Arbiter: the new trailer to this concept film has just been uploaded!
Mike has been keeping the crew updated on the progress of the film after the edit was locked. It’s exciting to finally see the visual effects, score, and color grading come into play. I knew it was going to look good, but I’m still blown away by the production value that is coming to life.
Mike did an awesome job cutting this one together. Also, hats off to Jesse, VFX supervisor.
Click play; you won’t regret it. It’s ALIIIIIVE!!!
Project Arbiter – the EDIT.
Saturday, August 28th, 2010Project Arbiter was the most ambitious editing project I’ve had the pleasure to tackle. I wrote about my experience being an on-set editor (including the joy of dealing with RED RAW!) in a previous post you can read here.
When principle photography was wrapped, I was excited to get my hands on the rest of the footage. I knew this was going to be a massive undertaking; the footage alone takes up almost 3TB of hard drive space!
Before production even began, Mike and I discussed what he was looking for in the edit. He’s had a lot of editing experience himself (which he loves to remind me about!), so it was nice to be able to communicate clearly what he had in mind. What he mainly emphasized is that he wanted the viewer to experience a “roller-coaster” of emotions… referring to the pacing of films like “The Dark Knight” and “No Country For Old Men”, in which story and characters build up slowly to engage viewers and then take them down an unexpected plunge, only to stabilize and then grip them again with a new twist! He really envisioned strength of character development balanced out with carnage and mayhem that the Arbiter brings.
I appreciated this approach because it’s way too easy to be caught up in the wow-factor of the concept and eye-candy of visual effects, especially with how gorgeous the footage already looks! Casting and performances were also on point, which gave me several options to carefully construct the backbone of the film: the story. Now as the editor, I take pride in knowing that how I piece together the film is absolutely critical to the success of that, so I took this role on very seriously.
Organizing the Onslaught:
I spent the first week simply reviewing and logging all of the footage available. If there’s anything I’ve learned in all my years editing is that the more organized you are now, the less headache there is later. I meticulously screened through every clip and created columns for all kinds of info to help organize myself.
Since we were expecting a 20-25 minute film, I also decided to split up the edit into several sequences. It allowed me to focus on the emotion of a scene or two without getting overwhelmed with others.
Cutting begins:
Now that I had all of the clips neatly organized in front of me, it was time to get cuttin’!
From the beginning, Mike pushed for a very aggressive schedule to get through post (full rough cut in just a few weeks!). He just wanted to make sure we didn’t get stuck in “post-hell.” So did I! I’ve heard about this place and it’s where many indie flicks go to die. It’s an often under-estimated part of the process and without proper preparation and continuing momentum, it would just become a statistic. Although it meant I had to put other projects on hold, I knew it was a smart move because it also allowed me to give 100% of my focus to the film.
The first scene I tackled was an intense confrontation between two characters, Heinrich and Reiner. I can’t get into too much detail about the choices I made in the edit, but I found that even when playing with a relatively simple dialogue scene, cutting can be really fun because timing is so crucial to establish pivotal emotional moments. I showed Mike a quick rough cut of the scene, and he was pretty happy with the direction it was going in.
But what’s Project Arbiter without the battle sequence? This was the part of the film that demanded complete focus and attention because so many things were going on. It’s a hectic and complex part of the film that involved parallel editing, and trying to make the pieces fit seamlessly was a tough puppy. Order of shots, continuity, timing, and knowing when to cut back and forth between sequences in the story all had to be taken into account. Also, because of the magnitude of VFX shots that were going to be in the completed film, I only had footage plates available in which CGI elements were to be placed in, which forced me to imagine the timing and movement of all of the tank and plane shots. Eventually I created placeholder shots with text like, “TANK!” and “EXPLOSION!” which helps when viewing the cut.
I continued forward and hammered out scene after scene. Within a few weeks, I was able to screen for Mike (Writer/Director), Vicki (Producer), and Jesse (VFX) a full rough cut of the film. We editors love to emphasize “rough” because it’s all too easy for people to be overly critical about it (and of course for us to become overly defensive)! But this was understood all-around that I had yet to really get my hands dirty. Still, they were able to offer overall thoughts and suggestions about what to keep in mind when I go back in to fine-tune it.
The next several weeks after that was a series of screenings, revisions and fine-tuning. I’m pretty stoked for the fine cut I handed over to Mike. I knew I had successfully fine-tuned the cut to his liking, judging by his reactions to the movie, the story, the actors, and not the edit itself. One of the comments he made while watching the latest cut: “Now we’ve got a MOVIE!”
From there, we tag-teamed on the final cut by splitting up the sequences and trading project files back and forth. We also brought in a few more crew members to view the edit and offer more feedback. It’s always interesting to observe how fresh eyes react to the film; they often spot things that are hard to catch because we are so familiar with the footage.
Online Conferencing:
One of the cool new features of Final Cut Pro 7 that we took full advantage of is iChat theater. This allows people to have a live view of what’s playing in the project timeline via iChat. Though it doesn’t play at full-res (understandably), it was still a great way to conference online while watching the edit together since we live 90 minutes away… And at the end of a long work day in full San Francisco traffic, it was helpful to my energy for discussion. It also allowed me to make revisions to an edit in real-time and show Mike the result within seconds. This allowed a very efficient flow of experimenting with ideas for cuts!
Reflection in the Director/Editor relationship:
I learned a lot about the director/editor relationship in this project. As editor, I know it’s my job to fully realize the director’s vision, but at the same time, I found it important to be able to construct the story in the best possible way, even if that meant offering alternate ways of cutting a scene that he didn’t expect. I mentioned earlier about Mike’s background in editing and how it helped our communication. Of course we’d butt heads sometimes, but it was all part of the process. Some things he liked and some things he didn’t. Because of his familiarity with the craft, it forced me to work harder in thinking of new ways to structure sequences that I could present to him. Some of the most rewarding moments came when he said, “that’s interesting you decided to cut it that way – it totally works!”
Now that picture is locked and VFX has officially started, I can rest knowing the film is in good hands. The potential for this film is limitless. I must say, it’s already impressive as a cut and I can only imagine how much more of an impact this will make when all color grading, visual effects, sound design and score fully kick in! I’m proud to have been an integral part of this team that is bringing Mike’s baby to life. ENGAGE!!!
Learn more behind-the-scenes from the talented crew and stay updated on the latest happenings on the official Project Arbiter blog!
48 HFP 2010 – Lessons Learned
Tuesday, August 24th, 2010I started writing this the very night I arrived home from San Jose after successfully completing and turning in our film.
I was still high on the adrenaline of the weekend and wanted to make sure I wrote down everything I learned… as well as ways to improve the next time around. It’s a bit more technical than my usual blogs, but if anybody out there can take something from this, or share their own advice, it’s all worth it!
what worked?
- NETWORK DRIVE. allowed for easy sharing of files back and forth between sound, vfx, and editing departments. definitely a setup keeper. though sometimes had to unplug to get internet. not enough inputs.
- MULTIPLE COMPS FOR TRANSCODING. transcoding was usually done on two computers, mine and ben’s. ben setup file sharing, so that he could basically copy the original files to his computer, transcode them over to mine, and then copy the original files back to my computer. seemed to work pretty well.
- MERGE CLIPS FOR SYNCING. syncing by hand is the best way so you can ensure you’ve got through all of the clips. one headache is sometimes there would be “second sticks”… in which there was a problem with the first clap (either not loud enough, or not on camera, or both cameras weren’t rolling, etc.) so then i would get mixed up on where to set my marker and in point.
- EARLY START ON SOUND DESIGN. Sound design worked well. i exported an early cut for mike so he can start placing sfx and ambiance. then by the time i was waiting for the new footage, he brought over his fcp file with all the sound effects and opened it on my computer, copied from his sequence to my new one, and then shifted sound clips as needed.
what didnt? and suggestions for next time
- EXPORT. the biggest headache was exporting the movie. website wants SD, but Vincent was willing to accept HD, but only in H264! we edited in ProRes LT. of course, exporting the native editing format is the fastest method to export. but transcoding to H264 would’ve taken way too long. with the minutes ticking away, Ben brought up the idea of exporting to miniDV! but it had to be done a certain way. basically, the sequence settings had to be changed to a certain NTSC DV format, then printed to tape. i’m not sure if the original sequence had to be changed, or if a new sequence was created and then elements were copied and pasted. question: when Print to Video renders the timeline… will it take the same amount of time as rendering the timeline first before printing to tape?
- QMASTER. Qmaster sets up a sort of render farm that if we figured out how to make it work, would’ve been super beneficial. the transcode time for one minute of ProRes LT to H264 clocked in at almost 6 minutes. for an 8 minute film, that’s about 48 minutes. give it one hour to be sure. i wonder how fast it wouldve worked if QMASTER was up (basically splits up the render work between multiple computers).
- ASSISTANT EDITOR FOR LOGGING. i really, REALLY could’ve used some help in logging. this took up wayyy too much time on my end. i definitely want an assistant to do this. or figure out a way for multiple people to log in the info and circled takes, especially once i have enough footage around to start playing with, i just want to focus on that while assistants and log, transfer, transcode, and sync for me!
- ASSISTANT EDITOR FOR AUDIO SYNCING. didn’t have any time at all to drop in the real audio at the end. i ended up cleaning the audio (some audio was just panned to one side, so i had to duplicate, then pan over to the other side). maybe an assistant can handle this. i wonder if someone on another computer can just sync the audio, and fix it INSIDE a merged clip. then i would just open up the project file, drag those merged clips, all ready to go, into my project bin, and be good. that would be DOPE.
- NOTE ABOUT SYNCING. you can see if a merged clip is out of sync by the weird half-marker line in the timeline of the viewer (the small triangles connected with a redline). but generally that’s how i did it, is go through each sound clip, listen for the take, label the clip, then go in and set marker, and in point. go through all the audio files and do this. then go through all the video clips, and set marker and In point for the clapper (judged by the audio, not the video, as Ben suggested. because video clips usually off from the audio. i.e. clapper sound happens before it closes. seemed to work okay, sometimes might still be a tad off.)
- AFTER EFFECTS EXPORTS. having to transcode the vfx exports took unnecessary amount of time. because AE doesn’t have ProRes codec, they either exported as animation or .PNG (huge files) and then transcoded using mpeg streamclip.
- PLURALEYES NO GOOD FOR 48HFP. PluralEyes was a huge headache. not only did some clips not get synced, some clips were incorrectly synced. it also would take upwards of 20 to 25 minutes for it to process it. because it puts all the unsynced clips in a sequence, it makes it a nightmare to organize. plus, the way people work with these syncs, is they cut and paste from the pluraleyes synced sequences. very impractical. the other method is to use these sequences as clips. but then you’d have an entire sequence of nested sequences. which at first thought sounds like it could be a nightmare in terms of cleaning up, but i haven’t looked into this yet. still, the fact that it incorrectly syncs clips is not worth it.
- EXPORT – have project files on another computer, also exporting a different version of the cut as a backup. this goes along with the idea that we wanted to have a shared drive from which all of the original footage can be accessed from. but concern was speed, especially if multiple computers are accessing the video files
- BACKUP – i actually didn’t even have a backup of the video files the whole weekend, except on CF cards they originally shot on. i decided to work on James’ iMac rather than my own laptop, but usually i have a SuperDuper backup which is great because it’s a bootable backup; in case the drive died, i would’ve been able to boot straight from the external HD and keep working as usual.
- SOONER PICTURE LOCK – this is an obvious one. i don’t know how often we can keep pushing these edits to the last minute… need to lock earlier so we have enough time to sweeten the audio and ensure a proper export without having a heart attack each time! set a realistic schedule.
Road Trip Americana: DAY 13 (Sunday, October 4th, 2009)
Saturday, October 10th, 2009in the morning, i had a warm plate of blueberry pancakes…

Then started the long drive to my next destination.. Weather was gloomy for the first several hours.

Hmmm… maybe i should’ve crashed here:

Drove through part of Oregon, found a bit of snow!


Then crossed the border into Nevada


Caught the Bears game through my iPhone

Was planning to make a night stop in Reno, but I was making good time and decided to push my way to the finish. Had one more chance to dive into a local eatery:


And when I saw the “Welcome to California” sign, I had to rock out to this!

then I was treated to a nice drive through a snow storm in the sierras.

Then the exhaustion started kickin in. Dizzy, feverish, spent. I felt like how this picture looks:

Summary:

Cities: Boise, ID > Walnut Creek, CA
Odometer Begin: 211470
Odometer End: 212110
Day Miles: 640
Gas Prices: $2.70, $2.95, $2.90
TOTAL Miles Across America: 4,464
Next: Summary, FAQ, and tips learned from my road trip. Feel free to ask me any questions of your own!
Road Trip Americana: DAY 12 (Saturday, October 3rd, 2009)
Wednesday, October 7th, 2009how they do omelettes in Salt Lake.

spoke with Jason about his latest project, Hell Hole.

he is a skilled DP who has been working on this original web series since the beginning of the year. it’s looking good! check it out at: http://www.facebook.com/pages/Hell-Hole-The-Series/112857746305
you can also check out his DP reel at: www.rjasonball.com
i made a few stops along the way to Boise.
- Salt Lake City Library. a must-see as recommended by my friend. yup, a PUBLIC library!


- Hill Aerospace Museum


then continued on…

I’m in IDAHO!

and met my 2nd couchsurfing host: Kent. we spoke briefly about couchsurfing and i told him how it has been difficult to find people willing to host me. we both agreed that it’s my lack of references (i just signed up when i started the trip anyways, so it’s understandable). but he told me the reason why he accepted me is that sometimes, you just have to give people a chance… and he gave me that chance.
Kent was a gracious host filled with many stories of his own travels. he’s seen most of and lived in many parts of South America, spending his time building orphanages and language schools there, giving children and many young adults a chance at a better life. inspiring.
he hooked it up with a nice Guatemalan style dinner.


met his son Wesley, and somehow ended up helping him move a huge dining table into his new house! hey i was getting a free couch to crash on! i gladly helped out.


he then treated us to a well-deserved round of beers and wings at their local watering hole.



Summary:

Cities: Salt Lake City, UT > Boise, ID
Odometer Begin: 211105
Odometer End: 211470
Day Miles: 365
Gas Prices: $2.68
TOTAL Miles So Far: 3,824
Road Trip Americana: DAY 11 (Friday, October 2nd, 2009)
Wednesday, October 7th, 2009as i crossed the border into Utah, i saw the signs for Moab which included a picture in the background of a very familiar rock formation, which i later learned was the “Delicate Arch” (google on iPhone saves the day!). after doing quick direction search, i find out that it is located in Arches National Park, near Moab, only about 1 hour off route from my destination to Salt Lake City.
best detour of my trip so far. stunning landscapes and formations.



squeezed in a 3 mile hike to the Delicate Arch, even though feeling a bit feverish. well worth the effort!



practiced some HDR (High Dynamic Range) photography.

exhausted by the time i made it back to my car, i still had 4 1/2 hours of driving ahead of me. a lot of the drive was at night in the mountains through a lonely, narrow, and isolated highway.

eventually found myself in civilization and discovered a new restaurant to try: Wingers.

looked like the typical chain restaurant. ordered the Original Wings Dinner. i was skeptical of their “Famous Original Sauce” but took one bite… and i was convinced! pretty damn good.

i ended up buying a bottle of sauce to bring home. really… it’s up their with Kinder’s Sauce.
arrived at my friend’s Jason’s house. haven’t seen him since Sundance Labs ‘05! we did a bit of catching up and eventually called it a night.
Summary:

Cities: Grand Junction, CO > Moab, UT > Salt Lake City, UT
Odometer Begin: 210723
Odometer End: 211105
Day Miles: 382
Gas Prices: $2.65
TOTAL Miles So Far: 3,459
NEXT: drive to Boise, ID
Road Trip Americana: DAY 10 (Thursday, October 1st, 2009)
Friday, October 2nd, 2009started the day off with a proper filipino breakfast. tocino, hot dog, and rice.

had some major work done on the car, replaced the engine belts and a pair of tires. then heard a loud grinding noise a few miles as i started driving! i found out that part of the bumper started falling apart and hitting the tire. but gaffer’s tape solves all rigging jobs!

the drive through the rockies makes Colorado the most scenic of all the states i’ve driven through so far. i constantly found myself wanting to pull over and capture the gorgeous views and rock formations.





no food adventures today, didn’t even have a proper dinner because i wasn’t too hungry. i attribute it to that power breakfast i had in the morning.
Summary:

Cities: Colorado Springs, CO > Grand Junction, CO
Odometer Begin: 210397
Odometer End: 210723
Day Miles: 326
Gas Prices: $2.36
TOTAL Miles So Far: 3,077
Road Trip Americana: DAY 9 (Wednesday, Sept. 30th, 2009)
Friday, October 2nd, 2009i spent today doing a bit of sightseeing around Colorado Springs and just hanging out with the Nicandros… family friends from when i was growing up in Vallejo, CA. as i mentioned in an earlier blog, i hadn’t seen them since i was 1991! it’s was pretty wild seeing them all married with children.
some of the highlights of Colorado Springs:
- the Air Force Academy.



- the Garden of the Gods.



catching up on 18 years…



i’ll have to browse the old shoeboxes for old photos of us as kids!
NEXT: drive through Colorado towards Salt Lake City.
Road Trip Americana: DAY 8 (Tuesday, Sept. 29th, 2009)
Friday, October 2nd, 2009started early and made my way mt. rushmore by 8am. it was a cold morning with a light breeze, and a nearly empty park. peaceful. it was quite the amazing view. i have always wanted to see this as a kid. i took more pictures here than anywhere else in my entire trip!


how Mt. Rushmore was meant to be finished:

probably my favorite tilt-shift photo of the trip so far:

found this guy wandering the parking lot!

after a couple of hours of touring the park, i was back on the road. i had a google-estimated 8 1/2 hour drive to colorado springs, so i wanted to get started early.
it’s true what my friend Ariani said about Wyoming… there’s really nothing around!


“3G”, “E”, “o”… none of these networks exist here. i was alone in Wyoming! but it was nice to be free for once from the shackles of the evil iPhone.



it made me a bit nervous knowing that my brother’s car wasn’t in the best shape and i was pushing it across the badlands. but i feel blessed to have made it safely.
bummed out at the lack of unique eateries on my route.

drove through Denver and snapped what i could as i was driving…


then arrived safely in Colorado Springs and i met with family friends i hadn’t seen in 18 years! and true to Filipino custom, the first action is to offer food, which i gladly accepted.

Summary:

Cities: Keystone, SD > somewhere in Wyoming > Colorado Springs, CO
Odometer Begin: 209887
Odometer End: 210397
Day Miles: 510
Gas Prices: $2.58
TOTAL Miles So Far: 2,751














