New Canon 7D firmware 2.0.0
It is with a slight sense of excitement that I write this, because after owning a 7D for many years, they have finally updated the firmware in the camera to include the single biggest feature it lacked.
The 7D now has manual audio level control!!
Why is this significant you ask?
When it comes to filming, picture quality is very important, however, as a bit of an audio phreak for quality, the 7D didn’t cut it at all. Why? Because it has a feature known as auto gain…
What auto gain does is detects the volume of the audio, and if it’s quiet, it boosts the levels. Now suppose you are in a quiet room, and you want the audio to have no noise in the background? Tough luck. The camera auto turns up the detection of the quietness, and bam! You hear sounds that weren’t there all of a sudden.
This new manual feature is of huge benefit to all the 7D users.
Thanks heaps Canon!!!
Here’s my update photos…
Whoa, didn’t know the Muppets worked at NASA!!!
Uncharted Territory
Well, here we go… It started a while ago, and to say the least I’m quietly excited. Our creative team at church has been asked to film and edit stories of people who have gone through struggles, and share where God is in it all.
We have a larger that usual team for this job, using various lighting, multiple cameras, steady-cams, slides, tripods and other gear. So far, the biggest challenge has been using footage from a RED camera. Now, 4k footage is brilliant and beautiful in it’s raw nature. It was great to be able to have the use of it, but in doing so, there have been other issues that we wouldn’t usually face when doing a simple one or two camera shoot.
The biggest problem with the RED footage, is that we have to down sample it to match the other formats, of 1080p@25f. Why you ask? Well, when using 1, 5 and 7 D cameras, they all shoot in H.264 footage. The reason we aren’t leaving it in 4k or using the raw files in the time lines, is because simply because of editing software compatibility, and currently the footage won’t be shown on a 4k device anyway.
The audio was recorded two ways, using wireless lapel mics directly in to a MacPro, and using a small boom mic, initially plugged in to a H4N Zoom with phantom power in the XLR input, and then directly to the RED camera – after we overcame some technical problems.
When you shoot 4 cameras, have various audio sources and the event is shot over several hours, organisation of the footage has to be paramount. Various folders were set up for each of the sessions, video footage, the shooter and camera they were using, as well as audio paths to store the correct files. Project files/folders were also set up and arranged for later conversion and the shifting of between programs during the colouring and sound edits.
The other challenge that would have taken hours to do was to syncronise all the footage so that it was in line. Before the shoot started, we syncronised all of our cameras to at least have a time stamp to roughly refer to. Making all the footage line up was going to be the biggest challenge, however a program I’d heard about many times and dismissed as not being need proved essential. It’s called Plural Eyes, and you just load the footage and audio of each session in a timeline, export as FCP-XML and load that file to PE. It then does the calculations and produces a new XML file ready to import back in, with everything synced. AMAZING! The new XML imported beautifully in PrProCS5.5 and FCP7 without any import dramas.
So now what is left? We are still awaiting the conversion of the RED files – which is still using 8 cores maxed out. This could take a few days at this rate… (update: 18 hours)
Because of program compatibility issues between software editing versions, we will be duplicating the project structures on portable disks, and then sharing the FCP-XML files for the main edits. It sounds crazy, but when you are working with PrPro5, and PrPro cs5.5 and FCP7, something has to give and you do what works… or will in theory.
When this has all happened and the initial story edit is complete, the round trip will be to add other footage, clean up things, colour it and then add and fix the audio and other music effects.
I’ll keep you posted on how it goes… It’s exciting.
My latest video creation
A new love that I’ve found since moving interstate has been that of filming and editing. I’ll admit I’m not the best in the world, and that there are probably much faster and more efficient ways of doing things, but at the moment as I grasp new projects, ideas, constructive criticism, and a creative feel, I’m enjoying learning about new and exciting techniques.
The most recent creation has been that of a carols promotional video. We planned to render (some elements), shoot, edit and colour all of it within a week. This surprisingly is what happened.
We filmed late on a Sunday afternoon, with time set aside for after the shoot, to do a time lapse of the park getting dark, to the incorporate it in to the video.
This worked really well, considering I had only done one time lapse attempt of something else at night, and this was only 3 days beforehand! This was of course after chatting to a camera nut who knows what to do properly of course.
The video was shot on a Canon 7D with a Sigma 24-70 F2.8 using the Cinestyle video profile. (Find out more here and here about this). This recorded the footage in an incredibly dull looking footage. This is something I had never done before, so it was a little bit of a gamble, considering I only had one week turn around, and that Sunday afternoon was the only time we had to film. I did know however, that this was going on in the DSLR industry, so the thought of “how hard can it be” came to mind. The LUT was loaded using the Red Giant free software that can be downloaded here.
There were problems using this kind of colour correction. Firstly I like seeing my footage in full colour when editing (yes, not good workflow yet I know), but this mean I couldn’t do this without applying the Red Giant filter and having to render. Even without having this filter on, it was still going to have to be added at the end, and thus add to the rendering process, just like I was going to have to with many of the other effects applied – such as the Vignette and at times a quick Brightness/Contrast filter.
Many of the effects that were used came from one of two places; After Effects, or Motion.
The scribble effect that was used for the facepainting, jumping castle and also the pony ride was done in AE, as I couldn’t find an effect like this in Motion. There were several problems for this and they were:
- I’d never used AE up until this point, and so all I had to go by to get the effect was tutorials. Thanks to those who do them! They are a big help.
- I had to find the most efficient way to do the edit. I saw it as two ways. 1. Make the edit in FCP and then export the entire project via an XML plugin and send it to AE, which I didn’t like the idea of for several reasons. or 2. Create the elements and export them back to FCP – which I ended up doing.
- Exporting the “scribbled” elements was also and interesting concept, but once I figured it out as an Uncompressed with Alpha, it seemed to work out.
- Play back in AE also confused me, especially with RAM previews as well. (Different story, and a good gotcha for new users).
- Render times sometimes took a long time to finish, such as the Motion projects that were imported, and also the stars and cloud “footage” which were just images with slow moving tweens.
Once these new elements were imported, they were then arranged and shrunk/edited as required.
Motion was also used for some of the other effects, such as the rain, and the smoke on the BBQ – both of which are built in effects. Thanks Apple. 🙂
The video editing codec I use is ProRes 422 LT 720p @ 25FPS with Compressor being the main conversion tool. Why not use MPEG Streamclip? Well I use compressor, as I can use more cores, plus other Apple devices and spread the load around a couple of computers and speed up the conversion process. I’ve set up QMaster/QAdministrator to work. Not that often that you can get a MacPro with 8 cores all at 100%! 🙂
All of the audio was tweaked in the Audition. I’m a massive fan of Audition as I think it kicks the pants of Apple’s SoundTrack (sorry FCP fans). Even though the sound was originally recorded on a H4N Zoom, there were issues with the quality because of the environment it was recorded in, so we re-recorded the sound in a studio and imported it as uncompressed AAC as FCP doesn’t like MP3 files @ 44.1k when the sequence was @ 48k.
I also did a brief colour on the video using the 3 way colour corrector. I need to learn how to use Color.
So, that’s the technical information about the video, now here it is!
Hope you can come to the carols on Bradbury!
My solution to the jquery mobile back button problem
As I’m new to this new jquery mobile, I’m bound to run in to troubles and find unique ways of accommodating solutions.
So, the my first problem I’ve encountered has been trying to implement a back button. After playing with codes and a few options, I got frustrated and have decided to do it my own way.
By default the back button shows, which is great, if your entire site is on one page. It stays self contained and works really well. But, if you are like me and need to use a CMS or implement a site on to multiple pages, you are going to find it a little harder. I could be wrong, and welcome comments on this, but It seems that when you move to an external page from where you just were, the jquery looses it’s history and can’t do a back to the previous page.
So, I just did this:
<body>
<div data-role="page" id="MainPage" data-theme="a" >
<div data-role="header">
<span style="font-size: 9px; text-align: center;">Header</span>
<!-- Copy this 'a' code -->
<a class="ui-btn-left ui-btn ui-btn-icon-left ui-btn-corner-all ui-shadow ui-btn-up-a" data-icon="arrow-l" data-rel="back" href="javascript:history.back(1) " data-theme="a">
<span class="ui-btn-inner ui-btn-corner-all">
<span class="ui-btn-text">Back</span>
<span class="ui-icon ui-icon-arrow-l ui-icon-shadow"></span>
</span>
</a>
</div>
<div data-role="content">
<p>Please select a job type</p>
<ul data-role="listview">
<li><a href="#page1">Page 1</a></li>
</ul>
<ul data-role="listview">
<li><a href="#page2">Page 2</a></li>
</ul>
</div>
<div data-role="footer">
<h4>Page Footer</h4>
</div>
</div>
<div data-role="page" id="page1">
<div data-role="header">
<h1>Page 1</h1>
</div>
<div data-role="content" data-add-back-btn="true">
<ul data-role="listview">
<li><a href="Page1.html" rel="external">External Link 1</a></li>
<li><a href="Page2.html" rel="external">External Link 3</a></li>
</ul>
</div>
<div data-role="footer">
<h4>Page Footer</h4>
</div>
</div>
etc...
I used the cs5.5 dreamweaver code base originally, with it only needing these slight mods. Let me know how you go.
- ← Previous
- 1
- …
- 10
- 11
- 12
- Next →
