|
4 | 4 | <description><![CDATA[Latest News from FCP Cafe]]></description> |
5 | 5 | <link>https://fcp.cafe</link> |
6 | 6 | <generator>FCP Cafe</generator> |
7 | | - <lastBuildDate>Fri, 16 Jan 2026 11:43:04 GMT</lastBuildDate> |
| 7 | + <lastBuildDate>Fri, 16 Jan 2026 12:33:52 GMT</lastBuildDate> |
8 | 8 | <atom:link href="https://fcp.cafe/rss.xml" rel="self" type="application/rss+xml"/> |
9 | | - <pubDate>Fri, 16 Jan 2026 11:43:04 GMT</pubDate> |
| 9 | + <pubDate>Fri, 16 Jan 2026 12:33:52 GMT</pubDate> |
10 | 10 | <item> |
11 | 11 | <title><![CDATA[23rd May 2023]]></title> |
12 | 12 | <description><![CDATA[<p>Iain Anderson has written a very detailed <a href="https://www.provideocoalition.com/final-cut-pro-10-6-6-for-mac/">Final Cut Pro 10.6.6 blog post</a> over at Pro Video Coalition.</p> |
@@ -12049,62 +12049,6 @@ You can learn more and download BRAW Toolbox on the <a href="https://brawtoolbox |
12049 | 12049 | <p>This is a free tool that allows you to completely customise your Final Cut Pro Workspace layout.</p> |
12050 | 12050 | <p>In theory it's amazing - and Patrokiras has done a great job building a fantastic website to customise things. It's a really nice user interface!</p> |
12051 | 12051 | <p>Because a <code>fcpworkspace</code> file is just a plist (Property List) - it's actually very easy to mess around with an customise - you can just open it in a text editor (I use <a href="https://www.barebones.com/products/bbedit/">BBEdit</a>).</p> |
12052 | | -<p>For example, here's the start of a file for example:</p> |
12053 | | -<pre><code><?xml version="1.0" encoding="UTF-8"?> |
12054 | | -<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> |
12055 | | -<plist version="1.0"> |
12056 | | -<dict> |
12057 | | - <key>AdditionalInformations</key> |
12058 | | - <dict> |
12059 | | - <key>timecodeHUDShowStateKey</key> |
12060 | | - <false/> |
12061 | | - <key>timecodeProjectHUDShowStateKey</key> |
12062 | | - <false/> |
12063 | | - </dict> |
12064 | | - <key>App Version</key> |
12065 | | - <integer>85</integer> |
12066 | | - <key>Auto Layout</key> |
12067 | | - <false/> |
12068 | | - <key>Bounds</key> |
12069 | | - <string>{{0, 45}, {2056, 1240}}</string> |
12070 | | - <key>Category</key> |
12071 | | - <integer>0</integer> |
12072 | | - <key>Display Name</key> |
12073 | | - <string>Final Cut Pro.saved</string> |
12074 | | - <key>Identifier</key> |
12075 | | - <string>C8AFE9FB-EF4C-4036-95E1-B7FFAC353E37</string> |
12076 | | - <key>Key Equivalent</key> |
12077 | | - <string></string> |
12078 | | - <key>Layout Inset</key> |
12079 | | - <real>0.0</real> |
12080 | | - <key>Layouts</key> |
12081 | | - <array> |
12082 | | - <dict> |
12083 | | - <key>Class</key> |
12084 | | - <string>PEMainWindowModule</string> |
12085 | | - <key>Content</key> |
12086 | | - <dict> |
12087 | | - <key>ToolbarConfiguration</key> |
12088 | | - <dict> |
12089 | | - <key>TB Display Mode</key> |
12090 | | - <integer>2</integer> |
12091 | | - <key>TB Icon Size Mode</key> |
12092 | | - <integer>1</integer> |
12093 | | - <key>TB Is Shown</key> |
12094 | | - <true/> |
12095 | | - <key>TB Size Mode</key> |
12096 | | - <integer>1</integer> |
12097 | | - </dict> |
12098 | | - <key>WindowClass</key> |
12099 | | - <string>PEWindow</string> |
12100 | | - <key>WindowState</key> |
12101 | | - <string>LKKeyWindow</string> |
12102 | | - <key>WindowStyleMask</key> |
12103 | | - <string>LKLargeMetricsMask NSClosableWindowMask NSMiniaturizableWindowMask NSResizableWindowMask NSTexturedBackgroundWindowMask NSTitledWindowMask</string> |
12104 | | - <key>releasedWhenClosed</key> |
12105 | | - <false/> |
12106 | | - </dict> |
12107 | | -</code></pre> |
12108 | 12052 | <p>Back when I first started working on FCPX Hacks, which later became CommandPost, I had a tool that allowed you to customise Final Cut Pro workspaces in a very similar fashion.</p> |
12109 | 12053 | <p><a href="https://alex4d.com">Alex Gollner (Alex4D)</a> was also messing around with these files about a decade ago.</p> |
12110 | 12054 | <p>However, what we discovered is that hacked or customised workspaces made Final Cut Pro pretty buggy and unstable, and we were generating lots of crash reports.</p> |
|
0 commit comments