-
Notifications
You must be signed in to change notification settings - Fork 19
Troubleshooting
This is our troubleshooting page, where we document some of the challenges users have had when building, compiling, and running OpenOctaveMidi-2011.
In our Linux world we are fortunate to have a lot of user choice in distro, window manager, versions of system apps and libraries, and so on. Usually things go together well, but sometimes a combination of hardware and/or software can throw up the occasional problem.
We hope that this page will go some way towards helping users get over some common issues other users have discovered, and help us make some tweaks to OpenOctaveMidi-2011 to aid you in your build/install, and running experience. This is by no means a complete list of issues and solutions, so if you discover a problem, and a solution, please let us know, so all of us in the OpenOctave community can help our fellow users.
Thanks, from the OpenOctave team.
More than one user
This is more than likely because you're using versions of Liblscp, Libgig, and Linuxsampler, that are out of date. SFZ is a recent addition to the Linuxsampler framework, and users should install Linuxsampler from svn to pick up the changes.
When building Linuxsampler, libgig, and liblscp, make sure the system tool libtools is up to date.
See here for build details, and Linuxsampler SVN paths:
Install the SSO sample lib following the instructions here:
We've tested this setup extensively, and know it works. You'll not only get a default modestly sized Orchestral Set to get you going, but follow the instructions, and you'll have a working template to begin with.
We've had a good run with the latest git repo version of the excellent CALF plugin suite, and in our testing of the effects plugins, all work fine. Please ask (nicely) your distro packaging specialist if they can check their current build of the CALF plugin suite, and if it's a bit dated, to consider upgrading. Thanks.
If you're feeling brave, and want to install the CALF plugin suite from git, you can find them here:
git clone http://repo.or.cz/r/calf.git
Take note of the requirements, which can be found here:
http://calf.sourceforge.net/?id=2
I'm not getting the Amber Midi light appearing in the track header, when i play my midi keyboard, and i'm sure i've got everything connected correctly.
Make sure the track is record-armed.
I can't record audio into my Audio track, and i'm definitely sure i've got all my ports and connections made correctly.
See above.
For any track to receive input, it must be record-armed.
This error comes up when the RTC device on your system does not have permissions set correctly. To solve this, pick the command line options that suit your current setup:
For much older alsa versions that don't have the HPET system included:
chmod 660 /dev/rtc
chgrp audio /dev/rtc
Newer Alsa versions now use the HPET timer, and add a symlink for RTC based applications. For newer kernels with the HPET portable rtc interface:
chmod 660 /dev/rtc0
chgrp audio /dev/rtc0
Make sure OOMidi can set the rtc clock in the old format:
echo 8192 > /proc/sys/dev/rtc/max-user-freq
check the max-user-freq is correctly set by typing:
cat /proc/sys/dev/rtc/max-user-freq
For the newer HPET symlinked RTC, or straight HPET:
echo 2048 >/sys/class/rtc/rtc0/max_user_freq
or:
echo 2048 >/proc/sys/dev/hpet/max-user-freq
Check this with:
cat /sys/class/rtc/rtc0/max_user_freq
or:
cat /proc/sys/dev/hpet/max-user-freq
Quick Start Manual Index
- Composer Menus
- Transport and Toolbars
- The Orchestra Pit
- Tracks
- Epic Views
- Mixerdock
- Midi Assign
- Punch Loop Marker
- Metronome
- Tempo and Keysignature
- Big Window
- Plugins
Links