Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

FCPx take 35sec to open since on Yosemite

Hi everyone


I looking for some help here. I am running a recently purchase Mac Pro (The core version) with the latest version of FCPx and since I upgraded to Yosemite, it now takes 35 seconds for Final Cut Pro to open while it was instant on 10.9. At first I thought that it was the upgrade that when wrong and made a clean install but nothing change and this whether or not you have

Mac Pro, OS X Yosemite (10.10)

Posted on Oct 27, 2014 5:00 PM

Reply
18 replies

Oct 27, 2014 5:40 PM in response to Akiba-Seattle

I agree that it seems to take longer. But once it loads, my experience is that FCP is faster on Yosemite than it ever was on Mavericks,


However, 35 secs does seem excessive. Do you have a lot of libraries and events that are being opened at launch? If so, hold down the option key when you launch the app to see how fast it loads with a single "empty" library.


Russ

Oct 27, 2014 11:14 PM in response to Russ H

Hi Russ


Thanks for your reply. I did what you wrote and this had NO effects whatsoever. The problem was there from day one just after I reinstalled my MacPro without any library on the Mac.


The symptom are as follow : Once you click on the icon to start the App, FCPx will "Hang" with the spinning wheel for at least 25 sec and then you will see in the FCPx splash screen that it loads all the project and so on. It looks like FCPx "freeze". In the activity monitor I have the following :Final Cut Pro (Not Responding) http://cl.ly/image/3B0r2a1b192p


Otherwise everything just work fine, I did not see any speed or other issues, It just take 30~35sec to open which turn me mad.


Cheers

Oct 28, 2014 5:46 AM in response to Akiba-Seattle

To be clear, are you saying that it takes 35 seconds to launch the application with a single, empty library?


Do you have your libraries on a media drive that's separate from your start-up drive?


If the answer to both of these questions is yes, then the only thing I can think of is something going on with a third party plug-in and Yosemite .


By way of comparison, these days I'm typically working with three libraries. So when I first launch FCP, it loads all three and the working project timeline. The elapsed time is similar to yours – about half a minute, However, if FCP were only loading a single, empty library, I would expect the whole process to take less than 5 seconds.


Russ

Oct 28, 2014 5:52 AM in response to Russ H

Hi Russ


1. To be clear, are you saying that it takes 35 seconds to launch the application with a single, empty library?

Yes

2. Do you have your libraries on a media drive that's separate from your start-up drive?

Yes, but does not matter where it is located, same problem.

3. can think of is something going on with a third party plug-in

No Plug-in


So yep, I also believe that the problem is either FCPx (not update since a while) or Yosemite

Oct 28, 2014 10:29 PM in response to Russ H

Found out what's wrong and there is nothing I can do to fix it without toying with the terminal, only Apple will have to figure this out.


I tried on a MacBookPro I own and I had the same problem as on my MacPro, tried with a new user account and same problem. Then I turned of my MacBooPro Wifi and :Bam! FCPx open now in just a few sec (not enough to count to 3)... I then try to connect my MBP to the network via ethernet and same problem.

Same on the MacPro... So it seems that it is related to network connectivity. If I unplug either my MacPro or MacBookPro for the internet (Wifi or Ethernet) FCPx open immediately...


So if someone at Apple is reading this thread, please fix this issue on your next upgrade!


Note it seems that I am not the only one and that other apps are touched by this problem... I have not tried the fix yet however.


Proposed Fix by Snaggletooth_DE :


Working workaround:

Use the following statements in Terminal.

sudo vi /etc/auto_master

In this file comment out /net with # (#/net .....)

sudo automount -vc

Fixed.


Slow file open dialogue box

http://www.fcp.co/forum/4-final-cut-pro-x-fcpx/19240-slow-start-up-of-fcpx-10-1- 1

Oct 29, 2014 4:03 AM in response to Akiba-Seattle

Akiba-Seattle wrote:


Found out what's wrong and there is nothing I can do to fix it without toying with the terminal, only Apple will have to figure this out.


I tried on a MacBookPro I own and I had the same problem as on my MacPro, tried with a new user account and same problem. Then I turned of my MacBooPro Wifi and :Bam! FCPx open now in just a few sec (not enough to count to 3)... I then try to connect my MBP to the network via ethernet and same problem.

Same on the MacPro... So it seems that it is related to network connectivity. If I unplug either my MacPro or MacBookPro for the internet (Wifi or Ethernet) FCPx open immediately...


So if someone at Apple is reading this thread, please fix this issue on your next upgrade!




It is clear that the problem you are experiencing is related to network access.

This is certainly not widespread, so it may worthwhile to figure out what it is in your settings that is different.

I would try clearing the caches and see if it helps.

Oct 29, 2014 5:14 AM in response to Luis Sequeira1

Ok, so I done what you suggested on my MacBookPro (outside now)


and here you are what's going on (part of it below, full txt here https://www.dropbox.com/s/9idf1sixekce4oy/FCPx.txt?dl=0)


10/29/14 9:09:58.905 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 54, ErrLogCount 18 ResolverIntf:5

10/29/14 9:09:59.905 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 19 ResolverIntf:5

10/29/14 9:10:00.914 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 20 ResolverIntf:5

10/29/14 9:10:02.000 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 21 ResolverIntf:5

10/29/14 9:10:03.086 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 22 ResolverIntf:5

10/29/14 9:10:04.172 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 23 ResolverIntf:5

10/29/14 9:10:05.259 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 24 ResolverIntf:5

10/29/14 9:10:06.297 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 25 ResolverIntf:5

10/29/14 9:10:07.396 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 26 ResolverIntf:5

10/29/14 9:10:08.483 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 27 ResolverIntf:5

10/29/14 9:10:09.562 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 28 ResolverIntf:5

10/29/14 9:10:10.609 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 29 ResolverIntf:5

10/29/14 9:10:11.667 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 30 ResolverIntf:5

10/29/14 9:10:12.727 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 31 ResolverIntf:5

10/29/14 9:10:13.823 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 32 ResolverIntf:5

10/29/14 9:10:14.845 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 33 ResolverIntf:5

10/29/14 9:10:15.851 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 34 ResolverIntf:5

10/29/14 9:10:16.859 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 35 ResolverIntf:5

10/29/14 9:10:17.868 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 36 ResolverIntf:5

10/29/14 9:10:18.877 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 37 ResolverIntf:5

10/29/14 9:10:19.886 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 38 ResolverIntf:5

10/29/14 9:10:20.981 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 39 ResolverIntf:5

10/29/14 9:10:22.080 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 40 ResolverIntf:5

10/29/14 9:10:23.118 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 41 ResolverIntf:5

10/29/14 9:10:24.181 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 42 ResolverIntf:5

10/29/14 9:10:25.264 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 43 ResolverIntf:5

10/29/14 9:10:26.357 PM discoveryd[49]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 2001:268:fd07:4::1 Port 53 errno 22, fd 52, ErrLogCount 44 ResolverIntf:5

Oct 29, 2014 5:53 AM in response to Luis Sequeira1

Ok so I am getting there, I succeed to fix my MacBookPro but not my MacPro... Just need a bit more help.


I have disable IPV6 on the MacBookPro using these :


networksetup -setv6off wi-fi

networksetup -setv6off ethernet


Work just fine, but on my MacPro I cannot make it work at all, Wi-Fi will work but not the ethernet (dual port)...


I listed all the port on the MacPro (see below)

networksetup -listallnetworkservices

An asterisk (*) denotes that a network service is disabled.

Bluetooth DUN

Ethernet 1

Ethernet 2

Wi-Fi

Bluetooth PAN

Thunderbolt Bridge

And when I try (every possible ways) with Ethernet (networksetup -setv6off ethernet, networksetup -setv6off ethernet 1, networksetup -setv6off ethernet1, networksetup -setv6off Ethernet 1, networksetup -setv6off Ethernet1)... I always end up with :

Ethernet1 is not a recognized network service.

** Error: The parameters were not valid.

What I am doing wrong?

Oct 29, 2014 6:01 AM in response to Akiba-Seattle

FIXED!!!!!


Sorry guys for this long thread, but I did it... So while the IPV6 Off option is NO longer available on OSX since 10.9 (Why oh god WHY!?!?!?) the option "Configure IPv6 : Link-local only" does the trick in my case!


Still this Apple really have to sort this out when it comes to IPv6 (MS, and other as well)...


Case closed! Thanks for all your patience and kind help!


PS, networksetup -setv6off ethernet still does not work on my MacPro and I would LOVE to know why?

Oct 29, 2014 6:05 AM in response to Akiba-Seattle

I am not familiar with the networksetup command, but from your description it looks like the name may should be entered as "Ethernet 1" (and likewise "Ethernet 2"). You'll need to put in the quotes to make the shell read this a single value, otherwise it will parse them as two separate parameters, "Ethernet" and "1".

Try


networksetup -setv6off "Ethernet 1"

or maybe

networksetup -setv6off "ethernet 1"


Also, in older versions of OS X one could turn IPV6 off for the various network ports in System Preferences->Network->Advanced. In Yosemite the options are "Automatically", "Manually" and "Link-local only"; maybe choosing the last option will do as well.

FCPx take 35sec to open since on Yosemite

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.