Yes I rendered the clips, still have the green blobs. Video card is great, 1gb dedicated memory to it.

Any other ideas?

Thanks for response!

Either the specific decoder used in your laptop's installation is buggy, or your graphics card's drivers are buggy. Please install the latest version driver.

all driver are updated...

"Yes I rendered the clips, still have the green blobs. Video card is great, 1gb dedicated memory to it."

Uhh, rendering has nothing to do with your graphics card. You can rule that one out.

No, you are not supposed to rule that one out. His preview is also buggy, he said. So if his decoder bugs out because of buggy gfx drivers, then the final rendering will also have the artifacts. It's a valid concern.

So, you say you have the latest drivers. Now, I want you to right click on the media bin on one of these problematic files, go to properties, and see which video decoder is used to decode them. Then tell us here.

"So if his decoder bugs out because of buggy gfx drivers,"

What relationship between graphics drivers and rendering codecs in Vegas are you trying to establish? Inquiring minds want to know.

@ Tilly,
Can you upload a short sample of your original video capture on your laptop somewhere? This is kind of a strange issue, and it would be best to able to see it in the raw.

If a graphics card driver is buggy, and DirectDraw miscalculates because of that, and Vegas uses uses DDraw to display, and therefore gets the artifacts, it will then pass these artifacts on the encoder. Therefore, there's a scenario where a buggy driver CAN instigate a buggy render.

Case in point was a buggy nvidia driver a year ago, that caused Magic Bullet to misbehave too, creating the wrong output. The exact same thing can happen to a decoder via way of DDraw or Vegas, or by the decoder itself, if the decoder talks to the driver directly for acceleration reasons. And if you have decoding wrong, the rendered output will also be wrong.

While it might not be what's happening in this case, it's absolutely possible.

"and Vegas uses uses DDraw to display,'

Excuse me,

Vegas does not use DirectShow. It uses a VFW interface, period.

I Suggest you get your facts straight before making such wild speculations. End of discussion.

>Vegas does not use DirectShow, no way, no how. It uses a VFW interface, period. I Suggest you get your facts straight before making such wild speculations

You have it all wrong! WHO said anything about Direct Show????

I said Direct DRAW. Which is similar to Direct 2D. Which is what non-gaming apps usually use to display performance-critical content. Like media players. And editors.

And besides, EVEN without the usage of DD, any other API used to get some accelerated performance out of the system would be affected by a buggy driver. So the main argument above (that a buggy gfx driver can affect output) **still stands**.

">Vegas does not use DirectShow, no way, no how. It uses a VFW interface, period. I Suggest you get your facts straight before making such wild speculations

You have it all wrong! WHO said anything about Direct Show????

I said Direct DRAW. Which is similar to Direct 2D. Which is what non-gaming apps usually use to display performance-critical content. Like media players. And editors.

And besides, EVEN without the usage of DD, any other API used to get some accelerated performance out of the system would be affected by a buggy driver. So the main argument above (that a buggy gfx driver can affect output) **still stands**."
OMG, I'll just let that one stand for itself.

Tilly, kindly upload a short sample of the video captured on your laptop somewhere (MediaFire?). It will help a lot in determining the cause of your problem. Sorry for all the background noise here.

Eugenia,

Vegas does not use any hardware (direct draw, direct show, or VFW) for rendering. And it uses the graphic card for previewing. All rendering is done in software. So any driver issue with the graphic card will not affect the final render. Other programs do use (magic bullet might be one) use hardware for preview and rendering and therefore your troubleshooting would be valid. In this case, it appears to be another issue.

This looks like a capture problem.

Dave T2

Thanks, Dave.
You see, DirectDraw is output generated by the DirectShow Video Rendering filter (I thought I had that right earlier). Just checked it and that is the case.

So, access to DD acceleration (either SW or HW) by Vegas' renderer doesn't exist, just as you said. DirectX (with which DShow was originally integrated) came along a few years after the last VFW build. I'm by no means an expert, but coming from those days, I tend to remember my history pretty well. (Terms like ActiveMovie, Quartz, and MCI don't mean a thing to the younger crowd.)

Now maybe we can get back on topic. I agree with you that it is probably some kind of capture issue and would really like to see the OP's clip if she/he hasn't been turned off completely by now. Those green blobs are really strange looking. Sorry I let that pebble get stuck in my shoe.

Guys, you don't really get the logic here. Vegas, with DD or not, uses an API to put stuff on screen, to display video. I wasn't talking about the encoder! I was talking about the DECODER and HOW Vegas caches and *displays* frames. And when I say "accelerated" I don't mean nVidia CUDA acceleration, but the basic 2D one: DirectDraw, or Direct2D. And if a driver has a bug, NO MATTER which display API you use (DirectDRAW or not), you CAN get artifacts on your output -- when you push your system. So when I mentioned DDRAW, I was talking about ***previewing***, not about the encoding process. DDRAW has nothing to do with encoders.

As for the Vegas encoders being "software", everyone knows that. *However*, the encoder is FED by the decoder's output (from the Vegas "pool of frames")! And if Vegas has the wrong output because of what I described in the paragraph above, then the final render will have it too.

And besides, how do you know that Vegas doesn't use DirectDRAW for previewing? Are you a Vegas engineer? AFAIK, most editors/players in the last 5+ years do use DDRAW to display things on Windows! Otherwise it's dead slow to playback video!

As I said above, this might not what's happening here, but what I describe above CAN happen in a general scenario.

As for the case here, maybe the user needs to buy a different FW cable and retry.

Eugenia,

Sorry Eugenia. The Vegas Render does not use anything related to the Graphics card. It may use DD to display the graphics and yes you can get errors in your DISPLAY but the decoder is software. It does not pass thru the graphics card. That is why many people like Vegas, It is not tied to any hardware (video card or otherwise).

There are some editing programs that can use the graphics to accelerate decoding and encoding. Vegas does not. You can use any graphics card that your computer supports and the Vegas decode/encode will work the same. The display may look different based on the capabilities of the graphics card, but it will not affect the FILE output of the rendered video.
Dave T2

I never said that either a Vegas encoder or decoder are hardware accelerated, I'm not that daft. I've been saying that Vegas has no such hardware acceleration (regarding encoders/decoders) for years now. But you don't understand the stream of logic here, the special scenario I'm presenting.

>It may use DD to display the graphics and yes you can get errors in your DISPLAY but the decoder is software.

Yes, we know that. But IF Vegas is using the display output (that quite possibly is using DDRAW) to put frames back in the frame pool, in order to *feed* the encoder, then the artifacts will be there, in the final render! It all depends how Vegas works internally. Without the source code, we can't be sure.

And btw, if a gfx driver has bugs, even pure 2D operations can have artifacts, when the CPU or the bandwidth of a gfx card is pushed. I have personally seen such problems with buggy 2D drivers in a variety of operating systems, not just Windows. You don't need "hardware acceleration" (which in your kind of meaning is nVidia CUDA or similar) to get such artifacts on a video app, or a 2D game, or a media player. "Hardware acceleration" has many meanings, and encoder/decoder hardware acceleration was not what I was talking about. But how you blit, how you overlay, how you page flip. All these operations, are still considered "hardware accelerated" in the modern world, via the usage of DDRAW or Direct2D. And there's a huge chance, that Vegas does use DDRAW for previewing. Any other 2D video app I know does.

Do you get the green streaks if the capture's played on another PC, Windows Media player or any other player?

Thanks!

Thanks to all the replies, sorry I have delayed getting a sample video to you guys to further help...been busy at work, but I appreciate everyone's time and ideas on how to fix this issue.

I have uploaded a small clip of the distorted picture, no green blobs in this specific clip but they do show up on the same video clip, just edited down a bit, but you can see the distorted picture to better give you an idea, i hope.




and another video

I seemed to have missed what the original file format was, and what you were trying to render it to. Any chance of making a native clip available so we could work with it ourselves? Cin

Any other ideas?

Did you buy a new cable and re-capture the same footage?

OK...I got a new cable in, highest quality...same distortion when capturing video.

I tried saving as different formats still have the same problems....

Any new ideas are welcomed...this is pretty frustrating