Capture hangs forever on both Windows boxes 95% of the time!

[ambushed19]

I've been trying to capture video using my Canopus ADVC50 on either of two different Windows computers for months, but 95% of the time the capture software hangs forever before capturing even a single frame. Most of the time I have to perform a hard reset to break out of the hang state.

One computer is a high-end desktop running XP Pro SP3 (the hardware details of which are given in my profile), and the other is an average Dell laptop running Vista Home Premium SP1. When I use Corel VideoStudio X2 on either machine, it hangs after the "start capture" button is pressed but before any frames are captured. If I use Vista's "Import Video using Windows Import Video", it hangs before I even get to the "start capture" screen. Note also that if it's going to fail, I cannot even preview what's coming in from the ADVC50.

What happens is this: I plug the Firewire cable from the ADVC50 into the proper firewire port on the computer. Both computers recognize it immediately, every time, and up comes a dialog box asking how I want to capture the video.

Under XP, the popup dialog lists the following capture options: "Capture Video using Windows Movie Maker (v2.1.4026.0); "Start Encoding using Windows Media Encoder 9 Series"; "Capture and Edit Video using Corel (formerly Ulead) VideoStudio X2 (i.e., v12); or "Take no action". I've never tried the "Start Encoding" option since I want DVD/MPEG-2 output for burning to a DVD. Otherwise, it doesn't matter which capture software I use: 95% of the time, it will hang.

Under Vista, an AutoPlay window pops up with the heading "Digital Video Device", which provides two options: "Import Video using Windows Import Video" and "Capture and Edit Video using Corel VideoStudio 12". I leave the "Always do this for this device" unchecked. I always try to capture in "DV" format, so I don't have to worry about any compression issues. As with XP, it doesn't matter which capture software I use: It will still hang 95% of the time.

The Windows Device Manager as well as SiSoft Sandra reports that the firewire ports on both machines are working properly. And recall that the ADVC50 is properly recognized 100% of the time on both machines, so it's working at least that well.

Every once in a rare while (5% of the time), the process will work correctly: The video is captured perfectly in DV format. But 95% of the time, the capture program hangs before I can begin capturing and even before I can see any preview of what's coming in, no matter what software I use. It appears to be waiting for something, but I don't know what. This problem isn't associated with the installation or un-installation of any hardware or software.

I thought the issue might be related to viruses or other malware, but I've purchased and run some of the most respected anti-malware tools on the market: Kaspersky KAV 2009, Avira AntiVir Premium 9, PC Tools' Spyware Doctor, SUPERAntiSpyware Professional, and others. These tools report that there's no malware present on either system.

Note also that I've tried both the external and internal firewire ports on the ADVC50, but the port doesn't make any difference.


So: What can I do to fix and/or avoid this problem completely? I've tried a great many video capture troubleshooting suggestions that I've found around the net, but nothing I've seen so far helps. Is there some diagnostic or other software that I can use to troubleshoot the problem?


Thanks!

[jagabo]

Try capturing with DVIO. If that hangs you know it's something about the firewire port or drivers (DVIO doesn't display the video as it's being captured).

[ambushed19]

Try capturing with DVIO. If that hangs you know it's something about the firewire port or drivers (DVIO doesn't display the video as it's being captured).

Thanks for your reply. I tried DVIO a few days ago. After navigating to the folder and file to capture to, I press "Capture Video from Camera". It doesn't hang, but it doesn't capture anything either. It just reports: "Cap: 0 Drop: 0 Size: 0.00 GB"

When I stop the capture and examine the output with GSpot v2.21, it reports that the file length is correct (127 KB), the Codec 4CC is "dvsd". It reports no error, but when I try to play the avi output file (with VLS or GOM or Windows Media Player, there's nothing there.

So if I understood you, this means that the firewire ports and drivers are fine. This is just what I would expect, since I get the same behavior on two different computers.

Any suggestion for what I should try next?

[minidv2dvd]

have you tried the "take no action" option, then started the software you wanted to capture with, set it up in capture mode, then started whatever you wanted to capture? i've never trusted the auto start feature of any windows os and always do it manually.

[jagabo]

I tried DVIO a few days ago. After navigating to the folder and file to capture to, I press "Capture Video from Camera". It doesn't hang, but it doesn't capture anything either. It just reports: "Cap: 0 Drop: 0 Size: 0.00 GB"

DVIO has no camera control functions. Did you press play on the camcorder before starting the cap?

[JohnnyMalaria]

Do you have anything capture related installed from Nero, Roxio or Pinnacle? These are notorious for messing up other capture software.

[ambushed19]

have you tried the "take no action" option, then started the software you wanted to capture with, set it up in capture mode, then started whatever you wanted to capture? i've never trusted the auto start feature of any windows os and always do it manually.

Thanks for your suggestion. I've now tried this several times. I chose "take no action", then I manually launched all of the capture apps on my system one at a time (now even including Windows Media Encoder 9 / wmenc.exe), but once I press "capture" or its equivalent, the software always hangs. Windows keeps running, but the capture app hangs so thoroughly that I always have to restart to get out of the hang.

I also have now tried VLC 0.9.9's "Open Capture Device" menu entry, but the settings/options aren't familiar. The other capture apps give the option of selecting "AVC Compliant DV Tape Recorder/Player" for both video and audio input, but VLC does not, so I don't know what to do.

Please also see my next post, which will be a general note to all readers...

[ambushed19]

General note to all readers:

First, please accept my enormous gratitude for your suggestions and assistance!

Now, here's some additional info... The XP Pro Device Manager tells me the following:

Under IEEE 1394 Bus host controllers, it shows "VIA OHCI Compliant IEEE 1394 Host Controller" and it reports that it's "working properly". The driver version is MS v5.1.2350.0, dated 7/1/2001.

Under "Imaging devices", it shows "AVC Compliant DV Tape Recorder/Player", and it is "working properly" also. The driver is MS v5.1.2600.0, also dated 7/1/2001.

Under "Sound, video and game controllers" -> "Video Codecs" it listed the following an hour or so ago:
ACDV 1.0
DivX 6.8.5 Codec
ffdshow video encoder
iccvid.dll
Indeo® video 5.10
ir32_32.dll
ir41_32.ax
iyuv_32.dll
msh261.drv
msh263.drv
msrle32.dll
msvidc32.dll
msyuv.dll
TechSmith Screen Capture Codec
tsbyuv.dll

When I selected "ACDV 1.0" and pressed Properties, I got the following message: "Status: Driver is enabled but not functioning properly". If I then press the "Settings..." button, I get the message: "Cannot load the ACDV 1.0 driver. The driver file may be missing. Try installing the driver again..." All the other video codecs reported no error.

It looked like I had finally found something that might lead to a fix, so I used the "Remove" button to remove the codec. I thought that since the name of the codec was "ACDV 1.0", it might well be related to the capture problem. But it turned out to be a codec from ACDSee Systems' ACDSee Photo Manager. I downloaded and installed the latest ACDV codec I could find (v2.9.0.2). The Device Manager now reports that all video codecs are working properly, so that didn't help after all.

I have now tried capturing on/with:
Two different computers running two different Windows operating systems.
Three different source VCRs, two VHS and one rock-solid Sony Super BetaMax.
Two different sets of analog cables.
Three different IEEE 1394 cables: Two 4-pin to 6-pin and one 6-pin to 6-pin.
Two different IEEE 1394 PCI adapters.
Seven different capture apps: Windows Movie Maker 2, Windows Media Encoder 9, Ulead VideoStudio 11Plus, Corel VideoStudio X2 (v12), Windows Vista Video Import, DVIO, and VLC.
Both home-made and commercial VHS and Beta tapes.
Jumper 6 (undocumented Macrovision remover) on the Canopus ADVC50 both on and off (all other jumpers, such as NTSC mode, have always been on.

Without some kind of diagnostic software, I can think of nothing else to try. I don't want to replace the Canopus until I'm more confident that it's not working (it cost $200). Someone suggested that since the ADVC50 is essentially a PCI card mounted in a 5.25" drive bay (which I've removed from the desktop machine's Antec case and supplied with external 12V power through it's Molex connector), I should try removing the PCI card and installing it directly into my motherboard. Unfortunately, the mobo I'm using is an Intel DQ35MP micro-ATX, and it only has one PCI slot, which is where my IEEE 1394 PCI card is installed.

Note that PCI standard voltage is 5v, but the Canopus only has a standard 12v Molex connector. That couldn't be part of the problem, could it?

Otherwise, I'm all out of ideas, so any and all suggestions are appreciated. I'm especially looking for some diagnostic software, or at least something that will let me preview what's coming in from the capture device/1394 port without actually writing the data to a file...

Thanks!

[ambushed19]

I tried DVIO a few days ago. After navigating to the folder and file to capture to, I press "Capture Video from Camera". It doesn't hang, but it doesn't capture anything either. It just reports: "Cap: 0 Drop: 0 Size: 0.00 GB"

DVIO has no camera control functions. Did you press play on the camcorder before starting the cap?

Well, I'm actually using VCRs rather than a camcorder, but yes, I did press play on the VCR.

[ambushed19]

Do you have anything capture related installed from Nero, Roxio or Pinnacle? These are notorious for messing up other capture software.

Thanks for your reply. I did not have any Roxio or Pinnacle software installed, but I did have Nero 8. I used Revo Uninstaller's maximum settings to uninstall the whole bloated monstrosity, but the same problem remains.

I also uninstalled other potentially interfering software, such as the "InterVideo Capture Device Service" and the like, but that didn't help either. The symptoms remain the same.

I sure wish I could find some diagnostic software...

[JohnnyMalaria]

A couple of thoughts:

Can you send a DV AVI file back to your Canopus or does it freeze too?
With XP, if you open My Computer you will see your DV device listed along side your hard drives etc. Opening the 'folder' should show you a video window with the feed coming from the Canopus. Does it?

You could use our software to help troubleshoot since it can output to a variety of things (files, video renderer etc) as well as provide details of the Windows components it is uses to achieve this (a diagnostic report can be created and emailed to us). Another helpful tool is GraphEdit. With this you can make the simplest capture process possible and then start adding bits to see what breaks it.

BTW, the "Video codecs" list is, believe it or not, pretty much useless. None of the capture programs you have tried use any of those components. The list is for the older Video for Windows technology. I suppose the list remains for backwards compatibility reasons.

[TimA-C]

Try downloading and installing the latest version of DirectX for your version of Windows from Microsoft - even if you think you're already running the current version!

[ambushed19]

A couple of thoughts:

Can you send a DV AVI file back to your Canopus or does it freeze too?

What a fascinating idea! The idea of converting digital video back to analog never even occurred to me. How would I send something out through the device? All of my software video players just play on the computer monitor, with one possible exception: VLC 0.9.9 has hundreds of obscure (to me, anyway) settings, including a variety of output settings. Could VLC do what you propose? I'd need instructions.

The Canopus ADVC-50 is a fairly basic unit, and mine was built in 2002. Here is a link to a sales brochure for the Canopus ADVC-50 (pdf) Do you think the unit is capable of digital to analog conversion in the first place?

With XP, if you open My Computer you will see your DV device listed along side your hard drives etc. Opening the 'folder' should show you a video window with the feed coming from the Canopus. Does it?

Wow! That's exactly the kind of diagnostic/preview tool I'd been looking for for ages, and there it was all the time! You're quite the font of useful and interesting info, Johnny; thanks several bunches.

Regrettably, it shows nothing. Also, if I click "Take a new picture", nothing happens. Would you say that's clear evidence the ADVC-50 simply isn't working? Or might there still be an OS issue?

You could use our software to help troubleshoot since it can output to a variety of things (files, video renderer etc) as well as provide details of the Windows components it is uses to achieve this (a diagnostic report can be created and emailed to us).

That would be great, Johnny. But I must have missed your company and software names somehow. Would you remind me, please?

Another helpful tool is GraphEdit. With this you can make the simplest capture process possible and then start adding bits to see what breaks it.

I'll look into it; thanks.

BTW, the "Video codecs" list is, believe it or not, pretty much useless. None of the capture programs you have tried use any of those components. The list is for the older Video for Windows technology. I suppose the list remains for backwards compatibility reasons.

You're pretty much an inexhaustible source of useful information I am in your debt, sir!

[ambushed19]

Try downloading and installing the latest version of DirectX for your version of Windows from Microsoft - even if you think you're already running the current version!

Good idea, and thanks. I just finished downloading DirectX 10 directly from Microsoft. I assume that would be the latest version?

It needed doing, but, alas, it hasn't helped...

[jagabo]

If your firewire port is sharing an IRQ with another device I would try moving cards around.

[JohnnyMalaria]

Most capture tools can also send the DV file back to the camcorder/converter. Our software (see signature) can along with WinDV, Windows Movie Maker and (I suspect) DVIO.

That you can't see it in My Computer and that you have removed Nero suggests a hardware issue. It is very unlikely to be the Canopus. Though rare, it could be clashing with another card in your system (not just FireWire).

[ambushed19]

If your firewire port is sharing an IRQ with another device I would try moving cards around.

Thanks for your reply. IRQ 21 is shared between the following devices:

21 : Intel(R) ICH9R SATA RAID Controller
21 : Intel(R) ICH9 Family USB Universal Host Controller - 2938
21 : VIA OHCI Compliant IEEE 1394 Host Controller

The Via 1394 controller uses their model VIA Fire VT6306/L IEEE 1394 Link-Layer / PHY Chipset

The "Resources" tab in the Device Manager shows "Use automatic settings" checked but grayed out. The "Change Setting..." button is also grayed out. The tab also reports "No conflicts".

Also, the Intel DQ35MP mobo only provides a single PCI slot, so I can't move it to a different slot.

Given all this, is it possible to change the IRQ for the 1394 card? If so, how?

[ambushed19]

Most capture tools can also send the DV file back to the camcorder/converter. Our software (see signature) can along with WinDV, Windows Movie Maker and (I suspect) DVIO.

As you saw in my previous response to you, I was surprised that this would be an option, since the brochure I linked to above says it only performs analog to digital conversion, and there's no RCA or S-Video or any other output connections. In any case, I found out how to do it with VideoStudio X2: One imports a DV AVI file, then sends it out to the device. When I pressed the "DV Recording" button (the mouse-over message said: "Output the file to a DV camcorder"), a window titled "DV Recording" popped up with the message: "Setting the capture preview window failed. Capture driver error. You can stop recording now and change the setting to use DirectShow - DV capture driver, or continue the transmitting process." There was only an OK button. The program hung at that point and I had to use shutdown->restart to clear it.

Is that message telling us something important? Such as that I'm using the wrong "DV capture driver" for input as well as output? Where would I look? How would I change the setting? I looked through all the settings options in VideoStudio, and nothing stood out or indicated a setting for "DirectShow - DV capture driver".

That you can't see it in My Computer and that you have removed Nero suggests a hardware issue. It is very unlikely to be the Canopus. Though rare, it could be clashing with another card in your system (not just FireWire).

Hmm.... The only other card installed is my NVIDIA GeForce 8400 GS with a driver dated 14-Jan-2009.

As for your signature, for some strange reason I'm not seeing anyone's sigs. I checked my profile settings, and the option to view others' sigs is enabled. I tried turning it off then on again, but I still don't see any sigs.

So I went to your profile page and found the link to enosoft.net. Is the free-for-personal use Ensoft DV Processor the product you're suggesting I try, or the Friendly DV product?

[ambushed19]

Update!

Right now, I'm capturing successfully under XP! I'm using VideoStudio X2's capture feature. I don't yet know if this represents a real breakthrough and a permanent fix or if this is just an example of the 5% of the time it's worked before. I'm going to take full advantage of this opportunity to capture a few of the VHS & Beta tapes that have been on my to do list for about a year. Thus, I won't know if my problem has been permanently fixed until after I'm done and I can risk rebooting and trying again.

If it is the long-sought permanent solution to my capture problems, my guess is that it's probably due to the fact that I downloaded and installed Ensoft's EnhancedDVDecoder_1.8.0_Trial and selected "Install Video for Windows version". I tried installing EnhancedDVDecoder without that option, but when I tested capturing, I got the same old symptoms. So I installed/enabled the Video for Windows version and then rebooted, and after that (i.e., right now), capturing is working great.

I also downloaded and installed two other Ensoft products: Ensoft Friendly DV, and the free-for-personal use DV Processor, so they might have had something to do with it also. If it works after rebooting and it also works on my Vista laptop, I'm certainly going to buy at least two seats of whatever product that fixed my problem!

I'll report back after I get the chance to reboot and test capturing again...

[JohnnyMalaria]

How bizarre. Video for Windows really shouldn't have a bearing on most capture tools unless something changed the registry in a peculiar way that our decoder puts right.

Re my signature, I've gotten into the habit of using it only once or twice at the start of a thread and then turning it off.

But I'm pleased that this problem seems to have gone away - I know the frustration this creates (to say the least).

[ambushed19]

Bummer.

It looks like the successful capturing under XP fell into the 5% success rate category after all. I was still able to capture again correctly after one shutdown->restart, but when I shut down completely then rebooted, the same old hang was back in force. I tried plugging in the Canopus to the Vista laptop, but that still hangs too (again using VideoStudio 12). Note that I first installed Ensoft's EnhancedDVDecoder_1.8.0_Trial and installed the "Video for Windows version" and enabled it's DV Decoder (DirectShow version) on Vista (I dl'd the Vista versions, too), but this time it didn't make any apparent difference.

*sigh*. Well, at least I got three full tapes digitized...

What should I try now?

[SHS]

Did ever stop to think that there maybe something wrong with Canopus ADVC50 it self.

[JohnnyMalaria]

So your XP and Vista are on separate machines? That pretty much rules out an internal hardware issue which leaves the Canopus or the FireWire cable

Have you tried the other direction (DV file to the Canopus)? Do you have another cable you could try?

The error message about the preview is also interesting. Do all of the capture programs you have tried have a preview window? It might be worth trying something that doesn't show you the video but simply dumps the captured video to file. To do this, you need to use GraphEdit. With it, you can create the most primitive way to capture.

I can't provide additional info right now other than you need to create a 'graph' like this:

MSDV --> AviMux --> File Writer

(I'll post back later with details)

[ambushed19]

Did ever stop to think that there maybe something wrong with Canopus ADVC50 it self.

Certainly! I've always recognized that this is a real possibility, and I have said so implicitly and explicitly. For one example, I wrote: "Without some kind of diagnostic software, I can think of nothing else to try. I don't want to replace the Canopus until I'm more confident that it's not working (it cost $200)."

[JohnnyMalaria]

Do you know anyone with a DV camcorder that you could try or someone with another PC that you could try your Canopus with. All Windows PCs come with Windows Movie Maker and the drivers necessary to capture from a DV device so you won't need to put any additional software on their system. And just about all PCs manufactured in the last 3 years or so have FireWire.

[ambushed19]

So your XP and Vista are on separate machines? That pretty much rules out an internal hardware issue which leaves the Canopus or the FireWire cable

Hello, again, Johnny, and thanks enormously for sticking with me on this!

It's true it rules out internal hardware problems, but it seems to me that we have not yet fully ruled out software issues. I've installed a lot of identical software on both machines, for example. And Windows 6 (Vista) is not all that different from Windows 5 (XP).

But I recognize that the inconsistency involved makes a hardware issue much more probable. But one thing I haven't mentioned before (because I thought it wasn't relevant) is this: I had the same inconsistency issue when I used a cheap Dazzler USB capture device under Vista on my Dell laptop. The Vista "Import Video" feature hung 95% of the time with the USB Dazzler, and worked the other 5%. I never tried the Dazzler with my XP Pro machine because it's a desktop and the source I was trying to capture was elsewhere. I don't think I still have the Dazzler, though...

Have you tried the other direction (DV file to the Canopus)?

Yep, that's what my earlier post here was about. Here's what happened: When I pressed the "DV Recording" button (the mouse-over message said: "Output the file to a DV camcorder"), a window titled "DV Recording" popped up with the message: "Setting the capture preview window failed. Capture driver error. You can stop recording now and change the setting to use DirectShow - DV capture driver, or continue the transmitting process." There was only an OK button. The program hung at that point and I had to use shutdown->restart to clear it.

But I haven't yet tried using GraphEdit, as you suggest in this reply. I'll try it after finishing my posting here and let you know what I find out...

Do you have another cable you could try?

Yes; I've now tried three different firewire cables: Two 4 to 6 pin cables and one 6-pin to 6-pin cable. I found no difference.

The error message about the preview is also interesting.

I strongly agree! I think it may hint at something important, but I'm nowhere near in your league, so I defer to you on this.

Do all of the capture programs you have tried have a preview window? It might be worth trying something that doesn't show you the video but simply dumps the captured video to file. To do this, you need to use GraphEdit. With it, you can create the most primitive way to capture.

I'll try it next, but note that I already tried DVIO with no luck, and it doesn't have a preview capability at all.

I can't provide additional info right now other than you need to create a 'graph' like this:

MSDV --> AviMux --> File Writer

(I'll post back later with details)

Great!

[JohnnyMalaria]

I don't think you've tried this yet:

With the Canopus connected, go to Device Manager and then to the entry for the Canopus. Right-click and uninstall the driver(s). Unplug the Canopus and shutdown the computer. Reconnect the Canopus and restart the computer. This forces Windows to reinstall the drivers from scratch and has been known to fix problems.

[ambushed19]

Do you know anyone with a DV camcorder that you could try or someone with another PC that you could try your Canopus with. All Windows PCs come with Windows Movie Maker and the drivers necessary to capture from a DV device so you won't need to put any additional software on their system. And just about all PCs manufactured in the last 3 years or so have FireWire.

I have a DV camcorder myself, but I'm confused about what you have in mind. Would you explain, please? Would I be trying to record some output? Recall that the Canopus ADVC-50 only converts analog to digital, not the reverse. If I'm to try it as a source, wouldn't I still have to use the same firewire capture software? I'm baffled...

Using another person's computer is not easily done, but what I can do is pull out one or both of two older desktops of my own running XP and try it there. The reason I didn't try this earlier is that one's got some as-yet-unidentified nasty malware infection that causes the machine to freeze up after about 20 minutes after I boot it up, and the other's OS is so screwed up I'd have to re-install XP Pro from scratch. I'll have to repair all that before I can try capturing on one or both of them (another reason I didn't bother is that I figured that since I couldn't get it reliably working on two different machines, a third wouldn't make much difference).

However, while I have four firewire cards, two of them are essentially inoperative (one hangs the system every time I try to boot with it installed, while the other is always ignored by XP, so it won't let me even install a driver). The third is a firewire 400 & 800 adapter that's a PCI-X card that I can only install in the desktop with the totally destroyed operating system. That leaves the one that's working correctly right now in the XP desktop I've been using all along.


(Sheesh, that's a lot of verbiage! Sorry!)

I'll have to decide which of the other two XP desktops to try to recover and then do it before I can try a third machine, so I'll leave that as a last resort. I'll try GraphEdit next, but first I'm about to see if -- by chance -- it's working right now. I'll report back soon...

[JohnnyMalaria]

The idea with the camcorder is to connect it and see if you can capture from it properly (or even just see it in My Computer). You can either put it in camera mode and just point it at something or put a tape in it. If everything behaves then it makes it more likely that the Canopus is at fault. If you still get choppy/no capture then it suggests an issue with your computers. It does seem unlikely that both computers would have the same hardware issue. If you don't have 4-pin to 4-pin cable, you can use the computer's FireWire interface as a hub. Just connect both the Canopus and camcorder to the interface with 4-pin to 6-pin cables.

Try the driver uninstall (see my previous reply), too.

Oh, and another thing to try that will help test the Canopus is to connect it to your camcorder via FireWire with a 4-pin to 4-pin cable. Put the camcorder in tape mode and, if needed, set the FireWire to DV IN instead of DV OUT (this depends on the make/model). Attach the Canopus to your analog source as usual. The camcorder should receive the DV from the Canopus and you should see the video on the camcorder's display. If this works properly then your Canopus is most likely okay (though some problems only happen with computers and not camcorders since the latter tend to be better designed as far as complying to the DV/FireWire specifications is concerned).

[ambushed19]

I don't think you've tried this yet:

With the Canopus connected, go to Device Manager and then to the entry for the Canopus. Right-click and uninstall the driver(s). Unplug the Canopus and shutdown the computer. Reconnect the Canopus and restart the computer. This forces Windows to reinstall the drivers from scratch and has been known to fix problems.

Unfortunately, that didn't fix the problem.

I tried GraphEdit and put together a basic filter chain as you suggested, but I'm not at all confident that I put it together right. It didn't capture any video, anyway. But that's all I know.

I then tried VirtualVCR with WAGged settings, and it certainly appeared to be capturing (I left the preview off). The resulting file after a short while was pretty big, but it wouldn't play, even though GSpot 2.70a declared it was a properly formatted DV Type 2 file. But when I opened it in UltraEdit to look at it in hex, it didn't look like real data at all: It was filled with zeros and FFs and FEs with almost nothing in between.

But VirtualVCR, like GraphEdit, is so highly configurable a neophyte such as myself can't be sure that the software was properly used...