Access Violations in PT 11.2.1

[Dave Modisette]

Could not complete the Open Recent Session 4 command because Access violation occurred, unable to read location: 0x0000000000000008

This is happening on some projects but not in others. I am restoring 11.1.3 to see if the problem disappears.

[Dave Modisette]

I'm back on PT 11.1.3 and the problem project is working fine again.

Anyone with an idea of what the problem could be? FWIW, I tried several versions of the problem project and they all threw the access violations.

[Bob Olhsson]

When I've gotten that it turned out to be a clocking issue.

[mrtomcat]

no problems here

[Shifted Music]

I have seen this error SEVERAL times when opening a session and after king an update or something like that.

for me my Mbox 3 Pro being reset or rather turned off and on and restarting the computer fixes it.

its a crazy thing in that the error doesn't at all lead me to think thats the cause but in the last few months and during times of updates and what not Ill leave the box on and install a new PT version then get the error when first opening it up...

I also pre maturely revered back and although it didn't take long to go back to my clone... I simply had to power cycle my interface and computer

[Dave Modisette]

Thanks for the replies. I'll install the update and see if fiddling with the RME settings will fix things.

[sw rec]

I have access violations occasionally on 11.1.3/Win 7, and they're ALWAYS at the same address.

[Dave Modisette]

Well I've installed the 11.2.1 update and the access violation window is back.

This time it says:

Could not complete the Open Session... command because Access violation occurred, unable to read location: 0x0000000000000008

A little different but it's the same location.

My soundcard is internal so there is no cycling it on and off. I've changed the Clock mode and buffer size and rebooted but I still get the same message.

FWIW, it's an RME HDSP9652 card.

[sw rec]

Watching this intently...mine only does it when I'm recording, but when it does, it makes the track completely unusable. It's done it on EVERY version of 11 to date.

[Dave Modisette]

And I'm back in PT 11.1.3 and the sessions are opening as expected.

It's been suggested in the GearSlutz forum to create a new session and then import the problem session tracks into it.

I might get industrious and try that to see if it works or I might just stay safe and use the tried and true workarounds.

Hey, if I can make SONAR work for 13 years, I can make any software work for me.