Patryk Kizny sends word of his (with partners) newest short film, Altissimo. Shot entirely in time lapse, and some with sliders, over one week in Switzerland. See the video page for more information about the making of this time lapse film and licensing.
Other good sources include the Zemanta plugin in WordPress that tries to fetch public domain photos for use on your blog. I only use them for non-commercial purposes as many of them go back to Flickr or Wikipedia and other public sources.
For music, check out Incompetech. Free for personal, non-commercial use – although I have donated to him as donations are certainly encouraged.
Separately, I posted a civil war battle re-enactment video on Youtube last night and shortly thereafter received a Youtube email saying that my video may violate a Sony music copyright. All videos on Youtube are automatically scanned by a pattern matcher that looks to see if copyrighted music is in your video.
A problem I have noted in the past is that this cannot distinguish between legitimate, even licensed use of music. In my case, they objected to the use of Taps, music written by a bugler and a General during the U.S. Civil War in about 1862, to honor the death of soldiers. By about 1871, Taps had become standard at military funerals and was formerly established as a standard in 1891. My recording came from the United States Army. I am having a hard time seeing how Sony has a copyright on a US Army performance of a Civil War era piece of music and have submitted this to Youtube’s dispute resolution.
Here is the video – a 2005 re-enactment of a Civil War battle:
That video was shot originally in SD and even a little bit in digital 8 or Hi8 analog formats – I no longer remember. I remastered the video yesterday to take advantage of technology improvements available since 2005. This included color adjustments, slight sharpening, new titles, and eventually output of the 720×480 original video in 1440×960 size before uploading to Youtube. The result, surprisingly, is a video that looks much better than SD – its not HD, of course but it really does look a lot better. Watch it full screen!
Meanwhile, I am just starting to edit the 2011 battle re-enactment. I will be using almost exclusively, video shot on a GH-2, a bit on a Canon SX-1, and only a little on the XH A1 video camera. That latter is because I made a stupid boo boo and did not get the quality I wanted on the video images. Unlike past years, which are all edited on Final Cut Pro, this year’s is being edited using Sony Vegas Movie Studio Platinum 11. Vegas does native AVCHD video editing, as well as Canon’s H.264 native format, and handles HDV – all without doing format conversions. I do not know when I will finish this as other things are a higher priority on my time.
Until now, most of my still photography was mostly family and vacation snapshots with only a bit being serious still photography. Most of my photography has been at 30 frames per second.
As a very happy owner of a Panasonic LumixGH-2 – which I bought for video work, of course – I am now getting interested in still photography once again. I say “once again” since I had (and still have) a darkroom that has not been used much in recent years. In other words, I used to do lots of still photography.
This week I joined the 21st century and begin working with RAW images. Having not been shooting and editing RAW images until now makes me feel like, well, a dork.
I downloaded the trial versions of Adobe Lightroom and Apple’s Aperture. I like both of them and especially like the electronic download price for Aperture ($80 at the Mac App store).
Unfortunately, after I imported an iPhoto library the program began crashing and bogged down to unbelievably slow, even after applying a number of tricks that do improve the speed. But the crashes, and Apple’s creating confusion about its professional products with the release of FCP X have some thinking that Apple may not continue on with Aperture. Since the release of version 3 – which was buggy and suffered from slow performance – their sales plummeted. Most of those problems have been fixed in 3.1 and it seems the new $80 price point might be an attempt to win back market share – or at least test if there is a market for Apple at that price. Who knows?
Regarding Final Cut Pro X – its billed as a successor, and therefore, presumably upgrade, to Final Cut Pro 7. But they left out sufficient features that many think it is a downgrade and are not happy with FCPX. Thousands of professionals have signed a petition to Apple asking them to re-instate FCP 7. They have good reasons to complain. FCP X drops features from FCP and is not compatible with FCP 7. That means, say, if your team is adding new editing workstations to work on existing projects, your team is stuck – FCP 7 has been discontinued and FCP X cannot edit your current FCP 7 projects. Quite a mess.
In fact, FCP X is an upgrade to Final Cut Express. Apple discontinued Final Cut Express upon introducing FCP X. They also added in features like importing from iMovie, something that professional editors have about zero likelihood of using. The key idea that seems missed so far is that FCP X is a upgrade to FCE. And while FCE was officially discontinued, it kind of looks like FCP was itself discontinued. It’s Final Cut Express – may be that is where the “X” comes from, “Express”?
Is Apple abandoning the professional market? That market always was small – but was influential in terms of respected individuals and teams buying Apple and encouraging others to do so. The bigger market is the pro-sumer market, not professionals. With the success of iPhone, iPod, and iPad, does Apple need those influencers still? Probably not.
Which gets us back to Aperture. Many now think Aperture may go the same way as FCP – which means, end of life. It was a professional product – perhaps with the price drop, Apple is trying to re-position it as a pro-sumer product and out of the crosshairs of Adobe’s better products.
Apple completely re-wrote its popular Final Cut Pro video editing software. And a lot of people say Apple turned it into iMovie Pro and they are not happy.
I use Final Cut Pro 7 for video editing. I do not plan to update to X.
Apple product upgrades often turn into a cascade of necessary but unexpected upgrades. I found that out last year with a $30 OS upgrade ended up requiring a $300 upgrade from FCP6 to 7. I was not impressed.
In 2008, my Macbook was stolen the same week Apple announced they were dropping Firewire from Macbooks. Apple’s attitude was that AVCHD was the future, so get over it and replace your camera. Right. My $1,200 notebook was stolen so I should replace that plus my 2 year old $4,000 worth of Firewire dependent cameras. I bought a used Macbook instead. Not all of us have Steve Job’s income and can upgrade everything annually.
With Final Cut Pro X, the fanboys say – don’t worry – within a year, Apple will have fixed everything. Uh huh.
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Cookie settingsACCEPT
Privacy & Cookies Policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.