This is the repository for the backend of the Interstell.AR software system. Although the source code is for the backend, the release channel of this repository contains all components of the system at the current point.
Note: Only macOS Mojave (10.14) or higher is supported at the moment.
- Grab the current release
- Install dependencies
- Open a terminal
- Navigate to the unzipped release folder
- Execute
./install_dependencies.sh
- Note: If you do not have the Apple Developer Tools installed on your machine yet, you will be prompted to download and install them.
They are necessary to compile C/C++ code on macOS. Following that, the script will install FFTW, liblo and libmapper to your machine (specifically, to
/usr/local/include
and/usr/local/lib
). - You may have to re-run the
./install_dependencies.sh
command if you did not have the Apple Developer Tools installed already. - If you already have some of the required dependencies installed,
you can instead navigate into the
dependencies
folder and use the dedicated installer scriptsinstall_fftw.sh
,install_liblo.sh
andinstall_libmapper.sh
.
- Note: If you do not have the Apple Developer Tools installed on your machine yet, you will be prompted to download and install them.
They are necessary to compile C/C++ code on macOS. Following that, the script will install FFTW, liblo and libmapper to your machine (specifically, to
- Open
interstellar_installer.pkg
and follow the installation process. This will install:- A standalone version of the backend
- Audio plugins in the VST3 and AU formats
- The "interstellar" application (the frontend of the system producing the visualisations)
- The "Webmapper" interface application
- Open your favourite digital audio workstation and add the
music-vis-backend
plugin to a track - Open the "interstellar" application in your Applications folder.
- Open the "Webmapper" application in your Applications folder.
- In the Webmapper interface you should now see one device named "music-vis-backend-libmapper.1". Additionally, you should see devices for all visual objects in the frontend. (See screenshot below)
If you decide to remove the software from your system:
- Open a terminal
- Navigate to the unzipped release folder
- Navigate to the folder
uninstall
- Uninstallation
- Run
./uninstall_everything.sh
to remove both the dependencies and the software (the plugins, the frontend application and the Webmapper application) - Run
./uninstall_dependencies.sh
if you want to remove the dependencies but keep the software. - Run
./uninstall_apps.sh
if you want to remove the software but keep the dependencies.
- Run
- Grab the current release
- Install dependencies
- Open a terminal
- Navigate to the unzipped release folder
- Execute
./install_dependencies.sh
- Note: If you do not have the Apple Developer Tools installed on your machine yet, you will be prompted to download and install them.
They are necessary to compile C/C++ code on macOS. Following that, the script will install FFTW, liblo and libmapper to your machine (specifically, to
/usr/local/include
and/usr/local/lib
). - You may have to re-run the
./install_dependencies.sh
command if you did not have the Apple Developer Tools installed already. - If you already have some of the required dependencies installed,
you can instead navigate into the
dependencies
folder and use the dedicated installer scriptsinstall_fftw.sh
,install_liblo.sh
andinstall_libmapper.sh
.
- Note: If you do not have the Apple Developer Tools installed on your machine yet, you will be prompted to download and install them.
They are necessary to compile C/C++ code on macOS. Following that, the script will install FFTW, liblo and libmapper to your machine (specifically, to
- Download and install JUCE
- Download the source code
- Make sure that there are no whitespaces in the path leading to your source folder
- Open the
music-vis-backend
folder in the IDE of your choice - Open the
CMakeLists.txt
file - Go to line 23 and change
"~/IJUCE"
inlist(APPEND CMAKE_PREFIX_PATH "~/IJUCE")
to your JUCE installation folder path - Run one of the CMake configurations
music-vis-backend_VST3
will build the VST3 pluginmusic-vis-backend_AU
will build the AU pluginmusic-vis-backend_Standalone
will build a standalone executable version (*.app file) of the software
- Results of the build process will be in the
cmake-build-debug/music-vis-backend_artefacts
orcmake-build-release/music-vis-backend_artefacts
folders, depending on your configuration - Code away :)