Print to tape quirck - really quircky

Caruso wrote on 1/4/2002, 2:09 PM
I have a project greater than the length of any of my available DV tapes which I am passing through my camcorder to my SVHS VCR. I, therefore, want to make use of the manual device control option. This option has been acting up when I print from the timeline (see my earlier posts regarding that problem), so I have opted, instead, to load the files in the batch window in Vidcap30's print to tape dialog.

VV30 prints to my vcr flawlessly except that, instead of terminating as I would expect after printing the last clip, it skips back to a point near the beginning of the first clip (there are six cips in this project), and records most of the production over again at least once before finally terminating.

The good news is that I can work with the output, I simply have to put my vcr into record mode to blank out the extra footage.

This is, of course, annoying and time consuming, and, for one who wants everything working properly, quite disturbing.

My system is a 900 mhz Compaq running WinXP Pro with plenty of storage space (FAT32 and NTSF). Memory is 128 MB 100mhz.

Vegas was running fine on my machine until I restored/re-installed WinXP. I have now restored/re-installed XP several times in hopes that that would solve my problem, but, so far, no joy.

Anyone else have experience with this problem? Any solutions?

Thanks.

Caruso

Comments

deef wrote on 1/4/2002, 4:11 PM
Hmmm...is this reproable?

So you have disabled DV device control and then are using the Record on Device button to output DV thru a DV device to a VCR, correct?

If you simply hit play without going to the device, does it properly stop at the end and auto-go to the beginning with paused-footage?

You might want to try enabled DV device control, since it doesn't matter with this approach, and then manually kick the VCR into record and then use the Preview on Device button to output DV and then use the play button to start feeding the DV out.
Caruso wrote on 1/4/2002, 5:21 PM
When I selected the last clip in the cue and pressed play (ok, I cheated by moving the scroller towards the end, I mean, that's a lengthy clip to sit through), it reached the end, skipped back to the beginning, started playing again.

I was only able to produce that occurrence one time.

Your suggestion to use device control raises one question (the answer to which I'll determine soon enough, I guess), but, VV30 seems to maintain fairly high awareness of the device . . . won't let you select device control if the record tab is set for write protect on the cassette, for instance. What will happen to my print session (that portion I'm passing through to my VCR) when my camcorder tape reaches the end and the machine jumps out of record mode . . . how will Vegas react? Will it continue sending the signal out over the firewire?

Just curious.

More curious, really, as to what's going on with my VV30 software. I wasn't having any of these problems early on.

Thanks in advance for your assistance.

Caruso
just4fun wrote on 1/6/2002, 3:34 AM
I was doing some security updates on my W2k machine and some registry adjusting for security reasons and after restarting and going into Vegas things got pretty 'quirky' on me. I reinstalled Microsoft's videcapture update and it restored all lost features. I had lost device detection and got quirky prints.

You've probably already done that 4 times, but it never hurts to suggest.
Caruso wrote on 1/6/2002, 5:35 AM
I did a repair reinstall of XP yesterday. The really nice feature of VV30 (IMO) is that in the most critical, problematic area of print to tape, one has several approach options available. I was able to load my project clips into the batch area in the Vidcap30 area and print to tape successfully that way. The only real adjustment I had to make was to create a mini project containing the opening test bars, render it, and add it as the opening clip in the list. Worked out fine.

That project is done (at last!!), and I'm moving on to new stuff. I'm hoping that clips captured, edited, and rendered from the current installation of XP will not be affected by the print from the timeline bugaboos I ran into as described in this thread. Will let you know.

Thanks for the comments.

Caruso