PT8 CPU Usage

[Ling]

Originally Posted by Bob Olhsson

Better to have it fixed right than deal with a quick fix that only breaks something else.

Plus one on that.

The little bit I've used PT8, I really like it. Looking forward to when I can use it a lot!

[Mark Seyler]

Hey, Driven01, you got there first with all the words I was going to use in about the same order!!
I agree with all of your post here, and especially like the idea of the sticky at the top of the forum. This does seem to be a pretty common complaint (and there are several more of jumpy mice, lock-ups etc which might just be related....) and it is a SERIOUS one for those affected... not something I can 'work round' as I can for a small irritation type bug where one function fails to operate in the expected fashion: I can do no serious work at all on PT8.
A sticky might be embarrassing for Digi (lots of unhappy (non)users are not a great advert) but would indicate that they are taking this crippling bug seriously and would help a lot of others understand 'oddities' in machine behaviour.
One point you make in passing, that there seems to be a myriad of PC combinations affected, does make one question the original testing again. If I was the only one I would blame my hardware, but everything from Intel / AMD / P4, duos, quads, various video cards, memory configs... everything.......? Some folk must just be lucky I guess and have a combination that does work. I, for one, would be very dubious about going out to upgrade my machine here in the UK in case I got another unworkable combination.

Digi also ought to be worried by the numbers recommending Reaper....

As to the blonde... I'd keep her in reserve and tell her not to hold her breath....
Mark

[deanguidry]

Originally Posted by RoMi

It looks like we got buried in the history dust... so...
in the mean time, encouraged by Shan, I jumped into the REAPER world and... I love it!
It is so efficient and powerful application and it has that... hmmm... freshness, openness and youth type of excitement feel...
It is a very, very, very lean application. It is fast and my CPU and RAM is barely touched by it.

I also tried it as ReWire in Pro Tools and it works great! REAPER accepts any kind of audio formats in the same session (I keep a lot of audio "notes" in ogg vorbis (lancer) format, so it saves me the conversion hassle and storage space. REAPER's plug-ins suite is BIG. REAPER accepts all kind of plug-ins formats (but RTAS).

I am sure I will be using REAPER. As soon as I get a CS update solving my PT8 problems in the CPU/RAM usage area, I will start to use PT again.

Robert

I am heavily into Reaper now, as well. Loads in 5 seconds. Much more intuitive. Infinite routing capabilities. Can you say "Automatic Delay Compensation"....no more phasing issues to worry about. Still using 002r clocked to Big Gen. Has not crashed, skipped, choked and starts recording/playing immediately when asked. If digidesign fixes pro tools and cures the crash issues and start/pause issues, and gives us automatic delay compensation, I'd revisit the platform again. But for now, I'm having great success and fun recording, mixing and mastering instead of constantly troubleshooting.

[The Weed]

I've said in another post that Digidesign should contract the Cockos/Reaper boys to recode Pro Tools and get it into the 21st Century. If they can bring a program as good as Reaper into existence in such a relatively short period of time, they surely must be able to "fix" Pro Tools.

Cheers,

[DigiTechSupt]

Originally Posted by Driven01

What would be of more help is that there's some sort of semi-realistic projection of when Digi feels the fix might be available. A lot of people are either "hanging" on to their current PT8 installation hoping on an imminent fix release, uninstalling 8 and reverting to 7.4 because they simply can't wait, or getting totally cheesed off and dumping PT altogether for another product that performs the way they expect it to.

We would like to be able to do this, but previous experience has burned us on making any kind of projection. The reason being - if you give one and it's off, there seems to be no end to the rage that people will express. It's a double-edged sword and our experience clearly suggests that not projecting dates, while still not ideal, is better overall for everyone's emotional well-being (whether they realize it or not). Seems contrary, I know, but I've personally seen this over my 6+ years here at Digi.

It'd also be nice if you guys could pop in every couple of weeks to give us all an update of where you're at in the process. This would let all of us know that 1.) Yes, they're still working on it, 2.) How far along in the process the issue is., and 3.) When we're getting close to a fix. I personally think that this alone would give us all a bit of hope and peace of mind.

Another idea that, in theory, would be great, but in practice has been difficult for much the same reason. The moment you give the 'we're close' message, then find out that a major problem has surfaced on the last day of testing and will delay the fix, things go seriously sideways. I do try to keep these updated, but the sheer volume of posts and other duties my job requires means that I may not be able to do a 'reassurance' post as often as people would like. Getting an update from engineering on every issue every couple of weeks is another story altogether...!

I might also suggest that you make this thread a sticky so that 1.) Users can quickly find the issue and know that they are not alone, 2.) post their Sandra reports, etc. to help the engineers pinpoint the problem area (although based on the miriad of PC configurations it has affected there doesn't appear to be much in common for anyone particular problem area related to PC's), and 3.) Centralize the problem in the DUC There's a boatload of related threads. I know it wouldn't be a pretty thing to have at the top of the DUC but it may help relieve some user related stress.

This is something that gets talked about here relatively frequently. Arguments go both ways of why we should or shouldn't sticky things. I'd like to have things centralized, but others argue that the number of stickies is already too many and adding more just clutters things up - and it gets used against us by the competition since they'll point everyone to all the stickied problems. How do we satisfy sales/marketing, tech support and customers simultaneously? If anyone finds and answer to that, patent it, because you'll make millions...!

[Bob Olhsson]

Originally Posted by The Weed

If they can bring a program as good as Reaper into existence in such a relatively short period of time, they surely must be able to "fix" Pro Tools...

That's comparing apples to oranges. A brand new application like Reaper has no backward-forward compatibility requirements.

[AlexLakis]

Originally Posted by Bob Olhsson

That's comparing apples to oranges. A brand new application like Reaper has no backward-forward compatibility requirements.

Perhaps it's time for Digidesign to move on from the ancient code nobody fully understands and start a new software line then.

They could call it "Pro Tools Good."

Then include an application that converts PT Good files to PT HD/LE/M-powered project files. Make it a toolkit with a snazzy name and charge us $1000 for it. That'd be sweet. Oh, wait, I guess they all ready have that with Logic and that $700 SSL project-file converter program? Too bad I want to use Pro Tools and not Logic...Hmm, that might be a good project for Cockos...

Ahh, good times...

[TOM@METRO]

[idylldon]

Bump.

[kernelpanic]

B
U
M
P