diff --git a/docs/README.md b/docs/README.md index 7c6501c..1e416b1 100644 --- a/docs/README.md +++ b/docs/README.md @@ -2,50 +2,12 @@ # Transfer Toolbox -After very careful consideration, we've decided to **stop the development of Transfer Toolbox**. +Transfer Toolbox allows you to convert **Final Cut Pro 10.7 (for Mac) Libraries** into **Final Cut Pro 1.3 (for iPad) Projects**! -When Final Cut Pro for iPad was first introduced, we were very excited about the possibilities of being able to transfer jobs seamlessly between Mac & iPad. - -Because we use [Sync-N-Link](https://apps.apple.com/us/app/sync-n-link-x/id517599985?mt=12) for synchronising all our timecode-synced cameras and external audio recorders, our ideal workflow was to be able to prepare everything on Mac, and just send across a Library from Mac to iPad, so that creatives/directors could start doing selects/favouriting directly on the iPad. - -With the initial release of **Final Cut Pro 1.0 (for iPad)**, we were able to make this happen on the day of release - which was VERY exciting. - -Directors loved being able to do fast selects/favourites using their Apple Pencil on the road. It was magical. - -Our initial plan was to provide this tool on the Mac App Store (like our other tools such as [BRAW Toolbox](https://brawtoolbox.io), [Marker Toolbox](https://markertoolbox.io) & [Gyroflow Toolbox](https://gyroflowtoolbox.io)), however Apple rejected it because: - -> Due to differences in the file formats, attempting other unsupported and undocumented paths may lead to broken projects or other issues. - -Undeterred, we decided to release it for free on this website, via GitHub. +> [:icon-desktop-download: Download for **free** here...](/download/) ![](static/transfer-toolbox-about.png) -Before releasing on GitHub, we had **107 beta testers** on Apple's TestFlight, which provided really useful support and feedback. There was a lot of interest on social media. - -Transfer Toolbox has since been downloaded over **418 times** on GitHub. - -Transfer Toolbox continued to work with the release of **Final Cut Pro 10.6.6 (for Mac)** and **Final Cut Pro 1.1 (for iPad)**, and we got a lot of great feedback. - -It was pretty amazing being able to setup a project on Mac, and just AirDrop it across to iPad to continue working, then send it back to Mac. - -However, as Apple warned, as **Final Cut Pro (for Mac)** and **Final Cut Pro (for iPad)** were updated and improved, Transfer Toolbox stopped working. - -It became clear that the workaround that made Transfer Toolbox work, was no longer a possibility. - -As we dug deeper into how Final Cut Pro (for Mac) Libraries differ from Final Cut Pro (for iPad) Projects with each update - it became obvious that, the technologies between the two platforms is quite different, and ever evolving. - -Apple seems to have been able to almost "start from scratch" with the iPad, and build newer modern frameworks, to really push the boundaries of what you can do on Apple Silicon. - -Quite simply, Final Cut Pro (for iPad) uses different core technologies under the hood than Final Cut Pro (for Mac). - -So whilst we loved the ability to be able to seamlessly move from Mac to iPad in the early days of Final Cut Pro (for iPad), we now realise that only Apple can do this functionality properly. - -We would encourage you to [provide feedback to Apple](https://www.apple.com/feedback/finalcutpro/) if you found Transfer Toolbox useful. The more people that request this functionality, the more likely they will eventually implement. - -The Transfer Toolbox icon was designed by the amazing [Matthew Skiles](https://matthewskiles.com). Hopefully we can eventually use it for something else! - -Thank you to EVERYONE who downloaded and supported Transfer Toolbox! - -You can learn more about our other applications over at [FCP Cafe](https://fcp.cafe/latenite-technology/). +You can now easily get from your Desktop to your iPad! Simply drag your existing Final Cut Pro library into the application's drop zone. -Onwards & Upwards! \ No newline at end of file +You can learn how to use [here](/how-to-use/). \ No newline at end of file diff --git a/docs/README.yml b/docs/README.yml index 6028c14..d9dfa8c 100644 --- a/docs/README.yml +++ b/docs/README.yml @@ -1,4 +1,4 @@ -label: Discontinued -icon: alert +label: Introduction +icon: home order: 9999999 image: /static/thumbnail.jpg \ No newline at end of file diff --git a/docs/appcast.html b/docs/appcast.html index 33af7ff..557ab01 100644 --- a/docs/appcast.html +++ b/docs/appcast.html @@ -9,6 +9,15 @@
Transfer Toolbox - Convert Final Cut Pro Mac Libraries into iPad Projects
Transfer Toolbox - Convert Final Cut Pro Mac Libraries into iPad Projects
+

Transfer Toolbox 1.1.0 (4)

+ +

πŸ”¨ Improvements

+ + +

Transfer Toolbox 1.0.2 (3)

diff --git a/docs/appcast.xml b/docs/appcast.xml index 8ab4258..93324c0 100644 --- a/docs/appcast.xml +++ b/docs/appcast.xml @@ -2,6 +2,15 @@ Transfer Toolbox + + 1.1.0 + https://transfertoolbox.io/appcast.html + Sun, 03 Dec 2023 15:00:52 +1100 + 4 + 1.1.0 + 12.6 + + 1.0.2 https://transfertoolbox.io/appcast.html diff --git a/docs/credits.md b/docs/credits.md new file mode 100644 index 0000000..57f3f1c --- /dev/null +++ b/docs/credits.md @@ -0,0 +1,93 @@ +# Credits + +Transfer Toolbox has been thrown together by [Chris Hocking](https://github.com/latenitefilms) at [LateNite Films](https://latenitefilms.com). + +The Transfer Toolbox icon was designed by [Matthew Skiles](https://matthewskiles.com){target="_blank"}. + +The Goblins featured in the icon are from LateNite's [Goblin Spoon](https://latenitefilms.com/originals/goblin-spoon/){target="_blank"} series, created by [Nicholas Issell](https://www.imdb.com/name/nm6395828/){target="_blank"}. + +Special thanks to [David Peterson](https://github.com/randomeizer)! + +Chris also created [CommandPost](https://commandpost.io), [BRAW Toolbox](https://brawtoolbox.io), [Marker Toolbox](https://markertoolbox.io) and [Gyroflow Toolbox](https://gyroflowtoolbox.io). + +--- + +## Sparkle + +Transfer Toolbox uses [**Sparkle**](https://sparkle-project.org){target="_blank"} for software updates. + +Copyright (c) 2006-2013 Andy Matuschak. +Copyright (c) 2009-2013 Elgato Systems GmbH. +Copyright (c) 2011-2014 Kornel LesiΕ„ski. +Copyright (c) 2015-2017 Mayur Pawashe. +Copyright (c) 2014 C.W. Betts. +Copyright (c) 2014 Petroules Corporation. +Copyright (c) 2014 Big Nerd Ranch. +All rights reserved. + +Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + +--- + +### External Licenses + +#### [bspatch.c and bsdiff.c, from bsdiff 4.3](http://www.daemonology.net/bsdiff/){target="_blank"} + +Copyright 2003-2005 Colin Percival +All rights reserved + +Redistribution and use in source and binary forms, with or without modification, are permitted providing that the following conditions are met: + +1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. +2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. + +THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +--- + +#### [sais.c and sais.c, from sais-lite (2010/08/07)](https://sites.google.com/site/yuta256/sais){target="_blank"} + +The sais-lite copyright is as follows: + +Copyright (c) 2008-2010 Yuta Mori All Rights Reserved. + +Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + +--- + +#### Portable C implementation of Ed25519, from https://github.com/orlp/ed25519 + +Copyright (c) 2015 Orson Peters + +This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. + +Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: + +1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. + +2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. + +3. This notice may not be removed or altered from any source distribution. + +--- + +#### SUSignatureVerifier.m + +Copyright (c) 2011 Mark Hamlin. + +All rights reserved. + +Redistribution and use in source and binary forms, with or without modification, are permitted providing that the following conditions are met: + +1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. +2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. + +THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. diff --git a/docs/credits.yml b/docs/credits.yml new file mode 100644 index 0000000..0f55901 --- /dev/null +++ b/docs/credits.yml @@ -0,0 +1,4 @@ +label: Credits +icon: people +order: 4000 +image: /static/thumbnail.jpg \ No newline at end of file diff --git a/docs/download.md b/docs/download.md new file mode 100644 index 0000000..541089a --- /dev/null +++ b/docs/download.md @@ -0,0 +1,15 @@ +# Download + +!!!success +Massive thanks to the **107 beta testers** on Apple's TestFlight for all their support and positive feedback! +!!! + +You can download **Transfer Toolbox v1.1.0** for free [here](https://github.com/latenitefilms/TransferToolbox/releases/download/1.1.0/Transfer-Toolbox-1-1-0.zip). + +Please make sure you [read the manual](/how-to-use/), and review the [System Requirements](/system-requirements/) before downloading. + +!!!primary +If you find Transfer Toolbox useful, consider [buying us a coffee](https://www.buymeacoffee.com/latenitefilms){target="_blank"} or [sponsoring CommandPost](https://commandpost.io/sponsor/){target="_blank"}. + + +!!! \ No newline at end of file diff --git a/docs/download.yml b/docs/download.yml new file mode 100644 index 0000000..58d1ad4 --- /dev/null +++ b/docs/download.yml @@ -0,0 +1,4 @@ +label: Download +icon: desktop-download +order: 9000 +image: /static/thumbnail.jpg \ No newline at end of file diff --git a/docs/how-to-use.md b/docs/how-to-use.md new file mode 100644 index 0000000..92f9f5c --- /dev/null +++ b/docs/how-to-use.md @@ -0,0 +1,256 @@ +# How To Use + +--- + +!!!danger Important +Final Cut Pro for iPad is obviously very new, so there are a bunch of **known issues and limitations**.
+Please read this **entire page** carefully, and do **workflow tests** before using on a proper job.
+We've been using Transfer Toolbox at [LateNite](https://latenitefilms.com){target="_blank"} since it's release, and it's been awesome - but **use at your own risk**. +!!! + +--- + +## Introduction + +Your **Final Cut Pro (for Mac) Library** should contain a **single Event** with the following naming convention: + +> **Default MM-DD-YY** + +For example: + +> **Default 05-31-23** + +You can handle multiple projects in that single Event, but their start timecode should all be **00:00:00:00**. + +Then, simply drag-and-drop your **Final Cut Pro (for Mac) library** onto the Library icon drop zone, or click the **Convert Library** button to manually select a **Final Cut Pro (for Mac) library**: + +![](static/transfer-toolbox.png) + +If you drag in a **Final Cut Pro (for Mac) Library** with multiple Events, you'll be presented with this warning: + +![](static/multiple-events.png) + +If you drag in a **Final Cut Pro (for Mac) Library** with the wrong Event naming convention, you'll be presented with this warning: + +![](static/invalid-event-name.png) + +If you've dragged in a valid **Final Cut Pro (for Mac) Library**, or you clicked **OK** to either of the above warnings, you will be presented with a Open Panel to **Grant Access** to that Library: + +![](static/grant-access.png) + +After clicking **Grant Access**, you'll be presented with a success message: + +![](static/victory.png) + +You'll now find a `.fcpproj` file in the same folder as your `.fcpbundle`: + +![](static/result-files.png) + +You can now use [Airdrop](https://support.apple.com/en-au/HT203106#:~:text=Select%20AirDrop%20in%20the%20sidebar,recipient%20shown%20in%20the%20window.){target="_blank"}, [iCloud Drive](https://support.apple.com/en-au/guide/mac-help/mchle5a61431/mac){target="_blank"} or other means (such as putting on an external hard drive) to move the project from your Mac to your iPad. + +You can now continue editing on **Final Cut Pro (for iPad)**! + +However, it's **very important** that you read the rest of the **Limitations & Known Issues** below, so that you're aware of things that don't translate properly between Mac and iPad. + +--- + +!!!primary +If you find Transfer Toolbox useful, consider [buying us a coffee](https://www.buymeacoffee.com/latenitefilms){target="_blank"} or [sponsoring CommandPost](https://commandpost.io/sponsor/){target="_blank"}. + + +!!! + +--- + +## Video Tutorial + +Serge M has done an awesome video explaining how Transfer Toolbox works on YouTube: + +[![](/static/serge-youtube.jpg)](https://www.youtube.com/watch?v=DZdyb2YCRNQ){target="_blank"} + +--- + +## Limitations & Known Issues + +Some very important things to keep in mind: + +- Transfer Toolbox requires **Final Cut Pro 10.7** and **Final Cut Pro 1.3 (for iPad)**. +- You should ensure your library only has a **single event** with the following naming convention: **Default MM-DD-YY** (i.e **Default 05-31-23**). +- Transfer Toolbox will warn you if it detects more than one event, or if you don't use the above event naming convention, but it still allows you to proceed. +- If you use a different event name, you may not see anything in your browser on the iPad. +- All project timecode should start at **00:00:00:00**. I **assume** this is because there's currently no way in Final Cut Pro (for iPad) to customise the start timecode of a timeline. +- All Motion Content and Media should be contained within the Library (i.e. set the Motion Content Storage Location to **In Library** in the Library Inspector on your Mac). +- Your Final Cut Pro (for Mac) timeline/project cannot have any **Stabilisation or Rolling Shutter** effects enabled. If you do, the iPad will just say **Import Failed**. +- Not all Motion Templates will display correctly on the iPad. For example, some Titles using the **Match Move Behaviour** don't appear correctly on Final Cut Pro (for iPad) - the positions are all wrong. +- **FxPlug4** effects (such as [BRAW Toolbox](https://brawtoolbox.io){target="_blank"}) will not work at all on the iPad. Whilst Final Cut Pro (for iPad) does seem to have FxPlug4 Frameworks, there's currently no mechanism for third party to add FxPlug4 to iPad. +- Final Cut Pro (for iPad) will always **ignore proxy files** - it will always use the Original high-quality media files. +- **Soundtracks** will come across from iPad to Mac. However, they're not "normal" audio clips, and won't appear if you export a FCPXML. This bug has been [reported to Apple](https://github.com/CommandPost/FCPCafe/issues/94){target="_blank"}. +- Some users have reported that when you AirDrop from Mac to iPad, it can take a few minutes for the project to appear in Final Cut Pro for iPad. We haven't been able to reproduce this on a 12.9inch iPad Pro, so it may be hardware dependant. Basically... be patient if using "older" devices. +- **Compound Clips** will come across correctly, however you cannot modify them in Final Cut Pro for iPad. +- **Multicam Clips** with more than 4 angles will come across correctly, however you still only have access to the first 4 angles in Final Cut Pro for iPad. +- The **Flow** transition does work correctly between Mac and iPad, however, interestingly, the rendering results can be visually different between platforms. Mac seems better quality than iPad. + +If you find any other issues or limitations, [please let us know](https://transfertoolbox.io/support/). + +--- + +## Custom Fonts + +!!!success Update! +Custom Fonts now appear correctly in **Final Cut Pro (for iPad) v1.1** user interface. Thanks Apple! +!!! + +Whilst it's possible to install Custom Fonts on your iPad using an app such as [Fontcase](https://apps.apple.com/au/app/fontcase-manage-your-type/id1205074470){target="_blank"}, and these fonts will appear in apps such as Pages and Numbers, they do **not** appear in the Final Cut Pro (for iPad) Inspector. + +You can also install fonts via apps that contain fonts, [via the App Store](https://support.apple.com/en-au/guide/ipad/ipad952422ba/ipados){target="_blank"}, however, these also do **not** appear in the Final Cut Pro (for iPad) Inspector. + +**Final Cut Pro (for iPad) only lists a very strict set of built-in fonts in the Inspector.** + +We have submitted a feature request to Apple, as [explained on FCP Cafe](https://github.com/CommandPost/FCPCafe/issues/200){target="_blank"}. + +**However**, if you use the same Custom Font within a Motion Template on Mac, it **will** work on iPad. + +For example, the [BBC](https://www.bbc.co.uk){target="_blank"} uses Final Cut Pro for a lot of their programs, so here's the familiar [BBC Reith](https://www.bbc.co.uk/branding/reith-font/){target="_blank"} font in Final Cut Pro for iPad: + +![](../static/bbc-font.jpeg) + +!!!warning Please Note: +You may only use BBC Reith if you have an agreement or other authorisation to collaborate with the BBC or BBC Studios. This may be as a broadcasting partner or co-production partner, event promoter, or as a customer of BBC Studios. +!!! + +However, even though the above screenshot shows the [BBC Reith](https://www.bbc.co.uk/branding/reith-font/){target="_blank"} font in the Inspector, it **won't** appear if you add another Title within Final Cut Pro (for iPad). + +You can edit the text though, as normal. Just keep in mind if you change the font to something else, you **can't** change it back. + +--- + +## Danger using External Drives on iPad + +The fact that you can just plug in an external drive into an iPad Pro via USB-C is awesome and amazing! + +However, for whatever strange reason, Apple decided not to include an **Eject** button in the **Files** app. + +We've now seen cases where if you "pull the plug" on an [macOS Extended or HFS+](https://en.wikipedia.org/wiki/HFS_Plus){target="_blank"} formatted external drive, whilst the iPad is still working on it, it can corrupt the the HFS+ partition. + +We haven't seen it happen first hand yet, however we suspect the same issue would happen on [APFS](https://en.wikipedia.org/wiki/Apple_File_System){target="_blank"} formatted drives. + +Once corrupted, the drive no longer appears on iPad. + +What's **worse** is that once the external drive is corrupt, as soon as you plug it into an Apple Silicon or Intel Mac, it will just crash the system straight away. An instant and fatal kernel panic. + +The only way we've been able to fix the corrupt drives is to use a Windows PC, and use [HFS+ for Windows by Paragon Software](https://www.paragon-software.com/home/hfs-windows/){target="_blank"} to mount and repair the drive. + +Once repaired on Windows, it works fine again on macOS and iPad. + +Given this, it's our **strong recommendation** that if you're using an external drives on iPad, that before you "pull the plug" you "force quit" all applications or better yet, [shutdown the iPad](https://support.apple.com/en-au/guide/ipad/ipad63d30b5a/ipados){target="_blank"} whenever ejecting drives. + +You can force quit application on the iPad, by tapping the bottom of the screen and dragging up to the middle, then stopping. This opens the **App Switcher**. You can then swipe up on an app to force quit it. + +If you're external drive has an LED status light, that's another good way to determine if the iPad is still doing "stuff" with it. + +--- + +## Storing Media on iCloud + +It is possible to store your media on iCloud Drive and effectively "share it" between your Mac and your iPad. + +When you import media into Final Cut Pro for iPad it will **always** copy to the library. + +However, because iPad's use [Apple File System (APFS)](https://support.apple.com/en-au/guide/disk-utility/dsku19ed921c/mac){target="_blank"} for their internal storage, even thought it's **copying** the files from the iCloud drive cache to the Final Cut Pro library, it doesn't actually take up any more "physical" drive space. + +When you duplicate a file in APFS, rather than immediately making a complete second copy of the file, the file system essentially just creates a new reference, or pointer, to the existing data. This means that, the duplicate file doesn't take up any extra space because it's just pointing to the same underlying data as the original file. + +When sending your project from Final Cut Pro on iPad back to your Mac, just export with the **Include All Media** option disabled, and then manually relink to your iCloud Drive files within Final Cut Pro on Mac. + +--- + +## Storing Media Externally + +!!!danger Important +Unfortunately, whilst this worked on **Final Cut Pro v1.0.0**, Apple has removed support for this workflow in **Final Cut Pro v1.0.1**.
+
+We are still testing and exploring other possibilities and workarounds for "linking to" external media. +!!! + +Interestingly, it is actually possible to "link" to media on an external hard drive. + +However, even though Final Cut Pro (for iPad) will "link" to the external drive initially, and when you first start editing, you'll be editing off the external drive - in the background, Final Cut Pro will start copying everything across to the internal drive. + +As far as we can tell, there's currently no way to stop Final Cut Pro from importing the footage to your iPad's internal drive. + +This works slightly differently to DaVinci Resolve (for iPad) and LumaFusion, which both support "linking" to external drives without having a local/internal copy. + +With that in mind, if you still want to "link" to your media initially, you'll need to create the Final Cut Pro library on macOS, and make sure you keep the media **external** to the library. + +As long as both the generated Final Cut Pro (for iPad) project and media are on the same external hard drive, in the same location as they were on the Mac, everything will work. + +The reason for this is that internally Final Cut Pro (for Mac) created document-scope security-scoped bookmarks to each media file, which Final Cut Pro (for iPad) can also use to get access to the files, even in a sandboxed environment. + +After creating a new Final Cut Pro (for iPad) project using Transfer Toolbox, you may need to open the library back up on the Mac, to update all the bookmarks. + +Simply right-click on the new Final Cut Pro (for iPad) project in Finder and select **Show Package Contents**. + +![_Screenshot of Finder_](static/show-package-contents.png) + +Within the package contents, two folders deep, you'll find the Final Cut Pro (for Mac) library that you can now open on your Mac. + +![_Screenshot of Finder_](static/inside-project.png) + +Once you open it, and allow Background Tasks to complete, you can then close it, as the document-scope security-scoped bookmarks should now be updated. + +We will investigate automating this process in a future update. + +You can then import Final Cut Pro (for iPad) libraries via the home screen: + +![_Screenshot of Final Cut Pro (for iPad)_](static/import-ipad.jpeg) + +Just select the project on your external drive: + +![_Screenshot of Final Cut Pro (for iPad)_](static/external-ssd.jpeg) + +--- + +## Supported Media + +Below is a list of Supported Media in Final Cut Pro for iPad: + +### Video Formats + +- Apple ProRes +- Apple ProRes RAW and Apple ProRes RAW HQ +- H.264 +- HEVC +- MXF (Apple ProRes) + +### Audio Formats + +- AAC +- AIFF +- BWF +- CAF +- MP3 +- MP4 +- WAV + +### Stills Formats + +- Apple ProRAW +- BMP +- GIF +- HEIF +- JPEG +- PNG +- PSD +- RAW +- TGA +- TIFF + +You can also find this information on [Apple's website](https://support.apple.com/en-au/guide/final-cut-pro-ipad/dev3f1bb94c2/ipados){target="_blank"}. + +--- + +## Camera Formats + +Final Cut Pro for iPad supports a wide range of third-party digital video and still cameras. + +You can see the full list on [Apple's website](https://support.apple.com/en-au/HT213668){target="_blank"}. \ No newline at end of file diff --git a/docs/how-to-use.yml b/docs/how-to-use.yml new file mode 100644 index 0000000..f1c17ff --- /dev/null +++ b/docs/how-to-use.yml @@ -0,0 +1,4 @@ +label: How To Use +icon: flame +order: 7900 +image: /static/thumbnail.jpg \ No newline at end of file diff --git a/docs/latenite-technology.md b/docs/latenite-technology.md new file mode 100644 index 0000000..10dc32c --- /dev/null +++ b/docs/latenite-technology.md @@ -0,0 +1,7 @@ +# Explore LateNite's Tools + +This website has been thrown together by [Chris Hocking](https://twitter.com/chrisatlatenite) at [LateNite](https://latenitefilms.com/technology). + +Constantly looking for ways to innovate, LateNite is as passionate about production and post production as it is storytelling. Their pursuit of creative excellence has seen them work closely with global cinematic technology companies to craft post workflow solutions and critically celebrated software in-house. + +You can learn more about LateNite's tools such as CommandPost, BRAW Toolbox, Gyroflow Toolbox, Marker Toolbox, Recall Toolbox and Fast Collections over at [FCP Cafe](https://fcp.cafe). \ No newline at end of file diff --git a/docs/latenite-technology.yml b/docs/latenite-technology.yml new file mode 100644 index 0000000..ab45b11 --- /dev/null +++ b/docs/latenite-technology.yml @@ -0,0 +1,4 @@ +label: Explore LateNite's Tools! +icon: zap +order: 8900 +image: /static/thumbnail.jpg \ No newline at end of file diff --git a/docs/privacy.md b/docs/privacy.md new file mode 100644 index 0000000..0fc8569 --- /dev/null +++ b/docs/privacy.md @@ -0,0 +1,19 @@ +# Privacy Policy + +This is the privacy policy for the Transfer Toolbox, macOS Application that is available on TestFlight and for free via GitHub. + +Transfer Toolbox does not collect any user data. No personal information is transmitted, stored, or used by this application. + +Transfer Toolbox does not use any third-party analytics or tracking tools. It does not contain any in-app purchases or advertisements. + +Transfer Toolbox does not communicate with any external servers or services, and it does not access any data on your device beyond what is necessary for the application to function properly. + +Apple may collect and use certain usage and performance data from the apps that are available on TestFlight. This data is used to help improve the App Store and the overall user experience. + +This data collection is not specific to any individual user, and it is not possible for app developers to opt out of this data collection by Apple. + +You can read Apple's App Store Privacy Policy [here](https://www.apple.com/legal/privacy/data/en/app-store/). + +We use this GitHub Repository for documentation hosting and technical support. You can read GitHub's Privacy Policy [here](https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement). + +If you have any questions or concerns, you can [submit an issue](https://github.com/latenitefilms/transfertoolbox/issues), or email us: support@latenitefilms.com \ No newline at end of file diff --git a/docs/privacy.yml b/docs/privacy.yml new file mode 100644 index 0000000..c7af074 --- /dev/null +++ b/docs/privacy.yml @@ -0,0 +1,4 @@ +label: Privacy Policy +icon: info +order: 2 +image: /static/thumbnail.jpg \ No newline at end of file diff --git a/docs/release-notes.md b/docs/release-notes.md new file mode 100644 index 0000000..35e25cb --- /dev/null +++ b/docs/release-notes.md @@ -0,0 +1,40 @@ +# Release Notes + +### 1.1.0 + +**πŸŽ‰ Released:** +- 3rd December 2023 + +**πŸ”¨ Improvements:** +- Transfer Toolbox is now compatible with Final Cut Pro 10.7 and Final Cut Pro 1.3 (for iPad). +- Updated Sparkle from v2.4.1 to v2.5.1. + +--- + +### 1.0.2 + +**πŸŽ‰ Released:** +- 18th June 2023 + +**πŸ“ Changes:** +- Transfer Toolbox will no longer be distributed on the Apple App Store or TestFlight, and instead will be a free download. + +--- + +### 1.0.1 + +**πŸŽ‰ Released:** +- 26th May 2023 + +**πŸ“ Changes:** +- Changed the App Store Subtitle. + +--- + +### 1.0.0 + +**πŸŽ‰ Released:** +- 26th May 2023 + +**Woohoo! πŸŽ‰** +- This is the first release of Transfer Toolbox on Apple's TestFlight. \ No newline at end of file diff --git a/docs/release-notes.yml b/docs/release-notes.yml new file mode 100644 index 0000000..05c3924 --- /dev/null +++ b/docs/release-notes.yml @@ -0,0 +1,4 @@ +label: Release Notes +icon: versions +order: 5000 +image: /static/thumbnail.jpg \ No newline at end of file diff --git a/docs/retype.yml b/docs/retype.yml index 5482eb9..0611b04 100644 --- a/docs/retype.yml +++ b/docs/retype.yml @@ -9,6 +9,20 @@ branding: links: +- text: Download + link: /download/ + icon: desktop-download + +- text: Issues + link: https://github.com/latenitefilms/transfertoolbox/issues + icon: issue-opened + target: blank + +- text: Discussions + link: https://github.com/latenitefilms/transfertoolbox/discussions + icon: comment-discussion + target: blank + - text: FCP Cafe link: https://fcp.cafe icon: flame @@ -20,7 +34,7 @@ links: target: blank - text: LateNite - link: https://latenitefilms.com/technology/ + link: /latenite-technology/ icon: light-bulb footer: diff --git a/docs/support.md b/docs/support.md new file mode 100644 index 0000000..0af3d73 --- /dev/null +++ b/docs/support.md @@ -0,0 +1,11 @@ +# Support + +If you run into any bugs, crashes, or you have a feature request, you can post an issue [here](https://github.com/latenitefilms/transfertoolbox/issues). + +If you have any general questions or feedback, you can discuss [here](https://github.com/latenitefilms/transfertoolbox/discussions). + +GitHub registration is free, and this GitHub repository is actively monitored by [LateNite Films](https://github.com/latenitefilms). + +You can also email us: [support@latenitefilms.com](mailto:support@latenitefilms.com?subject=Transfer%20Toolbox%20Support) + +We're based in **Melbourne, Australia** - you can check the timezone [here](https://www.timeanddate.com/worldclock/australia/melbourne). \ No newline at end of file diff --git a/docs/support.yml b/docs/support.yml new file mode 100644 index 0000000..76356a7 --- /dev/null +++ b/docs/support.yml @@ -0,0 +1,4 @@ +label: Support +icon: bug +order: 7500 +image: /static/thumbnail.jpg \ No newline at end of file diff --git a/docs/system-requirements.md b/docs/system-requirements.md new file mode 100644 index 0000000..c0fe1d0 --- /dev/null +++ b/docs/system-requirements.md @@ -0,0 +1,5 @@ +# System Requirements + +Transfer Toolbox requires **Final Cut Pro 10.7** and **Final Cut Pro 1.3 (for iPad)**. + +You can find Final Cut Pro's system requirements [here](https://www.apple.com/au/final-cut-pro/specs/). \ No newline at end of file diff --git a/docs/system-requirements.yml b/docs/system-requirements.yml new file mode 100644 index 0000000..86d95e1 --- /dev/null +++ b/docs/system-requirements.yml @@ -0,0 +1,4 @@ +label: System Requirements +icon: gear +order: 8998 +image: /static/thumbnail.jpg \ No newline at end of file diff --git a/docs/uninstall.md b/docs/uninstall.md new file mode 100644 index 0000000..39f7802 --- /dev/null +++ b/docs/uninstall.md @@ -0,0 +1,3 @@ +# Uninstall + +To uninstall Transfer Toolbox, simply drag the application to the trash/bin. \ No newline at end of file diff --git a/docs/uninstall.yml b/docs/uninstall.yml new file mode 100644 index 0000000..ca44d16 --- /dev/null +++ b/docs/uninstall.yml @@ -0,0 +1,4 @@ +label: Uninstall +icon: trash +order: 4900 +image: /static/thumbnail.jpg \ No newline at end of file diff --git a/docs/workflow.md b/docs/workflow.md new file mode 100644 index 0000000..55f0703 --- /dev/null +++ b/docs/workflow.md @@ -0,0 +1,27 @@ +# Workflow + +Why exactly would you want to move from a Mac to an iPad for Final Cut Pro? + +This page offers some workflow ideas and suggestions. + +--- + +### Dailies + +Final Cut Pro for iPad is perfect for reviewing and doing selects on dailies for all levels of projects, from short films to Hollywood Feature Films. + +When working in the advertising world, and especially in the corporate advertising world, a lot of agency staff don't have Mac laptops, but own an iPad. + +Whilst it's possible to use something like [Frame.io Camera to Cloud](https://frame.io/c2c){target="_blank"} to share proxies straight from camera to your iPad, because of the way it works, the audio channels might be incorrect, which makes relinking a challenge on the Mac end. + +The best option is to get an assistant editor to sync (using something like Sync-N-Link), and organise everything on the Mac. + +Once everything is ready to go on the Mac, you can use **Transfer Toolbox** to convert your Final Cut Pro for Mac library into a self-contained Final Cut Pro for iPad project. + +You can then send the project to clients/agency/director/mother via email, AirDrop, [PostLab](https://hedge.video/postlab/){target="_blank"}, iCloud Drive, Dropbox, [Digital Pigeon](https://digitalpigeon.com){target="_blank"}, Frame.io, etc. + +They can do their selects on the iPad, and once done, then the project back (without media), where the assistant can then open up on Final Cut Pro 10.7 and consolidate with the master library. + +Because of it's touch interface and Apple Pencil support, the iPad is the perfect rushes review platform - as it's fast and fun. + +Directors can also experiment with edits on Final Cut Pro for iPad - and everything will transfer perfectly back to the Mac. \ No newline at end of file diff --git a/docs/workflow.yml b/docs/workflow.yml new file mode 100644 index 0000000..f29fff0 --- /dev/null +++ b/docs/workflow.yml @@ -0,0 +1,4 @@ +label: Workflows +icon: device-camera-video +order: 7899 +image: /static/thumbnail.jpg \ No newline at end of file