You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 11, 2024. It is now read-only.
I've been exploring your "Loopdown" tool for managing sounds and loops and have a simple question: does it support applications located in custom directories, such as /Applications/Audio, instead of the default /Applications? We distribute numerous applications and organize them into sub-folders within "/Applications", but it seems Loopdown expects them to be in the root "/Applications" directory.
If this is the case, I would like to request a feature update that allows specifying custom paths/locations for applications. Alternatively, using mdfind to locate the application path by bundle ID could be another solution.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
Thanks for developing and updating Loopdown.
I've been exploring your "Loopdown" tool for managing sounds and loops and have a simple question: does it support applications located in custom directories, such as /Applications/Audio, instead of the default /Applications? We distribute numerous applications and organize them into sub-folders within "/Applications", but it seems Loopdown expects them to be in the root "/Applications" directory.
If this is the case, I would like to request a feature update that allows specifying custom paths/locations for applications. Alternatively, using
mdfind
to locate the application path by bundle ID could be another solution.The text was updated successfully, but these errors were encountered: