[Big Bad bill]

First of all let me say that ChicagoBobT was right all along. What I needed to do was isolate the problem. I did this by selecting those few frames in each clip that had the artifacts problem and then right clicking on the clip, selecting properties and then checking “Reduce Interlace Flicker”. This got rid of 99% of the pink.

Next let me apologize to all of you Vegas Pro users for slandering the new V8 by intimating that that there was something wrong with the avc application which cause the program to abort while rendering. Turns out mine was a hardware problem all along. My machine is a home build (Asus Striker Extreme, 8800gtx, Ocz 2TA1000VX22Gk (4gb) with Vista 32 home premium. I had the memory set to 4-4-4-15. By changing this to 5-5-5-15, the problem stopped almost entirely.

I’m now 10 days into using Vegas Pro 8 and liking it better every day.

[Big Bad bill]

Well, darn! Pink is back! If you’ll recall, when I tried this before it knocked me clean out of Vegas (2X). But this got me to thinking, I rendered a whole hour before so what gives? It seems you have to go to File (the Sony plugin isn’t visible when you use Ctl – M) and then “Render as” and then you’ll see Sony AVC(*.mp4,*m2ts,avc).” Every time I left it on this settimg plus the default “Blu-ray 1440×1080” it aborted Vegas. To cure this I went into “Custom” and to “Video” and changed the “video format” from AVC to AVCHD and it worked. Or at least it let me run the render program. It’s just too bad that at the end-of-the-day, the result still had a lot of pink stuff in it.

Here’s hoping that Sony gets around very quickly to fixing all this. I’m looking forward to being able to burn Blu-ray disks with their plugin.

[Big Bad bill]

It came with Vegas. I just tried to use it again (the Sony AVC plugin) to re-render the small segment I’ve been working with to see if it was the 32 bit thingie all along. It shut Vegas down two times in a row (renders for maybe a minute or so), so yes, I’d say it’s still a bit buggy . . . I’m taking a break right now, so catch you later.

Thanks again for your help.

[Big Bad bill]

I’ve done just that, zeroing in on just one minute of video that had the worst problem. (The pink artifacts appears elsewhere in the video, but if I can cure it in one spot hopefully . . .) Bingo! By going to MainConcept AVC/AAC (mp4) instead of the Sony plugin, I did eliminated the pink . . . but got another problem in its place. Now I have brakeup bands running accross the newly rendered segment in several places. Wow! I just fixed this one as well by going to 32 bit from 8 bit (read that somewhere in this forum – also).

Sorry about crying wolf. I’ve just been using Vegas Pro 8 for about a week so I’m definately a newby. I’ve always been an Adobe Pro user and the transition has been a bit rocky, but things are looking up. I think I’m going to like this new editor.

Thanks again for your help.

[Big Bad bill]

And yes, it was the m2ts files I can’t import or open. When I go to the file “open” there is a listing for “All Projects and Media Files.” Scrolling through this list I find no reference to m2ts files. For those of you who aren’t having a problem, is there a listing for “m2ts”?

[Big Bad bill]

I’m having the exact same problem (Vegas Pro 8 won’t import m2ts files–unsupported format). Is it possible that the program didn’t load the plugins (under: Sony\Vegas Pro 8.0\FileIO Plug-Ins\ there is a file called m2tsplug)? Help me out here fellows, I’m in way over my head.

[Big Bad bill]

I have found the solution to the problem. Just go to https://thejevans.com/halo2errorfix.aspx Follow the instructions and remove C++ 2005 and then run the Vegas 8 installation. Works fine!

[Big Bad bill]

I am running Vista 32 and I am getting exactly the same problem as set out above. Seems to be a problem removing the old C++ 2005 so that the Vegas Pro 8 can install a later one. Hope someone comes up with an answer soon. I’ve spent two days trying to figure this one out. If you do comes up with an answer please let me know.