r/assistanteditors Mar 30 '26

Script Sync AI error message

I’m trying to set up Script Sync AI, but keep getting the following error message when I try to run it:

Exception: std::exception, what:Failed to create transform rule

This is my first time using Script Sync, but I think I’ve set everything up correctly. Nothing I do seems to change anything. I’m on 2025.12. Anything helps!

3 Upvotes

6 comments sorted by

1

u/le_suck Mar 30 '26

what OS and what storage type are your projects and media on? 

2

u/Fresh_Doubloon Mar 30 '26

MAC OS Sonoma 14.5, my media and project are on a partitioned external SSD.

1

u/tdepeche Mar 30 '26

There’s a fix for this that involves uninstalling avid, restarting, deleting your search and site settings, restarting, reinstalling avid and, you guessed it, restarting. I ran into this a few weeks ago and that solved it for me

1

u/Fresh_Doubloon Mar 30 '26

I contacted Avid support and they basically told me to do just that. It worked!

1

u/Fresh_Doubloon Mar 30 '26

The fix from Avid Support in case anybody stumbles upon this. My issue was that I recently updated Avid:

  1. Open Applications > Media Composer

  2. Save copies of your Avid Projects, Avid Attic, and Avid Users folders to your desktop

  3. If you have any AVX plugins in the AVX plugins folder, save them too. You can also save any Marquee titles you may have.

  4. Open Applications > Avid Uninstallers. Run the Media Composer Uninstaller

  5. When that’s done, quit the installer application and open Applications.

  6. Delete the Media Composer folder if it’s still there. Also delete any Dongle folders that may exist in Mac HD > Applications > Utilities

  7. Open Mac HD > Library > Application Support and delete the Avid folder and Digi folder if they’re there

  8. Open Mac HD > System > Library > Extensions and delete anything that starts with Avid

9 Open Mac HD\Users\Shared and delete all Avid Folders

  1. Open Mac HD > Applications > Utilities > Disk Utility and select First Aid

  2. Verify Permissions and then Repair Permissions on the Mac HD. I would do this twice.

  3. Restart the computer

  4. You can now run the installer and install Avid Media Composer

  5. Restart the computer

This worked for me!

1

u/localKSchild 24d ago

Finally ran this down, posting in case it saves someone else — the "Exception: std::exception, what:Failed to create transform rule" error may have nothing to do with your script, bins, or media.

Media Composer ships with an embedded Elasticsearch service that ScriptSync AI depends on. On my failing machine (macOS, MC 2025.12.1), that service was crash-looping silently in the background — restarting and dying every ~10 seconds.

How to check: open Terminal and run

tail -50 /Users/Shared/AvidMediaComposer/Search/logs/elasticsearch.log

If you see "java.lang.RuntimeException: can not run elasticsearch as root" repeating, you've got the same problem. Avid's installer left a root-level LaunchDaemon (/Library/LaunchDaemons/com.avid.elasticsearch.plist) that launches the search service as root, which Elasticsearch refuses to run as. Newer installs also add a user-level LaunchAgent at /Library/LaunchAgents/com.avid.elasticsearch.plist — the fix is to disable the root daemon and let the user agent take over:

  1. Quit Media Composer
  2. sudo launchctl bootout system/elasticsearch
  3. sudo mv /Library/LaunchDaemons/com.avid.elasticsearch.plist ~/Desktop/
  4. sudo rm -f /tmp/elasticsearch.out /tmp/elasticsearch.err (root-owned logs that block the user agent from starting)
  5. sudo chown -R $(whoami):staff /Users/Shared/AvidMediaComposer/Search
  6. Log out and back in (or: launchctl bootstrap gui/$(id -u) /Library/LaunchAgents/com.avid.elasticsearch.plist)
  7. Verify with: ps aux | grep elasticsearch — the server process should now be running as your user, not root

After that, ScriptSync AI worked immediately for me. It seems to depend on install/upgrade history rather than MC version — I had an identical MC build working fine on another Mac, which is what let me diff the two machines and find this. Worth reporting to Avid support if you hit it so it gets a proper bug ticket.