By splitting tasks and processes between devices and operating systems, the creative process could become completely free of the hurdles so many of us have to clear during editing sessions. Sounds exciting, right?įor Final Cut Pro, this could result in the ability for the iPad to do some of the heavy lifting in terms of background rendering, or exporting, while the Mac gets down to the creative stuff (or vice-versa). Just imagine a unified architecture, married by Apple silicon and Apple’s ecosystem (which already enables such wonderful features like Universal Control and Handoff). I have my podcast co-host, Rob, to thank for this.Įver since the M1 was placed into an iPad Pro, he’s painted a picture of a future where the Mac and iPad can share their resources. Enough is enough – there has been too much chest-beating, marketing waffle, and Intel bullying what can that thing do when really put to the task?įinal Cut Pro is capable of really hitting Macs hard, and it needs to do the same on the iPad if it’s to be the truly brilliant mobile video editing rig it’s capable of becoming. I want to see the M1 chip sing on the iPads into which it has been inserted. I can’t stress this enough, so I’m going to give it a separate heading and ramble on about it again. That process needs to be completely seamless, and I can’t fathom how it’s going to work with the current state of Final Cut Pro libraries. I don’t really care how they do it, but I deeply love the idea of being able to start an edit on my MacBook Pro and then grab the iPad Pro so I can finish it at a coffee shop before my gym session. Clearly, Apple is going to have to either redesign the way in which libraries are created and maintained – or rely on some form of proxy-based file sync on iCloud. This ain’t gonna work in a cloud environment, obviously. You can easily send a library file into the terabytes for a 4K project if you dare explore beyond 30 minutes of footage. A total seamless method for syncing librariesįinal Cut Pro is dreadfully inefficient when it comes to its libraries. If the iPad version of Final Cut is feature deficient, it is a non-starter. This is Apple’s chance to give us a professional app that would enable video editors like myself to switch seamlessly from the Mac to a platform with touchscreen support and true take-it-to-the-coffee-shop portability. Until Apple does something meaningful with both iPadOS and its professional apps, the M1 in the iPad Air and iPad Pro is an utter waste of time. I’ve made my feelings about the presence of the M1 chip in the iPad clear. Otherwise, it’s of absolutely no use to me (or, I’d guess, most other pros). I want a full fat, unfiltered, pedal-to-the-metal version of Final Cut Pro on the iPad. If Apple really is going to strip the iPadOS version of its video editing suite of features it only deems appropriate for the Mac, they might as well stop now. The reference to Final Cut’s ‘Pro’ moniker in Bu’s tweet bothers me. Avoid the temptation to water down the feature set Regardless, if Apple is working on a version of Final Cut for the iPad, I’m both excited and nervous. I also have no idea who Majin Bu is, and consequently how useful this rumour is. #Apple /w7XF4acs1P- Majin Bu March 18, 2022 I believe it is an interface to manage projects saved on iCloud. I don't know anything else at the moment. I know it's not on par with the Pro (it doesn't manage plugins locally) and there is no upcoming launch. Apple is working on a version of Final Cut for the iPad.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |