I found the solution to Vegas Pro 8 and Vista

Coonass wrote on 10/26/2007, 10:46 AM
Simple as can be........
Vegas Pro 8 and Vista have serious problems.
Here's the way I solved them and I suggest all professional video editors do the same thing:
1. Open Vegas Pro 8 and save any and all veg files to EDL txt files.
2. Replace Vista with XP Professional with SP 2.
3. Uninstall Vegas Pro 8 and install Vegas 7.
4. Double check the EDL files you saved earlier. They MIGHT come up in Vegas 7. If so, good luck. If not......
5. Uninstall Vegas 7.
6. Install Avid Express Pro HD with Mojo on the XP Pro with SP2.
7. Wa La...problems solved.
Vegas Pro 8 and Vista are a joke.


MarkFoley wrote on 10/26/2007, 10:56 AM
don't let the door hit your ass on the way out.....
Coonass wrote on 10/26/2007, 11:07 AM
Don't worry about mine, worry about yours.
You're stuck with joke editing software.
I'm not.
Free at last.
deusx wrote on 10/26/2007, 11:07 AM
>>Install Avid Express Pro HD with Mojo on the XP Pro with SP2<<

You forgot the part where, after spending $3000 on that, you find out it won't run on your PC, so you have to spend another $2 - $3000 to buy avid approved hardware. And since time is money, by the time it all finally works, you have a $10 000 editing workstation that edits at 1/2 the speed of Vegas on my laptop.
Coonass wrote on 10/26/2007, 11:13 AM
I'm not too worried.
Got the AVID bundle with mojo dirt cheap brand new.
Put it on my quad core and I'm editing at super speed.
MarkFoley wrote on 10/26/2007, 11:15 AM
good for you...happy editing troll....
Cliff Etzel wrote on 10/26/2007, 11:22 AM
ROFL - With a name like Coonass - that should have been the first red flag - Avid is for those who can't think outside the box - archaic editing workflow and non-intuitive to boot.

Enjoy using your AVoID NLE, Troll.

Cliff Etzel
CorTed wrote on 10/26/2007, 11:28 AM
I understand the frustrations, as I am one with similar experiences with V8 and Vista. I really like Vegas and have been using it very succesfully and stable on the XP platform for years. I build a special top of the line box using Vista JUST for Vegas as it is now designed to run on Vista. I know that the members on this forum don't like to hear Vegas being bashed, which I completely understand, but I think it is clear that Vegas and Vista have issues that are appearently are not being addressed. The standard response is, just install XP, and your problems are gone. Since I have build my system around Vista, and Sony claims to work on Vista, I do not want to go back to XP. I love Vegas when it works, but I really want it to work on Vista.

Coonass wrote on 10/26/2007, 11:31 AM
Yada, yada, yada......
That's why the pros use Avid.
But if you do weddings and video your pets, Vegas works nicely.
I taught my dog to use it in less than a minute.
Coonass wrote on 10/26/2007, 11:35 AM
I agree, Ted.
But when trying to get any sensible response from Sony, all I get was an idiot who should be slinging burgers at Burger King.
Guy couldn't answer any questions and danced around my pinpointed questions.
Sony couldn't even tell me when the 64 bit beta was being released after they announced it.
Vegas died when Sony bought out Sonic Foundry.
jrazz wrote on 10/26/2007, 11:36 AM

What specifically are your problems with 8 and Vista? I am curious as I have one machine that came preloaded with Vista and I thought I would give it a go with Vegas 8. It captured fine, edited fine and rendered fine (From HDV to SDV) and that is all I did with it. It was a 54 minute project.

j razz
TGS wrote on 10/26/2007, 11:48 AM
This idiot is a shill. How dumb do you have to be to install Vegas and not get it? But then go out of your way to join the forum to brag about what an idiot you are?
Cliff Etzel wrote on 10/26/2007, 11:48 AM
That's why the pros use Avid

Yeah - I guess those wannabe's who produce ABC's Nightline on Vegas are a bunch of amateurs.

Cliff Etzel
CorTed wrote on 10/26/2007, 11:54 AM
j. razz,

I have been getting random crashing issues from the get go using V8. At first I thought it may be my machine so I tested my memory (4 gigs) extensively using memtest 86+ without any problems, ran various stress tests on the entire system for more than 24 hours without failures, so I feel pretty confident that the machine is OK. As soon as I run Vegas and load up a project, render it, it randomly crashes to desktop. (I mean program disappears!!)
Vista has this little gadget that shows your CPU usage and Memory usage. I have since figured out that when a project loads and consumes more than approx 75% after loading then during the render it is sure to crash at some point.
I had some rather large JPEGs in the project and after I down'resd all off them the problem went away, but only until I grew my project to this approx 75% memory limit.
It would be interesting if you could check on your Vista V8 if you could duplicate this memory constriction.
I love Vegas, and I am all for getting my problems fixed !!

jrazz wrote on 10/26/2007, 12:07 PM
Have you adjusted your RAM settings or your processor threads in Vegas? What are yours set at? And yes, large jpgs can definitely wreak havoc.

j razz
earthrisers wrote on 10/26/2007, 12:09 PM
I think Coonass is really Zippy, rejoining the forum under a new name after a layoff of a year or two. It's probably fun trying to get a rise out of forum members by poking sticks into the nest.

As for Vista/Vegas... I make my living as what I call a "Consulting Multitasker" -- in which role I use a dozen or more different, sophisticated software packages to do everything from video editing to web design to online curriculum development, to technical writing and editing, to... you get the picture.
So far, I have carefully avoided Vista, being unwilling to risk having my overly complicated environment fail to work on that platform. (Got a new DualCore2 system last spring, but ordered it with XP Pro rather than Vista.)
However, in forums like this one and in forums for other software packages, I try to follow other folks' experience with going to Vista. So I appreciate postings that have useful information about the platform, in relation to particular software packages. I might go Vista one of these days, but I'm definitely not in a hurry. It takes me almost 3 weeks to reinstall all my packages and reregister/reauthorize and reconfigure all of them, even when I simply go to a new XP system.
So... my long ramble is mainly to say I appreciate (civil) info that's posted on this forum, regarding the Vegas/Vista experience, and will continue to be informed by it.
kentwolf wrote on 10/26/2007, 12:11 PM
>>...that should have been the first red flag...

Zippy? Is that you? :)
CorTed wrote on 10/26/2007, 12:12 PM
Not sure of the exact settings you refer to but, if you are talking about Dynamic RAM preview values, yes, set them from 0 to 256.
As far as the threads tried 1, 2 ,3 and 4 ( I'm running Q6600- Quad core) sure like to use all 4 cores. All these were suggested by sony support as well.
Understand that large jpgs can give problems. This is why I sized them down to 1600x1200, but the problems did not do away.
Again, I sure would like to see a response by someone using Vista and having a project occupy 75% of memory after loading and then try to render....

jrazz wrote on 10/26/2007, 12:21 PM
Try setting your dynamic ram preview to 16 and utilizing 2 threads just for kicks.

Now, you are saying that you have Vegas utlizing 75 percent of your memory after loading. What do you mean? After loading a blank project? After loading one with a lot of jpgs? After loading any project at all (even without pictures)? Just out of curiosity, if it is the one with just the jpgs causing the issues, have you tried turning them into png files?

j razz
CorTed wrote on 10/26/2007, 12:41 PM
j razz, thanks for your replies and help. I will try your settings later today. What I mean is that after I load my project with various video files & pic files the memory ends up to be at 75%+ This is when render fails and crashes.
If I break the same project in half i.e. save the first half of the veg as take1.veg, and the second as take2.veg. Then load in Take1, memory usage maybe around 50-60% or so each. they both (without changing anything else) render fine over and over.....

Coonass wrote on 10/26/2007, 12:44 PM
"Yeah - I guess those wannabe's who produce ABC's Nightline on Vegas are a bunch of amateurs."

Thanks for the info. That may explain their huge ratings drop and why they are on the verge of being cancelled.
AtomicGreymon wrote on 10/26/2007, 2:19 PM
The transition to a new OS (especially a Microsoft OS) is always going to be bumpy. And seems to have become even more so starting with XP which, as I recall, also had huge problems with programs that worked perfectly fine under previous systems, even W2K Pro in some cases, and that was pretty close to XP.

Personally, I feel it's better to avoid Vista for now. I can't see many advantages with it for video editing... I suppose there's the whole "if you have 4GB of RAM or more" thing, but that's about all I can think. Most of Vista's new features seem to relate to horrid amounts of DRM, and making the GUI more attractive.

My cousin and I both bought new computers around the same time (about a month ago) and I installed the XP Pro license I'd been using on my previous PC while he upgraded to Vista Ultimate 64-bit. Even now, it's still causing him problems... and he doesn't even use any professional programs.

On the topic of the 64-bit version of Vegas, though... will this be a free update for current owners of Vegas Pro 8? Becuase I'd like to be able to install the 64-bit version when I finally am forced to upgrade to Vista sometime in the middle of next year.

As for Avid vs. Vegas, I can't comment. I've never used Avid... the NLEs I've got on my computer at the moment are Vegas Pro 8 and Premiere Pro CS3 (along with everything else from the Creative Suite Master Collection). Unless I absolutely need to do something in PPro (or especially AE) that Vegas can't do, I tend to stick to Vegas... it's much more intuitive and easy to use, while retaining most essential professional features; including some the Adobe programs don't have themselves (DD5.1 encoding, for instance... which requires an extra plug-in purchase to do in PPro). My only complaint about Vegas at the moment is that the interface could be just a litlte bit more modern-looking. Sony should definately take a look at that in the next major update/upgrade.

Other than that, I've considered picking up a MacBook at some point and trying Final Cut Studio in addition to the other 2 programs, but haven't done it yet.
Cliff Etzel wrote on 10/26/2007, 2:37 PM
As someone who decided to think outside the box and go with 64bit XP Pro to have all 4GB of my RAM seen I haven't experienced a single issue with Vegas running on my system. You can forget about the so called Pro AVoID apps even installing on any 64bit OS - it won't. Even Premier Pro 1.5 will install on 64bit XP Pro - albeit trying to get a DVD burner seen is another matter.

SONY Vegas, Acid Pro 4(!), Sound Forge, Cinescore, DVD Architect - all work natively for me and that speaks volumes about the quality of SONY's applications. Try to edit audio in an AVoID NLE - no can do - you have to go a separate audio editing application like Pro Tools - which I've heard has its own issues, although I can't say first hand. Vegas can handle audio editing on the timeline - that is forward thinking for digital content creation delivering to multiple distribution channels - not backwards as those who espouse traditional application suites would like to have users believe.

It cracks me up reading comments that rip on things people evidently have no clue about - making statements as fact based upon spin doctoring ad wizards.

Coonass - If you can't make Vegas work for you - that's too bad. But don't pollute this forum with your negativity - go back to the AVoID forums where they discuss AVoID issues.

Cliff Etzel
Nobody wrote on 10/26/2007, 2:59 PM
First, my admiration to those of you that are actually taking this joke thread and making something useful out of it.

Next... "7. Wa La...problems solved." Wa La? Really? (It must be that New French I've heard nothing about.)

Finally, I found the solution to Coonass. Simple as can be...

1. Click on user name Coonass in the first post.
2. Click on "Ignore Posts by Coonass".
3. When asked "Are you sure you want to hide this user's messages?", click on OK.
4. Voila (or Wa La)...problems solved.
Cliff Etzel wrote on 10/26/2007, 3:58 PM
Finally, I found the solution to Coonass. Simple as can be...

ROFL - great way to end the week

Cliff Etzel