Android accounts for one-quarter of mobile web traffic
Android is mopping up Apple and RIM's declining mobile mindshare in the US, you'll find nothing but corroboration from Quantcast. The analytics firm reckons a full one-quarter of mobile web traffic stateside comes from devices running Google's OS
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
720P/30 = FAIL, Max 7 min recording time in HD because of AVI 2GB limit = FAIL x2. Why Olympus?
It's not like you have your own line of video cameras you're worrying about cannibalizing.
Make it 24P and AVCHD!
You forget that this is the same company that, up until a scant year or so ago, produced fairly expensive digicams that could only record 10 *second* VGA movies.
Also, FYI, AVI does not have a 2GB limit. AVI is just a container ("audio-video-interleaved"). It can have a variety of codecs, from DV (which takes 12GB/hour) to Xvid to mpeg4 to Divx. The file system may have a file size limit, but for digicam memory cards these days, it's FAT32, which is limited to 4GB (FAT16 is 2GB).
What's ironic is that Olympus is dumping it's own crippled xD memory in favor of SDHC. I guess the xD's speed and capacity limitations were just too much for a camera like this.
I will take 30p over 24p any day, any time.
My guess is that they didn't want to pay the EU HD video tax (or whatever it's called).
Why not just give us both 24p and 30p on the current format or what not?
Also what about motion jpeg or what not, can you like record 8 mins worth of stuff in like a 2gb card at that res? Would that be a good choice or would the format the Olympus is using better in quality?
AVI has a 2G limit. And it's precisely because it is a container that it has a limit. It's the container that locates all the data sections in the file and thus has limits on file offset values.
Legacy AVI and NTFS -> 2GB limit due to internal AVI file limit
Legacy AVI and FAT32 -> 2GB limit due to internal AVI file limit
OpenDML AVI and FAT32 -> 4GB limit due to FAT32 filesize limit
OpenDML AVI and NTFS -> no filesize limits
Hmm, that's strange, since I have around 20 or so AVI files in my computer that are 10+GB in size. I guess that they don't actually exist. You could go and look at the video files of people who edit DV vids... they're all AVI, and most of the time they exceed 2GB by a good margin (since 2GB is only around 10 minutes in DV-land). Google it.
Motion Jpeg is one of the less efficient (and older) codecs, since it's just based on Jpeg... essentially a series of Jpeg images. AVChd is one of the newer, more efficient (smaller) formats, but so far the AVChd compression in even the better HD camcorders is still not as good as HDV, which is normally tape-based.
Ah,someone beat me to it.
What people are referring to is the legacy AVI limit, something from several years ago. It would be really strange for Olympus to be still using legacy AVI, since the current AVI has been in use for many years, but then, they did have 10 second vids on their digicams.
Anyways, although it's a nice looking digicam, I'm giving it a pass, since I don't want to be caught with another "gotcha" product from Olympus.
Well, NTFS actually does have a filesize limit. 256 TiB minus 64 KiB, that is... ;)
http://en.wikipedia.org/wiki/NTFS
@GB - That figure is the maximum volume size; the maximum file size is a 1/16 of that.
Its not fail. If you want video then get the GH1. Panasonic supplies components to both this Oly and the GH1. More importantly you get 720/60 with almost no jello effect, and a usable 1080/24 that would be perfect if it wasn't for the codec.
Relative to the market this camera is perfectly matched, and since this device uses the same sensor as the GH1 its guaranteed to be superior to Rebel T1i and D5000/D90 in terms of 'jello' effect.
Forget OpenDML AVI. It's not as compatible as original DVI, and the only reason to use AVI is for compatibility. There are far better container formats (MP4, MKV) once you go beyond AVI compatibility anyway.