-
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 exeripence. 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:
Anton (Thanks Anton for persisting in finding a solution)
Do NOT attempt to build with DSSI enabled. We've turned this off in OOM, as we're in the process of removing it. The problem DSSI app that triggered a segfault was Zynaddsubfx.
More than one user and Anton
This messages comes up in our Cmake file, as a check for jack2. We're aware of this, but it won't affect your install. It's on our list.
Anton's working in Opensuse, and installed jack2 = 1.9.7 from a distro package. When he removed that, and installed jack2 = 1.9.7 from source, this message disappeared. Maybe a clue for other users using distro packages.
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.
When starting OOStudio, make sure ALSA is not busy somewhere else, and you can start JACK ok. We're aware of this problem, and working on it.
This error comes up when the RTC device on your system does not have permissions set correctly. To solve this, Type the following:
chmod 660 /dev/rtc
chgrp audio /dev/rtc
NOTE: Alsa now uses the HPET timer, and adds a symlink for RTC based applications. For newer kernels with the portable rtc interface
chmod 660 /dev/rtc0
chgrp audio /dev/rtc0
make sure OOMidi can set the rtc clock:
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