I finally got to use PT8...

I've updated from 7.4, to 8 in the last week. I've been getting all sorts of errors when using my scroll wheel... other than that it's been pretty good.


EDIT: On a positive note, I haven't heard ANY white noise blasts since upgrading.
 
Love it, but I started using PT with this version. I love the new look, too (as already said, the color scheme is tweakable to make it look more 7.4-esque). The UI is a bit slow (especially if the plugin load exceeds like 50%) compared to other DAWs I am using (Sonar, Reaper). If you have multiple CPU-cores (I only have 2), you can limit the RTAS usage to fewer cores and then the remaining are available for the UI. If I reduce the cores from 2 to 1, the UI feels much quicker even under heavy RTAS-load, but then I run out of RTAS power ;-(.

I am currently in some kind of evaluation phase (PT?/Sonar?/Reaper?) and find myself using PT most of the time and getting things done and sound good very easily.
 
What's wierd is that the guy also said that the scroll slowness is only a problem with PCs, and doesn't effect Macs... all well. Unless 8 has some fantastic new functionality that you can't live without I wouldn't recommend it over v.7.4.
 
yeah i am... its wierd, its a little tempremental the scrolling thiing!! and this is on a macpro

You still on a G4 andy? on my quicksilver the scrolling is baaaad.
 
I've been experiencing problems with Protools recently, whenever I use certain plugins, including Nick Crow's 7170 the average CPU usage increases to about 70% and quite often reaches 98%, even if only a single track with just 7170 and boogex are on at max buffer size. (I have a quadcore 2.4GHz processor and previously never had the CPU usage go over 30%)

For anyone else suffering this bug, as far as I can tell the only workaround is to reduce the number of cores in use to one less than maximum.

As 7170 seems to be popular here, has anyone experienced this problem?
 
AliksWud said:
For anyone else suffering this bug, as far as I can tell the only workaround is to reduce the number of cores in use to one less than maximum.
Click to expand...

I had that problem, and the solution is exactly what Digi-Service told me.
didn't know that's a bug, just thought that's how PT works......actually that guy at the service.center told me PT should always be set up like that.
was that BS?
 
Yes I've read it me too. But you have to reduce the used core if you have a specific problem. It's because some plugins don't work well with all the cores.
In my case I use all the cores because I had no problem...and also because with only one core, there is much less horsepower!!
 
::XeS:: said:
Yes I've read it me too. But you have to reduce the used core if you have a specific problem. It's because some plugins don't work well with all the cores.
In my case I use all the cores because I had no problem...and also because with only one core, there is much less horsepower!!
Click to expand...

No. It is to do with the implementation of multiple cores within Pro Tools, and nothing to do with the plugins. You can confirm that by using the same plugins in another host such as Reaper.
 
Ok, but I can't work with the half of the cores...so I use all the cores because I have no problems (apart some error message for overload during the bouncing) :)
 
You must log in or register to reply here.

Similar threads

joelplagues
mptk licensing and activation. pt8 windows 7
Replies
0
Views
446
Backline
joelplagues
J
Jarkko Mattheiszen
Immediate help needed, upgraded Pro Tools 8 to 9 and now I haven't got the 8 license!
Replies
7
Views
1K
Backline
jipchen
J
Sloan
Finally got a 5150.
Replies
7
Views
1K
Backline
DeclanWhite
D
Gnash
SONAR TO PROTOOLS
Replies
6
Views
825
Backline
ElektricEyez
E
Wound
i finally got my keyboard!
Replies
6
Views
430
Skyfire
Shmeir
S
Top Bottom