Went back to 8.0 cs3, smooth sailing!

[Venture Studios]

Just wanted Digi support to know. I tried all their suggestions, updated my video drivers, swapped my card slots, used the 8.0 system driver with 8.0.1 and still had non stop 6031 errors. I reverted back to a clean install of 8.0 cs3. It's been 3 days now. I've had no 6031 errors and no clicks or pops. Just wanted to post this so it's documented. Digi the 6031 errors in 8.0.1 are not my computers fault, it's faulty programming that's leading to an overly sensitive error response.

[IntelDoc]

Went to CS3 again tonight myself. Was tired of dealing with the Elastic Audio bullS4iT and all the other errors that finally started.

Seems that when you upyour DSP during a session all hell breaks loose.

CS3 is fine for now....

Maybe 9.0 will be better. ;-)

Doc

[IntelDoc]

Absolutely ZERO issues last night on S3. Was even able to render out my EA fixes.

Interesting.....

Digi, fire your software guy......

[Venture Studios]

Let's keep coming with the posts. Anyone who was having 6031 errors with 8.0.1 who has now gone back to 8.0 and havent seen a 6031 as well as no clicks, pops or audible noise in their audio, please post here. This way the moderators will have something to show the programers. It is not our computers fault, this 6031 is mostly unnecessary and definitely over sensitive in it's execution. Otherwise known as a software glitch.

[Fullsound Recording]

Im at cs3 as well

[IntelDoc]

Ya it was pretty smooth last night. No issues at all. Honestly when I was at 8.01 I would see spikes when using a RTAS verb at 128. I usually bump that to 1024 buffer when I mix and have no issues. Once I was back at CS3 no issues. Track count seemed to work better as I noticed I was limited to that stupid MIXER DSP thing.

Whatever.... so far so good. Solid all night after a ghost restore.... THANK YOU GHOST SOFTWARE!

[Przemek]

Originally Posted by Venture Studios

Anyone who was having 6031 errors with 8.0.1 who has now gone back to 8.0 and havent seen a 6031 as well as no clicks, pops or audible noise in their audio, please post here. This way the moderators will have something to show the programers.

I had 8.0.1 and for some time it worked, but then it stopped working. Of course I did sth - I switched on MIDI interface. Now I'm back to cs3 and everything runs smooth with no single problem, with that interface. No dropouts nor glitches.

[x9blade]

out of curiosity, who if any, are using a digidesign midi i/o?

strange observation. when i went to the higher version of protools i expierienced all the 6031's also the pops and clicks
when going back to an image of a stable version, the problems STILL exsisted......... wierd! like it stayed with the hardware.
only when i uninstalled and reinstalled my native instruments kore control driver the error's and clicks went away.

[DigiTechSupt]

Originally Posted by Venture Studios

Just wanted Digi support to know. I tried all their suggestions, updated my video drivers, swapped my card slots, used the 8.0 system driver with 8.0.1 and still had non stop 6031 errors. I reverted back to a clean install of 8.0 cs3. It's been 3 days now. I've had no 6031 errors and no clicks or pops. Just wanted to post this so it's documented. Digi the 6031 errors in 8.0.1 are not my computers fault, it's faulty programming that's leading to an overly sensitive error response.

Your evaluation both correct and incorrect - we know that the trigger for 6031's are caused by system interrupts. The only way those could be happening are due to computer configuration. Just because you don't get 6031's or experience clicks/pops in 8.0.1 does not mean that the interrupts are not occurring - they still are, Pro Tools just isn't able to account for certain interrupt situations (which should be rare) that 8.0.3 will account for.

Ultimately, no matter how you slice it, it's computer configuration at 'fault' - if those interrupts didn't occur, you wouldn't get 6031's and, as you can see, there are many customers using 8.0.3 without 6031's.

Now, as far as it being too sensitive to these interrupts - that's something that may be the case. The engineer that implemented the code is back in the office now, so I'll be speaking to him and a few others about what can be done for those experiencing 6031's. Since no one was willing to work with us directly (let us see your system to test and determine which software/hardware was causing the interrupts), we have only our beta team and others that we've been able to work with in-house. ALL cases, as I indicated before, were solvable and it invariably came down to drivers, hardware misconfiguration or some other system configuration setting. What are certain people ignoring this evidence entirely and still shouting about 8.0.1 being a P.O.S., exactly?

MEAT, x9blade and odeu have been more than vocal about this - and are not giving us a fair shake as far as what we've done to accommodate them. Odeu has never even posted config info. How can we troubleshoot without specifics? We've offered anyone experiencing these errors to pay overnight shipping both ways and look at their system in 1-2 days so they would have minimal downtime. I'm confident we could have determined the cause, but doing long distance troubleshooting can be difficult, especially with PC's. We've responded to every thread as best we can and will continue to work toward a solution for everyone.

[Przemek]

Originally Posted by DigiTechSupt

Ultimately, no matter how you slice it, it's computer configuration at 'fault' - if those interrupts didn't occur, you wouldn't get 6031's and, as you can see, there are many customers using 8.0.3 without 6031's.

First - thank you for answers.

Second - yes, you are right - " it's computer configuration at 'fault' with 6031's" but the problem is much deeper IMO - who cares how you call it, 6031, "disk too slow" or "change buffer settings" - those errors shouldn't appear on our systems, simply because othar DAWs work perfectly. I understand, that Pro-Tools is different, but in that particular case different=worse. So - it is not computer fault, it's PT fault. Of course our computers are not super tight configured and we may have some old drivers and even viruses - but the point is why other software can live with it and PT cannot? One can download reaper and start working in 10 minutes from decision - using the same computer and the same hardware. Hundreds racks, many plug-ins, no problem. Switching back to PT - no way, 6031 with one stereo track. Switching back to cubase - works. I did it, I have to make coffee for client and install cubase in 10 minutes to be able to record stupid 2-track piano demo from kurzweil keyboard - no plug-ins, no fx, just one stereo track.
I understand that PT is not an easy piece of code - of course. But to be honest - who cares?

Originally Posted by DigiTechSupt

Now, as far as it being too sensitive to these interrupts - that's something that may be the case. The engineer that implemented the code is back in the office now, so I'll be speaking to him and a few others about what can be done for those experiencing 6031's.

You are joking, aren't you? Or you are just telling us that NOW you are talking about it at all? When it all started? And you are waiting for what?

Originally Posted by DigiTechSupt

Since no one was willing to work with us directly (let us see your system to test and determine which software/hardware was causing the interrupts)

I understand that this offer is for US customers, not me from Eastern Europe?