Known Issues

The SoundScape Renderer has moved to

Please do not hesitate to contact for support, feature requests, issues and bug reports.

This is a list of known issues relevant for the user:


Multi-channel WAV files would normally use the format WAVE_FORMAT_EXTENSIBLE, see
However, Ecasound doesn't know this format, that's why we have to use one of the abovementioned formats, although for files with more than 2 channels this is not compliant to the WAV standard.

To check the exact format of your WAV files, you can use sndfile-info (Debian package sndfile-programs), and to convert your files, you can use for example sox (Debian package sox) with the wavpcm option:

sox old.wav new.wavpcm
mv new.wavpcm new.wav

If a file can't be loaded -> connection to live input

If there is an error loading a specified audio file, the corresponding source is still created and (unexpectedly) connected to the first soundcard input channel.
We believe this is a bug in the JACK system related to the API function jack_connect(): If the destination_port argument is an empty string, the function returns (correctly) with an error. However, if the source_port argument is an empty string, the port is connected to the first "system" port (or the first port at all, or who knows ...).
And this is the case if the SSR cannot open a specified audio file.

If you also think that's a bug, feel free to report it to the JACK developers.

Conflicting JACK and Ecasound versions

There is a problem due to a special combination of ecasound and JACK versions on 64 bit systems leading to an error (terminating the SSR) similar to this:

(ecasoundc_sa) Error='read() error', cmd='cs-connect' last_error='' cmd_cnt=6 last_cnt=5.

We experienced this error on 64 bit systems with ecasound version and 2.7.0 in combination with JACK version 0.118.0.

Please try to update to the newest ecasound and JACK versions.

Annoying Ecasound message

You may have seen this message:

* Message from libecasoundc:
* 'ECASOUND' environment variable not set. Using the default value 
* value 'ECASOUND=ecasound'.

You can totally ignore this, but if it bothers you, you can disable it easily by specifying the following line in /etc/environment:


... or, if you prefer, you can put this in your $HOME/.bashrc:

export ECASOUND=ecasound

Segmentation Fault when Opening a Scene

This problem occured on some old SuSE systems.

When you start the SSR with GUI everything is alright at first. As soon as you open a scene a segmentation fault arises. This is a problem in the interaction between Qt and OpenGL. As a workaround, comment the line

renderText(0.18f * scale, 0.13f * scale, 0.0f, source->name.c_str(), f);

in the file src/gui/qopenglrenderer.cpp and recompile the code. The consequence is that the names of the sound sources will not be displayed anymore.

Choppy Sound on Cheap (On-Board) Sound Cards

Sometimes JACK doesn't play well with those on-board sound cards. One possibility to improve this, is to increase the frames/period setting from the default 2 to a more generous 3.
This can be done in the Settings dialog of qjackctl or with the command line option -n:

jackd -n 3

Old Issues

Following issues are no issues anymore in the current SSR version.

SSR for MacOSX: qt_menu.nib not found

This was fixed in MacPorts, see

Thanks to Chris Pike!

Compilation Error on Ubuntu and Archlinux

This issue was resolved in version 0.3.4.

Some newer distributions got more picky about the necessary #include commands.

If the SSR refuses to compile, add this to the file src/gui/qopenglplotter.h (somewhere at the beginning):

#include <GL/glu.h>

On MacOSX you'll need this instead:

#include <OpenGL/glu.h>

Polhemus tracker does not operate with SSR

This issue was resolved in version 0.3.3, where we changed the tracker selection. Use --tracker=polhemus and --tracker=intersense respectively. The serial port can be specified with --tracker-port=/dev/ttyUSB0 (or similar)

This can happen when both the Intersense tracker as well as the Polhemus tracker are compiled and the file isports.ini is apparent. The latter tells the Intersense tracker which port to use instead of the standard serial port /dev/ttyS0. If the isports.ini file lists the port to which the Polhemus tracker is connected it can happen that something that we have not fully understood goes wrong and the Pohlemus data can not be read. In this case you can either rename the file isports.ini or change its content.

It might be necessary to execute echo C > /dev/ttyS0 several times in order to make the Polhemus tracker operational again. You can check with cat /dev/ttyS0 if it delivers data.

Missing GUI Buttons and Timeline

This issue was resolved in version 0.3.2, the default setting for --enable-floating-control-panel is chosen depending on the installed Qt version.

Different versions of Qt show different behaviour regarding OpenGL Overlays and as a result, the GUI buttons are not shown in newer Qt versions.
To overcome this limitation, we provide two GUI variants:

  • traditional GUI, can be used up to Qt 4.6.x
  • floating control panel, should be used with Qt 4.7 and above

The floating control panel is the default setting on MacOSX, for Linux it can be activated with:

./configure --enable-floating-control-panel

OpenGL Linker Error

This issue was resolved in version 0.3.2.

On some systems, after running make, you'll get an error mentioning "glSelectBuffer".

For now, this is the solution (see also the issue below):

./configure LIBS=-lGL

IP interface isn't selected although boost libraries are installed

This issue was resolved in version 0.3.2.

This is similar to the previous issue, this should be the solution:

./configure LIBS=-lpthread

To avoid both errors, you can use the combination:

./configure LIBS="-lGL -lpthread" 

Audio files with spaces

This issue was resolved in version 0.3.2.

Please do not use audio files with spaces for scenes. Neither the filename nor the directory referenced in the scene (asd-file) should contain spaces.