Trouble Opening 12.3 Sessions on PT 10 System

[anackman]

My home studio has PT 12.3 and I do most of my daily work from there. But, I also have a commercial studio I work from when there are bigger sessions. That commercial studio runs PT 10. I am having a lot of trouble opening my 12.3 sessions on PT 10.

Unless I am totally in the dark, I was under the impression that 12.3 sessions could be opened on earlier systems. Right now, my work-around is to bounce stems of my 12.3 sessions and re-import them into new PT 10 sessions at the commercial studio. It sucks. This is an awful task because it duplicates all of my stuff and gets confusing.

What is the problem here? Why can't PT 12.3 sessions open on PT 10 systems?

On 10, Pro Tools loads the splash screen and all plugins, then it eventually crashes once it tries to render all the files and tracks of that session. I can't get past the rendering section of the loading process.

Please help. If there a simple fix or something I can do on my end, I'm happy to try it.

Am the only one that needs to use older systems occasionally? I can't believe every studio in the world has upgraded to 12, or even 11.

[lancemcv]

Can't you do a session save as older versions pt 9-10. I don't have put 12 but in 11 you can save sessions in older formats, or you could try starting a new pt 10'session and see if you can import the tracks from the pro tools 12 session.

[sw rec]

Lots of potential issues here...PT 12 is a TOTAlLY different animal than PT 10...unless your PT 10 rig has RTAS or 32-bit AAX versions of all the plugins used on the PT 12 rig, you're going to have all kinds of error messages about plugin compatibility.

Also wondering why AVID would write PT 10 to consider sessions on a version of Pro Tools that didn't even exist yet...sort of like expecting a PT 8 rig to open PT 12 sessions. It won't even know what a .ptx file IS. Backwards compatibility typically goes the OTHER direction...where PT 12 will open older (like PT10) sessions...then it's best to "save as" and work on the session as a PT 12 session.
But. Direct answer to the question...you should indeed do a "save as" and select a previous PT version from the drop-down menu. Then you should be good to go. I've done this where I wanted to open up a PT 12 session on my backup PT8.0.5 rig, and it works just fine.

[anackman]

I still can't open up PT 12.3 sessions on PT 10 systems. I've tried everything disabling troublesome plugins, saving a copy back at PT 9. Still nothing,. If I have a session that was started in PT 12.3, then I try to open it at a different studio running PT 10.3.9, Pro Tools crashes as it's loading the tracks and audio. It gets past the PT splash screen and loads all the system info, plugins, etc, then it crashes as the status bar is going across loading all the audio files, etc.

It makes no sense to me.

[albee1952]

Try holding the SHIFT key while opening the session. This will make all plugins inactive(but retain settings). If the session opens this way, at least you know its down to plugins.

[guatamas]

Originally Posted by albee1952

Try holding the SHIFT key while opening the session. This will make all plugins inactive(but retain settings). If the session opens this way, at least you know its down to plugins.

It does sound like it could be a plugin issue.

[sonidojamon]

Just found this:

Pro Tools 12 sessions that use more than 4 gigabytes of RAM will cause Pro Tools 10 or lower to quit unexpectedly
(PTSW-181963)
If you attempt to open a Pro Tools 12 session that uses more than 4 gigabytes of RAM in Pro Tools 10 or lower, Pro Tools will quit un-expectedly. To open such sessions in Pro Tools 10 or lower, first reduce the amount of session RAM usage to less than 4 gigabytes in Pro Tools 12 by removing virtual instruments that take up system memory.


Hope its helpfull

[midnightrambler]

Yes my first guess would have been the 4Gb limit that Pro Tools 10 has. You'll have to go back to 12 and commit any memory-heavy VIs and plug-ins (Melodyne in Polyphonic mode can eat up loads), delete unused playlists, delete unused/inactive tracks, commit Elastic, delete unused clips from the bin. Then you may have some luck opening it in 10.