search

jduerr / FCPX-Chapter-Extractor

Automator based Application for extracting Chapters with timestamps out of an FCPXML project file for usage in an YouTube videos description.
12 stars 2 forks source link

Doesn't work with Monterey? #2

Open teddis opened 2 years ago

teddis commented 2 years ago

Unfortunately, this appears to be incompatible with the latest Mac OS. The Finder says that the AutomatorFCPXExtractor.app is damaged. The service seems to install but doesn't appear in the Finder menu, perhaps related to the former issue?

jduerr commented 2 years ago

Ok, sorry for the inconvenience! I just exported a current version, sadly i can not test with Monerey since i'm still running Big Sur on my macs. Could you please checkout the current commit i pushed to the master branch and retry it?

Also - could you please verify that python is installed on your machine?

kind regards

Johannes

teddis commented 2 years ago

Thanks for quick reply!

My MacBook (OS 12.1) has python2.7 pre-installed at /usr/bin/python (a symlink).

Is this the correct version your app depends on?

If not, I am unable to modify /usr/bin/python as Apple locks that down. I cannot remove it or change the symlink (even as root!). I only have control over /usr/local/bin/python which points to python 3.9.9 (Nov 2021) which I installed via brew.

Your new update still fails for me. I get the following when running the app:

"FCPXML-Chapter_Standalone.app" is damaged and can't be opened. You should move it to the Trash."

Also, when I double click the workflow, it opens the Automator, is that right? Thanks Screen Shot 2022-02-03 at 6 11 43 PM .

jduerr commented 2 years ago

Using macOS 11.6.2, python version 2.7.16 is preinstalled in /usr/bin/python, too. So can't see any difference there. Yes, opening the workflow will lead to opening it in Automator, where you can see what exactly is being done. The workflow is receiving files from finder and handing them over to the python script as arguments.

Thy python script does the heavy lifting and outputs the text as string to the last step: ... saving the text (string) into a text file.

If using the automator workflow you could test it by adding your *.fcpxml file to the first step (Get specified finder items) directly in automator and hitting the "Run" button in the toolbars top right corner.

Bildschirmfoto 2022-02-04 um 05 47 52 AM

One thing i noticed, ... of course the extractor is working only with .fcpxml files. It does not work with .fcpxmld format. But the error message would be different if that would be the problem.

duncangroenewald commented 2 years ago

It's not working for me either. I can run the script from automator but the output file is empty.

AdamMannPro commented 2 years ago

Hi, Im still having the same issues as the above, I have modded the automator file but when running it, it says I need to install the app again. it will not run from Finder either.

Such a pity as this app was so helpful for my vlogs.

If there is anything I can do to help get this working I would be willing to do any testing or provide any further information. I am running macOS Monterey on a 2018 MBP.

AdamMannPro commented 2 years ago

Found a work around that works.

https://www.alfredapp.com/help/kb/python-2-monterey/

Just tested it myself and got it working.

Installed Homebrew and ran the terminal command on the site and it works, not the best workaround but until it is tested and resolved by the creator this will have to do.

swift2geek commented 1 year ago

Here is a working tool for Macos Ventura https://github.com/swift2geek/fcpx-extractor