Is 2020 better w Catalina?

[Rectifried]

on Mojave..seems kinda the same.. Cpu can be at 80 before losing its mind.. [instead of 40]
this disc cache thing is always "normal" but put it at 10.. to see.. theres NO clear answer to why/when this is good bad.. PT is always a knife edge dance. that has not clear reasons often for spikes


20 years on this platform, music not post

[Southsidemusic]

We have basically same great performance on our New Mac Pro’s we got last night (7.1) 28 core 384 GB ram as we did on our trashcans 12 core 64GB ram with HS and 2020.3 Ultimate.

Today we are working on a big track pop song with 200-220 ish audio tracks for many vocal takes and accoustic guitars and Tele and Strat takes.

A big selection of VI on there too. Maybe 85-90 VI tracks so about 300 tracks together and aux sends and automations. Opened from 4 days ago recorded on a trashcan with HS.

[Rectifried]

220 tracks!..

I dont know why on earth my Tcan 12core is so buggy sometimes.. optimised like mad, Clean Install 6 months ago
the Acustica stuff is a strain, as is the Ozone.. but really, I have 64gigs SSD etc etc.
omnishere zebra NI.. nothing too exotic.
but a pain to use, often enough.



quitting and restarting this very often, at the mix/end of session usually... because thats when it loves to screw me up


never more that 30-40 tracks
many of them committed.. which is even more bizarre







sounds like you have better "luck"...

I also used CPUsetter to contain PT to the real cores..

[Southsidemusic]

That does sound way too limited but we dont use either of the plugins you have as Ozone is a cpu hog and we use other gear for that and same with zebra? Dont know what that is. I guess its a VI synth but nothing we would use. Sorry but some plugins can cause havoc no matter how much ram you have as they use mostly CPU power. Ram would work with 32 GB as we had that in our trashcans before upping them and now 384 GB ram doesn’t make it better for the plugins but a bigger difference for audio.

[arche3]

Ozone. This is why you are bogged.

Sent from my SM-G986U using Tapatalk

[Flyingrockstudios]

Sometimes PT just has a mind of its own it seems. I was working on a tune this evening and all of the sudden ONLY CPU 12 out of 24(I have a 12 core trash can) goes to 100, all others at 0 and the top CPU usage meter pegs to 100% red and the tune would not play. Got the -9173 error, even though the session was playing fine for several hours today and several days before. I started disabling plug ins, then entire tracks and then I disabled all the tracks and the master fader, auxes, everything(about 30 tracks) and VI's were disabled, and still the same problem! CPU 12 usage was all the way up, and I wasn't even playing anything. I quit PT, and reopened with Shift down, and all plug ins disabled and it played fine(tracks that were audio or frozen from before played). I then re-enabled one track at a time, expecting to find the culprit. I never did. With all tracks and plug ins enabled the tune played perfectly after that. Why did this happen, I don't know. I work with software tools a lot, and most of the time unless something is a show stopper and I can easily reproduce it, I find a way around it and move on. I do have the send anonymous data to Avid box checked, and I've been sending them data more often then I would like. My VI's are all on the same 4 TB Thunderbolt 2 drive with about 3/4ths full. I think that's my bottleneck now, and I'm going to find some time during this shutdown to add another drive and move some of the VI's to the new drive.

[innesireinar]

Originally Posted by Flyingrockstudios

Sometimes PT just has a mind of its own it seems. I was working on a tune this evening and all of the sudden ONLY CPU 12 out of 24(I have a 12 core trash can) goes to 100, all others at 0 and the top CPU usage meter pegs to 100% red and the tune would not play. Got the -9173 error, even though the session was playing fine for several hours today and several days before. I started disabling plug ins, then entire tracks and then I disabled all the tracks and the master fader, auxes, everything(about 30 tracks) and VI's were disabled, and still the same problem! CPU 12 usage was all the way up, and I wasn't even playing anything. I quit PT, and reopened with Shift down, and all plug ins disabled and it played fine(tracks that were audio or frozen from before played). I then re-enabled one track at a time, expecting to find the culprit. I never did. With all tracks and plug ins enabled the tune played perfectly after that. Why did this happen, I don't know. I work with software tools a lot, and most of the time unless something is a show stopper and I can easily reproduce it, I find a way around it and move on. I do have the send anonymous data to Avid box checked, and I've been sending them data more often then I would like. My VI's are all on the same 4 TB Thunderbolt 2 drive with about 3/4ths full. I think that's my bottleneck now, and I'm going to find some time during this shutdown to add another drive and move some of the VI's to the new drive.

I suspect that the HDX system is more affected by aae errors than native's. Especially at low hd buffer setting. This could be caused by the streaming process between the card and the cpu given that on HDX both are involved. It could be interesting to note if this issue happens as well with only dsp plugins loaded. Btw I still have a yosemite part with pthd11 that I use for midi programming (given that it is not affected by the rounding errors on midi) and have noticed that is less affected by aae errors. Sometimes I get the 9171 at the first start of the session. I'm speaking about a very poor and old machine (see my sig)

[Rectifried]

Originally Posted by Flyingrockstudios

Sometimes PT just has a mind of its own it seems. I was working on a tune this evening and all of the sudden ONLY CPU 12 out of 24(I have a 12 core trash can) goes to 100, all others at 0 and the top CPU usage meter pegs to 100% red and the tune would not play. Got the -9173 error, even though the session was playing fine for several hours today and several days before. I started disabling plug ins, then entire tracks and then I disabled all the tracks and the master fader, auxes, everything(about 30 tracks) and VI's were disabled, and still the same problem! CPU 12 usage was all the way up, and I wasn't even playing anything. I quit PT, and reopened with Shift down, and all plug ins disabled and it played fine(tracks that were audio or frozen from before played). I then re-enabled one track at a time, expecting to find the culprit. I never did. With all tracks and plug ins enabled the tune played perfectly after that. Why did this happen, I don't know. I work with software tools a lot, and most of the time unless something is a show stopper and I can easily reproduce it, I find a way around it and move on. I do have the send anonymous data to Avid box checked, and I've been sending them data more often then I would like. My VI's are all on the same 4 TB Thunderbolt 2 drive with about 3/4ths full. I think that's my bottleneck now, and I'm going to find some time during this shutdown to add another drive and move some of the VI's to the new drive.

This is what I have had for months .. you have to fully quit pt to clear the cpu 100% thing .. I thought exactly like this ,, like the past , disable things and one will be the culprit , but no it’s caught in some cpu vortex, happens often when I stop to take a break and come back
Or it’s purely ozone
However this happens when not even using Izotope ozone

On the acustica fb group they rank pt as last in handling vi convolution type things,, reaper being first

[TNM]

Originally Posted by Southsidemusic

We have basically same great performance on our New Mac Pro’s we got last night (7.1) 28 core 384 GB ram as we did on our trashcans 12 core 64GB ram with HS and 2020.3 Ultimate.

Today we are working on a big track pop song with 200-220 ish audio tracks for many vocal takes and accoustic guitars and Tele and Strat takes.

A big selection of VI on there too. Maybe 85-90 VI tracks so about 300 tracks together and aux sends and automations. Opened from 4 days ago recorded on a trashcan with HS.

Fantastic, thanks. :) Just downloading and testing myself now.. pretty excited, but first to see if Vanilla got folders (please no one tell me, i want to find out for myself and see if I was an idiot all this time to be sure i'd be getting them).

Enjoy!

[TNM]

Folders are there, YAY!

Christopher...

tell me, has Catalina and PT 2020 given us video support back? Or should I still stay on Mojave for that?

Also, i noticed you said trashcans.. what about the two 28 core you ordered?

Cheers! and YAY to folders again! (I KNEW vanilla would get them, beat that, naysayers!)

Thanks Avid.