Well, it took me the first half of the year to get around to compiling my ‘iPhone view’ video for 2013 but I finally got a round to it so here it is:
Well, it took me the first half of the year to get around to compiling my ‘iPhone view’ video for 2013 but I finally got a round to it so here it is:
I have finally got myself a GoPro! This is a couple of test clips with footage shot in 720p 120fps mode on the GoPro Hero 3, then slowed down further in After Effects CS6 using Timestretch and Timewarp.
A bit glitchy due to the flickering from light behind it, I’ll try this again in bright daylight and compare results.
I’ve written quite a few posts about the various products that the guys over at Shedworx develop and that have been useful to me whilst working with video (AVCHD video in particular!). They’ve written a couple of articles which are great primers for people new to working with audio and video.
The articles explain the various aspects of audio and video such as Codecs and Bit Rates and are well worth reading, especially if you’ve never given much consideration to the output of your video or audio and have just gone for defaults in apps such as iMovie etc. Even if you’ve been working in these areas and have a good knowledge of this stuff they’re still worth a read.
Apple made their presence felt at the NAB show in Las Vegas with a preview of the next version of their Final Cut Pro video editing app, Final Cut Pro X.
In what is no doubt a long overdue update Final Cut Pro X brings what a lot of Pro video users have been waiting for: a totally redesigned interface, 64-bit memory addressing, multi-processor support, background rendering (no more render window), GPU rendering, use of more than 4GB RAM, video sizes from standard def up to 4k, real-time native format video processing – that’s quite a list!
The other announcement that is pretty awesome – a new price: $299 (not sure what that’ll be in £GBP yet, about £199 I’d guess) and, similar to Apple’s Aperture software which had a price drop recently, Final Cut Pro X will be available through Apple’s Mac App Store.
An often featured subject in blog posts here on Suburbia is the AVCHD file format. Previously AVCHD required transcoding into some other format such as ProRes in order to edit it in Final Cut Pro, so a good question is whether the new ‘real-time native processing’ feature means that this transcoding will be a thing of the past? This is a feature that Adobe’s Premiere Pro has had for a while, albeit one that requires quite powerful hardware to make use of it. It will be interesting to see how Final Cut Pro X compares with this.
Final Cut Pro X is due to be launched through the Mac App Store in June. In the mean time you can find out more about the new features via a couple of YouTube clips filmed at the preview announcement:
I just happened to be playing around with Flash this morning messing around doing a little shape tweening with a couple of symbols I found over on The Noun Project website so I thought I’d use that FLA file and see how Wallaby coped with it.
After starting Wallaby you get a very simple interface, a file select field that you use to select the FLA file and a large Status area that shows any errors and warnings encountered whilst converting your file. There are also Preferences that can be set which at the moment include automatically opening the converted file in your default browser and enabling logging.
After selecting my FLA file I clicked ‘Convert’ and after a few seconds it happily converted my file without any errors or warnings. I was interested to see what it would make of the shape tweened animation that I had made in Flash as this seemed like quite a challenge to convert.
That’s a total of 372kb in order to recreate the tweened animation in HTML / CSS / JS / SVG.
So how does this compare with the files output by Flash? Well, not very well when you look at both the amount of files required and their file size:
Even with that it’s still only a total of 17kb, about 1/20th the total size of the files that Wallaby outputs.
This particular animation is obviously a challenge for Wallaby to convert into anything closely competing in file size, so perhaps in this case it would be a better option to use a video clip to provide a non-Flash version of the animation? The same animation can be output as an H.264 video at the same frame rate and it comes in considerably smaller at 192kb:
That’s about half the size of the Wallaby output. It’s also likely to playback much better on mobile devices such as iPhone / iPad / iPod touch as Adobe warn that the output of shape tweened animation can result in playback performance difficulties on iOS devices.
This adds 201kb to the total file size required so that brings it to about 393kb, almost the same as Wallaby’s HTML5 output. I’m sure there are possibly slimmer options compared to JWPlayer for embedding that could reduce that down a bit but I reference JWPlayer as I consider it to be one of the best cross-platform methods of embedding video on website.
Of course I haven’t mentioned anything about delivering video in alternative codecs such as Ogg Theora or WebM to serve browsers like Opera, Firefox and Chrome, this would further increase the files and sizes involved. However, given that Wallaby is trying to provide a way for animated content created in Flash to be output and made playable on devices such as the iPad and iPhone it could also be considered that providing any kind of Flash fallback for video is unnecessary, so we could ignore the JWPlayer / JS completely and just use the regular HTML5 <video> tag and a single H.264 video, so we’d be back to a considerably smaller size than Wallaby’s output in this instance.
Overall Wallaby looks to be a pretty handy tool for people that are struggling to find a way to get their content viewable on the millions of devices that don’t (and likely never will) run Flash. For animation that doesn’t involve shape tweening I think the resulting file sizes will be a lot more favourable and it will be a reasonably efficient way to create animated content using standards-based technology.
I would say that the primary target user for Wallaby, at least at first, is for people doing online advertising. This is an area that is seeing a lot of activity with tools like Sencha Touch appearing, there’s definitely opportunity for a ‘killer app’ that makes creating banner advertising using all of these new emerging web technologies in a way that people are used to doing in the Flash IDE. There’s a lot of challenges in there technically, as well as a lot of issues such as accessibility, graceful degradation etc, but I think a lot of companies are focusing on this challenge now, so it’s good to see that Adobe is thinking about various ways of providing tools for the job.
I have included the HTML5 output as an iframe and also links to each animation in HTML5, SWF and H.264 formats. There is also a link to download all the assets of Wallaby’s output in a zip archive:
View SWF Output in new Window
View Video Output in new Window
Shedworx‘ essential AVCHD tool VoltaicHD just took a healthy step forward in functionality with the recent release of VoltaicHD 2. Highlights of the new features in the update are the ability to preview AVCHD / AVCHD Lite clips, the ability to edit native AVCHD video and the ability to upload video to YouTube and output to presets like iPhone, iPod etc.
Version 2 of VoltaicHD increases the scope of the app from simply being a tool to convert AVCHD format video footage to now include basic native editing of AVCHD footage. You can now preview AVCHD / AVCHD Lite video clips within the application and then set simple in and out points to define a section of raw AVCHD / AVCHD Lite video clips which can then be trimmed down and converted.
The interface is reminiscent of the new Quicktime X player that comes with the Mac OSX 10.6 Snow Leopard. It’s very easy to set the position of the start and end as the position in seconds within the movie is shown in a little tooltip when sliding them around. My own criticism with it is the same that I have with the new Quicktime X player in that you can’t use the mouse to fine-tune the position of these points. That’s a little thing that I miss from the old Quicktime Pro player’s editing capabilities.
Overall though the ability to trim down clips before conversion is a massive timesaver, instead of having to convert a whole chunk of AVCHD footage you can just roughly trim down to the section you want and then convert only the bit you want. Definitely a great and helpful improvement!
Along with the new preview / edit capability there is also the ability to convert and upload trimmed clips to YouTube directly from VoltaicHD 2.0. There are also preset output options for iPhone / iPod and AppleTV.
One of the things you’ll notice when you run VoltaicHD 2 compared to the previous version is the new drop-down menu options at the top of the window. From this menu you can select the specific option that you want, then combine that with a little bit of previewing and trimming in the clip details panel and you’re ready to go.
Both of these options make it really easy to get footage off your camera and online or onto your devices, take it with you or watch it on TV. Shedworx make another application called RevolverHD which enables you to create AVCHD DVDs that will work on most blu-ray players, however I find the ease of exporting video that’s ready to go onto my iPhone really convenient. As blu-ray players become more commonplace then I think I’ll use RevolverHD much more as a perfect way to send HD footage to my extended family.
It’s most definitely an upgrade I’d recommend for any VoltaicHD user, it’s worth noting that this is the first paid upgrade to Voltaic since it was released in July 2007. Don’t forget that VoltaicHD is available for both Mac OSX and Windows operating systems too.
If you’re an existing VoltaicHD user then you can upgrade to version 2 for only $9.99, or if you happen to have bought the previous version since July 2009 then you’re eligible for a free upgrade to VoltaicHD 2.0. First-time customers can buy VoltaicHD 2.0 for $39.99 which is still a great deal for a great bit of software!
Apple’s 09/09/09 Media event introduced some new things both expected and unexpected, many expected an iPod touch with a camera but instead there was an iPod nano with not only a camera but FM radio and a built-in pedometer! I was surprised about the FM radio as I never expected that to be added to an iPod. Here’s a few of the things Apple introduced today along with some thoughts / notes etc:
Now in multiple colours as well as a special edition stainless steel model. There were rumours that this tiny little iPod was going to be ditched but that didn’t happen. They also announced a new 2GB model along with shuffle-compatible third party headphones and controller peripherals. I’m not sure how much smaller you could make an iPod shuffle really. (iPod shuffle ?)
At first I didn’t think an iPod nano with a camera was that big a deal but after watching one of the video clips demoing the video features I found myself wanting one to carry around so that I could film things again. I’ve missed being able to film stuff since getting my iPhone 3G, however, there’s no way I’m buying yet another iPod so I’ll just have to look into getting an iPhone 3GS at christmas time instead! The nano’s video format is 640×480 pixel h.264 video and looks to be pretty good quality, it almost makes me wish Apple would just make a dedicated camera but I don’t think that will happen. (iPod nano ?)
There’s nothing that different in store for the iPod classic, just a simple storage bump from 120GB to 160GB instead. I still like the classic iPod and the scroll wheel, it’s a great interface for accessing files. The iPhone / iPod touch’s touch screen is great but the scroll wheel is still very efficient I think. I wonder though how much time is left for these iPods? Probably still a fair bit, but once flash memory gets into at least 128GB sizes I think the iPod classic will be assigned to the history books. (iPod classic ?)
There was no rumoured iPod touch-with-camera announced, just a price drop on the existing model as well as a 64GB model announced. I think a new version with a camera is in the works, it just doesn’t make sense for the nano to have it and not the touch. Also the lineup is now 8GB, 32GB and 64GB, I’d expect to see it become 16GB, 32GB and 64GB when the new model is announced. That’s just my speculation though. Update: This press release from Apple about the new iPod touch updates paints a slightly different picture though, it indicates that the 32GB and 64GB iPod touches have the same internals as the iPhone 3GS, “The 32GB and 64GB models also include up to 50 percent faster performance and support for even better graphics with Open GL ES 2.0“. Interesting. (iPod touch ?)
An expected announcement and one that took up the majority of the media event. iTunes 9 introduced a revamped interface (with it’s usual introduction of unusual / new interface aesthetics!) and a few other new features. One thing that’s disappeared though is the shopping cart feature, now you have to either add it to the also newly added Wish List feature or you have to use 1-Click purchasing! That’s a little bit scary.
There’s now also the option to share items on the store to either Facebook or Twitter, I was hoping for more integration with social networks, particularly last.fm but alas it’s not to be. One other thing I noticed is that iTunes now finally behaves like all other good Mac apps and will actually maximise when you click the maximise button! Previously this would toggle iTunes into it’s Mini Player mode, I’m really glad they’ve changed this.
Here’s a rundown of some of the new features of iTunes 9:
iPhone OS 3.1 for iPhone (and 3.1.1 for iPod touch) were announced too. It introduces a few new features that tie in with iTunes 9’s new features, nothing massively new but then again it is a point update. Amongst the various features shown on the iPhone OS software update page a couple of little tweaks caught my eye:
Being able to lock an iPhone remotely enhances the already brilliant MobileMe feature of locating your iPhone via GPS and also remotely wiping a lost iPhone. Anti-phishing support in Mobile Safari is a great feature too, something all browsers need these days.
Anyway, enough writing about it all, I’m going to go and re-organise my iPhone apps :)
After a few years of being available there are now many hard-disk based video cameras that use the AVCHD format for video, support for the format in video editing software is well supported now on both Mac OS X and Windows by apps like Final Cut Pro / Express, iMovie, Adobe Premiere, VoltaicHD and more. This all leads to a much simpler experience for users of AVCHD cameras than it was a couple of years ago.
More recent digital stills camera have started coming with the ability to shoot HD video, for many of the small compact cameras there became a need for high-quality efficient video format that could be used in small compact cameras with less capable hardware. The solution to this was a variant of the AVCHD format called AVCHD Lite.
The main differences between AVCHD Lite and the regular AVCHD: a maximum resolution of 1280 x 720p in AVCHD Lite compared to 1920 x 1080p in regular AVCHD and a less-intensive compression method – both of which make the format more suitable for less powerful camera hardware.
AVCHD Lite throws a spanner in the works because many of the existing AVCHD editing packages are incapable of supporting it without an update to the software. At the time of writing none of Apple’s video editing applications such as iMovie, Final Cut Pro or Express support the AVCHD Lite format. Adobe’s Premiere and Premiere Elements applications also do not appear to support AVCHD Lite at this time.
The only solution for AVCHD Lite on Mac OS X at the moment is the one that saved many an early adopter like myself a couple of years or so ago when AVCHD cameras first came out – VoltaicHD by Shedworx. This is a $35 app that will convert your AVCHD Lite footage to the Apple Intermediate Codec format that can then be used in any of Apple’s video editing applications.
Here’s a few links to some handy information about AVCHD Lite:
As of 04/06/09 iMovie now supports editing of AVCHD Lite files with the iMovie 8.0.3 update!
At the time of the review FlamingoHD was available for sale as a beta version (for those early adopters!), however, Shedworx have reached their first milestone and have now released version 1.0 of FlamingoHD to the world!
The main new feature in the final version 1.0 release is a new filmstrip view that lets you see keyframes from the video clips in your library. This is really handy and lets you see what scenes are within your various clips:
For a more detailed overview read my previous post: FlamingoHD – Helping you manage your AVCHD media or checkout the FlamingoHD page on the Shedworx website.
FlamingoHD is a new application by Shedworx (the guys that make VoltaicHD), with the purpose of helping you manage all of your AVCHD video footage. Although AVCHD has greater than ever support these days it still presents a challenge when it comes to managing all of the video that you’ve shot, especially as the convenience of shooting straight to disk or card kind of encourages you to record a lot more than you would when using tape!
FlamingoHD provides a solution to this problem by enabling direct import from your AVCHD camera or alternatively importing AVCHD clips that are already on your hard disk. It does this by providing a preview thumbnail of the video footage before you import it, this saves a lot of time compared to iMovie or Final Cut Pro as you can choose only the clips you want without having to convert the footage first.
The user interface is easy to understand as it features a left hand menu very similar to iPhoto or iTunes which contains sections for Devices, Events and Projects, very similar to the iLife applications.
The basic process is to select the source of your video footage. You can either connect your camera to your computer which will automatically show up in FlamingoHD as a device, or you can select ‘Import Media’ from the File menu to select either a single clip or a folder containing clips from a location on your hard disk, once selected they will show as a device in the ‘Devices’ section in the left hand menu. It’s also worth clarifying that FlamingoHD will actually import video, audio and images from your source device or location and can manage all of these assets within Events and Projects.
With a device selected ready for import you can then choose which clips you want to import into FlamingoHD, the imported files will automatically become an Event, or more than one Event if there are multiple clips shot on more than one day. This can be controlled by a preference which allows you to switch off this feature if you just want to import everything into one event.
The application preferences are worth checking out as there are a couple of other important preferences to consider. The first is ‘Hide media already imported’ which is enabled by default, this is useful when there are a lot of clips on a camera that you have already imported as it hides the ones you’ve already brought in.
The second important preference is ‘Copy imported media to Library area’, it’s important to set this appropriately because if it is ticked any clips imported from a folder on your computer will be copied to FlamingoHD’s Library which will take up more space and will result in duplicate files. Clips imported directly from a camera will be copied to the library regardless of this setting, the location of the Library for FlamingoHD can be set in the Base Location preference under the General tab.
Once you’ve imported clips into FlamingoHD you can then group clips together into Projects, these projects can then be sent to exported in via several methods, either ready for editing or as final output.
Projects are created by selecting ‘New Project…’ from the File menu, this adds an entry under the Projects section of the left hand menu which you can name to suit. Once the Project has been created you can drag and drop clips from any of the events that you previously created.
After creating a project you can then choose to export or convert your files. FlamingoHD has options to send files to VoltaicHD, RevolverHD, iMovie and also to the assets folder of other editing applications such as Final Cut Express or Final Cut Pro.
You can export by either right-clicking on the Project name or by selecting the Project and clicking on the ‘Media’ option from the main menu. The four options at the bottom of the menu allow you several choices for your project:
Send to VoltaicHD
This option will send your footage to VoltaicHD and it will be queued up and converted ready for use in whatever application you want.
Send to RevolverHD
Selecting this option will send your AVCHD files to RevolverHD where they can be burned as either AVCHD DVD or Blu-ray DVDs that can be played back on Blu-ray players such as the Playstation 3.
Send to iMovie…
This option is specifically for sending your project to iMovie, it creates a new project in iMovie and sends your clips to VoltaicHD for conversion, once converted you can open iMovie and all of the clips will be there in the new project.
Send to Editor…
Using this option will send files to a folder in the assets location of your preferred editing software, you can set this option in the Preferences of FlamingoHD. The AVCHD clips will be converted in VoltaicHD and copied to the folder. You can then open your editing software and bring in the files that are ready for editing.
FlamingoHD has worked pretty well for me so far but it is worth pointing out that (at the time of writing) that it is a 0.1 version, as such it’s beta software and still being actively developed. However, the developers Shedworx have made it available to purchase now for the reduced price of $29.99 while it is in beta, the price will increase after the beta period.
FlamingoHD already provides a very useful application for managing all of your AVCHD media, but one aspect I haven’t mentioned is that it will also handle any video format that is supported by Quicktime so it can also be used for cameras that don’t use AVCHD as the video format. For me this is the key to the application’s potential, it fulfils a function that Apple’s own iLife suite doesn’t provide, that of being a specific video asset management tool.
The only criticism I can see is that it currently doesn’t provide direct playback of the video clips that are imported into it, instead the files are opened into Quicktime player. The biggest drawback of this being that Quicktime player doesn’t currently support AVCHD clips. However, Apple’s next release of Mac OS X, 10.6 ‘Snow Leopard’, is supposed to support AVCHD so that will be one solution, but in the meantime perhaps enabling AVCHD clips to open in the open source VLC player could be integrated as this already provides playback of AVCHD footage. The next release version 0.2 will provide a film-strip view of clips which will at least make it easier to examine the clips in more detail without needing to open them.
Give it a try for yourself, there’s a demo version that is limited to a maximum of 2 events, 2 projects and 50 clips, this gives you enough to try it out and kick the tyres. There are also demo versions of VoltaicHD and RevolverHD so you can test out the whole workflow. Finally, don’t forget to give feedback to the developers via the FlamingoHD contact form, they’re keen to consider people’s ideas and to hear about any issues people encounter with the software.