VpVision ver 0.5 (rc3) -- PLEASE NOTE: This software is provided totally AS-IS, with no warranty express or implied. On2 Technologies, The Duck Corporation explicitly denies any warranty or indemnification of any kind for damages, failure to perform, etc. with respect to the software you have downloaded. USE AT YOUR OWN RISK!!! This is a VERY preliminary version of this product. VpVision is intended for personal use in time-shifting and archiving video material on a Windows- based personal computer. Requirements at this point are: 800 mhz PIII or better (1.4 ghz P4 recommended for 30 fps capture) bt848-based or similar capture/tuner card with VidCap drivers (other VidCap- capable cards/cameras may work for capture but not for channel changing. USB type cameras will not work correctly due to framerate limitations.) See www.on2.com/vpvision for some sketchy documentation on using the product. This is a pre-release build; the final release will include source code under a GPL license. Included in the install are components supporting VP3 (available at www.vp3.com), and an Ogg Vorbis ACM developed by Mr. Masao Kitagawa. Source code for these components will be provided in the final release. Installation instructions: * PLEASE make sure your video capture card works with the software it came with before attempting to run VpVision. * YOU MUST HAVE Vp3 Video-For-Windows version 3.2.4.0 or later installed. Go to http://vp3.com/getvp3/ to download and install the latest version. Earlier versions (3.2.2 or earlier) will not work correctly with VpVision. * Download and run Vp05install.exe Known issues, bugs, & missing features: * Encode performance should be better. We expect to spruce it up so that 30 fps is reliable on a 1 ghz. * During record, preview occasionally goes black. You can get it to work by moving the Duckvision window around. * Anything having to do with how many bytes are available, used so far in record mode, etc. is bogus * append time & date in record event dialog will crash at end of record (disable!) * Takes about 15 sec to load the app -- dunno why * Audio support limited to 44100 samples/sec, mono * Video support limited to 320x240 * While seeking, garbage frames are displayed (keyframe issues) -- will correct itself during playback * Skip function does not work * Audio sync problems on most systems after about 10 min. capture. If you're feeling adventurous, you can try this: add DWORD keys forceRate and forceScale in duckvision/duckvision/duckvision. Set them to values close to your FPS. For instance, if you captured at 30 fps (really 29.97), and video seems to run ahead, try setting it to 29.96 (forceRate = 29960, forceScale = 1000). This will be addressed in final release (automatic framerate recalc on capture) * On at least one machine, we've seen problems with CPU identification. If you see garbage frames during normal playback, try setting cpuID (in registry key duckvision/duckvision/duckvision, add it as a DWORD) to the appropriate value: X86 = 0, /* 486, Pentium plain, or any other x86 compatible */ PMMX = 1, /* Pentium with MMX */ PPRO = 2, /* Pentium Pro */ PII = 3, /* Pentium II */ C6X86 = 4, C6X86MX = 5, AMDK63D = 6, AMDK6 = 7, AMDK5 = 8, MACG3 = 9, MAC68K = 10, XMM = 11, /* SIMD instructions */ WMT = 12, /* Willamette Processor */ * Problems recording long material (>30 min) -- seems to think it's out of disk space (this has been 'fixed' by removing disk space check!) * App must be running to enable record events (final release will include a start bar daemon that will launch the main app at the appropriate time) * It's possible to play .VP3 files in Windows Media Player (just associate the VP3 extension with MediaPlayer, or open MediaPlayer first and open the .VP3 file from there -- in the file dialog, select "all types *.*" to get it to show the file). You can even seek around, though the sync is questionable after a seek. We hope to get better WMP compatibility in the final release. * Video quality setting is not working (I think). To change video compression settings for VP3 you will need to run an app such as VirtualDub, and set the compression parameters from there. The default parameters seem to work pretty well though. Leave auto-keyframe ON as the app does not set a keyframe value (otherwise your file will have no keyframes and you won't be able to seek at all, in VPVision or MediaPlayer). * The installer installs an ACM component for Vorbis audio that uses the format tag 0x6751 (as well as a few others). If by some rare chance you have already installed a version of this component (usually called vorbis.acm), there could be a conflict (this is very unlikely as it is not in general release). The one we install is called vpvorbis.acm. If you run into a problem, remove this key from the registry (or from system.ini in win95/98). Please send all comments, suggestions, and support problems to: vpvsupport@on2.com. Also send requests to be put on the mailing list for future releases, or to contribute as a developer, to vpvsupport.on2.com. Thank you for your interest in VPVision. We look forward to your feedback.