Hey,
I was hoping somebody might be able to help me narrow down the source of some issues I've been having. I'm running Pro Tools 11.3.1 on a late 2013 Mac Pro (OSX 10.10.2). I've experience a couple of strange bugs. Last week one my sessions appeared to lose all of it's clips from the clip list and then refused to save, citing a problem 'translating clips'. The regions in the edit window were present as normal and the session played back but the clip list was completely blank.
Yesterday I experienced a bug where a particular session file wouldn't open, even though I'd be using it ten minutes prior. Attempting to open the session resulted in the following error:
Could not complete the Open Session... command because Assertion in "/Volumes/Development/151228/ProTools/App/MacBuild/../PtSess/PtSess_RunTime.cpp", line 16689.
I know these symptoms might be a little vague but I was hoping someone might be able to point me in the right direction for at least beginning to identify the problem.
I got around both of these session errors by importing tracks into new blank sessions and copying the media.
Thanks,
Hurricane
I was hoping somebody might be able to help me narrow down the source of some issues I've been having. I'm running Pro Tools 11.3.1 on a late 2013 Mac Pro (OSX 10.10.2). I've experience a couple of strange bugs. Last week one my sessions appeared to lose all of it's clips from the clip list and then refused to save, citing a problem 'translating clips'. The regions in the edit window were present as normal and the session played back but the clip list was completely blank.
Yesterday I experienced a bug where a particular session file wouldn't open, even though I'd be using it ten minutes prior. Attempting to open the session resulted in the following error:
Could not complete the Open Session... command because Assertion in "/Volumes/Development/151228/ProTools/App/MacBuild/../PtSess/PtSess_RunTime.cpp", line 16689.
I know these symptoms might be a little vague but I was hoping someone might be able to point me in the right direction for at least beginning to identify the problem.
I got around both of these session errors by importing tracks into new blank sessions and copying the media.
Thanks,
Hurricane
Aucun commentaire:
Enregistrer un commentaire