Perrone Ford |
December 25th, 2009 11:58 AM |
Quote:
Originally Posted by Jim Snow
(Post 1464605)
There is something else going on in this thread and I'm not sure what it is. Maybe it's nothing more than a "lack of sleep and a purple brain." The most likely source of many of the "problems" mentioned in this thread is probably between the keyboard and the chair.
|
Entirely possible. But evidence seems to the contrary.
Quote:
Originally Posted by Jim Snow
(Post 1464605)
The ONE thing I do know is that I use Vegas every day and I don't see problems like those eluded to in this thread. If these problems were Vegas itself, they wouldn't selectively appear in only some systems. A particularly vulnerability that Vegas has is that it can be run on a wide variety of systems - - including those that are "whacked" by the user none of which would ever admit that they don't know everything there is to know about computers.
|
I'm glad you don't see these issues. What are you editing? What are you dropping onto the timeline, and how much of it? Also, what version of Vegas are you running? I have 4 systems running Vegas. The most bulletproof is the one running 8.0c on XP. It just works. The most buggy is the one running 9.0b/c on Win7.
I'm not sure what "whacked" is, but all my editing systems are installed the same way. Fresh OS install from scratch. Load NLE, load NLE support programs (GSpot, VLC, VirtualDub, Mpeg Streamclip), patch system. Done. I even went to open a help file on the Win7 system yesterday for one of the apps, and it couldn't because I hadn't installed Acrobat Reader. I run these system CLEAN.
Quote:
Originally Posted by Jim Snow
(Post 1464605)
i would encourage those who are reading this thread to realize that it's a good idea when reading a forum to look for the main body of understanding from a wide range of people. This is the best way to avoid being mislead by either fan boys or people with an "alternate" intent.
|
I would also encourage those choosing an NLE to speak to a variety of users. Visit the forums to see what problems users are having, and what their complaints are. Find out who's really using the software weekly or daily, and how they are using it. Find people who are using it like you plan to use it. If you're cutting feature films, talking to someone who's doing broadcast is not necessarily going to be the best reference. If you're editing home video for youtube, then talking with people who are editing long-form conferences or weddings is probably not going to be your best source of info.
I've worked with Vegas now for going on 6 years. I've cut everything from conferences, to promos and spec commercials, to movies on it. I've had my issues with it over that time but all had workarounds. The lastest stuff I and others are seeing in the newest versions is far more challenging because a lot of times there is no viable workaround. I've championed Vegas in the past, and it's still a good tool for many, and for certain kinds of work. But it's been a letdown for some workflows. Particularly those originating with mpeg4 based material.
|