Final Cut Pro Hacks

blog-banner

Updated (2nd DECEMBER 2016):


INTRODUCTION:

FCPX Hacks is a free and open source Hammerspoon script that adds a mountain-load of new features to Final Cut Pro. It originally started off as a little proof of concept project to make finding the browser playhead easier for Scott Simmons (read the original blog post below) – but has since grown into a huge collection of handy workflow hacks, shortcuts, tools and automation features to make editing within Final Cut Pro faster, easier and much more powerful.


SYSTEM REQUIREMENTS:

FCPX Hacks is compatible with Final Cut Pro 10.2.3 and 10.3.1 running macOS 10.10.5 or above.

It requires Hammerspoon 0.9.50 or above and works with any language and keyboard layout.

The Touch Bar feature requires macOS Sierra 10.12.1 build 16B2657 or later installed.


DONATE:

Coding crazy stuff like this takes a LOT of time (especially for a non-programmer), so if you find FCPX Hacks useful, PLEASE consider making a voluntary PayPal donation below (no matter how big or small) or buy a cool Wizards T-shirt so that I can continue to justify to my wife and the rest of the team at LateNite, that coding into the middle of the night is worthwhile!

Don’t have any spare cash? Then consider just sharing the news of FCPX Hacks online, so we can get more people testing it out. The more feedback I get, the quicker it is to squash bugs, and come up with cool new features to include.

Also, if there’s a feature that you or your company desperately need, please get in touch to discuss contracting me to throw it together as a priority.




DOWNLOAD:

Please be aware that I’m a filmmaker, not a programmer, so use at your own risk!

You can download the latest version of FCPX Hacks here (version 0.68 – 2nd Dec 2016 @ 23:00).

As some of the features in this script makes changes to Final Cut Pro’s internal files (which requires your Administrator password), please don’t use on mission critical or production systems without testing first. This scripts basically sits “on top” of Final Cut Pro, so it shouldn’t ever cause Final Cut Pro to crash to slow down – but always better to be safe than sorry!

After downloading and installing the latest version of Hammerspoon (which you must do first), you can just download and open up the above DMG file, then drag the script files on the left to the Hammerspoon folder on the right (replacing any existing files if you’ve previously installed FCPX Hacks). If you need help installing Hammerspoon, you can refer to the original blog entry below.

fcpx-install


SPECIAL THANKS:

MASSIVE thank you to Aaron Magill and Chris Jones for all their help and support with Hammerspoon – they’re both truly awesome people. Also, a very big thank you to Bill Cheeseman PFiddlesoft, for all his help with UI Browser and his very generous GUI Scripting advice. Thanks also to Hans Linssen, Yvan Koenig and Tim Webb for their troubleshooting help, and to Andreas Verhoeven & Robbert Klarenbeek for the work they’ve done with Touch Bar Demo App. Big thanks also to David Peterson for his XML and Github help!

MASSIVE thank you to the INCREDIBLE Andrew Kramer at Video Copilot for giving the world FX Console for FREE – and also inspiring me to rip off his genius idea and include a “console” feature in FCPX Hacks!

An equally MASSIVE thank you to the always amazing Karen Hocking, Daniel Daperis, David Hocking, Андрей Смирнов, Alex Gollner, Scott Simmons, Isaac J. Terronez, Shahin Shokoui, Ilyas Akhmedov and everyone in the FCPX Editors InSync Facebook Group for all their ideas and advice!

The FCPX Hacks logo was designed by the very generous and talented Sam Woodhall.


HOW TO USE:

FCPX Hacks adds a menu to the top right corner of the screen in the macOS menubar. This gives you quick and easy access to a range of shortcuts, automation tools, hacks and both the FCPX Hacks and Hammerspoon settings.

If you don’t want FCPX Hacks appearing in your menubar, you can also use an icon instead:


When you launch FCPX Hacks for the first time, it will use default shortcuts keys, which are listed below. However you can customise these shortcut keys via Final Cut Pro’s own Command Editor. This feature is disabled by default and must be activated by clicking Enable Hacks Shortcuts in Final Cut Pro from the FCPX Hacks menubar. As this feature changes Final Cut Pro’s internal keyboard layouts – it will require your Administrator password (so as with all of the Hacks, use with care).

Another handy feature is the Display Proxy/Original Icon. This inserts a blue or red dot (as shown in the first screenshot above) in the menubar to visually highlight if you’re watching Proxy or Original files in the Viewer. This is really handy to be able to instantly see if you’re watching full quality or not.

FCPX Hacks Console (Default Shortcut: CONTROL+SPACEBAR)
Inspired by Andrew Kramer’s INCREDIBLE FX Console free plugin for After Effects, we’ve also added an uglier and less feature-rich “console” to FCPX Hacks. It allows you to activate a bunch of the different shortcuts and automation features directly from the search tool. However, what’s really handy is that if you, for example, click Update Effects List from the Effects Shortcuts menu, ALL of your effects will appear in the console for easy access – allowing you to very quickly add effects with only your keyboard! You can right click on the Console to control what items are displayed (i.e. you may only want to see Effects).


SHORTCUTS:

Open Final Cut Pro (Default Shortcut: CONTROL+OPTION+COMMAND+L)
With FCPX Hacks open, you can now open Final Cut Pro at any time, system wide.

Create Optimized Media (No Default Shortcut)
This shortcut simply activates “Create Optimized Media” within the Final Cut Pro Import Preferences. This can save you a couple of clicks, and also allows you to quickly check whether the setting is ticked or not in one mouse click.

Create Multicam Optimized Media (No Default Shortcut)
This shortcut simply activates “Create optimized media for multicam clips” within the Final Cut Pro Playback Preferences. This can save you a couple of clicks, and also allows you to quickly check whether the setting is ticked or not in a single mouse click

Create Proxy Media (No Default Shortcut)
This shortcut simply activates “Create Proxy Media” within the Final Cut Pro Import Preferences. This can save you a couple of clicks, and also allows you to quickly check whether the setting is ticked or not in a single mouse click.

Leave Files in Place on Import (No Default Shortcut)
This shortcut simply activates “Leave in Place” within the Final Cut Pro Import Preferences. This can save you a couple of clicks, and also allows you to quickly check whether the setting is ticked or not in a single mouse click.

Enable Background Render (No Default Shortcut)
This shortcut simply activates “Background Render” within the Final Cut Pro Playback Preferences. This can save you a couple of clicks, and also allows you to quickly check whether the setting is ticked or not, as well as what the start after time is set to in a single mouse click.


AUTOMATION:

Highlight Browser Playhead (Default Shortcut: CONTROL+OPTION+COMMAND+H)
By default this feature puts a big red rectangle around the Final Cut Pro browser playhead to make it really easy to instantly spot. You can change the colour to Blue, Green or Yellow and the shape to a circle or diamond within the FCPX Hacks preferences.

highlight

Reveal in Browser & Highlight (Default Shortcut: CONTROL+OPTION+COMMAND+F)
The original feature of FCPX Hacks! This feature performs a normal “Reveal in Browser”, but then highlights the playhead so that you can spot it easily.

Single Match Frame & Highlight (Default Shortcut: CONTROL+OPTION+COMMAND+S)
This feature performs a normal “Reveal in Browser”, however whatever clip your playhead is over (for example, let’s say it’s a clip called “Test”) – this feature will then automatically insert “Test” into the Browser Search box, so that only the single clip appears in the Browser, and also highlights the playhead.

Reveal Multicam in Browser & Highlight (Default Shortcut: CONTROL+OPTION+COMMAND+D)
This feature performs essentially performs a “Reveal in Browser” command on the source clip within a multicam clip. Once match-framed into the browser, it will then highlight it for easily spotting.

Reveal Multicam in Angle Editor & Highlight (Default Shortcut: CONTROL+OPTION+COMMAND+G)
This feature allows you to easily “match frame” to whatever frame your playhead is over in the Multicam Angle editor, and will also highlight the source clip within the browser.

Cut n Switch Audio/Video/Both Angle 1-16 (No Default Shortcut)
Changes the multi-cam mode then performs a standard “Cut and Switch to Viewer Angle” shortcut in a single keypress.

cut-n-switch

Move To Playhead (No Default Shortcut)
Performs a Cut then Paste in a single keypress.

Select Clip at Lane 1-10 (No Default Shortcuts)
These shortcuts allow you to easily select clips outside of the Primary Storyline. For example, if you want to select a connected clip that’s directly above your primary storyline, you can assign the “Select Clip at Lane 1” to your preferred shortcut key via the Command Editor and away you go!

select-lane

Restore Keyword Preset (Default Shortcut: CONTROL+OPTION+COMMAND+1 TO 9)
Save Keyword Preset (Default Shortcut: CONTROL+OPTION+COMMAND+SHIFT+1 TO 9)
One of the coolest features of FCPX Hacks is the ability to save and restore up to nine keyword presets. What this means is that if you type in up to nine keywords in the Keyword Editor, you can save all of these these keyword shortcuts to a preset, and restore it at a later time – and even on a completely different library. This is great if you’re constantly using the same keywords between libraries, or you want to have more than the default nine keyword shortcuts.

fcpx-keywords

Timeline Clip Height Increase/Decrease (Default Shortcut: CONTROL+OPTION+COMMAND+PLUS OR MINUS)
Allows you to easily increase and decrease the timeline clip height. You can either press once to move in small increments, or hold down to increase/decrease quickly.

Batch Export from Browser (Default Shortcut: CONTROL+OPTION+COMMAND+E)
This incredible powerful feature allows you batch export multiple clips, or even multiple Smart or Keyword Collections directly from the Final Cut Pro browser. All you need to do is make your select, press the shortcut and let Final Cut Pro do it’s thing! The feature will always use the clip name as the filename, and will not overwrite files with the same name. 

batch-export

Scrolling Timeline (Default Shortcut: CONTROL+OPTION+COMMAND+W)
As its been the number one request on Richard Taylor’s Final Cut Pro X Top Requests Master List since day one, we’ve finally added a Scrolling Timeline option to Final Cut Pro. To activate and deactivate Scrolling Timeline Mode, by default you press CONTROL+OPTION+COMMAND+W, or select Enable Scrolling Timeline from the FCPX Hacks menu. Once activated, you will see a little notification on your screen saying “Scrolling Timeline Activated”. Now, if you have your mouse in the timeline area and press spacebar, the timeline will automatically scroll for you! However, if you press spacebar with the mouse outside of the timeline area – the timeline will playback as normal, allowing you to easily switch between the two modes. You can also deactivate the scrolling timeline during playback by pressing the Scrolling Timeline Mode shortcut key again (CONTROL+OPTION+COMMAND+W). Of course, this shortcut key can always be customised as explained above! If your playhead is not visible when you press play, FCPX Hacks will automatically move your playhead to the middle of the timeline. You can continue to use all your usual shortcuts (i.e. ‘Add Marker’ and ‘Blade’) whilst playing back and the playhead will remain static.

Select Color Board Puck (Default Shortcuts: CONTROL+OPTION+COMMAND+M , . / )
Until now there’s been no shortcut key to individual select Color Board pucks – however thanks to FCPX Hacks, you can now not only select individual pucks with a single mouse click, but also to make colour grading within Final Cut Pro a lot easier with a control surface, we’ve added lots of additional Color Board Shortcuts to the Command Editor – such as “Color Board: Color Puck 1 & Down” – which selects the Global puck within the Color panel and then moves the puck in a downward direction. If you hold one of these shortcuts down, the puck will continue to move until you release the shortcut. None of these shortcuts have defaults, so you’ll need to assign them in the Command Editor to use them.

Mouse Control of Color Board Pucks  (No Default Shortcut)
These shortcuts are unassigned by default, so you’ll need to activate Enable Hacks Shortcuts in Final Cut Pro to use them. Once assigned via the Final Cut Pro Command Editor, these shortcuts allow you to control the Color Board pucks with your mouse. For example, if you assign Mouse Control Color Puck 1 to the Q key, when you hold down the Q key and move your mouse – the puck will move with the mouse. As soon as you release the key, the puck will stop moving.

mouse-control

Enable Shortcuts During Fullscreen Playback (No Default Shortcut)
FCPX Hacks also adds the ability to perform Set Range Start, Set Range OutConnect to Primary Storyline, Connect to Primary Storyline Backtimed, Insert and Append to Storyline, whilst in fullscreen playback mode. This feature is off by default, and can be enabled via the FCPX Hacks Menubar. These shortcuts will still work, even if you customise your shortcuts for these commands (i.e. if you change the Set Range Start to a key other than I).

You can now Assign Individual Effects to Keyboard shortcuts via the FCPX Hacks menubar. For example, if you assign a “Directional Blur” to Effects Shortcut 1 via the menu, when you have a clip selected in the Final Cut Pro timeline and press CONTROL+SHIFT+1, it will automatically apply the “Directional Blur” effect to that clip. You can currently assign up to 5 individual effects shortcuts. However, before the “Assign Effects Shortcuts” buttons are enabled, you need to click Update Effects List first, at this will create a list of all the effects you currently have installed on your system. If you add new effects to Final Cut Pro, you’ll need to run this command again.


TOOLS:

Touch Bar (Default Shortcut: CONTROL+OPTION+COMMAND+Z)
For those that don’t have access to the fancy brand new MacBook Pro, inspired by the Touch Bar Demo App, we’re brought the Touch Bar to the desktop as an on-screen display! The Touch Bar offers some really handy features, such as the ability to view a “mini-timeline” allowing you to very quickly navigate your project. Via the FCPX Hacks menubar you can choose to have the Touch Bar appear wherever your mouse pointer is, to have it appear at the top centre of your timeline, for a more consistent experience. The Touch Bar will “disappear” when you close FCPX, and reposition itself if you resize the window. If you hold down the left OPTION key and click on the Touch Bar you can drag it to another location regardless of which mode you’re in.

touchbar

touchbar-settings

Paste From Clipboard History (No Default Shortcut)
This feature is off by default and must be activated by clicking Enable Clipboard History in the menubar. Once activated, every time you copy something in FCPX, it will be added to the Clipboard History. FCPX Hacks currently remembers the last 5 items – even after you restart your computer. If you want to clear your history, there’s a Clear Clipboard History option in the menubar. It currently labels everything by date and time (for now).

Paste from Shared Clipboard (No Default Shortcut)
This feature is off by default and must be activated by clicking both Enable Clipboard History and Enable Shared Clipboard from the FCPX Hacks menubar. When you click Enable Shared Clipboard you will be prompted to select a folder in which you’ll save your shared clipboard. This should be a network drive, or cloud storage such as iCloud or Dropbox, so multiple editors can access the shared clipboard at the same time. Once enabled, when you copy anything in FCPX it will automatically appear on all of your machines that are running FCPX Hacks and pointing to the same Shared Clipboard folder. This makes sharing assets between machines as easy as copying and pasting!

sharedclipboard

Import Shared XML File (No Default Shortcut)
This feature is off by default and must be activated by clicking Enable XML Sharing from the FCPX Hacks menubar. When you click this you will be prompted to select a folder which will act as your local “drop box” (i.e. where you drag Final Cut Pro libraries, events or clips to), as well as a folder to use as your “shared” folder (which should be a network drive, or cloud storage such as iCloud or Dropbox so that multiple editors can access this folder at the same time). Once enabled, if you drag anything from the Final Cut Pro browser to your drop folder, you will be presented with a dialog box to enter a name for this XML file. Once you enter a name and click “OK”, it will automatically appear on all of your machines that are running FCPX Hacks and pointing to the same shared folder.

shared-xml

Close Media Import When Card Inserted (No Default Shortcut)
This feature is off by default and must be activated by clicking Close Media Import When Card Inserted in the menubar. Once activated, this feature will automatically close the Media Import window in Final Cut Pro when you insert a camera card (such as an SD or CF card).

Mobile Notifications (No Default Shortcut)
This feature is off by default and must be activated by clicking Enable Mobile Notifications in the menubar. When activating this feature, you’ll be asked to enter your Prowl API key. If you don’t already have one, you can register and get one for free here.

Once activated, every time Final Cut Pro successfully or unsuccessfully completes an export, you’ll get an alert on any mobile devices that have the Prowl app installed, such as your iPhone or iPad.



HACKS:

Enable Timecode Overlay (Default Shortcut: CONTROL+OPTION+COMMAND+T)
This feature turns on a hidden Final Cut Pro preference that enables timecode overlays in the Viewer. As this is a “hack” it requires Final Cut Pro to restart before taking affect.

Enable Moving Markers (Default Shortcut: CONTROL+OPTION+COMMAND+Y)
This feature turns on a hidden Final Cut Pro preference originally discovered by Alex4D that allows you to move markers in your timeline with your mouse. As this is a “hack” it requires Final Cut Pro to restart before taking affect.

Enable Moving Markers (Default Shortcut: CONTROL+OPTION+COMMAND+P)
This feature turns on a hidden Final Cut Pro preference that allows you to continue rendering and performing other tasks whilst Final Cut Pro is still playing back in the timeline. As this is a “hack” it requires Final Cut Pro to restart before taking affect.

Change Backup Interval (Default Shortcut: CONTROL+OPTION+COMMAND+B)
This feature allows you to manipulate a hidden Final Cut Pro preference that allows you to change Final Cut’s internal backup interval. As this is a “hack” it requires Final Cut Pro to restart before taking affect.

Change Smart Collections Label (Currently Accessed by Menubar Only)
This feature allows you to change the label of the Smart Collection that’s added by default in every new Final Cut Pro project. This is just changing the meta-data behind the scenes, so it doesn’t affect your library at all (i.e. if you open the same library on another machine, it will go back to saying “Smart Collections”).


WHAT’S NEXT?

I’m also currently working on a bunch of other features based on things I’d love to see in Final Cut Pro, and also feedback from the Final Cut Pro community. If there’s something you’d love to see added to FCPX Hacks, let me know via the below poll. However, there’s a few things I won’t bother working on, as I ASSUME that Apple will do them in a future release, such as customising window layouts, an undo/actions history, and anything to do with audio roles or a potential role-based mixer.

What features would you like to see in FCPX Hacks?

Also, feel free to leave more detailed feature suggestions in the comments below, or shoot me through an email.

Thanks for testing!


ORIGINAL BLOG POST (15TH SEPTEMBER 2016):

Over the last few days, I’ve been having lots of discussions with other Final Cut Pro users on social media about how annoying the Reveal in Browser (aka ‘Match Frame’) feature in FCPX is. The problem is that if you have hundreds of clips within your browser, when you match frame it’s really hard to instantly visually see where the playhead is in a sea of other clips. It’s also really annoying if you’ve got your playhead at a specific position in the browser, then continue editing in the timeline for a hour or so, and want to easily jump back to that browser playhead position to continue where you left off. It’s VERY hard to spot which clip is selected and where the tiny white playhead is hiding in the browser!

To try and solve this, I quickly threw together a simple little AppleScript that uses the macOS Accessibility API to find out where the browsers playhead currently is, and then instantly move the mouse cursor to the playhead position. It was a bit of a hack job, but after a bit of experimenting, it finally worked. However, as many people commented, it’s a pretty bad idea to move the mouse as it breaks all the Apple Human Interface Guidelines. After playing with it for a while, I have to agree – it’s a bit strange having the mouse move on you!

One of the original ideas that Scott Simmons suggested was to somehow highlight the playhead position in the browser. My idea was to do this with a GIANT arrow, so the editor can instantly see where the playhead is. Despite a lot of Googling, I couldn’t work out how to do this with AppleScript or Automator, and I don’t have the time (or the skills) to jump into Xcode. Luckily however I discovered something called Hammerspoon.

To quote the manual: “At its core, Hammerspoon is just a bridge between the operating system and a Lua scripting engine. What gives Hammerspoon its power is a set of extensions that expose specific pieces of system functionality, to the user”.

Essentially – it’s like a more powerful and geekier version of Automator, and allows you to script a bunch of stuff to speed up everyday tasks. For example, you could write a script that changes which wireless access point you’re connected to with a click of a button, or have an alert pop up on your screen when a render is finished. There’s lots of examples here.

What I discovered is that Hammerspoon has the ability to not only handle AppleScript (so I could reuse the code I’ve already been playing with), but it can also draw things on the screen – which is exactly what I needed.

It’s also free, and open source. Bonus!

It uses the Lua scripting language – which I’ve never used before, but it seemed simple enough.

So, with a LOT of trial and error, playing with my new favourite tool UI Browser, reading through heaps of examples, some helpful Tweets, and AMAZING support from the Hammerspoon team – I was able to throw something together that seems to work!

Basically, the script I’ve made does three things (so far):

  • When you press CONTROL + OPTION + COMMAND + F it will perform a normal match frame in FCPX, but will also draw a red circle around the browser playhead temporarily so you can easily see where the playhead is.
  • When you press CONTROL + OPTION + COMMAND + H it will draw a red circle around the browser playhead (without doing a match frame). This is helpful if you’re just working in the browser, but you’ve ‘misplaced’ where the playhead currently is.
  • When you press CONTROL + OPTION + COMMAND + S it will perform a normal match frame, but it will also take the name from the clip you are match framing, and apply it to the search tool, so that only the match frame clip appears in your browser. I call this a “Single Match Frame”.

I’ve tried to code it so it works with all the common window layouts, however I’ve only tested it with FCPX 10.2.3 and macOS 10.11.6 on a MacBook Pro and a 5K iMac – so it MAY not work well on other systems. If it doesn’t work for you – let me know in the comments below.

I’ve noticed that the script can get very sluggish when you have lots (i.e. more than 500) clips in your event – whereas it’s really quick and snappy with events that only 50-100 clips. This seems to be a limitation of AppleScript, which I’ve been unable to solve thus far (if anyone has any ideas, please let me know!).

You’re also MORE than welcome to modify the script for your own needs (or fix my poorly designed code). I’ve been experimenting with it for saving/restoring FCPX window layouts, and also trying to implement a scrolling timeline – so there’s definitely some cool stuff you can do with it! I think a keyboard shortcut for “apply audio fade handle” is next on my list! If you come up with something cool, please make sure you share it in the comments below.

DISCLAIMER: I’m a filmmaker, not a programmer, so use this at your own risk. This script is provided “as is” with no warranty, so don’t come back to me if it blows things up. I’ve done very little testing outside my own machine, so the script may not work on all systems and configurations.

If you want to test it out, here’s how:

  • Download Hammerspoon. It’s free.
  • Hammerspoon comes as a ZIP file. Unzip it and drag the Hammerspoon.app to your Applications folder.
  • You can now run Hammerspoon. The first time you run it you’ll be presented with a Preferences panel:

hammerspoon-01

  • To actually function properly, Hammerspoon needs Accessibility permissions. Click the Enable Accessibility button.
  • You’ll then be presented with a Security window like the below. Click Open System Preferences.

hammerspoon-02

  • This will open the Security & Privacy system preferences. You’ll need to unlock the panel by clicking the paddock in the left hand corner of the screen, and enter in your computers password. Once the panel is unlocked, you’ll need to make sure the Hammerspoon item is ticked as per below. Once done, you can now close this window.

hammerspoon-03

  • Out of the box, Hammerspoon does nothing. What you need to do now is feed it some code!
  • So let’s Quit Hammerspoon for now.
  • You can download the latest script at the top of this page (I’ll be constantly updating this link as I slowly improve the script based on your feedback). This also comes as a ZIP. When you unzip it, you’ll find a file called init.lua and a folder called hs. This is what we need to give to Hammerspoon. The file is just a plain text file, so you can open it up in TextEdit (or my preference BBEdit) if you want to check out the code. The hs folder contains some additional Hammerscript modules not written by me.
  • We now need to move the downloaded init.lua and hs folder to ~/.hammerspoon/. The easiest way to do this is click Go > Go To Folder from the menubar in Finder (or press COMMAND + SHIFT + G from the desktop).

hammerspoon-04

  • You’ll then be presented with a dialogue box, where you need to type ~/.hammerspoon/.

hammerspoon-05

  • This will open the hidden Hammerspoon folder, where you need to drop in the previously downloaded init.lua file and hs folder.
  • Now when you open Hammerspoon it should load the script, ready to rock and roll!
  • You can now launch FCPX and see if it works by trying to match frame something (CONTROL + OPTION + COMMAND + F).
  • If it doesn’t work for some reason, the Hammerspoon application has a Console (COMMAND + R) which displays any error messages. If things don’t work as expected, let us know in the comments below so that we can fix things up.

That’s it! Hopefully it works for you and you find it useful. If it doesn’t work for you, or if you have any ideas, comments or suggestions, feel free to leave them in the comments below. Happy Cutting!

73 Responses

  1. Brian Seegmiller
    Sep 18, 2016 - 03:38 AM

    So I get the error message:

    — Lazy extension loading enabled
    — Loading ~/.hammerspoon/init.lua
    — Loading extension: hotkey
    11:35:55 hotkey: Enabled hotkey ⌘⌥⇧F19
    — Loading extension: application
    — Loading extension: uielement
    ********
    11:35:55 ERROR: hotkey: The hotkey was deleted, cannot enable it
    ********
    — Done.
    ********
    11:36:11 ERROR: hotkey: The hotkey was deleted, cannot enable it
    ********
    ********
    11:37:17 ERROR: hotkey: The hotkey was deleted, cannot enable it
    ********

    How do I fix this

    Reply
    • Chris Hocking
      Sep 18, 2016 - 10:02 AM

      Hi Brian,

      Thanks so much for testing out the script! Sorry it didn’t work for you straight out of the box.

      The hotkey error in the console is normal – so that’s not the issue.

      What version of macOS are you using? What version of FCPX?

      Are you using dual or multiple screens?

      If you are using dual screens, try switching to a single screen and see if that works.

      If you send me a screenshot of your WHOLE screen when the error happens, I might be able to work out a fix.

      Any questions let me know!

      Best Regards, Chris!

      Reply
      • Chris Hocking
        Sep 23, 2016 - 12:17 PM

        Hi Brian,

        I’ve just uploaded a new version of the script to the blog. Let me know if that fixes your issues.

        Any questions let me know!

        Best Regards, Chris!

        Reply
  2. Bruce Macbryde
    Sep 27, 2016 - 11:39 AM

    Using MacPro late 2013, 3.5 GHz 6-Core Intel Xeon E5, 24 GB 1866 MHz DDR3 ECC, AMD FirePro D500 3072 MB
    Final Cut Pro 10.2.3,
    Sys: 10.11.6.

    All shortcuts appear to work well

    Regards

    Bruce

    Reply
    • Chris Hocking
      Sep 27, 2016 - 11:41 AM

      Legend, thanks Bruce! Appreciate it!

      Reply
  3. Guillaume Solar-Pelletier
    Sep 27, 2016 - 11:09 PM

    Hi Chris!!

    This is so cool…First the script had an error but after restart it work fine!

    What you did with “Multicam Match Frame & Highlight Playhead” is very very nice.

    I was wondering if it is possible to highlight the playhead directly in the angle editor.

    As you did it in the browser is just crazy good, but in the angle editor would be awesome good!

    Thank Chris, this will help a lot!!!!

    Reply
    • Chris Hocking
      Sep 28, 2016 - 06:37 AM

      Thanks for your kind words Guillaume!

      Did you happen to take a screenshot of the errors you were having when you first opened the script?

      So basically, you want a “Reveal Multicam Clip in Angle Editor” as opposed to “Reveal Multicam Clip in Timeline”? If so, yes, that’s definitely possible – I’ll add it later today.

      Reply
      • Chris Hocking
        Sep 28, 2016 - 02:18 PM

        Version 0.20 now has a “Reveal Multicam Clip in Angle Editor & Highlight” feature.

        Hope this helps!

        Reply
  4. Sasu Riikonen
    Sep 27, 2016 - 11:15 PM

    How about making mark in/out and append to storyline commands work in full screen mode? That would be nice.

    Reply
    • Sasu Riikonen
      Sep 28, 2016 - 01:14 AM

      Just noticed append to storyline actually works when playing full screen, but mark in/out doesn’t .

      Reply
      • Chris Hocking
        Sep 28, 2016 - 06:40 AM

        Thanks for your feedback Sasu.

        Just so that I can get my head around it – you basically want the ability to add in and out points whilst in fullscreen playback mode (i.e. COMMAND + SHIFT + F), so that if you’re watching a clip from the browser you can apply in and out points, that appear in the browser? Is that correct?

        I’ll have a play – but I think the only way I could make this happen is that if I quickly jump back from full screen mode to the browser then back again, which would disrupt playback. Would this be an issue, or are you expecting continuous playback?

        Reply
        • Sasu Riikonen
          Sep 29, 2016 - 06:33 AM

          Yes that is what I mean. I would love to add in and out points in fullscreen playback mode. Now I have to exit fullscreen mode to add in and out points. Its so stupid because many other commands works in full screen mode.

          This is what I’m dreaming about:
          -Select clip in browser
          -enter full screen mode (CMD + SHIFT + F)
          -browse clip using J-K-L
          -mark in and out points (I, 0)
          -append to primary storyline (E)
          -select next clip (DOWN ARROW)
          -etc.

          So I could make rough cut never leaving full screen mode. How nice would be that? Now I have to exit full screen mode to mark in and out points. And that pretty much makes that workflow useless. Everything else works fine.

          It’s hard to say how disturbing is the problem you described. Thank you for your effort.

          Reply
          • Chris Hocking
            Oct 03, 2016 - 11:41 PM

            Hi Sasu,

            Version 0.26 of the script now enables keyboard shortcuts during full-screen (CMD+SHIFT+F) playback. It’s a bit of a hack job – all it does is very quickly exit full screen mode, press the shortcut key you wanted, then re-enter full-screen mode, so you’ll see the screen flash – but it works (assuming you haven’t changed the default FCPX keyboard shortcuts).

            Any bugs or issues let me know!

  5. jose angel
    Sep 28, 2016 - 06:13 AM

    Go to install and try it. Sounds all fantastic.

    Hope will be possible to “make playhead” static in the middle of the screen, moving timeline not playhead.

    Also some kind of usefull color correction under shuttle pro will be welcome.

    Thanks for your job and for share with us.

    King regards.

    Reply
    • Chris Hocking
      Sep 28, 2016 - 06:42 AM

      Thanks for your kind words Jose!

      I think doing a “static playhead” in the timeline should be technically possible. I’ll have a play and see if I can make it work – although I’d expect Apple to do this themselves in the next update (fingers crossed!).

      What shortcuts keys are you missing that prevents you from currently doing colour correction using the Shuttle Pro?

      Reply
      • jose angel
        Oct 03, 2016 - 11:27 AM

        [fingers crossed here too]

        Here is a link to shuttle pro settings i try to for doing color correction, but i have not success with it.

        Some one send me some scrip to make it work, but i´m not able to do.

        Link to pdf file: https://infinit.io/_/R92PSpL
        if you want shuttle pro settings file, here are: https://infinit.io/_/372kuFM

        Regards.

        Jose Angel.

        Reply
        • Chris Hocking
          Oct 03, 2016 - 11:54 AM

          Using our script, you should have no issues controlling the Colour Board using a Shuttle Pro.

          Within FCPX, you’ll need to assign shortcut keys to the “Color Board: Nudge Puck Up/Down/Left/Right” commands, and then assign them to your Shuttle Pro (which you’ve probably already done).

          With the help of my script, rather than using the “Select Next/Previous Puck” commands, you can use my “Select Color Board Puck 1-4” shortcuts to select the puck you want to control – saving you some button presses.

          Any issues let me know!

          Reply
  6. Ashok
    Sep 30, 2016 - 01:49 AM

    Hi Chris,

    Just installed Hammerspoon and took it out on a spin. Works beautifully.
    Thank you for it.

    Mark In / Out in full screen mode would make the edits so much more fun. And fast. But without leaving full screen. So cool it would be.

    Thanks again for the awesome hack. You are a rockstar.

    Reply
    • Chris Hocking
      Sep 30, 2016 - 04:39 PM

      Thanks for your kind words Ashok!

      Yes, I’m currently trying to come up with a good way to solve the full-screen in/out issue. Will update the blog if I eventually come up with a suitable fix. Stay tuned!

      Reply
      • Chris Hocking
        Oct 03, 2016 - 11:39 PM

        Hi Ashok,

        Version 0.26 of the script now enables keyboard shortcuts during full-screen (CMD+SHIFT+F) playback. It’s a bit of a hack job – all it does is very quickly exit full screen mode, press the shortcut key you wanted, then re-enter full-screen mode, so you’ll see the screen flash – but it works (assuming you haven’t changed the default FCPX keyboard shortcuts).

        Any bugs or issues let me know!

        Reply
        • Ashok
          Oct 07, 2016 - 12:17 AM

          Hi Chris,
          Thanks for the responses and the update. Tried it a couple of times. Seems to work just fine.
          Will definitely keep you posted on any developments.
          Thanks again for what you are doing.
          Warm regards.

          Reply
  7. Jeremy W
    Oct 04, 2016 - 03:46 AM

    Hi-
    What does the “Leave in place on import” actually do in comparison to built-in functionality?
    Thanks.

    Reply
    • Chris Hocking
      Oct 04, 2016 - 08:49 AM

      “Background Render”, “Leave in Place”, “Create Optimised Media” & “Create Proxy Media” simply automate the ticking of the boxes within Final Cut Pro’s preferences. They don’t do anything different to the built-in functionality – it just saves you a couple of mouse clicks, and also allows you to visually see what your settings currently are with a single mouse click.

      Reply
  8. Alex Gollner
    Oct 07, 2016 - 10:26 AM

    New feature suggestion: Highlight proxy mode. Draw a single point dark red line across the bottom of window title bars when you are in proxy mode

    Reply
    • Chris Hocking
      Oct 07, 2016 - 10:37 AM

      Yeah, I’ve been meaning to do this. Will give it a bash sometime soon!

      Thanks for all your ideas and advice Alex!

      Reply
      • Chris Hocking
        Oct 07, 2016 - 11:03 PM

        Version 0.30 now allows you to display an optional Proxy/Original icon in the Menubar. Enjoy!

        Reply
  9. Iñaki Sanz
    Oct 11, 2016 - 01:09 AM

    I get this messge when running Hammerspoon:

    Begin Hammerspoon script:

    — Loading extension: uielement
    — Loading extension: fs
    — Loading extension: host
    — Loading extension: osascript
    — Loading extension: http
    — Loading extension: pathwatcher
    [FCPX HACKS] ERROR: Wasn’t able to retrieve the Active Command Set.
    — Loading extension: menubar
    — Loading extension: settings
    — Loading extension: application
    *** ERROR: /Users/inyaki/.hammerspoon/init.lua:6114: attempt to call a nil value (method ‘isRunning’)
    stack traceback:
    /Users/inyaki/.hammerspoon/init.lua:6114: in function ‘isFinalCutProFrontmost’
    /Users/inyaki/.hammerspoon/init.lua:676: in function ‘refreshMenuBar’
    /Users/inyaki/.hammerspoon/init.lua:259: in function ‘loadScript’

    Reply
    • Chris Hocking
      Oct 11, 2016 - 10:08 AM

      Thanks for testing! What version of the script are you running?

      Try downloading the latest version and see if that fixes your problem.

      If you’re still getting errors, send me an email with the full contents of the console, and I’ll try and troubleshoot.

      Reply
      • Iñaki Sanz
        Oct 11, 2016 - 06:44 PM

        Last version (version 0.37 – 11th Oct 2016 @ 1666) works fine! Thanks, Chris.

        Reply
        • Chris Hocking
          Oct 11, 2016 - 07:23 PM

          Great news! Thanks for testing Iñaki!

          Reply
  10. jose angel
    Oct 14, 2016 - 08:22 PM

    0,38 here working as expected. Great job.

    Some improvement….. add stabilization to multicam clips ?

    King regards.

    Reply
    • Chris Hocking
      Oct 15, 2016 - 08:58 AM

      Great news! Thanks so much for testing Jose!

      I think stabilisation to multi-cam clips is probably something only Apple can do, but I’ll definitely look into it.

      Reply
      • jose angel
        Oct 21, 2016 - 02:02 AM

        maybe go the way match frame inside angle editor, revert it to “select range”, cut it inside it´s own angle, and now we can apply the desired effect.

        Reply
        • Chris Hocking
          Oct 21, 2016 - 02:39 PM

          Great idea! This is definitely a possibility.

          Although, there are now a couple of 3rd party tools that allow stabilisers on multi-cam clips, so I think this currently falls towards the bottom of the priority list.

          Reply
  11. Knut Hake
    Oct 16, 2016 - 12:00 AM

    Hi Chris,

    Great work you are doing here.

    Here are my hack- wishes :

    – [ ] detailed trimming feedback when trimming with keyboard (2up display)
    should appear also on keyboard use, not only when dragging with the mouse/trackpad ) 2 up display and a 4 up display for slide and roll!

    – [ ] Proper dynamic trimming
    with jkl when using trim tool ( as in precision editor: Select edge with [ ] \ Ctrl E to open it Shift / or JKL to play Shift X to edit Refine with . , /

    – [ ] replace at playhead command

    – [ ] Folders for events

    – Dragable Effect or Effects from the Inspector to a clip or selected clips in the Timeline or Event Browser

    – [ ] Column in browser for “last modified“

    – [ ] Allow skimming of project thumbnails

    You are a magician.

    Reply
    • Chris Hocking
      Oct 16, 2016 - 07:56 PM

      Thanks for your kind feedback Knut! Very much appreciated!

      Replies as follows:

      1) In regards to detailed trimming feedback, I THINK this might be possible. Basically what I would do is instead of using the default shortcut keys, I’d make my own that essentially “clicks” the end of the clips and drags it a frame. Once you “release” the keys, the mouse would stop “holding” the end of the clips. It might be tricky though, as how much you need the mouse depends on the zoom factor, your screen size, etc. Maybe this is something we wait and see if Apple fixes themselves in the next version, and if not, I’m happy to give it a bash.

      2) I’m not exactly sure what you mean by “proper dynamic trimming” (probably because I never use the Precision Editor) – so might need some more clarification on this one.

      3) This should be possible. Basically, I would just select whatever clip in the Primary Storyline is under the playhead, then perform a replace. Would you expect the playhead to go back to the original position?

      4) Unless anyone has any clever ideas, I think “Folders for Events” is only something Apple could do.

      5) I THINK “Draggable Effects” is something only Apple could do. However, I could potentially make a shortcut key that allows you to copy the select effect(s) to whatever primary storyline clip is under the playhead currently.

      6) In regards to a “last modified” column, I think this is something only Apple could do, but I’ll look into it to see if there’s any “hacky” way to make it work.

      7) There is a secret preference for “Enable Sequence Filmstrips” – but I’ve never work out what it actually does. I’ll keep playing, as maybe this could be what you’re after.

      Reply
      • Knut Hake
        Oct 16, 2016 - 08:22 PM

        Chris,

        Thank you for considering my wishes.

        1) It’s been on my wishlist I sent to Apple from day one.
        I just do not get why the behaviour is different on keyboard use.

        2) something that I actually miss from avid or fcp7
        See here: https://youtu.be/CmWPzalVPJA
        Or here: https://vimeo.com/115933292

        I don’t use the Precision editor either. Clumsy and cannot expand audio.

        3) replace at playhead should replace at playhead from selected browser clip to playhead position in timeline. Great for swapping takes.

        Thank you for your great effort to make a great tool even better.

        Reply
  12. David L.
    Oct 21, 2016 - 07:42 AM

    Hi,
    great work! Could you get the thumbnails in the timeline loading during playback? This would be an awesome addition to the scrolling timeline!

    Reply
    • Chris Hocking
      Oct 21, 2016 - 02:37 PM

      Unfortunately, I think that’s something only Apple can do. This might also be the reason why they’ve never done a scrolling timeline of their own!

      Reply
  13. Eric Conley
    Oct 22, 2016 - 06:49 AM

    Love the FCPX Hacks! I started with them because of the move marker function. Other functions like timecode and find frame indicator are awesome also.
    One I have always missed, is replacing a clip while keeping the existing attributes from the old clip, like effects, transforms etc. In addition to that, is replacing a clip while matching the timecode from original clip. For example a graphic you started 2 seconds into the clip has been updated, now you need to replace it in the timeline. Hold down option(or something) and replace with the same in point from the original. Another example would be replacing a stock footage comp with the new full resolution purchased footage.

    Reply
    • Chris Hocking
      Oct 22, 2016 - 11:45 AM

      Thanks for your kind words Eric!

      I discovered recently that when you copy a clip to the clipboard, all of the clip metadata is also stored in the clipboard, so I’m hoping to work out some cool ways to manipulate this data in the future – this could be useful for a “replace and keep attributes” shortcut, as you suggest. I’ll add it to my list of things to play with!

      Reply
  14. Dave
    Oct 24, 2016 - 06:30 AM

    Hi Chris, thanks for your work; it’s very clever.

    A comment and a question from me; the scrolling timeline is a great feature but works intermittently for me. I’m on a late 2011 iMac running sierra with 24gig of ram. I’ve enabled it in the menu but it scrolls for a while and then stops and then will start again quite randomly.
    I’m really interested in how you managed to enable this feature but apple have never bothered. What part of the operating system are you accessing to get it working?

    Reply
    • Chris Hocking
      Oct 24, 2016 - 07:03 AM

      Hi Dave,

      Thanks for your kind words.

      What version of the script are you using? If you’re not using the latest version (0.48), try downloading and see if that helps.

      When you say the scrolling timeline stops working – do you mean it fails to activate when you press spacebar (i.e. you press spacebar and it doesn’t scroll), or do you mean it starts scrolling when you press spacebar but stops working randomly if you leave it playing?

      Keep in mind that the scrolling timeline ONLY works if you have your mouse in the timeline area. Read the blog above for an explanation.

      Behind the scenes the scrolling timeline functionality is quite simple. All I’m doing is monitoring the playhead position, then adjusting the scroll bar at the bottom of the timeline to compensate using GUI Scripting. Apple could EASILY do this (far easier than the method I’m using) – however, my GUESS is the reason they haven’t done this is because as you’ll see in my version, the timeline thumbnails and waveforms don’t automatically update. I’d imagine if they want a scrolling timeline feature, they’d need to re-think how they cache the timeline thumbnails and waveforms – which might be quite a big engineering challenge.

      Thanks for testing! If you’re still having issues let me know!

      Best Regards, Chris!

      Reply
      • Eric Conley
        Oct 25, 2016 - 08:01 AM

        Chris,

        I have found that when I have the Timeline Index window open, the scrolling feature stops. Not the end of the world, just an FYI.

        Reply
        • Chris Hocking
          Oct 25, 2016 - 08:35 AM

          That’s interesting – thanks Eric! I’ll have a look to see what’s happening.

          Reply
          • Chris Hocking
            Oct 25, 2016 - 07:15 PM

            Eric, this should now be fixed in FCPX Hacks 0.51. Thanks for testing!

      • Dave
        Oct 26, 2016 - 01:57 PM

        Thanks for your reply, Chris. I had to take the software off my machine as there seemed to be some issue with the up and down arrows not jumping from cut point to cut point. With fcpx hacks removed functionality returned.
        As for the issue with the timeline intermittently scrolling; My experience has been that the space bar isn’t activating scrolling but that the feature seems randomly kick in after a while (I’ve made sure the mouse is in the timeline area). Could this be an issue with the magnification level?
        Also, I’m using my own customised keyboard shortcuts…would that be an issue?

        Reply
        • Chris Hocking
          Oct 26, 2016 - 02:41 PM

          Sorry to hear you’re still having issues! That’s annoying.

          Ummm… that’s strange about the arrows not jumping from cut point to cut point. The only thing I can think is maybe that FCPX Hacks got confused, and it was thinking the timeline was playing when it actually wasn’t. Toggling the Scrolling Timeline Activation (CONTROL+OPTION+COMMAND+W) stops “watching” the timeline, and should fix the issue.

          That’s also strange about the timeline intermittently scrolling. Again, my only guess is that you’ve done some kind of key combination that’s confused FCPX Hacks thinking the timeline is playing when it really isn’t. Again, toggling CONTROL+OPTION+COMMAND+W should fix the issue.

          If you haven’t already, try downloading the latest version (0.53) and let me know if you’re still having issues, and we’ll try and come up with a fix. Maybe try using it without “Enable Hacks Shortcuts in Final Cut Pro” ticked for a while and see if it works fine, then if it does try enable the Hacks shortcuts, and see if that causes the issues.

          If you originally used one of the REALLY early versions of FCPX Hacks, it might also be worth pressing “Trash FCPX Hacks Preferences” from the “FCPX Hacks > FCPX Hacks Settings” menubar, to see if that helps and using a new keyboard layout.

          Hope this helps!

          Reply
  15. Michael
    Oct 25, 2016 - 04:06 AM

    Would be useful to provide a script to circle the download button on this page ;-) Or put a big red button at the top! Finally I found the download link somewhere in the middle of the (long) text….

    Reply
    • Chris Hocking
      Oct 25, 2016 - 07:07 AM

      Haha… good point, thanks Michael! Fixed!

      Reply
  16. Francisco Rios
    Oct 25, 2016 - 12:44 PM

    Hi Man! Great WORK!!
    Did anybody mention marks on timeline? We had before on FCP7, so we can jump through entire timeline on specific places …
    BEST!

    Reply
    • Chris Hocking
      Oct 25, 2016 - 07:30 PM

      Thanks for your kind words Francisco!

      I’m sure a LOT of editors would LOVE to see timeline markers – however, I think it would be an absolutely MASSIVE task for me to try and implement. Let’s see what Apple does later this week – and if they don’t add it, then I’ll have a proper think.

      Although – the Timeline Index is a pretty good alternative to markers?

      Reply
  17. ron
    Oct 25, 2016 - 07:56 PM

    Hi Chris,

    First of all thank you so much for this excellent plugin to FCPX !!! I am only starting to use it and already loving it THAT MUCH !
    Great work !

    And in order to make it even more fantastic, do you think it is possible to implement a function that could trim synchronized (or compound or multicam) clips to the useful video length (i.e. remove black frames at start & end) in the browser ?

    I mean, when you sync a bunch of audio & video, if those have not the same length, those black frames at the beginning of the clips are a real PITA. If you zoom out in your browser to check all your shots … all of them are black !! This is even more painful when the audio has never been cut and syncs on videos that are dramatically shorter.

    This situation is especially happening when syncing using Pluraleyes which for whatever reason does not trim to video length ,,, but trims at random some amount of black frames before and after the video.

    If possible, this feature alone would save hours in handling media before editing !

    Anyway, all the best and keep up the good work !

    Cheers

    R.

    Reply
    • Chris Hocking
      Oct 25, 2016 - 09:19 PM

      Thanks for your kind words Ron!

      This is definitely possible – but I’m not exactly sure about the best way to go about it. I could make a feature that basically just “controls” the mouse and keyboard (like the Batch Export feature does) – which would work, but it could be pretty fragile and inefficient if you’ve got hundreds of clips you want to “process”. What would probably be better and smarter (especially if you’re using PluralEyes anyway) is to write something that accepts and XML then spits back out a “fixed” XML. I’m happy to give it a bash – but it probably won’t be for quite some time, as I’ve never really played with XMLs… yet.

      Let’s hope that Apple fixes this later this week! It’s also definitely worth sending Red Giant and email to see if they can update PluralEyes!

      Reply
  18. Mohamedwanas
    Oct 27, 2016 - 11:33 PM

    Thank you for this good work but I have issue : FCPX Hacks not work when I have installed both Final cut pro 7&X … when I click open final cut in FCPX Hacks in the menu bar it lunches Final Cut pro7 not x ?
    Should I uninstall fcp7 ?

    Reply
    • Chris Hocking
      Oct 28, 2016 - 04:30 AM

      Good question! I’ve uninstalled FCP7 on all our machines, so I haven’t tested it. FCPX Hacks ASSUMES that FCPX is installed in the Applications folder as “Final Cut Pro” – so try renaming FCP7 to something else, and make sure FCPX has the “Final Cut Pro” name in the root of the Applications folder.

      Reply
  19. John
    Nov 04, 2016 - 07:12 AM

    Love FCPX Hacks! I had only heard about the highlighting feature, but then I heard about timecode overlays and I immediately installed. And I donated to hopefully keep momentum going after the 10.3 update! I would love it if you could turn off the header on the source code overlay only because it takes up extra space on the screen and it’s fully apparent what each column is without the header. A secondary request would be the ability to customize its location, even if it’s a few fixed positions (top left, bottom center, etc.) Thanks for all of your work!

    Reply
    • Chris Hocking
      Nov 19, 2016 - 11:57 AM

      Sorry for the delayed reply John – I’ve been off on a shoot the last couple of weeks.

      The interface of the timecode overlay is actually designed by Apple – all I’m doing is enabling the visibility of a hidden overlay. Unfortunately I haven’t yet worked out a way to “tweak” how that overlay works.

      Thanks so much for your support and your donation! Yesterday I released an update that brings back the scrolling timeline to 10.3, and I’m hoping to fix up the rest of the features in the coming days. Stay tuned!

      Reply
  20. Alejo
    Nov 24, 2016 - 10:38 AM

    It would be great a tool to find duplicated clips or with the same file name in browser.
    Great work!
    Thanks!

    Reply
    • Chris Hocking
      Nov 24, 2016 - 12:04 PM

      Hi Alejo,

      Thanks for the feedback!

      That’s certainly an interesting idea, that sounds useful. However, the only way I can think that you could do this is via XML – you’d export an XML of a Smart or Keyword collection, process it, and bring it back into FCPX as a NEW Keyword Collection.

      Curious… why do you need to find clips with the same name?

      Reply
      • Alex Gollner
        Dec 03, 2016 - 02:31 AM

        Dupe detection could work by making a ‘Used 2 times’ ‘Used 3 times’ keywords. The editor would have to drag the project to an external application which would have to process the XML to work out which ranges should have the keyword (tag) assigned. Then those tags would be discoverable in the timeline index.

        Reply
        • Chris Hocking
          Dec 03, 2016 - 08:33 AM

          Great idea Alex, however I feel like this is something Intelligent Assistance should make!

          It’s definitely possible using FCPX Hacks, but my knowledge of FCPXML is pretty limited, so i would take me a while to build this. One day when I eventually solve he ability to drag and drop Final Cut Pro Libraries, Events & Event items into the FCPX Hacks menubar (so that I no longer have to do the Dropbox workaround for XML Sharing), then I’ll spend some more time really playing with FCPXML manipulation, as it opens up lots of doors.

          However, having said that, I think what could potentially be even MORE interesting is rather than using FCPXML is using the clipboard metadata for this kind of thing. I’m thinking you just CMD+A your timeline, then CMD+C, then from the FCPX Hacks menu there’s a list of “Process Clipboard Contents” items – such as “Add Dupe Detection Keywords”, and when you click it, we process and manipulate the clipboard data, and paste it back into Final Cut Pro like magic. This would, in theory at least, avoid all the metadata limitations of FCPXML.

          Like my knowledge of FCPXML however, my knowledge of the Final Cut Pro’s proprietary clipboard XML is even more limited – so this might require something far smarter than me to help work out and solve. I am trying to work out how to copy and paste between FCPX and After Effects though, so if I can work this out, maybe it will help with all the other things later down the line.

          Thanks for all your support and promotion Alex! HUGELY appreciated!

          Reply
  21. Ricky Dominguez
    Dec 01, 2016 - 01:23 AM

    I can’t update to macOS Sierra because I have a Mac Pro Early 2009 and I would like to prevent to get this message “Error: could not detect Touch Bar support” every time I start my Mac.

    Thanks for FCPX Hacks.

    Reply
    • Chris Hocking
      Dec 01, 2016 - 07:48 AM

      Thanks Ricky! This will be fixed in the next update – hopefully later today. Stay tuned!

      Reply
      • Chris Hocking
        Dec 02, 2016 - 11:22 PM

        Ricky – this should now be fixed in FCPX Hacks 0.68. Any issues let me know!

        Reply
  22. Eric Conley
    Dec 02, 2016 - 07:56 AM

    Well, the apple updates got me. Yesterday, I updated FCPX to 10.3.1. When I try to start Hammerspoon, it tells me that I don’t have a compatible version. Only 10.2.3 or 10.3 work. I miss the hacks already :( Please help.

    Reply
    • Chris Hocking
      Dec 02, 2016 - 04:43 PM

      Sorry for the delay Eric! I keep on getting caught up with “real work”, however, I’m HOPING to release a new version of FCPX Hacks later tonight which fixes this, along with a bunch of other bugs and issues people have reported. I’ll email you once it’s up. Stay tuned!

      Reply
    • Chris Hocking
      Dec 02, 2016 - 11:22 PM

      FCPX Hacks 0.68 now supports Final Cut Pro 10.3.1 – enjoy!

      Reply
      • Craig Kuehne
        Dec 03, 2016 - 06:22 AM

        I have Final Cut Pro X 10.3.1 in the root of my Applications Folder, but it still says it can’t find it, and needs at least version 10.3. I’m running 0.68. Any ideas? Regardless, thank you for spending so much time on something very helpful. I know it’s well appreciated. :)

        Reply
        • Chris Hocking
          Dec 03, 2016 - 08:21 AM

          Hi Craig,

          Have you renamed the Final Cut Pro application? As long as you have 10.3.1 in the Applications folder and it’s called “Final Cut Pro.app” – it should work fine. If you renamed it something else, it won’t work.

          If you’re still having issues – feel free to email me to problem solve: https://latenitefilms.com/contact/

          Thanks for testing!

          Reply
      • A. Menéndez
        Dec 03, 2016 - 07:17 AM

        I have the same problem, which began after updating to FCPX 10.3.1.

        Updating FCPX Hacks to version 0.68 hasn’t solved the problem.

        After I updated Hacks it curiously once launched my legacy version of Final Cut Pro (v. 7) and now I keep getting the message “We couldn’t find a compatible version of Final Cut Pro installed on this system. Please make sure Final Cut Pro 10.2.3 or 10.3 is installed in the root of the Applications folder and hasn’t been renamed.”

        Reply
        • A. Menéndez
          Dec 03, 2016 - 07:47 AM

          I renamed Final Cut Pro to something else then back to Final Cut Pro. Also I renamed the old version (which is in a subfolder) to Final Cut Legacy. Not sure what exactly did the trick but everything is working fine now. Thanks!

          Reply
          • Chris Hocking
            Dec 03, 2016 - 08:25 AM

            Interesting! Well, it could be that whenever you launch “Final Cut Pro 7”, macOS will then regard “Final Cut Pro 7” as “Final Cut Pro”, until you close it and launch “Final Cut Pro 10.3”. As they’re both called “Final Cut Pro”, I can completely understand why macOS would get confused!

            I no longer have “Final Cut Pro 7” installed, so unfortunately I can’t do any testing on this – sorry! But as long as “Final Cut Pro 10.3” is named “Final Cut Pro” in the root of the Applications folder, and has been launched at least once prior to running Hammerspoon – it SHOULD all work.

            Thanks heaps for testing!

Leave a Comment