brian/Cardinal
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Rename doc to folder docs

Browse source 
Signed-off-by: falkTX <falktx@falktx.com>
This commit is contained in:
falkTX 2022-02-11 14:46:21 +00:00
parent bc7999e2d2
commit 4a7921ee90
No known key found for this signature in database
GPG key ID: CDBAA37ABC74FBA0
14 changed files with 42 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

25
docs/FAQ.md Normal file
View file

@ -0,0 +1,25 @@
# Frequently Asked Questions
This document contains a few frequently asked auestions (known as "FAQ") regarding the Cardinal project.
# Why does Cardinal exist?
Many reasons, most of them described on the [README](../README.md#why).
But basically we want an open-source plugin version of "Rack Pro",
where we are free to change things as we see fit, work on new features and fix bugs.
This is simply not possible with proprietary software, which is the case of "Rack Pro".
# Changes are lost on restart
This is intentional.
Cardinal is meant to be a self-contained plugin, and as such it does not save any files whatsoever.
This includes user preferences (like list of favourites) or last used project.
As a plugin, the state will be saved together with the host/DAW project.
# On FreeBSD and Linux the menu item "Save As/Export..." does nothing
The save-file dialogs in Cardinal requires a working [xdg-desktop-portal](https://github.com/flatpak/xdg-desktop-portal) DBus implementation from your desktop environment.
Typically your desktop already provides this, if not consider looking for a package to install with "desktop-portal" in the name.
The open-file dialogs in Cardinal do not have this restriction, with a fallback in case desktop portal is not available.