Skip to content

Troubleshooting

Jump to bottom Edit New page
Arthur Poiret edited this page Sep 25, 2023 · 7 revisions

Common errors

"OwlPlug is damaged and can't be opened" on macOS

Long even before Catalina macOS has been marking files that are downloaded from the internet with a filesystem attribute. It seems that from 10.5 (Leopard) a File Quarantine was introduced. However, from Catalina and up, it seems the protection has been upgraded and you won't be able to simply run anything you've downloaded. More info here

Open a Terminal and run the following command:

sudo xattr -rd com.apple.quarantine /Applications/OwlPlug.app/

Restrictions for macOS Ventura users are far heavier for non-notarized app. The procedure seems to be the following for Ventura (but needs confirmation)

  • Attempting to run OwlPlug may show a window explaining it cannot be opened because "Apple cannot check it for malicious software." Click Ok.
  • Open System Preferences and select Security & Privacy.
  • If the padlock in the bottom left is locked, click it and authenticate to unlock it.
  • Next to the message explaining the app "was blocked from use because it is not from an identified developer," click Open Anyway.
  • Close System Preferences.
  • Run the app.
  • A notice will reiterate the warning about an inability to check if it is malicious each time you run the app. Click Open.

Error message on startup: OwlPlug is already running

OwlPlug is probably stuck and invisible. Try to manually kill the process from command line or Task manager.

If any OwlPlug process are running, check logs to identify the conflict.

Error message on startup: Failed to launch JVM

Antivirus may disrupt application startup and execution. Owlplug may also require to be run as Administrator on Windows depending local security policies.

Crash during a plugin Scan / Sync

When Native Discovery is enabled in Options, plugins are deeply scanned to retrieve metadata. If something bad happen during metadata discovery, the entire application will crash. This is a known issue in OwlPlug (and some DAWs when you try to load a corrupted plugin)

To retrieve which plugin is responsible of the crash, you can change OwlPlug log level to DEBUG and look for the last scanned plugin in logs.

You can also try to run OwlPlug from a terminal to catch logs produced on STDOUT by native components and plugins.

Windows

OwlPlug.exe | MORE

Common debug operations

Retrieve application logs

Logs are stored on the OwlPlug workspace in user home directory.

Windows

C:/Users/{you}/.owlplug/logs

MacOS

/home/{you}/.owlplug/logs

Increase log level

  1. Browse to OwlPlug workspace directory

Windows

C:/Users/{you}/.owlplug

MacOs

/Users/{you}/.owlplug
  1. Create a new file logging.properties in the workspace directory, and add the following line to set OwlPlug log level to DEBUG.
# logging.properties
com.owlplug=DEBUG

Available log levels are TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF, ALL. The default log level is INFO for com.owlplug logger.

Wiki Index

Clone this wiki locally