[Rikki Blow]

no worries Bob.

and yes, I’d prefer to move to El Cap rather than Sierra yet, but I can’t see any Apple-authorised download to do that – looks like I’ll have to search for a less orthodox route to El Cap, as Apple want me to jump from Yosemite to Sierra as far as I can tell.

(unless anyone knows better?)

[Rikki Blow]

My workflow for this is:

Name the first compound clip either generically, or with name of whoever you’re identing first in the project.

When you want to add a new lower third ident in the timeline, go to the browser, and duplicate that compound clip (Command+D), rename that newly copied clip as your next ident, and then connect it where appropriate on the timeline. (Just make sure you SELECT your newly named duplicate before renaming/connecting, as the highlight will still be on the original clip after you first create the duplicate). Go into the newly connected clip in the timeline and put in the new name text that you want.

Any changes to a compound clip WITHIN a library, will affect them all (unless they are duplicates with different names). Compound clips copied from one library to another, become new unconnected entities.

[Rikki Blow]

i’m mid big projects right now – going on the next month – AND i’m still on yosemite so can’t move to FCPX 3 directly.

i’m so tempted to upgrade the OS and move to 10.3 cos it seems to have so many good new things, but i think i have to be sensible and wait till current work crop is over rather than risk any problems with both OS and FCPX upgrades in mid project

?

i’ll look forward to command-up for xmas then!

[Rikki Blow]

[Bob Woodhead] ” Then Command-up/down to select connected up and down from Primary. Very fast.”

having said my thanks, i still can’t get this bit to work.

searched for Command-Up in the command editor, and it only came up with Alt-Command-Up (which i already knew is ‘lift from storyline).

also tried searching the Command Editor using words like ‘Select’ and ‘Switch’ to see if I could find the command I needed, but can’t see anything relevant.

perhaps you could go into the Command editor, do the ‘Command-Up’ thing on your set up, and let me know how the function is described so i can search for it and assign it?

really bemused, this should be a simple key command to achieve, and it’s defying me.

thanks

[Rikki Blow]

brilliant.

i knew there had to be a way.

i never knew about ‘C’

this will make a big difference to my speed and my RSI!

ta.

[Rikki Blow]

well, THANK YOU.

i thought i was a reasonably expert user, but have neither ever needed ‘open from backup’ before, nor, therefore, come across it.

very simple fix and now that i know, blindingly obvious.

sorry for appearing so newb, and thanks for taking the time to respond. i love this forum.

[Rikki Blow]

i think i’ve sussed it!

it did seem to be on any and all types of clips, but it started in a project that had synchronised clips.

even breaking them apart and apparently dealing with the original clips, i couldn’t get the stabilisation option back until i found them in browser and dragged them into timeline again as replacements.

i’d already tried this replacement trick on the synchronised clips so thought it wasn’t a solution, which is why i went on to pref trash and application re-install, and then panicked and posted.

once broken apart though, this replacement solution worked.

[Rikki Blow]

well this may be an old thread, but i’m on 10.2.3 and it’s just started happening for me.

stabilisation has completely disappeared.

i’ve trashed prefs, re-installed, tried the XML trick, and tried the ‘replace from start’ trick, and still no joy. i no longer have video stabilisation in FCPX.

go figure.

anyone any ideas?

[Rikki Blow]

Further research leads me to conclude I may need to do update some 3rd party effects, as this new ‘save FX preset option’ is crashing other folks’ systems too, but when I try saving FCPX own FX I’m having no problem.
https://discussions.apple.com/thread/7042555

[Rikki Blow]

Thanks for the advice.

I’ve realised that the problem is actually a saved preset – I’d created the category “RIKKI”, but can’t find this folder anywhere.

It seems that the new ‘category’ system doesn’t actually create new folders (certainly on my system), instead somehow embedding the category info along with the preset name, which appears in Preferences/Application Support/ProApps

So, I managed to fix the current problem by deleting the offending preset, and, da-da, the category disappeared too, so I don’t get crashes.

However, this has opened a new can of worms, because I’ve realised that any attempt to save a preset is crashing FCPX, and coming back in, any attempt to access the saved preset takes me back to crash scenario.

I’ve done all the usual things – trashed preferences, caches, saved states, etc. Logged in in safe mode, used disc utility to fix permissions, etc.

As long as I don’t have any saved presets, and as long as I don’t try to save one, everything works very smoothly, but all those usual techniques seem to have no effect on the issue that saving presets causes.

I see another poster had similar problem, but fixed with these usual steps (https://forums.creativecow.net/thread/344/38894).

When I try to save a preset, taking a look after the crash (and just before the next one), I see that the preset gets saved with an incomplete outline image. I don’t know whether this is usual for saved presets or an indication/clue of the problem.