PT11 file unreadable by PT11

[Nayon]

While erasing Melodyne parts, a glitch happened and when I play over this part, the sound for the entire file goes out. I tried to cut out the corrupt section but to no avail.

I had a previous version saved and I'm trying for the first time (I'm a new user) to import files or clips, but no matter what file I'm in, the import window tells me the PT file is unreadable.

What am I doing wrong? Is there another way to copy audio from a file to another?

[DetroitT]

Maybe try bypassing Melodyne or deleting the sound you transferred into Mel.
When Melodyne has audio in-it, that is dominant.

[Nayon]

I have tried importing from a template file which has no recording at all and the import window still tells me that PT files are unreadable. I can't understand it since the files are fully operating when I open them with PT and play them.

[Southsidemusic]

Originally Posted by Nayon

I have tried importing from a template file which has no recording at all and the import window still tells me that PT files are unreadable. I can't understand it since the files are fully operating when I open them with PT and play them.

Sorry if i don't understand what you are saying but are you trying to open PT files in Melodyne or are you trying to open old session files made in PT11 in PT11?

Best
Chris

[Nayon]

What I am trying to do is this: I can't seem to be able to work with my most recent file (post glitch) because no matter what I do, when it plays over the part when the glitch happend, the sound goes out and then I have to close the file and re-open it for the sound to come back.

So I am trying to work on my back up file I made of the one I was workin on, and I am trying to import the guitar tracks I made, post back up, but before the glitch happened, to the saved file. From my back up file opened in PT, everything plays nice. I go file/import/audio and select the damaged file for source and a message appear at the bottom of the import window telling me the file is unreadable by PT. I tried import clip group instead and get the same message.

The parts before and after the glitch plays fine, I should be able to access them. The easiest thing would be to get rid of this glitch but I have no idea how to do it. It made a strong crakeling noise when it happened. I have erased all Melodyne files in that region, tried a time cut to that region and it was still there.

[Southsidemusic]

That sounds absurd

I will talk to one of the engineers in and see what he says

I have never heard of this and therefor I can't chime in with any valuable help but hopefully someone else will be able to offer advice and I will ask here too.

Best of Luck
Christopher

[Nayon]

Bare in mind I have tried to import from other undamaged files and I get the same message.

The only detail I can think of that may have some influence on this is this;

for some reason, when I save my sessions, the files end up in ''my documents'' instead of the bounced files. I've never had any problems working on them afterwards so I didn't make a big case of it. Should the files be stored in a special place for them to be ''readable''?

[Bruce Paine]

I would try creating a new blank session, and importing session data from the original:
Pro Tool Reference Guide (v11.2)
Chapter 17: Importing and Exporting Session Data

These subsections may help:
Importing Session Data...328
Import Session Data Dialog...330

[Southsidemusic]

The files assosiated with the session should be on an external harddrive and in the audio bounce folder where your other audio files are. If you are recording to your main computer drive you will have issues like this crash and other problems all over the place.

Check to see exacly where the files end up and let us know

Christopher

[Nayon]

To Bruce Paine:

Thank you for your suggestion, I have tried this but I still got the same message.


Christopher;

Thank you for all your attention. Indeed I am not using an external hard drive, only an exterior memory. For the moment, I think I'll just re do the lost recording and I will look into making sure the next files end up in the bounce files folder. I'll try to transfer the ones I have already to see if it makes a difference at the 'unreadable' level.

Thanks again.