Damaged Project

I was doing vocal recording today in Logic 8.
After the whole day Logic crashed I got the usual - Saved as crashed option. After restart "Minor Repair" and the "Warning - Damaged Song"
The whole song opened containing nothing at all.
I opened the version I saved 30 minutes before in another name. Same thing here.
I opened all the 10 previous versions in Project File Backups and all of them are the same?
How could this be possible that 12 different saved project files are all damaged?
Is this a nasty bug or? I have never seen it before in my whole life and it scared me as I might revert back to Logic 7 after this. A whole day of vocal editing down the drain!
I have always been able to get back to a project from the Project File Backups?

You can't open projects in older software.

Similar Messages

  • Have a message window that says damaged project can't open

    Have a message window that says can't open project because project damaged can this be resolved and reopen to continue working on project?

    Mumphie
    What version of Premiere Elements are you using and on what computer operating system is it running?
    You have not given us enough information with which to help you. For starters, besides version and computer operating system, please supply
    1. Project Preset
    2. Properties of Source Media
    3. Details of the projects save/close.
    Also please review the Adobe document on troubleshooting damaged projects.
    Troubleshoot a damaged project file | Adobe Premiere Elements
    After that we can customize the troubleshooting strategy to your particular circumstances.
    Any questions or need clarification, please ask.
    Looking forward to your follow up.
    Thanks.
    ATR

  • HELP! Warning! Damaged project! (Ginst)

    Today when I launch Garageband on my iPad I get the message:
    "Warning! Damaged project! (Ginst)". I press OK and Garageband then tries to load the last song I was working on and then crashes.
    Any help would be greatly appreciated.
    David

    And I can't even get into GarageBand now to do anything else, since it auto-loads the last project you worked on.  Massively frustrating.
    In that case it should help to reset GarageBand. You can do that from the "Settings" app. Scroll down to GarageBand and switch the "Reset GarageBand" switch to "On".
    This will reset it to factory settings and you can pick a different project, when you open GarageBand again. Sometimes this even helps to open a broken project, but I would not not rely on that, that the corrupted project can be opened after resetting GarageBand.

  • Damaged Project : "Encapsulate or Repair" ?

    Yesterday I received the dreaded 'damaged project' error message that I've read so much about...
    Luckily I was able to restore the project using an earlier version (in song backups). I did attempt to repair the project prior to this using the "repair" option (which clearly doesn't work - it just duplicated all my tracks & messed up all my sample references). I presume the "encapsulate" option is just a report summary, but correct me if I'm wrong - has anyone tried this option or had any success with the "repair" option, or is it simply quicker (& better) to rebuild a project from an earlier version?

    What causes a project to become damaged? It seems unique to Logic 8 (I've not experienced this with earlier versions of Logic or any other sequencer)... Time is money on any commercial session, so I'm keen to avoid it in the future.

  • Adjustment Layer Crashes Premiere or Damages Project

    Nearly every time I have tried to use an adjustment layer in Premiere Pro CS6, the application has hung if I tried to scrub through the video. Yesterday I decided to try placing an adjustmnet layer and only using the play function rather than scrubbing and it seemed to work alright. However, this morning premiere will no longer open the project file. Instead it give me the error message "The project could not be loaded, it may be damaged or contain outdated elements." This is an extremely heinous bug! Can anyone help or is this feature really just unusable?!!
    Additionally, because I was so fastidious about saving, given the previous crashes, the only functioning autosave is 6 hours out of date!
    HELP!

    I use ALs a lot, and haven't yet seen this behavior.
    Have you added any effects to the AL?  Does scrubbing work OK without the AL?

  • Premiere Elements 8 - Damaged Project

    How do you repair a damaged Premiere Elements 8 project. Mine refuses to open, saying it's damaged

    You might get better answers in the dedicated forum for Premiere Elements:
    http://forums.adobe.com/community/premiere_elements

  • Corrupt / Damaged Project

    I worked really hard on this ongoing Captivate 2 project
    & decided to add Navigation Menus to it via Captivate 2's new
    Menu feature.
    I did that & went back & forth a few times to alter
    the Menu items.
    All of the sudden, I tried opening my project & it tells
    me that the project is either damaged or corrupt.
    I didn't do anything negative to it; didn't loose a network
    connection while I had it open; I tried rebooting the file server a
    few times & to no avail, cannot open this particular project.
    This happened a few days ago & I'm still stuck.
    Does anyone have any advise that they can share?

    Hi Michael
    I'm seeing lots of references here to networks. Is your
    project by chance placed on the network? And you are opening
    Captivate on your local PC and making edits to the project while it
    is in the network location? If so, that's likely your issue. My
    guess is that there is typically little to no chance of recovery of
    the original project. So you will likely have to start over.
    One possibility would be to try creating a new, blank project
    that is sized identically to the errant one. Then click File >
    Import/Export > Import Slides/Objects from other Adobe Captivate
    projects... and see if the movie can be recovered that way. I
    believe I've seen my fellow Community Expert Larry Walther (AKA
    CatBandit) report that if you get to the Captivate start screen and
    hover the link to the corrupt project and you actually see
    information, your chances of recovery are greater. But if you don't
    see information in the popup, you are probably sunk. Not sure if
    this still applies in the Captivate 2 world, but it probably does.
    Assuming this fails to work, and further assuming you were
    editing files while they are on a Network share, consider this a
    lesson hard earned and vow never to edit projects while on the
    network ever again. It's always best practice to work off your
    local PC. This means the C drive. Now if your IT folks insist on
    having your project files stored on the network share for backup
    purposes, this is fine. Just be sure to copy there frequently. Not
    only will it provide them with a warm fuzzy, it will likely give
    you a good avenue of recovery if something happens to your project.
    In addition to this, you might want to take a moment to complete a
    Wish form asking the Captivate developers to please, Please, PLEASE
    provide some sort of a decompiler that will take a Captivate
    created. .SWF or .EXE and convert it to a working .CP file. I
    suggest this because I regularly see posts where the .CP file is
    somehow corrupt and the person has a working .SWF. And I know other
    decompilers are out there.
    The link for suggestions is visited by
    clicking
    here.
    Cheers... Rick

  • Damaged project won't preview

    Warning - An iMovie project file can become corrupted and there doesn't seem to be any way to recover it. Like many others on this forum, I've learned this the hard way. Just search for "repair" or "corrupt". Plenty of posts but no solutions beyond reverting to a backup. Are there really no solutions?
    In my case, iMovie starts and is working fine on other projects, but I've got one project that hangs iM whenever I try to preview ("play") it. By hang, I mean the beachball spins and CPU usage goes to 100% forever. Oddly, I can skim through it OK and I've even been able to copy and paste out the sequence into a new project. That'll save me a ton of work but I'll still have to replace all the music and titles.
    I'm not happy that so much work has been lost. This shouldn't ever happen. But you should plan for it if you don't want to be crying with the rest of us.

    Rockin' good news. It appears that, while my project is damaged and cannot preview, it functions in every other way. I was able to continue editing, albeit "blindly", and then share a fully working movie to the media browser. Whew!
    This would have been tough if my project wasn't already almost complete. All the video was done and all I was doing was adding the final chapter markers and placing a few songs. This isn't too hard to do without previews.
    One other comment: If you're really careful about setting your preferences and project settings, it's possible to copy and paste from one project to another with pretty good fidelity: Transition and slide times, and KBE settings can be maintained. This is a partial solution to adding one project to another, to concatenate them. I had a problem moving stabilization settings, they all got set to "max" in the transfer, but later found a preference setting that might have caused that. I haven't confirmed whether you can avoid that problem. Of course sound effects and music don't transfer, but these can be replicated fairly quickly if they weren't too complex.

  • Damaged Project File

    I was saving a project i was doing and the computer crashed and when i went to open it back up after it restarted premier said the file is damaged and can not be opened. is there anyway to get it to work because i have spent way to much time on it to start over again

    Look in your Autosaved files folder. Which should be a subfolder of the
    project folder. You may loose some work, but its better than having to
    recreate from scratch.

  • How to repair a damaged project microsoft?

    MPP Project file causes Project 2010 to the closure. . Does anyone have a clue as to how to solve?
    There is a way to solve the mpp viewer than it is online?

    MPP Viewer Tool from http://www.mpp.viewertool.com/ great
    for recovering files from a flash and other media.
    Here's another version of кecovery  : http://www.filerepairforum.com/forum/microsoft/microsoft-aa/project/1118-how-to-view-corrupted-mpp-file-of-microsoft-project

  • I am unable to open a project that I have worked on and saved.  I get an error message that the file is damaged and cannot be opened.

    I am unable to open a project that I have worked on and saved.  I get an error message that the file is damaged and cannot be opened.

    Leslie Tanaka
    Travel and detours have kept me from following up sooner. If the problem that you wrote about still persists.....
    Let us go back over that Adobe document regarding troubleshooting damaged projects.
    3. Delete the Application Preferences
    Where you able to follow that path and delete the Adobe Premiere Elements Prefs file at the end of the path? And, after you did, did the saved/closed programs still refuse to open? If you could not carry out this procedure, what were the limiting factors that kept you from do
    7. Test to see if individual media files are causing the problem.
    That is an important one. How far did you get into following the instructions given in the document? If you could not complete the test, what was the major block that prevented you from doing so?
    I want to make sure that we have gone through everything in that document and ruled all factors there in or out. If it was a matter of you not understanding the instructions, I am hoping that the above will channel you questions to me so that I can clarify anything that you did not understand in the Adobe document instructions.
    I do not recall if I asked previously. Even if you cannot open all your saved/closed projects, can you still open a new project and save/close it? Maybe even reopen it?
    Please review and consider.
    Thank you.
    ATR

  • Transfer to new PC: The project could not be loaded, it may be damaged or contain outdated elements

    The Problem
    I have transferred a large and functioning Premiere Pro project to a more powerful PC but am unable to run it, stopped by the error message "The project could not be loaded, it may be damaged or contain outdated elements".
    Facts
    The new PC has a 6-core processor and a different hard drive configuration but the operating system on both is Windows 7 and both PCs host up-to-date Premiere Pro CS6 (as part of Adobe Production Premium). The PCs are networked and Premiere Pro on the old PC can successfully load and run the project file located on the new PC, proving that the transferred file is not damaged. Also, preceding versions of the same project generate the same error message when run on the new PC except, very oddly, for earlier versions saved on or before 28 June 2011, when the project was only a fifth of its current size; those versions load correctly. Contemporary notes show that the editing carried out that day was simple timeline editing, ie no After Effects etc (that came later), and the project has worked fine then and since.
    So I don't have a damaged project file and don't know what "outdated elements" means.
    Help
    Any help solving this problem would be much appreciated.

    Hi Vinay
    As suggested I renamed the additional folder, created a new project, set 'Custom' editing mode, 'Microsoft AVI' as the preview format with 'Uncompressed' codec.
    Unfortunately the results were similar to before: On importing the original project into the new project I was sequentially asked for the locations of various files, including After Effects .aep files. The final file location request, for an mp3 audio file, was followed by lots of conforming and indexing. During this process the 'Where is the file XXX.mp3? window stayed locked open. Eventually, with all conforming etc finished, this window was still open and locked. Clicking anywhere on the screen caused a 'ding' and another, smaller, box opened, listing three .aep files. This box asked no questions and gave no options for selecting a file location so, with the topmost file highlighted, I just clicked 'ok' and the box disappeared, leaving the 'Where is the file XXX.mp3?' box still open.
    The importing process took about 30 minutes. I waited another 10 minutes, in case something was happening in the background, but with the Task Manager CPU usage value sitting on 0 or 1%, I used it to shut down the project.
    For what it is worth, I created a simple new project on the old PC – just a few video clips and transitions in a single sequence (no After Effects etc). This project was then transferred to the new PC and it opened successfully.
    Again I remain grateful to you for this and any more advice.
    Best regards
    Dave

  • Flash Pro CC saved fla project - "Could not load scene into memory. Your document may be damaged."

    Hi all, I've been working on a project in Flash Professional CC in windows 7 that was started in a previous version of Flash Pro and occasionally after I've saved the project and tried to open it the next day I get the "Could not load scene into memory. Your document may be damaged." message and only a blank Scene 2 in the project. I've previously been reverting back to the old saved project file and starting over. Its wasted a lot of time so far.
    I can still open the same exact project in CS6 on another older computer but not in CC. I can also save the fla in CS6, transfer it to the other computer and then it will work again (for now). This isn't going to be an option in the future as CS6 was a trial version that is on its last use today.
    I've tried to create a new flash pro cc project and just copied and pasted the library and scene layout from the old project into the new project. This worked for a couple of saves/ opens but the error has happened again.  I'm scared that now that I've reached the point in the project were my work in the animation/ visual side will start to be more intensive that I will continuosly have to worry about losing all of my work. I'm using a document class so the AS3 code hasn't been an issue thankfully. Any help would be appreciated.

    Thanks for the reply Amy, that is essentially what I am doing already only I'm not using version control software I'm just managing it on my own since its a solo project, though I have been considerring using git anyway. It still doesn't explain why I can open and save the supposedly damaged project (according to CC) in CS6 and only then will it work again in CC. Also I'm not gettting a chance to save as a new version over and over for long. Its only a couple of days max, usually just over one day, and I've primarily been working on the code in Flash Builder with little functional change in the actual fla project. Its primarily changing movieclips instance names, which in this project is tedious and time consuming. Having to revert back to the older working version is exaclty what I'm trying to avoid. I shouldn't have to commit the project to a repository every little change that I make to the fla file.

  • About that damaged Premiere Elements 0.9 project of mine + a few questions....

    First off, I should have posted this thread for a while ago, but stuff in life etc came in the the way and such. Anyway, remember that stupid damaged project of mine which kept on crashing my Adobe Premiere Elements 0.9 with a "Serious Error" message?. Well, that issue, as far as I can remember, never really got resolved. However, it sort of got resolved on it's own as I went further sideways instead of trying to go forward when I couldn't. More clearly, even tough the project was damaged and kept crashing my Premiere Elements, I was still able to get out a WMV movie/video of the half-finnished project. Then I uploaded that video in that little test-project I did a time ago when troubleshooting about this. And in that test-project I continued from where I last was working on the half-finnished project. So far and up until the finnished results of the whole project and video, that newer project never ever crashed nor interrupted anything like the other, damaged project did. And now, for a while ago, that project I started on, which became damaged and started crashing, and by continuing on it on from a saved videoversion of it on a new project, it's all completely finnished and working very well. I still have that musicvideo (yes, it's a musicvideo project) saved as a WMV video file, still working and going smoothly and as I created it to be, all completely finnished. While I'm so happy with the ending results and that this all finally sorted out in the end, I am still kind of confused and also pretty nervous and worried about If this same crashing dilemma, like with that damaged project of mine, might happen again in the future... And If it does, what then? Is my Afobe Premiere Elements program then damaged forever? Will I be able to create new projects and work with them as I use to without any worry etc? Or is this project-crashing problem with that "Serious Error" message just some kind of random probem which may and can occur from time to time randomly? Is this just some kind of random thing that just sometimes occurs and is to walk by with creating a new project like I did? Or is this problem something to look out for worry about in the future?
    I've double checked also, nothing is wrong with my computers speed, harddrive nor prestation etc, plus I'm using a PC for my videoprojects alongside with all my games. But I've heard that using too much videoeffects in a Adobe Premiere project, even in the latest version, may be too much for the project and thus it'll crash like my damaged project did.... But then again, this is just something I've heard. What do you guys think? Do you believe and know If using too many video effects in a Premiere Elements project, even the latest versions of the same program, could be too much for the project and thus causing it to crash and cause trouble etc? Or do you know of another theory of why a Adobe Premiere Element project just suddenly goes damaged and just goes crashing while a "Serious Error" message comes popping up? Why is things like this happening and what can be done to solve and fix it?
    I know that I don't have any reason to ask for the moment as my problem sort of got resolved, but I'm still worried about my future projects I have in planned. Also, I'm thinking sort of forward and to the future here, and then all those Premiere Elements users who also may encounter this same problem....
    Any advice, help and tipses by and from anyone on this issue and the questions I asked here is highly welcome and appreciated!
    Greetings,
    ZeldAlice

    First off, I should have posted this thread for a while ago, but stuff in life etc came in the the way and such. Anyway, remember that stupid damaged project of mine which kept on crashing my Adobe Premiere Elements 0.9 with a "Serious Error" message?. Well, that issue, as far as I can remember, never really got resolved. However, it sort of got resolved on it's own as I went further sideways instead of trying to go forward when I couldn't. More clearly, even tough the project was damaged and kept crashing my Premiere Elements, I was still able to get out a WMV movie/video of the half-finnished project. Then I uploaded that video in that little test-project I did a time ago when troubleshooting about this. And in that test-project I continued from where I last was working on the half-finnished project. So far and up until the finnished results of the whole project and video, that newer project never ever crashed nor interrupted anything like the other, damaged project did. And now, for a while ago, that project I started on, which became damaged and started crashing, and by continuing on it on from a saved videoversion of it on a new project, it's all completely finnished and working very well. I still have that musicvideo (yes, it's a musicvideo project) saved as a WMV video file, still working and going smoothly and as I created it to be, all completely finnished. While I'm so happy with the ending results and that this all finally sorted out in the end, I am still kind of confused and also pretty nervous and worried about If this same crashing dilemma, like with that damaged project of mine, might happen again in the future... And If it does, what then? Is my Afobe Premiere Elements program then damaged forever? Will I be able to create new projects and work with them as I use to without any worry etc? Or is this project-crashing problem with that "Serious Error" message just some kind of random probem which may and can occur from time to time randomly? Is this just some kind of random thing that just sometimes occurs and is to walk by with creating a new project like I did? Or is this problem something to look out for worry about in the future?
    I've double checked also, nothing is wrong with my computers speed, harddrive nor prestation etc, plus I'm using a PC for my videoprojects alongside with all my games. But I've heard that using too much videoeffects in a Adobe Premiere project, even in the latest version, may be too much for the project and thus it'll crash like my damaged project did.... But then again, this is just something I've heard. What do you guys think? Do you believe and know If using too many video effects in a Premiere Elements project, even the latest versions of the same program, could be too much for the project and thus causing it to crash and cause trouble etc? Or do you know of another theory of why a Adobe Premiere Element project just suddenly goes damaged and just goes crashing while a "Serious Error" message comes popping up? Why is things like this happening and what can be done to solve and fix it?
    I know that I don't have any reason to ask for the moment as my problem sort of got resolved, but I'm still worried about my future projects I have in planned. Also, I'm thinking sort of forward and to the future here, and then all those Premiere Elements users who also may encounter this same problem....
    Any advice, help and tipses by and from anyone on this issue and the questions I asked here is highly welcome and appreciated!
    Greetings,
    ZeldAlice

  • Project appears to be damaged and cannot be opened

    Hi there,
    Premiere pro edits made in Trail version of Premiere pro CS6. saved on external hard drive. They now won't open on the new full version of Premiere pro CS6 have bought and installed.
    This includes Auto saved versions and opening new project and trying to import.
    Same PC laptop but has been recently formatted -
    Windows 7
    Radeon graphics
    Intel core i5
    Could loading a beta version of a graphics card have anything to do with it. The trial version worked fine on my laptop but I the full version wouldn't because of a video module problem which i had to fix but downloading a AMD beta version for it to load.
    Any help would be much appreciated
    regards
    David

    pamelaproof
    Just saw your thread and thought that I would contribute these comments....
    a. As asked by SG, what version of Premiere Elements are you using and on what computer operating system is it running?
    b. I am jumping ahead of the classical questions on your source media, project settings, computer environment and the like to cut to the damaged project aspects of issues. In that regard have you read the Adobe Tech Note that addresses troubleshooting suspected damaged projects?
    http://helpx.adobe.com/premiere-elements/kb/troubleshoot-damaged-projects-premiere-element s.html
    c. But you cannot escape the answers being in the details. Best not to take anything for granted by the person asking the question nor the person asking the questions. SG started off with some important questions. I do not see answers to those questions yet in order for him and others to sort through to an answer for you. Please answer his questions before mine so that we can rule factors in or out as asked.
    Thanks.
    ATR

Maybe you are looking for