Just a quick example of where a new file format might be useful: in general, real frames don't exist in modern video, if you consider a frame to be a sort of snapshot in time.
Excuse me? DV, DVCPRO, Pixlet, AVC-Intra ... these are all i-frame-only codecs, just like "iFrame".
Besides, the concept of frames and "snapshots in time" exist in every codec ... it just takes you longer to decode it, that's all. There are timecodes and discrete temporal points in every digital video ever made, and you can call upon QuickTime to take you to that frame and "show" it. Yes, it might require the decoding of several p-frames and a preceding i-frame, but so what?
Actually, where the whole "snapshot in time" concept starts to fall down is in CMOS sensors, just like the ones used by Sanyo Xacti. Shoot some 60fps video and wobble the camera side-to-side, and you'll see the whole frame of video get a large slant in it, changing direction when you do. That's because the frame is "scanned" over time, from top to bottom, instead of captured in an instant as you would get in a CCD camera.
The concept was just the same in tube cameras (going back to the early 1990s now), so, no big deal.
Having said all that, I'm a proud owner of an HD1000 and the HD2000 and HD2000A look like brilliant products that I would recommend. QuickTime works *perfectly* with the MP4 files that come out of the cards ... in fact I don't know what the hell all the whinging is about when people complain about Sanyo and compatibility. QuickTime Player is the "Notepad" of video, but it works equally well in Final Cut Pro. (Never used Express, hehe).
Maybe it's the Windows users complaining. They were never good at standards in Windows. I bet it's Windows Movie Maker that refuses to handle MP4 files, even though the rest of the consumer electronics universe knows how.
What's more, these huge frames quickly eat up bandwidth, reducing the amount available to record other kinds of frame data.
Well that's why this new iFrame codec may be a bit of a non-starter. It probably chews up space, like 25Mbps the way DV did. It's amazing that I upgraded from SD to HD and lost 60% of my (non-temporary) disk space requirements as a result.
A new format that was designed to be read bi-directionally would allow for more efficient editing and smaller file sizes or higher quality by eliminating the need for these extra big frames. As would a file format that removed the need to perform this activity while editing, perhaps by saving smaller resolution cues in place of full fledged snapshots.
It's all cool in theory, up to a point. If you're playing with 25Mbps you can get something like iFrame 960x540x30fps, or you could equally get h264 1920x1080x60fps ... I know which I would choose.
Of course, professional formats are 100Mbps or 200Mbps or more, and once you're at that size, just go for i-frames only why not!
In the professional world, if you want to do clever editing and tricks like chroma-key, i-frames only are still a Very Good Idea.
CK.