Why is this happening?
 

Feel free to move this to the correct forum.

I've done a music video and when I try to render it out
in interlaced mode with Vegas this happends (see file)

When I render in deinterlace it stops. I can't really tell
what's wrong. I've tried almost every thing I can think of
but nothing hepls exept deinterlace it.

Perhaps someone out there have had the same problem?
(oh, and changeing upper/lower feild order does not help)

http://www.atamashi.com/glorious/hard.avi

If you could post a few stills that would be more helpful - I for one can't download 20 MB right now.

But 99% of the time what people think are interlacing problems actually disappear when played on a normal TV set, so try that to be sure there's a real problem.

I've tried that. Looked the same.
Well, I cant post stills because it's a motion problem.
You have to see a movie clip to understand the problem.

If it is an interlace problem, a few stills should show the problem. Do you have a field order choice in Vegas? If so, swap the order and see what happens.

err... one thing to remember is that if u use an interlaced method, then render in anythign LESS than "best" artifacts WILL be noticable,
Im not about to downlaod 20mb, but if this is the issue (interlacing) there are many ways around the issue

Thanks very much Jim, you've given me hope. I have a similar setup as you and I'm getting an error when capturing; however my error doesn't show up until after stopping (very frustrating when I'm trying to capture a full tape!). I started 2 threads on the SoFo site; one about the above and one about latency in my external monitor,but both seeming to be a firewire issue. I'll try your remedy and report back.
Thanks again Jim,
Randy
BTW, I wonder if having an additional firewire card or 2 (as opposed to using one 3 port card) would allow us to use the 3 devices concurrently...just a thought (or shot in the dark)

The error after stopping also happened to me just FYI.

Well that's very encouraging then; I've got a bunch of different capturing to do tomorrow, I'll unplug everything but my capture device and keep my fingers crossed. BTW Jim, I edited my post (before reading your latest, just in case you missed it) and wondering if 2 or 3, 1-port firewire cards (as opposed to one 3-port cards would save us from having to plug/unplug everything. I should also mention that I never had this problem on my old PC which reinforces my suspicions of the firewire card.
Randy

Randy,

The results of my last capture test (3 seconds ago) confirm that it's the canopus DV / Analog converter that's the bad guy for sure. I left my Firewire hard drive on and it didn't interfere with the capture process.

I now own 2 firewire cards from all this trial and error and they're both good so maybe I'll try that suggestion of yours to put them both in the computer and see if I still have conflicts.

Jim

Please let me know how it works out Jim.
Thanks,
Randy

Randy,

Your theory proved correct.

I installed the second 1394 card and attached the canopus DV/Analog converter to that. Capture worked just fine when my camera was attached to the other 1394 card ! I even powered on the Canapus and capture still worked flawlessly.

Mystery solved. I guess I'll keep both 1394 cards and run the setup as it sits.

Great...I'm off to buy a new (1 or 2 port) firewire card!
I'm hoping this also has something to do with my external monitor latency.
Randy

The IMPROPER way is to Ctrl-drag the edge of the scrolling media to the desired length. It's faster and seems to work well. It may make the render time a bit longer, and if you get flicker or anything like that you should probably stick to the PROPER method.

I did a test for you (I don't normally use credit rolls much) I put one proper and one improper credit roll alongside each other (using track motion squeeze) and rendered to PAL DV. The scroll was 40 seconds and .250 playback respectively. No difference in rendering quality was discovered.
The default font even looked so good after the squeeze that I would recommend using it like that.

Of course, if you need to go lower than .25, you either have to, once again, do it the "correct" way OR apply a velocity envelope. Since you have to have the screen open to enter the text anyway, I've found it just as easy to type in the correct number to begin with.

It WOULD be nice is there was an option for the number to match "the length of the event".