-
-
Notifications
You must be signed in to change notification settings - Fork 12
Troubleshooting
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
sudo xattr -rd com.apple.quarantine /Applications/OwlPlug.app/
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.
Antivirus may disrupt application startup and execution. Owlplug may also require to be run as Administrator on Windows depending local security policies.
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
Log are stored on the OwlPlug workspace in user home directory.
Windows
C:/Users/{you}/.owlplug/logs
MacOs
/home/{you}/.owlplug/logs
- Browse to OwlPlug workspace directory
Windows
C:/Users/{you}/.owlplug
MacOs
/Users/{you}/.owlplug
- 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.
- Home
- Getting Started
- User Guide
-
Developer Guide
- Environment Configuration