# ShuttlePRO V2 Compatibility with Final Cut Pro and iPad Pro **URL:** \ **Category:** PRO v2/Xpress\ **Created:** [September 15, 2026, 10:31am UTC](https://care.contourdesign.com/t/shuttlepro-v2-compatibility-with-final-cut-pro-and-ipad-pro/229 "2026-09-15T10:31:50Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![MarcosPalau](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@MarcosPalau](https://care.contourdesign.com/u/MarcosPalau)\ **Post date:** [September 15, 2026, 10:31am UTC](https://care.contourdesign.com/t/shuttlepro-v2-compatibility-with-final-cut-pro-and-ipad-pro/229/1 "2026-09-15T10:31:50Z")
Dear Contour Support Team, First of all, I would like to thank you for creating such a fantastic device. I have been using the ShuttlePRO v2 for a long time, and it has become an essential part of my editing workflow. It works wonderfully with my Mac, and has made working in Final Cut Pro much faster and more comfortable. However, since the introduction of Apple Creator Studio, I have encountered an issue with Final Cut Pro. The ShuttlePRO v2 no longer seems to correctly detect when I am working in Final Cut Pro. Instead, it appears to use the All Applications profile. The only workaround I have found is to assign my Final Cut Pro keyboard shortcuts directly to the All Applications profile. This allows me to use the ShuttlePRO v2 while editing, but it creates another problem. When I switch to Finder or another application, those same buttons are still configured with my Final Cut Pro shortcuts, which causes conflicts and makes the controller much less practical. I am not sure whether I am doing something incorrectly, whether this is a known compatibility issue related to Apple Creator Studio, or whether the Shuttle software still needs an update to properly recognize Final Cut Pro in this new environment. Could you please let me know if there is currently a solution or workaround for this, or if an update is planned? I would also like to mention that I use Final Cut Pro on my iPad Pro through my Apple Creator Studio subscription. However, as far as I understand, the ShuttlePRO v2 is not compatible with iPadOS. This is actually one of the main reasons why I rarely use Final Cut on the iPad. The ShuttlePRO v2 has become such an important part of the way I edit that working without it feels considerably less efficient. I would therefore like to ask whether iPadOS compatibility for the ShuttlePRO v2 is something you are considering for the future, or if perhaps there is already a way to use the ShuttlePRO v2 with Final Cut Pro on an iPad Pro that I am not aware of. Thank you very much for your help, and again, congratulations on creating such a useful product. After using the ShuttlePRO v2 for so long, it is hard for me to imagine editing without it. Kind regards, Marcos Palau. ---
**Author:** ![ContourCare](https://yyz2.discourse-cdn.com/flex004/user_avatar/care.contourdesign.com/contourcare/32/39_2.png) [@ContourCare](https://care.contourdesign.com/u/ContourCare)\ **Post date:** [September 16, 2026, 9:26am UTC](https://care.contourdesign.com/t/shuttlepro-v2-compatibility-with-final-cut-pro-and-ipad-pro/229/2 "2026-09-16T09:26:14Z")
Hi MarcosPalau, Thank you for reaching out to us. It sounds like the update to Final Cut Pro has been updated with a new program name. This results in the existing profile no longer pointing to the correct program path. This can be fixed in two different ways. 1. You will need to create a new profile from scratch, that points to the newly updated program, that appears to have a new name. 2. Alternatively, you can go to the folder directory, and find the Contour folder. Inside the folder you can find the “Multimedia Controller” folder, which has a file called Contour\_Default\_Backup.json. This file can be opened in a text editor, and you can here edit the existing path of Final Cut Pro, to point at the new profile. This should solve the issue directly, but will also prevent you from using older versions of Final Cut Pro if you ever choose to do so. You will also have to manually update this path if this should happen again. This should fix the issue of the applcation not seeing the correct version of the program. In regards to your question about IpadOS - we are not planning to support this platform, and will, as it stands right now, only support MacOS. I hope this helps, and that you have a great day.