Overnight, VE instance pushes CPU 30%-40%

[pqlior@mac.com]

Hey guys, without any change, I noticed that my instance of VE in my mix session bumps the CPU usage 30%-40%
Anyone else has this bug? This session sat around 50% last night and today is in the 80's

[musicman691]

Originally Posted by pqlior@mac.com

Hey guys, without any change, I noticed that my instance of VE in my mix session bumps the CPU usage 30%-40%
Anyone else has this bug? This session sat around 50% last night and today is in the 80's

Memory leak? Have you rebooted? That may fix the issue.

[pqlior@mac.com]

Originally Posted by musicman691

Memory leak? Have you rebooted? That may fix the issue.

Rebooted. Didn't help...
Anyone else? VE people also suggesting memory leak. Workaround anyone?

Lior
____________________


Sent from an inherently faulty typing apparatus... ;-)

[pqlior@mac.com]

Trashing prefs seems to have done the job...
I made sure to build clean prefs on a blank session, quit, restart, and ONLY THEN open the last session.
CPU usage is down to the 50% area now.

[pqlior@mac.com]

Aaaaaaand it's back. Took al of 3 minutes.

[musicman691]

Originally Posted by pqlior@mac.com

Trashing prefs seems to have done the job...
I made sure to build clean prefs on a blank session, quit, restart, and ONLY THEN open the last session.
CPU usage is down to the 50% area now.

You're talking about trashing PT prefs right? I still think it's a memory leak.

[pqlior@mac.com]

Originally Posted by musicman691

You're talking about trashing PT prefs right? I still think it's a memory leak.

Yes- PT prefs. How do you address a memory leak?

[musicman691]

Originally Posted by pqlior@mac.com

Yes- PT prefs. How do you address a memory leak?

Generally you fix a memory leak by rebooting the computer. How to find what's causing it is a bit more difficult. Strip out everything from VEPro and see if you have issues. If you still do remove VEpro from the session and continue. If you still do it's in PT. Keep removing stuff until the leak stops. A memory leak is something where memory usage increases for no action on your part and keeps increasing.

[pqlior@mac.com]

VERY strange symptoms. I went back to the clean session I saved today (of last night's mix) after the prefs trash and it's fine... (with the same VE session attached to it) If I import a plugin from last night's session (A UAD SSL strip) it jumps back up BUT doesn't go away when I remove the plug. (that track is NOT sending to VE)

Seems to be related to internal bussing... When I Open the session, it's fine. Then, when I put my 'print track' into INPUT, the session jumps 35%
I've been working this way for YEARS and it never behaved this way...

[musicman691]

Originally Posted by pqlior@mac.com

VERY strange symptoms. I went back to the clean session I saved today (of last night's mix) after the prefs trash and it's fine... (with the same VE session attached to it) If I import a plugin from last night's session (A UAD SSL strip) it jumps back up BUT doesn't go away when I remove the plug. (that track is NOT sending to VE)

Seems to be related to internal bussing... When I Open the session, it's fine. Then, when I put my 'print track' into INPUT, the session jumps 35%
I've been working this way for YEARS and it never behaved this way...

Do you have a send to a 'bus to nowhere'?

But I rarely pay attention to the cpu usage window in PT anyway. Unless I have an issue I don't even open it.