For issues with exporting to MOV or AVI on a Mac, especially with an M1 chip, there are several potential solutions and troubleshooting steps you can take based on the contexts provided:

1. Check for Permission Issues: Ensure Spine has the necessary permissions to write to the destination folder. MacOS can sometimes restrict access to certain folders, so try exporting to a different location, such as your desktop or a newly created folder in your home directory.

2. Review the Spine Log: The spine.log file can provide valuable insights into what might be going wrong during the export process. You can find the log file by following the path <user home folder>/Library/Application Support/Spine/spine.log. Reviewing this file for any error messages or warnings can help identify the issue.

3. Update Spine: Ensure you are using the latest version of Spine. Although you mentioned using version 4.2.14, it's always a good idea to check for any updates or patches that might address export issues.

4. FFmpeg Compatibility: Spine uses FFmpeg for video encoding. There might be compatibility issues with the version of FFmpeg bundled with Spine, especially on newer hardware like the M1 chip. While direct manipulation of FFmpeg within Spine isn't typically user-accessible, understanding that this component is crucial for video exports can be helpful.

5. File and Path Names: Ensure that the file names and paths do not contain special characters or are too long. Simplify the names and try exporting again.

6. Export Settings: Experiment with different export settings, such as changing the codec or reducing the video quality, to see if certain configurations are more successful.

7. Software and Hardware Compatibility: There could be compatibility issues with the M1 chip and the version of Spine or MacOS you are using. Searching for any known issues with Spine on M1 Macs could provide more specific guidance.

8. Alternative Export Methods: As a temporary workaround, consider exporting your animation as a sequence of images and then using third-party video editing software to compile the images into a video. This method also allows for more control over the final video's codec and settings.

If after trying these steps you still encounter issues, it might be related to a more specific problem with Spine's compatibility with MacOS on M1 chips or a bug in the software that needs to be addressed in a future update.

Rex Thanks for showing the log, but I removed the image because it shows your registered email address on your license.
In general, it is easier to refer to the logs if they are in text form, so the next time you encounter an error, it would be helpful if you could post the contents of spine.log in text form.

I was able to confirm that the Bad CPU Type In Executable error was logged. It seems to be a problem specific to Mac PCs using the M1 chip. Did you install the Intel version of Spine? Spine natively supports Apple Silicon. If you downloaded the Intel version, try downloading the Apple Silicon version installer from your license page, reinstalling Spine, and see if the error is resolved.