Just installed avid 5.8 (PC) from 5.7.5 with No issues

As soon as I try to add audio clip gain of try to render clip i get error that that states i have Buffer Overrun detected which has corrupted the programs internal state.

This project has been created from the previous version. and after install of 5.8 just kept the project to continue on.. Any ideas as to what the issue is? or is this a buggy 5.8.

I also loaded the 5.8 onto another computer with the same result....hmm

Thanks in advance for reply

As an update to this I have just re-installed 5.7.5 on one computer and kept QT7.3.1 and is fine..no problems, the project has no issues with the audio gain & render issues that 5.8 does....this buffer overrun terminates the program..by the way.

Any one have an idea ...would be helpful..  ?

thanks
rob

Could you post some more info like specs etc? If i can reproduce it here as well we have something to escalate. In order to do so i need more info from you. Especially system specs...

Thx.. Menno

SYSTEM 1 (Main) Editing computer

system specs are QT 7.3.1

Graphics card and driver Nvdia Quadro FX1100    6.14.10.9185

DX9.0c

3G Ram

ASUS MB p4C800E

No Antivirus s/w and Media player 10 installed

SYSYEM 2 (Testing Computer)

QT7.3.1

MATROX G550

6.12.01.1960

DX9.0c

2gRAM

ASUS P5P800

Has Antiviris software and Media Player 10

Both machines have been built by me with avid specs in mind. Both played 5.7.5 OK

The issue with 5.8 occurrs when I tried to render or add in the audio gain selection, there may be other issues, but did not get that far, because the error terminates the program. The project i was using on 5.8 installed program was a version 575 project and would play and scrub through fine. This error that came up was a visual basic c++ runtime error Buffer overrun.... which has corrupted the programs internal state.

If you need more info, please specify what you need. To have the issue occur on 2 separtate machines, is a little of a worry. System 1 has 5.7.5 back on and it works fine even with the QT7.3.1 installed.

Hope this helps .

couple of things I forgot that might be helpful

Windows XP Pro 32bit

Running PAL 25i OMFI selection, not MXI, running AIFF-C audio format

let me know if you need anything else

Rob

Thx Rob, good enough so far. Will see if i can reproduce this ..

Menno

I'm also getting this error and program crash when I try to turn on sample plot, audio auto gain, or try to render a motion effect  Or when I add edit (cut a clip)

Avid 5.8
Windows XP SP2
Intel Core 2 Quad q6600 2.4ghz
2gb ddr2 ram
Abit ip35
quadro fx 1500
creative soundblaster <--- I suspect this the culprit???? maybe.

Thanks for your response there keegan

I am not sure if the SB card is the problem. I have been using the same audio card for a while without a problem on other avid versions. Put 5.8 on 2 computer systems and had the same issue. A little bizarre..The program must work on some systems as this problem is not happening to eveyone.

I went back to 5.7.5 and eveything works fine..

What version of avid were you using before  you changed to 5.8 by the way?

If you think it is the audio card, try using the onboard sound to see what happens.. that may or may not help as sometimes I find avid sys gets upset with onboard sound cards.. just a thought..

 

Let me know how you get on..with the issue and what you do. at the moment I am sticking with 5.7.5.

regards

Rob

I am also having a problem with 5.8.  I get the same message when I try to export my timeline to a .mov file.  Or if I try to cut (add an edit) I get the same error.  Completely clueless on why this is happening.  Is it suggested to revert back to an earlier edition?

Computer Specs:

Video Card: Nvidia Geforce 8800 GTX
Processor: Intel(R) Core(TM)2 Quad CPU @ 2.66GHz (4 CPUs), ~2.9GHz
Memory: Four 1Gig Sticks
Sound: On Motherboard
OS: Windows Vista Home Premium

Any help would be greatly appreciated.   Thanks.

~J

iamthefox:

I am also having a problem with 5.8.  I get the same message when I try to export my timeline to a .mov file.  Or if I try to cut (add an edit) I get the same error.  Completely clueless on why this is happening.  Is it suggested to revert back to an earlier edition?

Computer Specs:

Video Card: Nvidia Geforce 8800 GTX
Processor: Intel(R) Core(TM)2 Quad CPU @ 2.66GHz (4 CPUs), ~2.9GHz
Memory: Four 1Gig Sticks
Sound: On Motherboard

OS: Windows Vista Home Premium

Any help would be greatly appreciated.   Thanks.

Well that ain't gonna work with Vista at all! XP Professional nothing more.. nothing less.

Menno

Thanks Guys

But this problem has also occurred with Xp pro.. So any solutions to that one. I am still using 575 and will not be upgrading to the next version. I have had this issue on 2 separate computers (XP pro).

Well that was easy haha thanks.

Just installed 5.8 (which worked fine), however, it's crashing with this exact error whenever I add any transition in the timeline (even on a brand new project).

I have tried this on many different types of video but the result is the same.

Spec:
Windows XP Pro 32bit, Service Pack 2.
Intel Core 2 Quad CPU @ 2.66Ghz
2.57GB RAM
nForce 680i LT SLI 775 T1 Motherboard
GeForce 8800 GTS 640 MB, 'ForceWare' version 169.21, Driver version 6.14.11.6921
DirectX 9.0c
Quicktime 7.4

I am not sure if your graphics driver is the one certified by avid.. please check that. However I believe this problem is related to the 5.8 version as 575 works..with the same specs... Would suggest go back to 575 as eveything seems to be fine..

I  believe avid may need to look at this issue. Their must be some incompatible issue with hardware. I dunno.. but this, in my opinion, has been the most serious crash I have seen in the avid system to date.

thanks

Hi there,

I'm having the same problems as above. I get an buffer overrun error when I make an edit and the program shuts down.

These are my specs:

Windows XP Home edition
servicepack 3
Intel Pentium 4 3,4 GHz
1,5 GB RAM

Recently I bought a new graphicscard: an ATI Radeon Sapphire HD 2600 XT

Before the graphicscard switch (I had an old nVidea 8300XL) I encountered no problems at all.