Currently Being ModeratedNov 7, 2012 5:39 AM (in response to somanna)
Could it be that you are being too quick off the mark and FCP X (or even your computer) is still in the process of setting itself up.
After FCP X has apparently finished its setup procedure, have you left it a minutes or so to allow everything to settle down? Or is it still sluggish ten minutes later?
How many projects are in the Project Library and how many tracks are you using in your current project?
Currently Being ModeratedNov 7, 2012 8:26 AM (in response to Ian R. Brown)
Thanks for entering this thread.
No, I am not being too quick off the mark. No, I have not waited for as long a period as 10 minutes to know whether the timeline becomes responsive...and hence, should it have in it the potential to 'start working' at that time, I do not know whether it would behave sluggishly or otherwise. [Hope you understand what I write, you should!]
I have 6 projects in my Mac's HD, about 11 projects [including versions] in my Seagate external, and 2 projects in my Lacie external.
I am afraid I do not understand what you mean by: ' how many tracks are you using in your current project?'
I have this:
Hope this helps.
Regards. Take care.
Currently Being ModeratedNov 7, 2012 8:33 AM (in response to Jakob Peterhänsel)
My mind always is on the lookout for humor, and I am afraid whether what you have written [bugreport.apple.com] is some thing I should laugh at and add a ' ' or something which I should take seriously and approach the Apple folks. BTW, if your reply is of the serious stuff, then let me let you know something which I feel is taking place: I feel Apple is eavesdropping on these forums and hence I need not take the trouble to report @bugreport.apple.com!
Currently Being ModeratedNov 7, 2012 8:40 AM (in response to somanna)
I find that if I start editing the moment the complete interface appears I can have problems because FCP X is still moving things "secretly" into place.
Leaving it a few seconds allows everything to settle down.
I didn't mention 10 minutes . . . . . it should be fully functional in well under a minute.
It's not the projects on your HD that slow down the startup but those in the Project Library.
As you know, any projects not in use should be hidden in another folder.
To all intents and purposes every layer of clips, titles etc. above the normal timeline is like a track.
So towards the end you have 5 layers (or tracks) of video in one place.
Currently Being ModeratedNov 7, 2012 8:42 AM (in response to Jakob Peterhänsel)
I have been to the site you asked me to and found that I am not eligible to report bugs:
You must be a Registered Apple Developer to file bugs via Bug Reporter.
Register at http://developer.apple.com/programs/register/
Looks intimidating stuff to me! I have to be a Registered Apple Developer to file a report!
Currently Being ModeratedNov 7, 2012 8:52 AM (in response to Ian R. Brown)
Thanks Ian for the reply and further details.
Yeah I do wait for the fcpx to fully load and I have not been unreasonable or impatient in my approach. I am minded to go for the app 'event manager' to hide inactive projects.
The problem I have raised is luckily surmountable, but I am hoping that this inconvenience is done away [having to quit fcpx and trashing preferences before starting it again].
Currently Being ModeratedNov 7, 2012 9:16 AM (in response to Karsten Schlüter)
Hello Karsten, how are you? And hello again Ian. Let me now rewrite the problem for clarity's sake, this part of the post being copied and pasted for feedback purpose.
Ever since the upgrade from 10-0-5 to 10-0-6 of FCPX, I have been facing this problem of a non-responding timeline: after a day's work, I usually minimise the FCPX after checking the render box in playback preferences [as I edit with background render turned off] and put my Mac to sleep. Previously, when in 10-0-5, I could, after waking up my Mac, click upon the FCPX icon in the dock and I could start my editing work almost instantaneously. But, after the upgrade to 10-0-6, I find that though the fcpx opens up, the timeline is either inactive or very sluggish. The playhead moves to the place of click after a long time interval or does not move at all. More importantly, the keyboard also ceases to function. The non-functioning of the keyboard I have also encountered even during the editing process itself...it occured twice in the recent past: at the first time I was busy pasting attributes to several clips, and the second time when I was rapidly adding text to titles. The inability to use the keyboard functions is not restricted to fcpx alone, but spreads to other programs as well...I cannot enter text in a word document and neither can I type any address in the address bar of my browser.
The workaround I have adopted to this problem has been this: quitting FCPX and shutting dowm my Mac; next, after starting up my Mac, I first trash FCPX preferences and then open up my FCPX. This done, and things become smooth once again, I can use the keyboard functions not only in FCPX but also in the other programs. If I omit the trashing of preferences step which I mentioned above, the keyboard continues to be dead and the FCPX timeline non-responsive.
Currently Being ModeratedNov 7, 2012 10:15 AM (in response to somanna)
Hello Karsten, how are you? … I have been facing this problem of a non-responding timeline: …
thanks for asking, fine as possible
hard to give any advice due to complexity of your set-up.
on first launch after update, usually FCPX 'updates' Projects - only Tom Wolsky does know
so, first assumption: FCPX isn't done with updating ALL your projects.
after sleep-mode, your drive don't wake-up fast enough ...
no idea, how to fix that.
when editing, my set-up doesn't allow sleep-mode ...
busy or off