Save Copy in - crashes

[Sir Hannes]

Hi,

I am on PT11, Mavericks. I must clean my 90min-session so I want to do a copy-in on my external harddrive. that's not working. either its a WD or a Samsung or anything else, after 20min of working, PT11 crashes. There is no help-file or text what happend. On the harddisk I find a folder with around 20 to 25 GB (the original session is 56GB, videofile is just 2gb) and a strange file "sdfcZWMFcrvhHTBX", no file-extension, OSX says its a PT-Session file.

- the harddrives are ok (checked with harddrive manager). and right now I finished copying the whole session.

What's wrong? Any ideas or links?

[Drew Mazurek]

Try doing it to the same drive, then you can just drag and drop afterwards?

At least one variable will have been removed.

[ronwasserman]

Create new session, import the session you're working on and then try a save copy as. (another thing to try.)

[Sir Hannes]

Hi,

can't copy on the same drive, SSD is on limit
And I am too scared to import the whole big session with tons of data in a new session with all plugins and routings etc.
I work today in the mixing theatre, there I'll try their MacPro. Its PT11 on MountainLion.

Can't understand that PT behavior.

Cheers
Joh

[Farhoof]

If I'm not mistaking, this can happen when the copy folder path is too long, combined with a very long file name in the clip list. Try saving it to the root folder of the backup drive.
Or it could be some illegal character like "/"

[Shifted Music]

Originally Posted by Sir Hannes

Hi,

can't copy on the same drive, SSD is on limit
And I am too scared to import the whole big session with tons of data in a new session with all plugins and routings etc.
I work today in the mixing theatre, there I'll try their MacPro. Its PT11 on MountainLion.

Can't understand that PT behavior.

Cheers
Joh

when you say SSD is on limit... you mean its just about full? is so how much room remains.

It is possible that save copy in needs room for some temporary files to facilitate the save.

If at all possible make more room (preferably permanently) on the ssd to start.

which may be why it will work on another machine, if it did on the one you were going to try it on.

[Sir Hannes]

Of course, there was no time at the mixing stage for copy-session-in... I am so glad that there was only on PT crash while mixing. But read my experiences now at the finishing process, please:

My copy-in setting is:
- 24Bit without changing audio data
- shorter names (english roman)
- only main playlist
- only selected tracks
- no video

I did what you guys told me to try:
- shortest folder path, no special characters
- more empty space on internal SSD => same issue (ERROR, PT11 crashes, leaving a 25GB folder without a session file)
- creating a new session, import selected tracks => big big error: PT generates more and more data, session grew up till my SSD is full (> 80GB) - this is a serious problem/big bug!

or:
- creating a new session, import selected tracks => audio files gets restored until task manager says "Unknown Error" - nothing else, no further description. feels like pointing around in the air

I checked the release notes for the 11.2.2 update - but nothing special to risk my running feature film

What the hell is this software doing?
Where can I find a email-support or contact form for the technical stuff?

[Darryl Ramm]

This can be caused by a corrupt session, can be a corrupt plugin, with possibly no other signs.

Trashing prefs might be worth trying. If that does not work then do you have older archives/backups of the session? I'd also try opening a copy of the session on a different computer, try doing a save as of that even if all the plugins and IO is wrong, you just want to see if it can be opened/save as works at all. If not then you know you have worse problems...

I hope you did that new session creation test with a totally empty session, not creating from a template, not a copy of any other session. And I hopefully you also tried trashing prefs first.

Rule #1 of debugging issues is always suspect plugins... so you should temporarily move all third party plugin files out of the Pro Tools plugin folder and try again to create a new empty session. That will give a clue if the bug is in a plugin or in Pro Tools itself. If it does not happen to bare Pro Tools then you can put the plugin files back in batches to try to track down which one is the problem.

Avid support is contactable if you purchase an ASC or if you have a support subscription. Details on their (European) Avid Web site.

[dwaynedelario]

Just to throw it out there... you could import everything into a destination session without copying anything, and then use the project window to copy all the audio into the new directory. Might be worth a shot.

[dwaynedelario]

Sorry I realize the terminology has changed in PT11. By Project window, I mean a new workspace and then click on the session in the lefthand tab. Then click into audio files folder. Select all (or sections at a time) and re-link with copy.