FCPX Text Message Not Working…for me.

Home Forums Final Cut Pro X FCPX Text Message Not Working…for me.

Tagged: ,

This topic contains 4 replies, has 2 voices, and was last updated by  Benjamin Brodbeck 5 years, 3 months ago. This post has been viewed 753 times

  • Author
    Posts
  • #1150
    +1

    Benjamin Brodbeck
    Participant
    3p
      • Topics: 1
      • Replies: 2
      • Total Posts: 3

    I have compiled the FCPX Text Message app in AppleScript editor per the instructions in your article. If I run the app within Apple Script editor, I do indeed get a text message on my iPhone. The issue I run into is in FCPX. When I choose the FCPX-Text.app from the “Open With” drop down the file exports successfully and I do not get a text message. Any ideas of what I may be doing wrong?

  • #1151

    Jasper Thayer
    Keymaster
    2p
    • Hollywood, CA
      • Topics: 9
      • Replies: 32
      • Total Posts: 41

    Heya Benjamin,

    Thanks for visiting the forum! For others that may be reading this topic Benjamin is referring to the tutorial on how to receive a text message when FCPX finishes exporting.

    It seems as though you’re doing everything correctly. I am thinking it’s a problem with the recent OS version because even after exporting I can not “Open With” the FCXP-Text.app although I could do it in earlier versions.

    I seen that you’re an Apple Technical Coordinator so I figure you know what you’re doing per the instructions and it appears as though you’re saving the script as an Application from AppleScript.

    I just tried to get it to work in FCPX 10.1.2 and I couldn’t get it to work either, although it worked in previous versions. If I double click the FCPX-Text.app application or right-click the app and “open” it then it will send a message, so opening the app will send the message. It seems as though the current issue is that OSX is not allowing a Quicktime movie file to “Open With” the AppleScript application.

    I thought perhaps it’s because the FCPX-Text.app application is not a “recommended” app… for instance if you right-click a shared Quicktime movie file and try to “Open With” the FCPX-Text.app application then it initially won’t allow you to select it (the app is greyed out) because it’s not a recommended app. You’d have to choose to enable all applications in order to choose to open a Quicktime movie with the AppleScript application that was created. Even when you do that it still doesn’t “open” the app (and send a text message). So I thought it might be a “recommended” app issue with the most recent OSX version. So then I tried to “Open With” Motion, which is greyed out and not a “recommended” app. When I tried that it at least attempted to open Motion so I don’t think it’s an issue with the app being a “recommended” app or not. Honestly… I do not know WTF the problem is now.

    I don’t think it’s a FCPX issue though. I think it’s a recent OSX issue. I’ll be investigating the issue further on my backup machines that have previous versions of FCPX and OSX so that I can try to pinpoint what software update is causing the problem.

    If you hear of anything else regarding the issue please keep me updated through this forum topic.

    UPDATE: I discovered a workaround that seems to work for the issue. Open Automator.app and create an application. Add the Utilities action named “Launch Application” to your untitled Automator application. From the “Launch Application” action settings select the FCPX-Text.app application and then save the Automator application and name it something like FCPX-Text-Workaround.app or something. Then from the FCPX Share settings choose to “Open With” FCPX-Text-Workaround.app, which will then open FCPX-Text.app and send the text message.

    Hope that helps!

    Jasper Thayer
    Apple Certified Trainer
    https://FinalCutProX.net

  • #1152
    +1

    Benjamin Brodbeck
    Participant
    3p
      • Topics: 1
      • Replies: 2
      • Total Posts: 3

    Well Hot Dog! It works now! Thanks for the snappy research and response! I didn’t have time to super sleuth this problem myself tonight so this is really cool that you found a workaround!

    Thank You!

    Ben Brodbeck

    • #1153

      Jasper Thayer
      Keymaster
      2p
      • Hollywood, CA
        • Topics: 9
        • Replies: 32
        • Total Posts: 41

      Heya sure thang! I really wanted this to work so I’m glad I found a workaround too.

      It’s funny because I actually wrote about that workaround in the last paragraph of the tutorial. I just re-read the original tutorial and figured out the workaround by reading the last paragraph that describes using Automator to trigger AppleScripts.

      I’ll update the original tutorial article to include the Automator workaround with screenshots so that people using newer versions of OSX and FCPX will not experience the same issue that you did.

      Jasper Thayer
      Apple Certified Trainer
      https://FinalCutProX.net

  • #1155
    +1

    Benjamin Brodbeck
    Participant
    3p
      • Topics: 1
      • Replies: 2
      • Total Posts: 3

    Cool! I’ve got several people on Twitter asking how this was done so I’ll be sending the traffic your way.

You must be logged in to reply to this topic.