I think "Print to Tape" function had bugs that were corrected in version 3. As a side note, VF2.0 had a sync problem with "print to tape" also (corrected in VF2.0c). VV version 3.0c, (downloadable from this site) may fix your problem? If you are unclear what version you are running, go to the HELP-->ABOUT menu and check there.

Here's a list of bug fixes in 3.0c:
http://www.sonicfoundry.com/download/step2.asp?DID=375

Thank you for your quick replys. I am runnung P4 1.8G 512meg 7200 drive and Vegas 3.0c. I am using the same drive for video as for other apps and while I know that can be a problem I sometimes think that is an easy out as an excuse. I have 80 Gb drive with about 30% used.
Any more ideas?

Sorry, forgot to mention I was running XP.

Okay FF - I'm not that IT savvy, but from what I understand, having a second, third or even fourth HD for video activity is not just about having plenty of space for the large video files we manipulate, but it is more to do with the type of activity that our "system" hds have to perform while at the same time having to place and manipulate those "lumpy" DV-avi files back to itself - yes?

I've got 4 external hds - if I can get away with it I don't now do any "dumping" or managment of DV-avis or whatever back to the system disc. I believe my system is becoming more and more stable as a result AND as I use the various s/w options I have been bringing together. I try out a piece of s/w, see if it works and then move on. While I have been "gathering" this software, there has been more demands being made on my system, registry, ram, ram managment etc etc. As I say, I aint no IT techie, but it seems sensible to remove as much of the intensive activity a hard disk MAY undergo as much as I can - and let/allow the system disc free reign to get on with what it is good or better at doing - yes?

I suppose what would be really neat is if one of our more IT savvy colleagues was to post some "typical" data that would indetify the type of "strain" a hard disc undergoes in normal circumstances AND then compare this to the need to access and manipulate small or large DV-avi files WHILE at the same time taking instructions from Vegas Video. This in turn might identify the potential "mis-writes" or potential error creation resulting from a hard disc under "strain" [my word!].

Nothing like an imperical approach to solve and resolve a knotty problem - Sir Peter Medwar "Art of the Soluable" did it for me - a good read!

Grazie

Okay,
Do you have your VV on the main system drive and only put video on the other drives? That is do you capture to another drive and render to another drive. Do you then print from another drive? Your VV is not on the same drive as your video files? Are your drivees USB, firewire connected or what. External I assume!

Here we go - good questions to clear this up:

1. "Do you have your VV on the main system drive" - yes.

2. "and only put video on the other drives?" - mostly yes, unless I need to be out and about with this laptop to do very,very short range stuff. Then back to base and upload to one of the externals - yes?

3. "That is do you capture to another drive and render to another drive." - I've exeprimented in both directions. I've captured and rendered to same AND to different drives. There could be a "trade-off" doing this as the hds will, in a sense need time to talk to each other - yes? I don't have imperical data to support either of these options.

4. "Do you then print from another drive?" - as I said above, I've experimented with both options.

5. "Your VV is not on the same drive as your video files?" Correct - but with the caveat that I DO put my VV project files on my system hd - they are small and provide a "walk-away" option for removing my laptop from my non-travel freindly MAXTORS - yes?

6. "Are your drivees USB, firewire connected or what." All external. All firewire. All daisy-chained together.

I hope this helps. Playing around with the "configuration" of these drives was an experience that showed me the adaptability of firewire. So far so good. I've used the 4 external firewire drives extensively with VideoFactory, stable. I've recently upgraded to Veags Video and have had some prelimenary valuable and successful results in this direction - drives holding together, slamming and splashing avis all over the place - doesn't appear to have hassled them at all.

The one question you haven't asked is - what speed are your drives? They are all 7200rpm.

Apologies that I can't give you any more imperical data - as I say I aint no IT techie. But if it works - hey . . . .

Please get back if you have found the above logical and understandable - yes?

Regards,

Grazie

Hi firefighter,

This isn't going to solve your problem, but...

I don't think it's got anything to do with the drives.

I'm running Win2000Pro on an AMD 900, 512MB, 40GB 7200, and a 40GB 5400 HD(used only for storage of finished rendered video files), 64MB Video, 4MB video (on second monitor), and a cheap ebay special ($20) Firewire card.

I have NO problems printing back to DV. I have done this SEVERAL times. On a system of this size, it shouldn't matter if anything is running in the background, but I usually don't have anything other than the usual running anyway.

How about your Firewire card. Is it the culprit? Cheap or not, there could be a problem there.

Neil

I am using VV 3.0a(107).

I have also used print to tape on a P4 1.8 XP Toshiba laptop, 32MB GeForce, 60GB 7200 HD. Playback isn't all that great (jumpy), but PtoT worked fine. Again it was VV 3.0a (107).

Hmmm.......


Neil

VV 3.0c here.

Hmmmm . . . too - gnfoster. Maybe this is it - yes?

Grazie

Very Possible.

I have seen other here before having different problems and using VV 3.0c.

Not saying that's it, but "if it ain't broke don't fix it". I'm sticking with VV 3.0a (107) until it doesn't work anymore.

Not sure if you can go backwards without uninstalling, and don't know what problems THAT might incur.


Neil

I had similar problems long ago printing to tape and the culprit was my firewire card. I've had total success with a card bundled with Pinnacle Studio 7.

FWIW
Michael

gnfoster: the biggest consideration is that .veg files saved in 3.0c will NOT open in previous versions of Vegas, so in effect you can't ever go back. But, i would still recommend the upgrade. 3.0c fixes many problems and it appears to run very well for almost all users.

Chienworks - sorry to butt in here, But , is the Vegas server having its oil changed or tyres replaced? - Just gave an email colleague an option to view my [ yuk yuk ]masterpiece over there. Don't look to healthy - boo hoo! Any news? - . . . This message will self destruct in 4 seconds -Bogn-Bong "Thank You!" . . . .

Grazie

Grazie: are you referring to vegasusers.com? It seems to be running fine for me. I'm watching your Wembley video right now and it's downloading fine. There have been 21 successful video downloads in the last 45 minutes.

Yast - Chienworks - I got all panicky - DOAH! I should know better by now - Sorry for the intrusion on this thread - Grazie

promise i' l l keep very - q u i e t . . . n o w :0

I've been told and experienced that:

1. Editing from a firewire drive can cause issues because of the read/write speed not being as fast as an internal drive

and 2. A dedicated hard drive for video/audio only will prevent glitches. Using a system disk for both purposes is only asking for issues. Even if it's partitioned, it's only reading from one hard drive needle, which is going to need to access files or what not during a burn. I would suggest getting a large internal drive.

Yes, very understandabel, and thanks. I didn't ask about the drive speed-I just assumed it to be 7200 or faster.

Well, I have disconnected all my usb connections. Emptied my start menu. Defrfragged. stopped all background programs. Removed the stupid Dazzle device that was sharing the IRQ with the IEEE card. Made sure DMA was engaged. And I still have the print to tape problem. I get blank spots (blue screen) in varying spots. I get the same thing if I try to "Preview to device". I have been told that the "blue screen" seems to be a sign of an IRQ problem. Anybody know anything about this. Apparently my IEEE (TI) card is still sharing IRQ9 with a USB card. I've been told I need to physically move the IEEE card. Can this be?? Help!

FF - I'm truly sorry to hear about your ongoing problems. If you haven't already lost patience with the process yet, is it possible for you to try to PTT to another Cammy - only a thought. Can you also try Capturing to from and from that other cammy as well. I'm starting to run out of ideas/fixes/solutions very fast. I'd really like to know if the DV hardware is playing up - yes? If you could also try your cammy on another set-up - yes? - Oh yes another thought is, have you got MS MovieMaker to try your luck with?

I'm trying!

Best regards

Grazie

Hi Firefighter,

You may have to jump through a number of hoops to get the FW card IRQ isolated... XP has made this a real challenge.

If your usb card is sharing, you might try removing that, just to see if it resolves the issue. If so, then you can take the odyssey into XP-IRQ land.



HTH, MPH

Tips:
http://www.martyhedler.com/homepage/Vegas_Tutorials.html