3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
FCPX & OSXx 10.10 bug
30 Oct 2014 14:06 #55163
by BenB
FCPX & OSXx 10.10 bug was created by BenB
Teaching a class this week. FCPX 10.1.3 with OSX 10.10 bugs; Custom Renaming;
1- If you manually change the name of a clip, it will not change back to Original Camera name. 2- If you edit Custom Rename preset, the Custom Name with Counter, fill in a custom name, set counter to 3 digits, click OK, BANG, GUI goes wacko, FCPX crashes. All this done on a rMBP, nMP, and 4 iMacs. Embarrassing in a class...
1- If you manually change the name of a clip, it will not change back to Original Camera name. 2- If you edit Custom Rename preset, the Custom Name with Counter, fill in a custom name, set counter to 3 digits, click OK, BANG, GUI goes wacko, FCPX crashes. All this done on a rMBP, nMP, and 4 iMacs. Embarrassing in a class...
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
30 Oct 2014 14:15 #55164
by Tom Wolsky
Replied by Tom Wolsky on topic FCPX & OSXx 10.10 bug
Not seeing 1. I change the name of a clip to "ranch and hills." Use the Info inspector to change back to camera name and I get Clip #1.
Not getting 2 either on a rMBP with 10.10.
Wonder if there's something else you did prior to that to set off the naming problem.
Were these clean 10.10 installs or upgrades?
Not getting 2 either on a rMBP with 10.10.
Wonder if there's something else you did prior to that to set off the naming problem.
Were these clean 10.10 installs or upgrades?
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
Less
More
- Posts: 4455
- Thank you received: 962
30 Oct 2014 16:28 #55172
by ronny courtens
Replied by ronny courtens on topic FCPX & OSXx 10.10 bug
I can confirm issue #1. Renaming a clip, wether with a created Custom Name or just entering it in the Info > Name box, will not allow to change back to Original Camera Name. Tested with different clips in different formats.
I don't see issue #2. Applying a Custom Name with Counter, counter set to different numbers of digits, works OK
Tested both on clean installs and on a test system updated over Mavericks.
Overall FCP X seems quite stable for playing around with on Yosemite on a test machine. But there is no way on the world I will update our production system to Yosemite until FCP X has been properly updated for this OS. And even then I will thoroughly test it before even considering using it in production.
- Ronny
I don't see issue #2. Applying a Custom Name with Counter, counter set to different numbers of digits, works OK
Tested both on clean installs and on a test system updated over Mavericks.
Overall FCP X seems quite stable for playing around with on Yosemite on a test machine. But there is no way on the world I will update our production system to Yosemite until FCP X has been properly updated for this OS. And even then I will thoroughly test it before even considering using it in production.
- Ronny
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
30 Oct 2014 16:40 #55173
by Tom Wolsky
Replied by Tom Wolsky on topic FCPX & OSXx 10.10 bug
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
Less
More
- Posts: 4455
- Thank you received: 962
30 Oct 2014 16:46 #55175
by ronny courtens
Replied by ronny courtens on topic FCPX & OSXx 10.10 bug
Tom, do you have any clips that don't have date/time as their original camera name? If so, please test this on such a clip.
- Ronny
- Ronny
Please Log in to join the conversation.
30 Oct 2014 17:00 - 30 Oct 2014 17:03 #55181
by smg669
I just tried it on a C300 clip that was auto-named with the clip name (AA6829) upon import (and not the date). Was able to use the Apply Custom Name - Original Name From Camera command and it worked as expected. The bug must be specific to a certain subset of camera type(s).
--- Oh wait. I just realized I'm not on 10.10 yet. So, if it's a 10.10 only thing, I'm of no help.
Replied by smg669 on topic FCPX & OSXx 10.10 bug
ronny courtens wrote: Tom, do you have any clips that don't have date/time as their original camera name? If so, please test this on such a clip.
- Ronny
I just tried it on a C300 clip that was auto-named with the clip name (AA6829) upon import (and not the date). Was able to use the Apply Custom Name - Original Name From Camera command and it worked as expected. The bug must be specific to a certain subset of camera type(s).
--- Oh wait. I just realized I'm not on 10.10 yet. So, if it's a 10.10 only thing, I'm of no help.
Last edit: 30 Oct 2014 17:03 by smg669.
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
30 Oct 2014 17:03 #55182
by Tom Wolsky
Replied by Tom Wolsky on topic FCPX & OSXx 10.10 bug
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
Less
More
- Posts: 4455
- Thank you received: 962
30 Oct 2014 17:11 - 30 Oct 2014 17:11 #55184
by ronny courtens
Replied by ronny courtens on topic FCPX & OSXx 10.10 bug
Scott,
Thank you for testing this.
Tom,
When you change the name of the clip "clip#1 12008-02-06 10:31:35" to "ranch" and then you select Apply Custom Name > Original Name from Camera, I see the name changes to "clip#1" and the rest of the original clip name is lost. Is that correct?
- Ronny
Thank you for testing this.
Tom,
When you change the name of the clip "clip#1 12008-02-06 10:31:35" to "ranch" and then you select Apply Custom Name > Original Name from Camera, I see the name changes to "clip#1" and the rest of the original clip name is lost. Is that correct?
- Ronny
Last edit: 30 Oct 2014 17:11 by ronny courtens.
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
30 Oct 2014 17:20 - 30 Oct 2014 17:22 #55185
by Tom Wolsky
Replied by Tom Wolsky on topic FCPX & OSXx 10.10 bug
That's right. This is a recent import of AVCHD media, which uses the new FCP style of importing clips with the actual camera name Clip #1, etc. rather than date/time stamp, which it used in earlier versions.
P.S. I have other clips that have date/time stamp converted to ProRes that have come from an XF camera, and that reverts to the Canon naming convention like AA0053.
P.S. I have other clips that have date/time stamp converted to ProRes that have come from an XF camera, and that reverts to the Canon naming convention like AA0053.
Last edit: 30 Oct 2014 17:22 by Tom Wolsky.
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
Less
More
- Posts: 4455
- Thank you received: 962
30 Oct 2014 17:27 #55186
by ronny courtens
Replied by ronny courtens on topic FCPX & OSXx 10.10 bug
Okay, Tom. Thanks for clarifying.
- Ronny
- Ronny
Please Log in to join the conversation.
31 Oct 2014 00:07 #55248
by BenB
Replied by BenB on topic FCPX & OSXx 10.10 bug
I also found that the Match Frame function, while teaching class today, doesn't work as it used to. Hardly anything is done to the clip, or nothing is done to the clip.
Please Log in to join the conversation.


