There are no current "bugs" that you'd call "issues" although there are always things that people would like to see new, or done differently. It's likely more helpful if you list YOUR specific issues so we can address them that way. Sorta hard to prove a negative, but if we knew what you were wanting to avoid....
There's also a 30 day trial you can download. Click the Products tab above to try it out.

I used quite lot a Premiere 6, 6.5 / Canopus DVRaptor RT card setup in the past and know what you mean by hidden issues (mother board issue, memory issue, pci card issue, installation issues, mpeg export issue, strange rendering issues, plugin issues, drivers issues, titling issues, name it!...) .

So many things "were supposed to work but never worked or never worked reliably at all" in Adobe/Canopus solution that video editing was mostly a frustrating, not creative, experience.

All that is supposed to work in Vegas actually works, beleive it or not! That's probably unique in the video editing software world i know of and was really a refreshing experience for me 3 years ago... :-)

Thank you folks for the quick responses and I apologize for the late one. I started a few years back with my Hi8 camcorder using Studio 7, then 8. I wasted at least a full year of my life with that program. I tried several others, but they just didn't feel right; either too much handholding or I had to go 'around the world' to do something that should be very simple. Then I found Magix Video Deluxe. It was quick, made sense most of the time, but since it originates from Germany, the translation of the documentation was awful. Video Deluxe was upgraded (at least they called it an upgrade) to Movie Edit Pro 2004, which is what I have used up until this point. My issue this week was a problem with importing AVIs transferred from my dvcam. They would import, but I noticed a choppiness in some of the captured clips. Stepping through frame by frame, I found that either some frames had been duplicated. I know it was a problem with MEP because I opened the same AVI in other programs and there was no duplication of frames. I just seem to find a new issue with every project I work on.

I would just like to know any of the known issues with Vegas before I lay out the bucks for the program. Thanks again for your responses.

You won't find anything in Vegas that will stop you from editing... It doesn't crash and can edit pretty much anything you feed it with..

Not any brand new ones:

Here

Here

Here

Here

Here

Here

Here


and Here


On the other hand, Vegas has the best support forum of any on the on the internet and the color correction tools are incredible. It's capabilities, once you get used to dealing with the issues are pretty amazing.

John

Many people have reported phantom or flash frames appearing in projects. They will go away if you exit the project and then restart, but if you don't take the trouble to do that, they can end up in your rendered video. Very nasty!

Richard Hunter

If you don't need the full program, Sony also makes Vegas Movie Studio which is $99.

Buy Vegas - . .. ok? . ..


G

Well I have to chime in here because I am, after all, the realist of this lot. :)

First I am going to say that for what you seem to want to use Vegas for you will be fine and it is a wise investement. However I need to toss in a few "issues" that might affect you - here is a nice simple quote of myself from another thread:

And still those who say before Sony adds items they should fix everything that dosn't work or needs work. Things like the media managment and the black frame/gap issue that may, or may not, be related to the whole ripple issue. And one of the biggest bugs that has existed from at least Vegas 4 to 5, is the VidCap 'feature' that will not save project capture information...something so big most people didn't even notice it. (not being ironic, being truthful - I didn't even notice until I read Grazies post on the topic)

To expand on this - Spot said that Vegas didn't really have any current "bugs" that were "issues". But to be fair - Several people have complained about media management in Vegas, so that may or may not be of concern to you. The VidCap utility is pretty amazing in what it *doesn't* do, I know I was shocked. So this may be of concern to you. And the "black frame" issue is very real but no one can really put their fingers on what causes it. Once we seem to be doing the same thing someone pops in with "but that isn't what I did..." and just shoots it down. Just yesterday I was doing dialog editing and I noticed something was not quite right at one quick cut, so I frame by frame - and here is a black frame...in the final version - so I look at the version that I output in Vegas - the locked version of picture that this final color corrected/film looked/effect added version was based on - yep - Damn it to hell!!! A bloody black frame. My bad that I didn't notice it but now they have to go and do a one frame cut and re-output onto the master tape. And I had to do a one frame pull up over 4 different projects, (Dialog edit, Music Edit, Efx edit, final mix) which in my case also means I have to go in and manually re-check things because I have many 'locked' audio tracks that do not pull up/ripple because - well, the tracks are 'locked' - it is normal behavor, not the fault of Vegas. Yes, some will say that is not a fault of Vegas either because I did not check my edit before outputting, but the real issue is that Vegas even *has* this issue and people *need* to frame by frame through the entire project looking at every cut before outputting. I am not the only one who feels this way, look around on the topic. Now I dunno if this "black frame" issue has ever been truely classified as a "bug" but ceritanly it is a very real issue. (And I do believe that Spot had finally experienced this but I am not sure if it was a 'black frame' or a 'flash frame'. It was discovered on a Vegas "how to" DVD) (And by the way the "flash frame" issue is another issue all together)

Now another common "sell point" given by the cult of Vegas (joke) is that Vegas "never crashes" - not true. It does crash every now and then and some people make it crash more than others (I guess I fit into the category). I have started to point out that if Vegas were so perfect we would still be on version 1 or 2. Fact is there have been issues that caused Vegas to crash and because systems and OS's (And the 'fixes' to those OS's) vary there probably always will be. No software developer can test every single config that people use and because Vegas is *not* dependant on any sort of hardware and will run on a 'minimum' basic system it is, in reality, going to crash for various reasons every now and then. It may or may not crash for what you will use it for - but if it does crash be aware that at least one person has said that may happen. What I can not say is what might make it crash - but around here because "Vegas never crashes" the first response you are likely to get it "Something is wrong with your computer". At times this may be true however it is important to remember that Vegas it is not 100% perfect, otherwise who cares about the next version? And that goes right back to my quote above - I am one of those people who would like to see certian things added, but I also would really like to see some of the older, unresolved "issues" "fixed" first.

And, LOL, I was reading some old posts and here is another "issue" that may affect you - doing at PTT. I had forgotten this post - but someone asked about certian issues with Premiere verses Vegas. I got asked about PTT (Firewire only in this case) and I had to clarify the steps that I take - and here is what I said:

A normal workflow in Premiere 6.5 for me is to work away and when I am done hit the play button on the timeline and the record button on the deck. With Vegas it is like this - work away and zoom in to each edit to check for black frames, check to make sure that both audio and video are selected before hitting "del" on a cut, make sure the ripple is actually working, hit PTT, wait for any and all effects to render out than wait for all audio to render - even if there is nothing to be rendered audio wise - and than sit back and hope the PTT to actually works.

Notes about above quote -
~ Vegas always pre-renders all audio to *.w64 format before output to tape.
~ Vegas does not really retain "temp" pre-renders well (Version 5 might have fixed this)
~ Vegas has never played audio out via firewire unless it is during an actual PTT via firewire.
~ Sometimes, if you are not careful, if you delete something from the timeline and have ripple turned on you can create a HUGE mess as far as sync goes. You have to make sure that both audio and video are higlighted before deleting a section.

[You won't find anything in Vegas that will stop you from editing... It doesn't crash and can edit pretty much anything you feed it with..]

Unless you are win2k sp4 platform. V5 seems to crash during some tasks.

Wow, filmy, thanks for the info. And Mahesh, I'm on Win XP SP2.

Thanks for honest response filmy.

I have had the flash show up in some projects with my current editor (which required rediting at the flash points), but having a quick workaround with Vegas in exiting and restarting the project is no big deal.