View Single Post
Old Dec 15, 2011, 11:36 PM
Tom Frank is online now
Find More Posts by Tom Frank
Dance the skies...
Tom Frank's Avatar
United States, MA, Walpole
Joined Dec 2003
19,012 Posts
What's NOT Included In the Release Firmware

Since I listed all the features that were being worked on for the #16 back in the #11 thread, I thought I should mention a couple that have not met expectations yet.
  • 640x480 @ (60fps) - this mode spits out 60 fps, but for yet undetermined reasons, the frames are not unique. To be exact, every other frame is a duplicate, so it's no different from a normal 30 fps video in terms of smooth motion, yet the file size is about twice as big. No bargain there, so this option was omitted from the release firmware. If the problem can determined and fixed, this feature would be added in a future firmware update.

  • The .AVI firmware DOES allow for no lost video between individual saved video clips during the normal stop/save/continue function of the camera. It does this by buffering the frames where the video clips are split, so there is about a 1 sec. "overlap" of video at the end of one clip and the beginning of the next. It's possible to align these separate clips with a really good editor that can manipulate and split or overlay the back-to-back "overlap" in time alignment for smooth motion playback.

    But that's where a significant problem arises with many editors. Some lose all playing information if the very first frame of a clip is removed. Editing with Virtual Dub editor, for example, has this problem. making trimming horribly involved, and even pausing a play back in Vdub prevents the remaining video from playing unless the timeline marker is drug back to the beginning to get the playing information again, then drug back to where you want to resume playing. The first frame MUST be kept with any file trimming. Better commercial editors keep the first file header information in memory, so you can trim/edit normally! Other require trimming the first frame and keeoing it at the beginning of the video. Then the file can be re-encoded and play/edited properly.

    Re-encoding the native .AVI file before any post editing is one workaround to fix the abnormal .AVI header structure, allowing normal editing if necessary. But some file conversion utilities do not parse the native file properly to re-package without errors into a new .AVI container. Ironically, Virtual Dub is NOT one of them. So even though editing the native file with Vdub is an exercise in frustration, you can load in the native video, immediately re-encode it, and load the re-encoded file back in to edit normally!

    This is all hard to grasp until you try it with your favorite editing program (WMM and WLMM will NOT work).
Tom Frank is online now Find More Posts by Tom Frank
Last edited by Tom Frank; Dec 03, 2012 at 10:20 AM. Reason: deleted some .AVI comments and obsolete sample video link
Reply With Quote