|
|
Post by mulmany on Nov 14, 2015 10:25:53 GMT -6
I know there is alot out there on this subject, but nothing that addresses a solution. I need to finish a current project on pt10 since I was using rtas plugs extensively on the old PT9 session.
I am now running a 2012 2.4ghz Mac mini, mountain lion, 16 gigs RAM, 2 SSD.
Some of the old sessions run great, barely breaking 15% native cpu load. I have 2 that run at 10% load then after 5min crash the cpu spiking to 100%. I can wait it out and it takes about 2mins then the cpu stabilizes, but it cycles again in 5 to 10 mins.
I have tried all the tricks I could find online. Buffer changes, core changes, ect.
Any suggestions?
|
|
|
|
Post by tonycamphd on Nov 14, 2015 11:55:58 GMT -6
I'm on 10 for a few more weeks, it seems whenever i've run into weird issues like that, a simple save, shut down PT, restart, repair disk permissions, restart AGAIN, reopen PT and session, it will stabilize. Because of that instability i set my back up for every minute, I look forward to upgrading to PT12 as i've heard it's eons more stable, and uses much less cpu resources than 10.
good luck P
|
|
|
|
Post by mulmany on Nov 14, 2015 12:07:30 GMT -6
I'm on 10 for a few more weeks, it seems whenever i've run into weird issues like that, a simple save, shut down PT, restart, repair disk permissions, restart AGAIN, reopen PT and session, it will stabilize. Because of that instability i set my back up for every minute, I look forward to upgrading to PT12 as i've heard it's eons more stable, and uses much less cpu resources than 10. good luck P Yeah, I did the disc repair, shut down, and restarts. Not much of a change. I bought a Fast track from Alto which came with a full version of 10,11,12, so I still have 9 if I can't get through these issues. Great deal on it. |
|
|
|
Post by kcatthedog on Nov 14, 2015 16:33:30 GMT -6
|
|
|
|
Post by mulmany on Nov 14, 2015 23:34:56 GMT -6
Well, i have done just about everything that I can think of and find on the web. I have 3 Sessions that will not allow me to play though the entire song without overloading the CPU. One of these 3 is a 13 track session it was not pulling more then 12% on my old PT9 system. I tried a save copy in, to see if it was a file issue but no luck. This is happening in PT10 and 12, even with every plug disabled. Very frustrated. Need to figure out what is wrong with these 3 sessions.
|
|
|
|
Post by kcatthedog on Nov 15, 2015 6:13:09 GMT -6
What happens if you make all tracks inactive and then re activate each individually ? Do you have a culprit track ? What happens if you reintroduce one at a time:rebuilding the load ? What happens if you export everything to a new session ?
|
|
|
|
Post by swurveman on Nov 15, 2015 9:21:40 GMT -6
What do you guys use for a buffer size?
I use 256, but occasionally PT struggles. I'll put in a plugin and get a message that PT has run out of CPU power, but then it pauses and works. So, I'm wondering if a bump up will help. I'd rather use a standard buffer, as PT has to shut down and start up again if I change it, while Cubase can do it on the fly.
|
|
|
|
Post by mulmany on Nov 15, 2015 12:30:28 GMT -6
What happens if you make all tracks inactive and then re activate each individually ? Do you have a culprit track ? What happens if you reintroduce one at a time:rebuilding the load ? What happens if you export everything to a new session ? I have not tried deactivating the actual tracks. My next move was to consolidate and delete regions and see what happens. I can run the working session at a 128 buffer, but am using 256. |
|
|
|
Post by kcatthedog on Nov 15, 2015 13:17:26 GMT -6
Well perhaps you only have one bad track as opposed to the whole session ?
|
|
|
|
Post by mulmany on Nov 15, 2015 13:50:00 GMT -6
Well perhaps you only have one bad track as opposed to the whole session ? Yeah hopefully, just really odd that 3 out of the 8 have the issue. The others run like I thought they would on the new system and PT. |
|
|
|
Post by formatcyes on Nov 15, 2015 13:51:56 GMT -6
It's kind of what PT does
|
|
|
|
Post by kcatthedog on Nov 15, 2015 14:13:28 GMT -6
Ah it's not typically true that protools has inexplicable cpu spikes ?
The only time I have experienced this was while beta testing ssd4 for Slate and the sram consumption and related cpu spikes were caused by the beta software not inherent to pro tools.
The fact that these current spikes are happening, all else being the same, except different gen of protools is also interesting, as 11 and 12 are 64 bit vs 10's 32 bit and each successive pro tools version has successive bug fixes.
So, the commonality are actually the sessions and the host computer: to me, no disrepect,they are more suspect? I wonder if something is just corrupted in the sessions ?
Why not experiment and export one session to a new session ? My understanding is that that loads your tracks into a brand new clean session:worth a try ?
|
|
|
|
Post by mulmany on Nov 15, 2015 14:48:40 GMT -6
This is my next step. Need to rule out all session file commonality.
I already tried a copy session in, that had the same issue. Need to look at the files themselves.
|
|
|
|
Post by mulmany on Nov 15, 2015 20:54:51 GMT -6
So, ran the sessions tonight. Turned the track voices off before starting.
Introduced 1 track voice back in at the beginning and middle of the song. No issues what so ever!
Opened different session, played it twice through before the cpu started freaking out. Quickly turned a track voice off, cpu went back to normal operation. Turned the track back on and played the song through multiple times. Worked perfectly.
I am a little lost on a why, but at least I figured out a work around if it starts up again on these 3 tracks.
|
|
|
|
Post by tyford on Nov 16, 2015 16:52:32 GMT -6
Thanks for posting that, Pat.
I was going to add, "run Disk Warrior" to the list. Oh and I have had a few PT plugins get wacky and cause problems. Sans-Amp, as I recall and even the PT 10 de-esser.
Regards,
Ty Ford
|
|
|
|
Post by mulmany on Nov 16, 2015 18:59:39 GMT -6
Thanks for posting that, Pat. I was going to add, "run Disk Warrior" to the list. Oh and I have had a few PT plugins get wacky and cause problems. Sans-Amp, as I recall and even the PT 10 de-esser. Regards, Ty Ford Yeah, it was a fun couple of days... I love banging my head against a wall trying to figure out random/inconsistent computer issues. The funny thing is there are tons of threads describing almost my same issue, and almost all of them never list a solution. On a side note I also found out that on a duel install of 10 and 12, the 10 preferences don't get put in the correct folder, they are scattered about. The 12 preferences are however neatly packaged in a self contained folder. |
|
|
|
Post by mulmany on Nov 21, 2015 20:51:06 GMT -6
Well, I thought this was a isolated issue and that it could be fixed by turning off all tracks. Well that does not seem to be the case. Prepping for a live tracking session, set up a template and did a test drive of 16 tracks at a 64 buffer. System freaked out. Tried different buffers got it kinda working, then the cpu would creep up and crash.
I am now uninstalling and reinstalling the system.
|
|
