Vegas 8a crash report to Sony. Can U duplicate it?

DSW wrote on 11/9/2007, 1:10 PM

OK I have done some more test now that my deadline is past. Here is what I have discovered:

My computer is a Quad Core, with two GB of ram, built on an Intel MB running XP. I have four HD all WD. One for programs is a 10,000rpm raptor 74GB. The other three are 500GB. One for Video captures, one for Digital Juice and Music and one to render to. I have an M-Audio sound card, Delta 66 with the Omni Studio breakout Box. The video card is a Radeon X1650 running two monitors One Dell 24" and One Dell 19" CRT. The computer does not have any virus protection loaded as it is never on the Internet.

I have two cameras a Canon XH-A1 that I shoot with and a Canon HV-20 that I use to capture with. My last project was 24p HDV.

I started out using Vegas 7e. Then when my project was about 70% done (12 min using about 50-60 different clips) it crashed. I heard that Vegas 8a took care of all the problems so I upgraded, but it crashed too. Here are the Problems I am having:

Vegas 8a on my computer (and according to the boards a lot of other people) cannot capture HDV. It moves in slow motion and splits one capture into several individual files. I have done test and discovered that it does the same thing in DV as well as HDV.

Because I could not capture using Vegas 8a I used Vegas 7e to capture my footage. My project also crashed in Vegas 8a. Finally I split my project into six smaller projects and individually rendered them out using the supplied Cineform codec. (24P 1440x1080) I was able to stitch these files together in a new Vegas project with no crashing.

I pulled up the task manager and watched the PF usage. As I import clips from the explorer to the time line the PF usage jumps about 40MB for each clip I put on the time line from its start of about 420 MB. It does not seem to care if the clip is longer or shorter it is still about 40MB. Even if I delete a clip from off the time line it does not delete its memory usage because it is still in the project media. So it does not take long to build up to 1.5-1.8GB of PF usage and the program crashes every time, very repeatable. My final time line with the 6 different rendered clips still added the 40MB per clip its just that there were now less clips so I did not reach the high memory use point of 1.5-1.8GB. In short I think it is a memory problem. Some people are not having problems because they may have only one or two clips on the time line. Let me know if you need more information.

Blessings,

David Wendt

Comments

CorTed wrote on 11/9/2007, 2:32 PM

For what it is worth David, I have notified Sony support over a month ago now about this strange memory "fill-up".
I have tesed and seen the same thing happen on my set up using regular DV and various 1600/1200 Jpeg pictures. I have asked them to see if they could duplicate, but have told me they cannot.
It is so strange that there are not more people seeing this. I wonder if this is due to the many different clips we are putting on the timeline, and subsequently filling up the memory resources.
In one of my tests I also found out that if I opened another project (without selecting NEW from the file menu first, it appeared to not clear the RAM.

Ted

darg wrote on 11/10/2007, 12:12 AM

Hi,

for me, it looks like that there are more people out here who are having the same problem. It looks like that the memory fill is causing many different failures and crashes. I have this problem also. It only happens with HD, if you are shooting only in SD it will never happen, so most of the people will never have this issue as long as HD is only minor in the market. I have even tried to setup Pro8 on four computer of different brands and all four show the same issue with HD, so it's not the hardware. A friend of mine in Germany has tested my project files, they are all ok, I have tested his HD material and it happend again. So it's not the footage.
The interesting part is, that his system is German, all my four computer are USversions of XP and Vista!!! Most of the posts that I have seen in different forums comes from US or english "speaking" systems. Who knows?!
The magical PFUsage seems to be 1.72GB, than all my machines crashed and I'm reaching 1.72GB pretty fast with HD. It's just about 2.5minutes of material. This must be serious thing, an expensive software can not force me to think and work in 2 minute projects!!!!
I hope Sony is helping us.

Regards

Axel

Wolfgang S. wrote on 11/10/2007, 2:10 AM

Axel, have these tests be done with Canon HDV-clips? We have a lot of users, using the Canon HV20 or the Canon A1 in the some German forums - but I never heard here comlains about the increas of the page file, that seems to crash the PC in the start-posting.

darg wrote on 11/10/2007, 8:59 AM

Hi Wolfgang,

my files are coming from a Canon HV10. I got another test file from a contact in Germany but I'm not sure if it is Canon or whatever.
It seems like that the PF issue is coupled to many different tasks and so to many different crashes. The point is that Pr8 is doing something that is loading the PF extremely and this already by just putting clips in the time line.

Axel

Marco. wrote on 11/10/2007, 9:42 AM

>> but I'm not sure if it is Canon or whatever.

That one is from an Sony FX1.

Marco

Marco. wrote on 11/10/2007, 1:54 PM

I now can repro which certain files.

Which capture tools did you guys use?

Marco

darg wrote on 11/11/2007, 3:45 PM

My problems are now solved after recapturing with Vegas Pro8. Since I had my files from HDVSplitt, something seems to be different so that Vegas screwed up the memory usage. After recapturing with Vegas everything is going fine.

Thanks

Axel

krew wrote on 11/12/2007, 1:26 PM

I just got a quad core (Intel 3.0Ghz Extreme) a few weeks ago and every single program I have works brilliantly, except for Vegas 8.0. I constantly get the BSOD complaining of memory conflicts or somesuch when I try to render from DV to mp4 or mpg. My experience is that Vegas will cause a blue screen about 40% of the time when I try to render. It's very, very disappointing. I too am surprised that more people aren't having this issue.

On the bright side, as a test I ran a little project that took 32 mins and 15 seconds to render on my AMD FX55+ computer, and on the quad core it rendered in 3 minutes and 10 seconds. :-)

edited to add: I should note that on my older computer Vegas 8.0 worked flawlessly, which leads me to wonder if its a problem with quad core?

DSW wrote on 11/12/2007, 1:55 PM

Axel,

You were able to get Vegas 8a to capture HDV? From a Canon A-1? That may solve my problem, but Vegas 8a capture moves in slow motion and chops my footage into little tiny clips of just a second or two. Unusable at this point. I am wondering if it is hardware, another software conflict or a problem with Vegas 8a. What is your computer system and what camera are you using? Also, do you have any specific settings?

Thanks,

David

DSW wrote on 11/14/2007, 2:13 PM

I have heard back from Sony. They informed me that they are working on a fix to the Canon 24F bug/ Memory problem. If you are having problems please send it in to Sony so Vegas 8b can be the best it can be:)

Blessings,

David

CorTed wrote on 11/14/2007, 2:28 PM

Thanks for the update David.
I hope 8b will arrive soon and fixes all of my memory issues.

Ted

rob@flodine.net wrote on 11/15/2007, 6:45 AM

Not sure if this helps but I have been having crashes and freezes with HD (m2ts/AVC) and Vegas 8a. After a fresh install to a new partition etc eventually found that the problem was with 32bit floating pixel format, once this was changed to 8bit (as V 7- ) everything went swimmingly and rendered as HD or SD in much less time too!
Shame really as the 32bit colour was an extra incentive to upgrade to V8 and the V1p camera. :-(
Have requested Sony support....
Regards
RobFlo