What's Hot:
My first test on my XP laptop was to capture some video footage from my mini-DV camcorder using a firewire/iLink connection. The camcorder had a mix of standard and widescreen clips. The capture session went well.
Another test was to encode an existing wmv video file on my hard drive. The encoding, which is a conversion from wmv to MPEG-2, went along at about real time speed.
The video encoder did a quick and good job with most input file types. I gave it a pack of 30 assorted files to chew on. It handled most well, but couldn't process some of them such as:
- PAL to NTSC conversions.
- WMV files made with the screen capture codec.
- WMV files encoded with a Microsoft MPEG-4 codec.
- For some reason it hung at the end of a type II DV-AVI file made by Movie Maker 1.
For the most part it chugged along nicely through the pack, a mix of standard, widescreen, and odd sized videos.
Once I had some video files, I decided to make a video DVD. Things went well until I got to the step of designing the menu. This step I needed to skip (see the What's Not section) and the disc burned successfully with a default menu.
What's Not:
The captured clip from my camcorder was a DV-AVI file. Playing it back in Windows Media Player showed the visual looking alright, but I didn't hear any audio.
I then tried to use the file converter to turn the captured DV-AVI file into an MPEG-2 file needed for a DVD. The process started okay but sort of hung when 36% finished. At that point it had encoded the first 7,678 frames. All indication was that it was still running but with no more progress.
I followed that first encoding test with a batch of small video files made by different apps with differing codecs. It finished the first five successfully, and stopped at the 100% mark of the 6th one. It had the same symptoms, sitting there working but not achieving anything.
After a few more successes I got a message about conversion of PAL files to DVD NTSC not being supported, and a Gear app crash in the middle of converting an MPEG-4 file.
The app crashed on my XP laptop a number of times at regular spots:
- When I pressed the options button of the Audio Editor.
- When I pressed the create menu and graphics option before pressing the create volume button when making a DVD project.
'Hangs' might not be as bad as crashes. I experienced them when:
- Encoding a batch of video files. It would get to the 100% conversion mark of a few files and sit there until I stopped/cancelled the line item.
- Dealing with a DV-AVI type II file.
Ripping a full audio CD to WMA files is slower with GEAR Video 8 than with Windows Media Player 11. It took 17 minutes on my XP system to rip a 23 track album to a set of MP3 files and 15 minutes to WMA. Window Media Player 11 took 6 minutes to rip the same disc to WMA files.
GEAR Video did better on my Vista laptop, ripping the same disc in 8 minutes, slightly longer than the 6 minutes for Windows Media Player.
The video DVD played in WinDV and Windows Media Player 11 with a good basic functional menu that.GEAR Video had created with default menu screens and buttons, However, the mix of standard and widescreen videos all played in standard 4:3 aspect ratio. GEAR Video hadn't handled the different aspect ratios appropriately. There were also some unexpected visual artifacts in a couple of the videos, things not in the originals.