Thanks for replying. I got so frustrated I shut down my laptop and walked away. When I turned it back on and turned on FCPX the timeline had suddenly reappeared.
Tom, I would love to have offered a screenshot. Not sure how interesting it would have been, as the entire window the timeline shows up in, was literally 1 whole solid shade of light gray. I'll post a screenshot if it happens again.
Thanks for responding so quickly.
---- correction --- it just happened again. I will try and post a screenshot.
This first view is just after I opened the project that I first noticed the problem in the last time. I explained what happened and how it happened, above.
I noticed this time around that when I opened another project BEFORE this project, everything appeared just fine. So I thought my problem was solved. However, when I went to work with this project, it happened again.
This is what it looks like when I choose the "show timeline index" option (red arrow). You can tell FCPx is trying to draw the window, but is unsuccessful. Look at the tip of the yellow arrow. You can see part of the window appears to be drawn, but that's it. That's all it will do.
I suppose my next step will be to delete this project and start over, and see if this happens again. I'd rather not recreate this, as it could be a potential nightmare if it happens to one of my projects which I've spent a good deal of time on.
I have had (EXACTLY) the same problem for about a week now. My timline in one project turned completely grey and I have not been able to open it since. I can open the timeline for other projects if I do not open the damaged project first, but if I go into the damaged project then try to open a different one afterwards, then none of the timelines for any of my projects work. I can play the damaged project by selecting it in the projects window and hitting the space bar, but it plays with no sound (the sound still works on my other projects, just not the damaged one).
I have trashed my preferences, I have relinked files, I have restarted the program and my computer several times, all with no result.
I am curious, what happened when you deleated the project and started over? I am hesitant to do this just because I don't want to spend another 3 months on a project only to have it disapear. If anyone knows what is happening and how to fix it, any help would be appreciated.
Hi there Tom, no I didn't trash my preferences. I've owned a mac since 2008 and through all of my issues I can honestly say I have never had to trash my preferences. The mere sound of it makes me nervous. I'm just glad i realized there was a problem before Terrapin86, here did. Losing a 3 month project would have done some damage to my mac loyalty (having a microsoft coder for a husband makes it an easy turn-to-the-darkside option).
I think the problem may have begun with my the first chunk of video I brought down to the timeline. I'm only guessing this is the problem, but it's the only one that makes sense.
The first clip I decided to work with, which I dragged to the timline, gave me an error message, of sorts. FCPx said it couldn't recognize the file type (?) and asked me what size I wanted to make it and what frame rate I wanted to use. Normally this is an automated process, but because it couldn't figure out this info on its own I was going to have to put it all in there myself.
Instead of doing that, I deleted the clip I put in there and went and found a clip that did have all of the necessary information, and I used that as my first clip 'for the moment'. After FCPx took the info it needed to establish the properties of the project I started dragging the clips I was going to use, to the timeline, and then I deleted that first clip (because my intent was just to get a clip in there that could give FCPx the project properties information it needed).
I'm assuming this is where the problem came from. The way it manifested itself though, I just don't understand. Because it happened the way I wrote at the beginning of the string. I wasn't even really "editing" anything at the time. I was just moving along the timeline, looking at clips, and ... *poof* it all just disappeared on me. But like Terrapin86 said - I could still play the project because I could see it in my viewer window. Weird, but true. I could hit the play button in the viewer window, play it, and stop it, but as far as anything to do with the timeline, that was gone. Disappeared.
If I restarted FCPx I could use any other project and they would all work just fine, but like Terrapin86 said, if I used the damaged one and then went to view the projects that were not damaged, they would all appear to have this same timeline problem. On a reboot, they would all return to normal, and if I used them but didn't touch the one that was truly damaged, they would work just fine. But once I accessed that damaged one, ... everything broke.
Terrapin86 - to answer your question - I hadn't done much work on mine so I could easily delete and start over. That's what I did. I'd say try making a duplicate project, but you'd just wind up copying the mistake over, most likely. I wish I could be more help.
I have had the same problem for the last four days. My timeline and timeline index vanished when I simply tried to alter the time of an audio clip. Once I got into the problem, I realized that the timeline data was there, even after the timeline and it's index had vanished. I was able to use the right arrow (player controls) to move along to each element in the invisible timeline and see the related data in the info window. I could even select all clips and see that the info window was now showing multiple values: meaning the data was there, but something was hanging the timeline up.
I also saw that if I opened another project after after being in the one with the corrupted timeline that newly opened project had a vanished timeline as well. The Timeline Index was, however, still visible in the newly opened project. If I quit and re-started FCPX those newly open projects moved back to normal mode with timeline and index operating normally.
Next Step: I created a new project. I went back to the corrupted project, right arrowed from element to element selecting one at a time. Then I touch the “transforming/resizing” tool to ensure the clip was active. I copied the clip, closed the corrupted project, opened the new holding project and pasted that clip in.
I could not see the timeline, but I expected that. I could, however, see the timeline index. The clip was there. I knew that if I closed and restarted the app without going into the corrupted timeline project the chances were good for the timeline, index and clip would be visible. It was.
It was clear that the corruption was a bug somewhere the the project file. I had a choice to call for support or do the work around and rebuild the timeline one-clip-at-a-time. With over 130 elements (audio, video, text, and hold (freeze frames, butting up the the key video clips) I saw that the the amount of time was going to be a long long time. I tried to select all the clips in the corrupted project. That was successful, but when trying to paste them into the new project the App would crash. Too much for our spinning ball editor.
I dreaded having to call the Pro Apps people, usually in Austin, because I had been getting this corporate (Adobe/Microsoft/WallStreet) kind of response:
“We see your 90 day phone support has run out. We can send you an emil about what to do or you can pay $99 to talk with us on the phone or pay $700+ for a years of phone support.
I would tell them that when I crossed over from FCP 7 Legacy and we (people who edit and make video/films for a living) were all worried about this app because we couldn’t import any of the old work, etc.. We all know the fear and contradictions over FCPX. I explained that when I talked to an Apple Pro App person, when I was deciding to invest in the new version, I asked him, “Was Apple going to stand by us if we crossed over from legacy, since there were bound to be bugs — we all knew that when we first started with Final Cut Pro version 1. This advisor said yes. He never said, We will help you for 90 days after that you have to pay or you are on your own — even if it is our inevitable bug. The Pro App Advisor I talked to in Austin said “Who told you that Apple would support you? I want to read what he said in your records. Give me the case number!”
I said “You won’t find that in my records. This was a good faith recommendation by an Apple Rep who understood there were going to be bugs. The Pro App guy cut me off and said we have already spent too much time talking. Do you want me to sign you up for $99 or do you want the annual support...?”
I said, “This is very unfair. This is a bug in the software. You should be supporting professional users trying to help you debug the software. After it gets back to the solid stability of Legacy, charging money after 90 days is fair, but this software is is not working right.
He said, “There is nothing wrong with FCPX. I use it all the time and have never had a problem. I am thinking — this guy is making home movies. I said, “Do you read anything on the internet from professional users having problems. Again, he said “There is nothing wrong with FCPX. I’ve been a filmmaker for 17 years. All problems are 3rd Party related.
There wasn’t much left to say. We you know this type of discussion.
I contacted people in Customer relations determined to ensure this issue finds it’s way to policy people at Apple HQ in Cupertino on the loop. These community relations people got it. They know that as Apple grows there are signs of people who are more predatory in nature, seeking money over the equity of the principle that users should not pay to debug a product, especially one we make our living’s on. Especially, since we were taking a step to support Apple FCPX and not heading straight to Premiere or Avid.
After establishing a honest point with the Community Relations people I contacted a Pro App person who had a realistic perspectives of the first generation flaws of FCPX and together we found a work around that demonstrated that it was in fact a bug.
All of this has been documented (pro app advisors names and comments, etc..) because this policy issues has to be dealt with — connecting good people in Apple with users who care about the future of Apple.
Here is the work around.
- Close the project that is corrupted and make sure it is highlighted in the Project Library.
- Go to File/Export XML and save that file.
- Re-import that file, generating a new project.
- Close and Restart the FCPX App.
- STAY AWAY FROM THE PROJECT FILE WITH THE CORRUPTED TIMELINE.
- Open the newly project created via the XML import.
- Everything should be there and working fine.
The application code has to be debugged. I have sent the corrupted project file to be added with the Advisor’s note to be sent to the proper people in Apple.
To revoke any argument from the Pro App people in Austin — that this problem was being cause by some 3rd Party App, or something wrong with my drives or computer, I built a new drive (in my Mac Pro Bay 1) with Lion 10.7.3. I did not install or use any other potential influencing elements of hardware of software —testing the bug hypothesis on the start up drive alone.
The hypothesis that the app is buggy related to the timeline (not to mention the dozens of other issues we have all faced) is correct. I also went back and repeated the work-around process on external drives connected via Firewire 400/800 and eSata. The same work-around was successful.
Finally, if you attempt this work-around and it resolves the problem, in the short term, please note for other users your opinion with regard to the attitude that FCPX is already working fine and that we should be paying $99 per issue or $700+ to get support for problems that are based in this new and unstable version of Final Cut Pro X.
Currently Being ModeratedMay 1, 2012 11:31 AM (in response to Norman Jayo)
Norman Jayo (or is it Rio?),
Thanks for posting the work around! I encountered this problem today for the first time and was very happy to find this thread. Here are a couple things to note, however:
- COLOR BALANCE AND SHAPE MASK LOSS -- If you use the above work around, and you have any shape masks with color corrections on them (or any color corrections, it seems) you will probably have to redo them.
- NO AUDIO ON FINAL EXPORT -- I'm not 100% sure it's related, but I just tried exporting my movie to Quicktime (Share > Export Media...) and when the final output movie is generated, the sound is missing. Given that this only happens when I export this project (and not other, never-corrupted-before projects), I'm pretty sure this has something to do with the above workaround. And yes, I did choose "Video and Audio" from the export menu (not "Video Only"). Yes, my speakers are on, etc. etc. I also tried exporting JUST the audio and got a silent audio file.
Has anyone else experienced the audio problem in their export, and have you figured out what to do?
I can see the loss of the color balance and shape mask. That loss is part of the bug. Still, that allows for a level of project recovery that is a lot easier than loosing everything.
I have had the audio problem you speak of, but not in the context of a vanishing timeline and recovering most of the project elelments via XML export and re-import.
Try this: Create a new project (this will be pristine and nbot carrying the bug that crept into the original project). Now got back to the original project where you lost your audio — I am assuming audio playback within this project timeline still works and that it is only on export that the audio is lost. Copy the audio and paste it into the new project, go to share and export.
Currently Being ModeratedMay 1, 2012 12:54 PM (in response to Norman Jayo)
Thanks Rio, I will try that when I get the chance. You are correct that audio within the project timeline still works, but not on export. When you say to "copy the audio and paste it into the new project" I am guessing I will need to separate out the audio from all video/audio clips so that the audio appears as separate green waveforms? Also, I think you meant to imply that the new project should contain the rendered video I just exported? If so, is that going to double-encode it as H.264? I do not have Compressor right now so I would prefer to do this all in Final Cut without lossy double-encoding.
I was saying highligh all and copy everything - rendering is your choice. You can always re-render if the specs are there. I am not sure what is triggering the bug. I was just trying to save the core elements thast were lost in the vanisged timeline.
I am not using audio from any of the cameras. I have synced to external recordings viaa clap-board. I am going to take a quick look right now and see if the camera's audio is still there after I copied everything to the new project....
Yes, the audio is still attached — though down at -96db — and still plays back, so the work around should get you back to a timeline.
I am using 442 (HQ) on the export, as I am justing taking the clips over to Motion to add some stuff.
Good Luck Fronzy
This has happened to me about four times and three of those times I was able to get it back through a trashing of preferences and then a re-start, but this time it took Norman's solution. One thing that seems to be common for me in having this happen is I am trying to add a gap at the end of the timeline in an effort to seperate two quotes or another section of the video. The screen blips and I am sent to gray timelineland.
A fix is necessary.