Pro Tools 8.0.4cs2 Update FINALLY!

[MikeLip]

Originally Posted by markblasco

When a company that claims to be the best option out there can't get their software to work correctly after almost 2 years, well, there is just no excuse for that.

It works here. Yes the 64bit drivers are screwy, but they weren't the intention of V8 release anyway.

I'm not sure what feature is your problem, but there is always a solution and sometimes that is another DAW.

Mike.

[FordVan]

Originally Posted by MikeLip

I'm not sure what feature is your problem, but there is always a solution and sometimes that is another DAW.

Mike.

That is a great option IF you can get your money back for the flawed DAW you purchase because of the advertising claims.

[sw rec]

That is a great option IF you can get your money back for the flawed DAW you purchase because of the advertising claims.

Experience has shown this to be an argument presented by those who do their research AFTER point of purchase instead of BEFORE.If it's that flawed, there wouldn't be so many of us making a living with it....

[guitardom]

Originally Posted by markblasco

This definitely makes sense, and if PT8 had come out a month or two ago, I could agree about it being a valid argument, but the fact that PT8 has been out for so long changes things. When a company that claims to be the best option out there can't get their software to work correctly after almost 2 years, well, there is just no excuse for that.

To be fair, these timeline issues have not been a problem for anywhere that long. They arose with the development of the 64 bit driver in the later days of 8.03 and in 8.04.

[ripsta415]

no problems here so far. this version has been running very smooth for the last few days of using 8.04 cs2
Thank You for no more crappy distorted playback

[markblasco]

Originally Posted by guitardom

To be fair, these timeline issues have not been a problem for anywhere that long. They arose with the development of the 64 bit driver in the later days of 8.03 and in 8.04.

Yes, but (and please correct me if I am wrong), before that there were issues with other things, such as white noise bursts. I guess I can't say definitively that there has never been a PT8 version that worked correctly, but over the last 1-2 years I kept waiting for someone to say that it was finally working exactly right, but all I kept hearing were the problems that weren't fixed yet. Instead of hearing people say "the newest version has fixed all of the outstanding issues", I'd hear "go back to version 8.0._, that is the most stable version so far".

[markblasco]

Originally Posted by MikeLip

It works here. Yes the 64bit drivers are screwy, but they weren't the intention of V8 release anyway.

I'm not sure what feature is your problem, but there is always a solution and sometimes that is another DAW.

Mike.

I don't have an issue with any of the features, or the lacking features. I have used and loved (let me say that again a little louder), LOVED ProTools for years and years. If not for a few features that ProTools lacks, I would want to use it for everything (unfortunately, the lack of VST plugins makes film scoring rather difficult, which is one of the reasons I use Reaper). I have many complaints about ProTools which I don't ever bring up, because I understand that not all software is going to have all features. For a long time I even partially backed up the idea that you needed very specific hardware and had to jump through lots of hoops to get a ProTools LE system to work correctly, because at the time it was very stable once working, and was ahead of the competition. Most of all, several years ago, it seemed like it all worked. Period. When I helped someone setup their ProTools rig, I didn't have to worry about noise bursts, or random sample offsets, or clocks getting reset, or crackling outputs.

If these issues were happening in the first release of PT8, I wouldn't be so concerned, since we would all know that an update would come along to fix it. However, when updates come out months and months later that don't fix problems, and some of the major players on this board who know exactly what they are doing are having their speakers blow, or losing paid session time, than there is a problem.

If the next version of ProTools comes out and just works, than I will be happy. I don't know if I will use it a lot (that depends on features), but I will use it. If they can get a working 8.0.4 driver to work with Win7, I will be happy. I just haven't seen anything since the release of PT8 which shows me that they are ever going to get things working 100% correctly, and to me that is unacceptable.

Heck, right now all I really want is a working ASIO driver for win7. I bought my 003 last year after a long time using my 001, and specifically waited until Win7 was out to see if they were going to release an 004. If I had known it would have taken this long to get a working driver for Win7, I honestly might have gone out and purchased a different audio interface.

[gscaife]

My 003 is freezing consistently. The control surface readout strip freezes and the faders quit responding. Closing the session does not clear the 003, and opening another session doesn't reset the previous session's fader settings or control surface readout strip either! The on screen faders still are movable but the 003 surface stays frozen.

If I power off the 003 it will reset. If I open a previously saved session and close it without saving everything appears to be working normally. If I make a small change (like moving a fader), close and save the session, the 003 retains the session info on the readout strip and fader positions. If I open another session the 003 is does not appear to “read in” the previous sessions saved settings.

This all began with the 8.0.4 upgrade and continues with 8.0.4cs2. WinXP with all the MS patches and service packs applied and current.

Any suggestions?

[TOM@METRO]

Originally Posted by gscaife

My 003 is freezing consistently. The control surface readout strip freezes and the faders quit responding. Closing the session does not clear the 003, and opening another session doesn't reset the previous session's fader settings or control surface readout strip either! The on screen faders still are movable but the 003 surface stays frozen.

If I power off the 003 it will reset. If I open a previously saved session and close it without saving everything appears to be working normally. If I make a small change (like moving a fader), close and save the session, the 003 retains the session info on the readout strip and fader positions. If I open another session the 003 is does not appear to “read in” the previous sessions saved settings.

This all began with the 8.0.4 upgrade and continues with 8.0.4cs2. WinXP with all the MS patches and service packs applied and current.

Any suggestions?

We don't know anything about your system hardware, what OS you are using or what you have done to troubleshoot this so far. You may want to go over this thread and start a new thread of your own with more information on it. And tell us what PT version were you running when all was well.

[mdb]

Is there any information on the deforming/distorting audio bug?*
I't not in the cs2 update, but maybe I missed something else.
I thought there was a topic on this somewhere but I can't find it.

*A bug where, after a while the audio sounds broken/distorted/aliased, and after changing the H/W buffer size (smaller or bigger) it's solved again for a while.