More than just talk

So, we're into week 3 of my internship @ redWEB.

I spent most of monday writing notes about how we can "package" video for redWeb's clients. It was a tough task, one that comes down to estimating how long it takes to do all the little jobs involved with making a film. For example, research … How long do you schedule for good old fashioned research? Storyboarding … How long might it take to storyboard a 3 minute video?

I think the estimates I made are actually quite accurate. But, of course, there are always things that take longer than expected, so, it will be interesting to compare these estimates with how long it really takes to do all these film-producing jobs.

Tomorrow I start filming on the mini-documenatary about redWEB. This will be part of my final thesis, which, I have decided will be about how to use video for marketing and communication. Their will also be a healthy dose of Social Media thrown into the mix, too.

In preparation for filming tomorrow I spent today testing my set up. I have a small Panasonic HD video camera, a H2 Zoom digital audio recorder, and, a set of lights that I borrowed from Aarhus Film Workshop. In fact, I am very grateful to Aarhus Film Workshop. It has been quite some time since I have been there doing filmy stuff, so, it was very generous of them to agree to loan me a few lights for my degree project.

The lights I have are known as "Red Heads". They're small, not particularly lightweight, but, they are perfect for small video projects like this one.

The lights worked perfectly. The small HD camera isn't "professional" by any stretch of the imagination. But. It shoots 1080p at 30 frames a second, or, 1080i at 60 frames. I chose 1080p at 30 frames. The "p" stands for "progressive," which, also means that the video has more of a fluid look, as opposed to the dryer "video" look of 1080i -- the "i" stands for "interlaced," which, means you're shooting video with two fields, upper and lower, and that's what gives it the dry video look.

I used to shoot a lot of stuff on DV. I remember spending a lot rendering time de-interlacing DV to give it more of a fluid, or, film-like, look. Most HD cameras have the ability to shoot progressively, which looks great and saves all that rendering time later on trying to achieve the film look.

If video becomes a regular thing for me down at redWEB, then, long term it will be a good idea to invest in a Canon EOS 600D, or, something similar. Why? Well …. http://vimeo.com/24000798

With the small camera I have at the moment we can produce good quality video with a little fiddling in post production. But. With a Canon EOS, well, you get the quality of HD video combined with exceptional optics, and, the results look amazing.

The best thing is that the Canon cameras aren't hugely expensive. So. If video continues down at redWEB after my internship, meaning, if I continue making videos for them, then, I'll go out and buy one with my first pay cheque if necessary -- we'll really be able to start producing videos that look way beyond good quality. But. Good quality is where we'll start for now.

So, today's aim was to test the Panasonic HD camera and see what we can do.

I started out with setting up the camera and shooting a shot of myself sitting in a chair, as though being interviewed, no lights, no jiggery-pokery of any kind:

Nolights

I am sitting in a room with white walls. You can see there is a window behind me. The light in the room is actually not bad. But, with a little jiggery-pokery, it's possible to enhance what the room already gives you. That to me is the secret of lighting a subject well. Be aware of the setting, aware of what the room is already giving you, and, add to it to highlight what you are filming.

The next thing I did was set up the lights. Nothing fancy. I used two lights. A key light at a 45 degree(ish) angle off to my right, and, a fill light off to my left. The fill light was low, about a meter off the floor, and, actually pointing away from me. The fill was pointed at a large white reflector, which diffuses and reflects the light back onto me:

Lightnoblur

So, with the lights on, I become the subject, rather than just part of the background, which (to me) is what the first photo looks like.

One of the nice effects of placing a large reflector board in front of a subject is that it gives a nice highlight to their eyes. The reflector is actually reflected in their eyes. You see this effect all the time, and, perhaps never really think about it. You can use light directly to give a subject highlights in their eyes. But. For this situation I felt using the reflector board to do it gives a much more subtle and natural looking effect.

I filmed myself for a minute or so. I also had my H2 Zoom audio recorder set up just off to my left. It's a really good quality recorder, and, I know it gives much better results than the onboard microphone on the little HD camera. On top of that, I can place the H2 Zoom much closer to the subject, where as the camera, in this situation, is actually about 4 meters away.

Having filmed myself, it was then time to transfer the results onto the computer and perform some more jiggery-pokery:

Lights

The first thing I did was load the footage into Adobe Premiere. I have been a Final Cut Pro guy for quite some time. But. I have tried several times to get to grips with Final Cut Pro X (the latest version) and have always come away utterly frustrated. Apple decided to totally reinvent the software -- changing its interface and how it operates completely -- which left long time FCP users like myself tearing their hair out because, basically, it was a whole new program … To stick with it, you'd have to learn it all over again, and, considering that programs like Adobe Premiere still work like non-linear editors have done for years, it's actually easier to switch.

I opened up Premiere and literally started editing right away. With FCPX I spent the first few hours trying to figure out where things were. And, even when I started editing, Apple (in their infinite-loopy wisdom) decided to change the workflow as well, so, choosing clips and getting them onto the timeline -- which actually isn't a timeline at all in the new FCP -- was just plain awkward.

So, I have switched to Premiere for the time being. I am also interested in checking out Avid Media Composer. But. Premiere works, so, Premiere it is for now.

Having loaded in my test footage the first thing todo was take the audio I'd record in the H2 Zoom and sync it up. This took me about five minutes. It's just a case of dropping the audio onto the timeline and moving it until the sound from the camera and the sound you have added are aligned. You can really hear it when it isn't aligned, even if it is off by a single frame, you can hear a slight echo. Once the external sound was synced, I switched off the sound from the camera footage, and, suddenly I had much fuller and clearer sound.

I should say at this point that I did spend some time in Bias Peak Studio cleaning up the sound from the H2 before dropping it in Premiere.

Now it was time to perform the extra jiggery-pokery. I wanted to add an effect that works really well for further highlighting a subject. I wanted to blur the background slightly. This involves layering two lots of video on top of each other. The bottom layer is your footage with a slight gaussian blur. The top layer is your footage with a garbage or shape matte applied to it. A garbage or shape matte cuts out your subject and removes most of the background. But. Because you have the background, etc, in your first layer of video, the effect makes your subject sharp, with the background slightly blurred. Feather the edges of the garbage or shape matte and the two layers blend together seamlessly.

It's an effect that works really well, and, I have to say that I like it so much that I will have to make sure I don't over use it from now on.

The next step was to do a little colour grading. I adjusted the contrast and brightness a little, and, the saturation. I had manually set the white balance on the camera when I filmed to adjust it to the lighting conditions, so, no real colour correction was needed.

The final result, I feel, is actually a much richer looking picture. The subject is highlighted in a very subtle and natural looking way. All in all, good results from a camera that, as I said earlier, is a long way from the more professional cameras available.

The test, however, had two down sides. The first, the room was very echoey. While I managed to tweak the sound from the H2 zoom, I couldn't get rid of what the echoey room did to my voice completely -- it sounded a little hollow. To combat this tomorrow -- I am interviewing my boss Christian in the same room -- I went out to a hardware store and bought a bunch of thick moving blankets. I will hang them in suitable places in the room which should help deaden the echo.

The second down side, which, isn't really a downside … rendering! Having performed all the jiggery-pokery I wanted to do on my test footage I went to render the results. The compute came up with an estimate of three hours! So, I left the rendering until it was time for me to go home. I then set it to render and will see the full results of today's test first thing tomorrow morning.

I did take the still images I posted here, so, from those I have a pretty good idea of what the final results will look like.

I can't wait to film the interview tomorrow. I have been talking about filming and doing videos down at redWEB since I arrived, and. tomorrow I will finally be able to start doing more than just talk.


How long does it take to make 150 sound effects?

From Evernote:

How long does it take to make 150 sound effects?

Well, it's the end of week two of my internship @ redWEB.dk.

This week I have mostly been working on sound effects for a flash game. We spent a whole morning last Tuesday recording as many different sounds as we could using, well, anything we could find. I actually took all of my daughter's musical instruments and rattly things to the office just for the occasion.

I also took in a USB stick with a library of sound effects that I happen to own. I mean, you can't be a used-to-be-filmmaker-come-filmaker-again without having things like sound effects kicking around on a hard drive somewhere.

I also spent some time searching for sound effects online. There are plenty of websites around (soundjay.com, for example), however, the game that we're making is for commercial purposes, so, I really had to make sure that whatever we downloaded was free for such use.

It's a whole different level, in a way, than producing projects at school. I mean, we borrowed all sorts of media for school projects because we knew they'd not really go beyond the realms of the school. But. Out in the commercial world of website and multimedia production you really have to make sure you have the rights to use the media you find online; it'll be the company you're working for and you who'll get into trouble if you don't check the rights.

We made many of the sound effects we're using for the flash game. Supplementing any gaps from the library I already have the rights to use, and, some sounds from soundjay.com -- a useful site, as most of the sounds there are free for personal and commercial use.

Having recorded our own sounds for an entire morning, it was then my job to process them. This involved running the sounds through Bias Peak Pro 7, using Sound Soap Pro to clean away any unwanted background noise, etc. I then had to clip each piece of sound as tightly as possible, and, export each one as an mp3.

Aj7ddjqceaakriu
(Photo by )

We ended up with about 150 sound effects, which, took me 12.5 hours to process.

Why am I being so exact about the time spent? Well, now that I am out in the big wide world of commercial web and media production, I have to account properly for my time. The same will hold for anything I do in future at redWEB. For example, I am starting to film the mini-documentary about the company next week, so, as soon as I start a particular part of the process -- like editing, for example -- I need to track how long it takes me.

This isn't because my boss at redWEB is breathing down my neck. It's because if redWEB is going to keep making videos for their clients in future, we need to know how long it takes to do certain things. We'll then know, for example, that editing a 3 minute video takes 16 hours. That way, we know how to budget projects for clients, and, give accurate estimates on how long the process takes.

This is a whole new way of thinking for me. I have never been one to track my time. I mean, as a student (especially one with a family), I just worked as long as I needed to work to get a project done. The same went for writing, and, making the films I have made previously; we had a schedule, but, we were young and reckless and thought nothing of pulling a string of all-nighters just to get things done.

All-nighters are a thing of the past for me. I have a family. A daughter who wakes up early, even at the weekend. Also, I am forty! When I was twenty, I could pull an all-nighter and not think twice. These days, well, it takes days to recover from missing a night of sleep.

So. Learning to be older and wiser. I realise it's time to track my time. Figure out how long it takes to edit a three minute video or process 150 sound effects for a flash game. That way, I (and redWEB) know how long it will take the next time we do it, so, we can schedule the correct amount of time during sensible working hours to get the job done right.

It takes 12.5 hours to process 150 sound effects. It might take a little less time the next time as we'll find ways to do things quicker. But. For now. It takes 12.5 hours. Not a minute more. And certainly not a minute less.

Sounds like this:

(download)

Full circle

From Evernote:

Full circle

It's odd how life can bring you full circle. Those who know me are aware of my background as a writer and filmmaker … Something that I thought I had to leave behind.

Why?

Well, I am 40. I have a family. Writing and film weren't paying the bills. This is partly why I dived into becoming a Multimedia Designer. I have always had a great interest in all things webby, so, changing direction wasn't a huge issue for me -- infact, I am pleased I did it.

Taking a degree in Multimedia Design was a great decision. I discovered the joy of coding; actually building a website with nothing more than a text editor and a browser. Learning to build the web, rather than just surf it, has changed the way I think and do things, for the better.

During my degree I became aware that my filmmaking skills weren't something I'd leave behind. Being a Multimedia Designer isn't just coding, it's about creating all sorts of things for the web, and, video for the web is one of them.

In fact, I ended up running workshops for other students, teaching them the basics of filmmaking. Showing them how to handle a camera and set up lights. The last workshop I did a few months ago was attended by over 80 students!

The interest and need to produce good quality video for the web has become hugely apparent to me (and, no doubt, to that room full of eager students I taught a few months ago).

These days it's easy to film, and, easy to cut video together -- iPhones and iMovie made it that way. But. Making a video production look professional is more than just the tools you use. It takes skill. Knowledge. And, well, a splash of talent, too.

I know I have the skill. And the knowledge to make films. I went to film school in my early twenties, worked freelance on and off for a number of years, and, I have even written and directed my own short films.

So, it's ironic in some way that, having changed direction into Multimedia Design, that I find myself coming out of the other side of my education moving back towards film.

I am almost two weeks into my internship at redWEB.dk, and, it seems my purpose there is all about film.

Yesterday, Karsten (redWEB's flash developer) and I spent the morning recording sound effects for a game he's producing. It's now my job to process the sound and make it usable for the game … Producing sound is part of video production, something I am more than familiar with.

Once I am finished processing the sound effects I will start producing a short video to show off one of redWEB's products, redSHOP. redWEB has another department called, redCOMPONENT. This department produces some backend solutions for Joomla (an Open Source content management system for building websites). redSHOP is one of their backend solutions for turning a Joomla website into a web shop or e-commerce site.

As you can imagine these kinds of products are useful, but, also difficult to nutshell for potential clients. So, it's my job to make a video to nutshell what redSHOP is all about.

On top of producing this small video, I am producing a short documentary about the company as a whole. The idea of the documentary is to show what the company is all about … In fact, show more than just what the company is about. I want to capture the process of making a website. I want to capture the passion, hard work, and dedication of redWEB's developers and designers.

The company has two very strong founders, Christian Bennike and Ronnie Christiansen. Strictly speaking, Ronnie founded redWEB. He started the company alone and built it into one of Denmark's top web companies.

Christian started a company called, Web Zoo. Web Zoo is known for it's strong design ethic and visual identity.

Ronnie and Christian found their companies working together rather a lot, so, it made sense to them to put the two together under one name, redWEB.

Of course, one aspect of making the documentary is to help promote the company. But. I am not going into this with promotion in mind. For me, it's about capturing the company as it is. Capturing the people as they, and, the process of how they go about doing what they do in a way that makes it clear that producing a website is more than just writing code -- it really does take commitment and passion to make something that's right for the client, which, isn't always what the client wants. It's about what the users of the website need. That is what a web designer and developer strives to achieve.

The first part of making the documentary starts with redWEB's foundations: Christian and Ronnie. I will be filming interviews with both of them next week. This will form the foundation of the film, it's spine, I guess. Once I have those interviews in the can, I'll start building the film around them … Building a picture of redWEB as a company to show what it really takes to build for the web.

So, next week I will put up lights, set up a microphone, and stand with a camera in my hand. Full circle. A filmmaker once again.