I had another go at using sooperlooper today, and it turns out that my workaround just delays the problem. Starting up sooperlooper from the command line with no arguments works fine, but as soon as I start slgui on a separate command line, the engine segfaults and slgui tries to spawn its own engine and fails. It's starting to look like something of an OSC problem.
The behaviour is similar to that described at an old thread here: http://ccrma-mail.stanford.edu/pipermail/planetccrma/2005-October/010554.html The solution there was to install liblo 0.16.4 from an RPM. I have liblo 0.23-2.1build1 installed from universe. [EMAIL PROTECTED]:~# dpkg --list | grep liblo ii liblo0 0.23-2.1build1 Lightweight OSC library ii liblo0-dev 0.23-2.1build1 Lightweight OSC library -- development files [EMAIL PROTECTED]:~# dpkg --list | grep soop ii sooperlooper 1.0.8c-2ubuntu1 Looping Sampler [EMAIL PROTECTED]:~# jackd -dalsa -d hw:1 -r 44100 -p 1024 -n 4 & [1] 8447 [EMAIL PROTECTED]:~# jackd 0.102.20 Copyright 2001-2005 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. loading driver .. apparent rate = 44100 creating alsa driver ... hw:1|hw:1|1024|4|44100|0|0|nomon|swmeter|-|32bit control device hw:1 configuring for 44100Hz, period = 1024 frames, buffer = 4 periods ALSA: final selected sample format for capture: 24bit little-endian ALSA: use 4 periods for capture ALSA: final selected sample format for playback: 24bit little-endian ALSA: use 4 periods for playback [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# sooperlooper SooperLooper 1.0.8c Copyright 2005 Jesse Chappell OSC server URI (network) is: osc.udp://cheese:9951/ Up to this point jackd and the sooperlooper engine have started successfully. Upon running slgui, the engine segfaults. -- Sooperlooper segfaults when launched from slgui https://bugs.launchpad.net/bugs/115152 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
