PT 2022.10 crashes with buffer change

[s.d. finley]

MacBook Pro 2020 -11.7 Big Sur- UA Arrow interface-PT 2022.10 Studio

Rather light session 8 audio tracks and very few plug ins. Granted it was 45 minutes of full audio across 8 channels. I change buffer from 128 to 64 and I get the spinning beachball of death. Twice it happened and the 2nd time it crashed Avid Crash manager popped up and I send the report to Avid.

[s.d. finley]

Must be an issue with the longer audio files because when I do the same buffer size change on a session with more audio tracks-30- but less than 4 minutes of music I have no issues at all

[Darryl Ramm]

Or a problematic or corrupted session? What happens after you try a Save Session In for the problematic session? And what happens with doing this in both sessions when you use Built-In Output/Speakers or whatever as the playback engine?

[albee1952]

How much free space on your recording drive?

[s.d. finley]

Originally Posted by Darryl Ramm

Or a problematic or corrupted session? What happens after you try a Save Session In for the problematic session? And what happens with doing this in both sessions when you use Built-In Output/Speakers or whatever as the playback engine?

I will try importing the wave files into a new session. No issues saving that session.

[s.d. finley]

Originally Posted by albee1952

How much free space on your recording drive?

over 350 GBs

[s.d. finley]

Originally Posted by Darryl Ramm

-snip-corrupted session?

Looks like the issue was the session was corrupted. I switched playback engine to MacBook Speaker output, created a new session and imported session data. Thought I would try the import data before importing wavs. New session had no issue changing the buffer to 64. I switched playback engine to the UA Arrow and no issues changing the buffer to 64 then higher and back to 64.

The original session was created on 2022.6. was originally recorded on a Lynx 16 with the USB2 card. I have had corrupted sessions before those behaved much differently. I will have to keep that in mind. Thanks for the suggestion Darryl!

[Darryl Ramm]

Hey neat that worked. With plugins involved in saving the session file I'm surprised we don't see more issues... and I have a theory that session file corruption/incompatibility may cause weird problems more than we think.