Avid Pro Audio Community

Avid Pro Audio Community

How to Join & Post  •  Community Terms of Use  •  Help Us Help You

Knowledge Base Search  •  Community Search  •  Learn & Support


Avid Home Page

Go Back   Avid Pro Audio Community > Pro Tools Software > Pro Tools

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 03-26-2023, 07:00 AM
FunkzzaJ FunkzzaJ is offline
Member
 
Join Date: Nov 2018
Location: Sweden
Posts: 248
Default 2023.3 - BAD TRACK eats CPU

Hi all !
Stumbled on something strange here.

Preamble
Upgrading to 2023.3, I took on to go through optimizations again. Did so, and also, moved out and in again between used- and un-uised folders. Arturia is now in the un-used folder. Then I started chasing bad plugs in some older sessions by inactivating/bypassing . After chasing some down, I could run those sessions in buffer size 64, while previously barely doable in size 1024. But it was a little as chasing a gost, because a previously bad plug, could end up good, and vice versa. So then I discovered that the bad behaviour followed Pro Tools tracks rather than plugins.

TESTS
For non-playing Instrument Tracks with Instrument Plugin instanciated on it:
Bad = PT system usage window shows an all-core CPU usage @ 64 buff
Good = PT ssystem usage window shows no or near zero CPU usage @64

Created three similar simple sessions.
7 Instrument tracks with the same instrument plugs instanciated on them
1 AUX track to where all instruments are bussed. AUX out to main out.

Instrument plugins used for the three test sessions were the Mini Grand, XPAND 2 and Falcon 2.8

FINDINGS
The first created track, upper most in the edit window, is where the instrument plugin yields the bad behaviour. All other 6 instrument track plugins was all good behaving.

Moving the first track to another position among the tracks, the bad behaviour follows the track. The now new uppermost track is all good behaving. So I label it a BAD TRACK.

Deliting the bad track makes the now uppermost track now to becom a BAD TRACK.

Workaround I found was to let the BAD TRACK remain, but inactivate it. With that the performance seem to take a serious jump !!

YOU TOO OR IS IT JUST ME?
Anyone have any idea what is happening here, can you reproduce it. Known issue, Bug.

SYSTEM
PC, W11, PT 2022.3
SSD C: 512 GB
HDD D: 1000 GB
DDR4 : 32 GB
Should I provide a Sandra Report?

/T
__________________
Free beer tomorrow !!
- but until then -
we're stuck in the present moment
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Today's AIR FX and Instrument 2023.3 updates re-install 2023.2! off the wall Pro Tools 9 03-28-2023 10:33 AM
chemical that eats away aurolex foam? m4ca General Discussion 3 09-18-2007 05:00 PM
Pro Tools 7.1 eats processors Geenome20 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) 1 11-08-2006 09:18 AM
scsi or ide? 32 tracks eats my power.... tlester 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) 9 08-12-2002 06:57 AM
PT5 Eats, Careful guys! johnwhynot Pro Tools TDM Systems (Mac) 0 06-24-2000 11:49 PM


All times are GMT -7. The time now is 06:39 AM.


Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com