I haven't really posted anything of late, mostly because it's been easier to link to Twitter or Facebook.
But this space is too good to leave empty, so I'll have to be more active here soon.
In the meanwhile, just follow me on Twitter.
Sunday, October 10, 2010
Saturday, May 16, 2009
Panasonic GH-1 HD DSLR
Like Canon, Panasonic is releasing a Digital SLR camera that outputs 1920x1080 video.
Panasonic's GH-1 will output video using the AVCHD codec used in a lot of consumer camcorders.
You can read about it here with various specs:
http://www.dpreview.com/news/0903/09030315panasoniclumixdmcgh1.asp
The camera is available for pre-order on Amazon for $1499:
http://www.amazon.com/exec/obidos/ASIN/B001WAKSCW/
The camera is a Micro Four Thirds, so it's not a full 35mm sensor, but still can have shallow depth of field.
http://en.wikipedia.org/wiki/Micro_Four_Thirds
There is a part you may find curious:
NTSC: [Full HD] 1920 x 1080, 60i (sensor output is 24fps)
This means that the file that is created is at 29.97 then needs to be reverse telecined to 23.976.
This isn't normally a problem since Panasonic DVX100, Canon XL2 and other tape based cameras need to be reverse telecined when capturing from the 24P mode.
The issue will be on how to reverse telecine it. The camera is out in Japan so there is raw camera footage to test with.
Final Cut Pro on an Intel Mac only can handle AVCHD footage, so I converted to ProRes first using Toast 9.
I tried Compressor, and it doesn't do the reverse telecine well.
I tried a free app called JES Deinterlacer, and it did the reverse telecine, but there were interlace artifacts.
If any of you want to try to test out the footage yourself you can find it here:
http://www.dvxuser.com/V6/showthread.php?t=170685
There are discussions about the issues with the compression.
http://prolost.com/blog/2009/5/9/would-you-like-a-little-camera-with-your-mount.html
Saturday, November 1, 2008
Interesting Issues With LTO Compatibility
LTO, (Linear Tape Open) http://en.wikipedia.org/wiki/Linear_Tape-Open is becoming a popular backup/archive format, especially for productions that uses tapeless cameras. LTO is the preferred backup/archive format for bonding and insurance companies, so a lot of productions are backing up their dailies to LTO tapes.
The cameras, whether they use portable capture formats like P2, flash cards or hard drives or are tethered to a field recorder like the S Two, need to have the media offloaded and backed up so the recording devices can be reused.
The unfortunate part is that there is no constancy about HOW the media is written to an LTO tape.
Quantum makes an A-Series line of LTO drives that are network-attached, and MXF metadata aware, http://www.quantum.com/Products/TapeDrives/LTOUltrium/LTO-3A/Index.aspx.
At the moment, it's not known if any LTOs written on a A-Series drive can be read on a standard LTO drive without special software. So at the moment, LTO tapes written on an A-series drive need to be extracted off of an A-series drive. My assumption is that the A-series is proprietary to Quantum and no other manufacturer makes them.
This limitation may be fine if these LTO tapes stay in-house or given to someone with an A-series drive, but can be problematic if the tapes are given to someone with a standard LTO drive and can't recognize the tapes.
At the recent HD Expo, I saw a custom P2 field offload/backup/archive system, with an LTO drive build into it. Since the whole system is Windows based, the manufacturer decided to use Symantec Backup as their backup/archive software. Once again, this is fine if the tapes stay in-house or given to someone who is using Symantec Backup, but problematic if given to someone who's not using it.
There is also the dilemma with these proprietary hardware/software is not just compatibility at the present, but compatibility in the future. No one knows if the A-series LTO line and Symantec Backup will be around in 5, 10 or 20 years, let alone backwards compatible with current versions.
Last weekend at a demonstration of the Arri D21 Digital Cinema Camera, the S Two representative, www.stwo-corp.com, mentioned they do their backup/archive to LTO using tar (tape archive) http://en.wikipedia.org/wiki/Tarball.
Tar is common in the Unix/Linux workstation platforms, which has been used in post productions since the 90s. While a lot of post houses have moved to inexpensive desktop systems using Windows, Linux and OS X, and data is being transported by hard drives and secure high speed data lines, the use of tar is still common when delivering a tape based backup/archive, since it's a non-proprietary format.
Tar itself has various flavors and shortcomings, and is far from being the perfect choice for backup/archive. It just happens to be more common.
Until the bonding and insurance companies become more specific on how the LTO tapes need to be written, we will have a variety of formatting.
The only way to make it easier to deal with is proper labeling of how the tape is written, what software, and the contents of the tape. This is the only way of insuring that all the contents of the tape can be properly extracted.
The cameras, whether they use portable capture formats like P2, flash cards or hard drives or are tethered to a field recorder like the S Two, need to have the media offloaded and backed up so the recording devices can be reused.
The unfortunate part is that there is no constancy about HOW the media is written to an LTO tape.
Quantum makes an A-Series line of LTO drives that are network-attached, and MXF metadata aware, http://www.quantum.com/Products/TapeDrives/LTOUltrium/LTO-3A/Index.aspx.
At the moment, it's not known if any LTOs written on a A-Series drive can be read on a standard LTO drive without special software. So at the moment, LTO tapes written on an A-series drive need to be extracted off of an A-series drive. My assumption is that the A-series is proprietary to Quantum and no other manufacturer makes them.
This limitation may be fine if these LTO tapes stay in-house or given to someone with an A-series drive, but can be problematic if the tapes are given to someone with a standard LTO drive and can't recognize the tapes.
At the recent HD Expo, I saw a custom P2 field offload/backup/archive system, with an LTO drive build into it. Since the whole system is Windows based, the manufacturer decided to use Symantec Backup as their backup/archive software. Once again, this is fine if the tapes stay in-house or given to someone who is using Symantec Backup, but problematic if given to someone who's not using it.
There is also the dilemma with these proprietary hardware/software is not just compatibility at the present, but compatibility in the future. No one knows if the A-series LTO line and Symantec Backup will be around in 5, 10 or 20 years, let alone backwards compatible with current versions.
Last weekend at a demonstration of the Arri D21 Digital Cinema Camera, the S Two representative, www.stwo-corp.com, mentioned they do their backup/archive to LTO using tar (tape archive) http://en.wikipedia.org/wiki/Tarball.
Tar is common in the Unix/Linux workstation platforms, which has been used in post productions since the 90s. While a lot of post houses have moved to inexpensive desktop systems using Windows, Linux and OS X, and data is being transported by hard drives and secure high speed data lines, the use of tar is still common when delivering a tape based backup/archive, since it's a non-proprietary format.
Tar itself has various flavors and shortcomings, and is far from being the perfect choice for backup/archive. It just happens to be more common.
Until the bonding and insurance companies become more specific on how the LTO tapes need to be written, we will have a variety of formatting.
The only way to make it easier to deal with is proper labeling of how the tape is written, what software, and the contents of the tape. This is the only way of insuring that all the contents of the tape can be properly extracted.
Subscribe to:
Posts (Atom)