Install and See
MSP6.0VE
was first loaded onto a Pyro rig which had VS4, Premiere 5.1, MSP5.2 and
the DVSoft CODEC. The latter had to be removed (per the installation readme
in the Pyro disk). The updates were installed, including the latest from
the ADS Web site My update did not come with a printed manual, but it
is available as a pdf file on the CD, Like most, I didn’t print it. These
pdf files can be hard to read: there is a lot of unnecessary formatting
visible, and the page to page flow is designed for printing, not online
browsing. There must be a better way, nonetheless, it is a way
of delivering the manual for a budget product.
CAPTURE module
After
this, the first attempt at Capture revealed the “repainting” bug (see
picture at left) which again, a readme file identifies as being known
with ATI graphics adapter cards. My Pyro rig actually has an i810 chipset
all-onboard mobo – the i810 provides the graphics adapter function – so
this repaint problem is wider than Ulead indicate. Of course, this feedback
has been passed to them.
Like the VS4, MSP6 capture defaults to a dialogue box when you hit the capture button. Only after you have put in the details and clicked the button does capture commence. But if you check off the dialogue box in the settings, it is then awkward to set the capture file name. Clumsy.
Batch capture – first try. Again, the dialogue box kept popping up. It was awkward to work through a tape marking in and out as it played using the F3 and F4 keys. Again, it is the file naming issue. I found the default settings to be clumsy. This reviewer hasn’t yet gone back to batch capture to experiment with settings for smooth working. Others have, and report it works.
Another thing to note. It seems MSP6 auto-detects installed CODECs, and will prefer a proprietary DV CODEC over the Windows “DV video encoder.” In fact, the DV video encoder does not appear as an option in the Project settings if another DV CODEC is present. There is no way of controlling which DV CODEC is used in capture, and if the “foreign” CODEC is present, the captured files are unusable in MSP6. However, it seems Video Studio will still capture useable files even with a “foreign” DV CODEC present.
Introduction
Installation
MSP6 with the Raptor
Troubleshooting
What Next?