View Full Version : Vegas 8 issues


Hugh Mobley
October 9th, 2007, 09:17 AM
It took about a month for Sony to get back to me with thei regarding all the issues with the new V8

Thanks for replying.

There will be an update to Vegas 8.0 coming out shortly. Please download it when it is available from the link below, and let me know if you continue to have problems:

Jeff Harper
October 12th, 2007, 01:44 AM
I have been biting my tongue, but Vegas 8 is the buggiest major software program I've ever used. I zeroed out my hard drive, did a clean install of windows and installed everything in a precise order, etc etc and still it has bugs.

I will be happy to install the update, thank you.

So far, not using the Titler, the biggest advantage I have found with 8 is it seems to render faster...but I haven't actually timed it...can anyone confirm?

Graham Bernard
October 13th, 2007, 12:44 AM
. . . but Vegas 8 is the buggiest major software program I've ever used.

Wow! That's going some!

Anyway, its not been my experience, 'cos I use VPro8 daily. No major glitches here. And definitely NONE that would require a "clean install of windows"? I think I would be truly annoyed. I'd like to know what your system is using to work? HD space? Are you editing on system drive?

Actually if the newer update gets right for you that which was going wrong, then maybe it was a clean install that did it? See? In any event, we wouldn't know either way.

What have you had go wrong?

Grazie

Jeff Harper
October 13th, 2007, 03:11 AM
Yes, that was a strong statement I made...but the single thing that bothers me the most is the pics and peaks on the timeline disappear when I toggle up or down the timeline, and I have to wait for them to rebuild, its like it can't keep up. I do edits where I am moving back and forth a lot during certain stages of the edit, and this is a hassle. Also, the program will freeze up (not crash) and sometimes it will catch up, sometimes I have to restart...needless to say I save my work often, but I always have. It's these little things that bug me quite a bit.

I run a Dell Precision with a Q6600 lots of ram and I use a 10K raptor drive as my work drive, and I'm not doing HD.

Graham Bernard
October 13th, 2007, 07:48 AM
I run a Dell Precision with a Q6600 lots of ram and I use a 10K raptor drive as my work drive, and I'm not doing HD.

I meant what/how much HD=hard drive space do you have. Or are you saying that you have a separate media/work drive? Or are you doing everything on your system drive? And what is a 10k Raptor drive? 10k, what ever it is, it sounds kinda tiny?

And no, you really shouldn't be getting what you are saying. And again, I really don't think it is Vegas either.

Not being able to zoom up and down the Timeline is such a very basic procedure, and if Vegas was not doing this, then, I would have thought that the clamouring for a fix would have been heard right around the planet! Well, it isn't. And as you have pointed out, you are not doing HD.

Let's hear how much free hard disk space and whatnot. Yes?

Grazie

Mike Kujbida
October 13th, 2007, 08:46 AM
...but the single thing that bothers me the most is the pics and peaks on the timeline disappear when I toggle up or down the timeline, and I have to wait for them to rebuild, its like it can't keep up.

Check under Options - General and make sure that "Build peaks for visible events only" isn't checked.

Ian Stark
October 13th, 2007, 10:06 AM
10k Raptor drive = very fast. 10,000 rpm to be exact, compared with the typical 7200 rpm and lower on most drives.

I have a 150Gb Raptor as my system drive. At this time I think 150Gb is the largest capacity Raptor available but I may be wrong.

Jeff Harper
October 13th, 2007, 11:01 AM
Mike, good suggestion, but it is not checked....that was the first thing I thought of too...yes Graham, a work drive is a drive for storing the footage I am working on at the moment...I then move it off when I go the next project. My sytem drive is a small raptor meant for OS only. And while they are not SCSI like I used to run, they are fast enough.

Marc Salvatore
October 13th, 2007, 12:05 PM
I've been having lots of crashing in Vegas 8 as well. Everything was working fine for straight cuts and multi cam editing but as my project started to grow in size (25 minutes with over 500 files) and when I began to bring in quicktime, psd and jpeg files and do various effects work I started crashing multiple times daily. It's a real pain.

I should also note that I am using Cineform Neo files in an HDV 1080i project.

Marc

Jeff Harper
October 15th, 2007, 06:17 AM
I absolutely do not recommend this upgrade unless you need a feature 8 has over 7. I had decided to hold off, then decided that a clean install over a new would eliminate all of the issues. I was wrong.

It is as if the "Build Peaks for Visible Events Only" is checked, so I checked the box, shut down and restarted and then unchecked the box, but that didn't do any good either.

And Graham my hardware is more than adequate, and my work drive is only half-full, and it is defragmented. That is not a bad question though, because I have worked with an overly full and/or fragmented hard disc drive and seen similar issues.

7 worked fine, I wish I would have stuck with it.

Willard Hill
October 15th, 2007, 01:35 PM
I have encountered another issue concerning crashes. I have captured several tapes as m2t files. Some were shot with an XL-H1 in 60i and some with a Sony HVR-A1u. All were captured using the Sony to save wear and tear on the Canon. Each tape was captured to a separate veg. file. I scroll through the timeline and log the scenes on an Excel spreadsheet. There are no problems with crashes with footage shot with the Canon, but Vegas 8 crashes repeatedly on two tapes shot with the Sony. If I open the same files in Vegas 7 they work perfectly. When the problem occurs a large green band goes through the scene and the following error message appears: "Vegas has encountered a problem and needs to close."

David Rice
October 15th, 2007, 03:54 PM
I stopped using 8 for the same reason. If I use newly captured footage with my Canon Hv20, no problem.

If I mix older footage on the timeline that was shot with a Sony HC1, Sony HC3, and Canon HV10, Vegas 8 crashes.

I'm staying with 7d for now.

Mauritius Seeger
October 15th, 2007, 09:26 PM
god, i hope sony get their act together and fix these problems. it would be such a shame if vegas dissapeared due to buggieness. it's currently the only program i know of that justifies using a PC's

Matt Bishop
October 16th, 2007, 07:53 AM
This is very interesting to hear. I personally have been using vegas 8 pro for 2 months now,every single day, and have yet to run into any problems at all. I upgraded from 6 and everything has been working just as well and much much faster. I think your computer build has a lot to do with it. Not that there is anything wrong with any of your setups, but this software just isn't working well with it all. I'm using a dell XPS , windows vista, loaded with RAM and about he fastest processor you can buy right now and it's performed flawlessly . I also have 8 on 2 other computers here and have had no problems with them either. Similar setups, all dell built computers.
good luck to you all! I have faith that sony will correct any issues.

David Rice
October 16th, 2007, 08:10 AM
Matt,

Have you tried working on projects that mix multiple video clips on the timeline from a combination of different Sony and Canon Camcorders?

I have a Dell XP, 1.5 gig of Ram, on a computer that is designated for Vegas only. I also use 5 different external hard drives. When I mix footage on the timeline from the above Camcorders, Pro 8 crashes.

Steven Davis
October 16th, 2007, 08:28 AM
My two cents, I have Vegas 6 and for no good reason I have had the same crash for the past couple of days, it's random, sometimes caused by ctrl-z and typically doesn't 'save' before crashing, so I could lose 30 minutes of work. So I've been hitting ctrl-s after almost every cut. Very annoying. I think in it's history, Vegas has been buggy, there are many error reports on this board.

And it has been my experience when you contact Sony about errors, typically you get a response that is very broad, probably on a cue card, and from someone who may or may not know how to turn their computer on by themselves. But that's just my opinion.

Marc Salvatore
October 16th, 2007, 12:01 PM
Matt,

I agree that it can be computer specific, but it can also be the type of projects we work on. I can work in Vegas 8 for days with zero problems but when I start adding quicktime, psds, effects, over 500 files etc. things start going haywire. I using a pretty beefy system (dual Zeon, 4 gigs ram, XP Pro) and this system worked fine in DV on a more complex project in Vegas 7.

Regards,

Marc

Jon McGuffin
October 16th, 2007, 09:57 PM
This is indeed interesting to read...

I purchased Vegas 8 Pro the day it was made available via upgrade and it's been sitting on my desk ever since. I knew, without any of these posts, it was going to be buggy as virtually all software suffers from this issue upon release.

For the same reason I continue to NOT recommend running Microsoft Vista if you can help it, it's never really a good idea to run software upon it's initial release. It's just a fact that, unfortunately, the best beta testing for these software developers occurs in the first 6 months of a products release date. Once they release an update or two, I'm sure it'll be fine.

I do agree with the few posts in here though regarding this being one of the better products made available for the PC. Frankly, I view Vegas as kind of a champion product for the PC and am really hoping Sony can continue to develop and enhance this product. It really is a shame when this software is released and is buggy enough to make the PC look bad when standing up against NLE's like FCP.

Jon

Willard Hill
October 17th, 2007, 07:55 AM
I remember when Vegas 7.0 came out that it would not build audio peaks on footage taken with the Sony HVR-A1u. Version 7.B fixed that. I hope Vegas 8 follows the same pattern and gets the bugs ironed out. I am one of those that experience the black frame issue with m2t files in Vegas 7 and this does seemed to be fixed or greatly improved in 8.0. It works perfectly with Cineform but I am working on a very long project and the large files take too much disk space.

I had the problem quite frequently with Vegas 6 that Steven Davis mentions. It was usually brought on by multiple undos. It seemed that if I gave it a bit of time between pressing the ctrl z and the ctrl,alt,z keys that it minimized these.

7.d was the most stable version that I have ran in my short time of using the program. Overall I am extremely pleased with it. Let's just hope they get the issues with 8.0 resolved.

Edward Troxel
October 17th, 2007, 02:54 PM
Vegas 8.0a and DVD Architect 4.5a were just released!

http://www.sonycreativesoftware.com/download/step2.asp?DID=764

http://www.sonycreativesoftware.com/download/step2.asp?DID=766

LOT'S of changes in Vegas Pro 8.0a!

Jeff Harper
October 17th, 2007, 02:57 PM
Thanks Edward!

Ian Stark
October 17th, 2007, 03:07 PM
Time to take ProType Titler out for another spin then! Thanks for the heads up, Edward.

Dave Haynie
October 18th, 2007, 12:08 AM
I have encountered another issue concerning crashes. I have captured several tapes as m2t files. Some were shot with an XL-H1 in 60i and some with a Sony HVR-A1u. All were captured using the Sony to save wear and tear on the Canon. Each tape was captured to a separate veg. file. I scroll through the timeline and log the scenes on an Excel spreadsheet. There are no problems with crashes with footage shot with the Canon, but Vegas 8 crashes repeatedly on two tapes shot with the Sony. If I open the same files in Vegas 7 they work perfectly. When the problem occurs a large green band goes through the scene and the following error message appears: "Vegas has encountered a problem and needs to close."

Neither Vegas 7 nor Vegas 8 is adept at dealing with HDV captures that have dropouts... or even SD stuff with dropouts, in some cases. I recently found that Vegas 8 was getting real crashy, but noticed it was related to one capture I had from my Canon HV10. Removing that pretty much eliminated the problem (well, other than the known issues reported in the Pro Titler and multcam, both of which I easily found on my own).

Not that Vegas SHOULD crash on HDV errors, but I think it always has, and it stands to reason that faster HDV performance in Vegas 8 might well come at the cost of some error checking. Double check the video independently to see if there are dropouts, and if so, try recapturing the tape (I've found HDVSplit more reliable at HDV capture than Vegas7; I haven't tried Vegas8 yet).

Dave Haynie
October 18th, 2007, 12:14 AM
One really annoying "feature" in Vegas 8, which seems to be new... I'm seeing some difference between the displayed audio waveforms and the actual audio, here and there.

On my current project, I'm synching up two HDV cameras, then editing as a video multitrack... in theory. What I found was that, while I thought I had matched the audio, I hadn't really. The truth was revealed if I zoomed way in... I would see correct audio waveform display for both tracks. But when zoomed out a bit, one waveform display is considerably off... like by a few seconds or more. Ouch!

Not a big deal, once it was all locked in, but I've been using the Vegas audio display for multi-cam and field recorder sync for years and years, and never seen a problem like this until Vegas 8. Both tracks are HDV MPEG-2 transport stream files.

Lars Siden
October 18th, 2007, 06:33 AM
I have noticed that having the Matroska Splitter and/or FFDshow installed can mess up the NLE:s. I don't have Vegas 8 - But I have PPro CS3 - and there I had all kinds of strange behaviour before I uninstalled all "extra" codec stuff that I had.

For instance PPro would allocate ALL memory available when opening a m2t file when I had "dscaler" and ffdshow installed.

// lazze

Willard Hill
October 18th, 2007, 10:43 AM
Dave
I think you are on to something there. I trimmed both of the captures which caused crashes in Vegas 7 and then did the save-as thing to make copies of the scenes in use in the timeline and then deleted the original capture. In both cases if I place the trimmed copies in an 8.0 timeline it will now play o.k.