[linux-audio-user] ANN: bristol 0.9.5-60

Nick Copeland nickycopeland at hotmail.com
Fri Sep 29 10:09:31 EDT 2006

The 'zombied' message from jack and the 'midi write error' from brighton 
indicate that bristol, the engine, has ungracefully exit, most typically a 
segfault. Depending on your shell and write permissions on the 'bin' 
directory you may be able to do the following:

nowhiskey at murija2:~/software/nove/bristol/bristol-0.9.5/bin$ limit 
coredumpsize unlimited
nowhiskey at murija2:~/software/nove/bristol/bristol-0.9.5/bin$ ./startBristol 
-rhodes -jack

Now do whatever until the error occurs and if you now close the synth window 
from the title bar you will get a core dump IF you have write permissions in 
the current directory. If you do not want to have write permissions on the 
bristol/bin directory then try the following:

nowhiskey at murija2:~/software/nove/bristol/bristol-0.9.5/bin$ cd /tmp
nowhiskey at murija2:/tmp$ ~/software/nove/bristol/bristol-0.9.5/startBristol 
-rhodes -jack

The coredump as an enclosure, or the stack backtrace from GDB will help to 
track down the cause of the problem.



>From: Dragan Noveski <perodog at gmx.net>
>Reply-To: A list for linux audio users 
><linux-audio-user at music.columbia.edu>
>To: A list for linux audio users <linux-audio-user at music.columbia.edu>
>Subject: Re: [linux-audio-user] ANN: bristol 0.9.5-60
>Date: Fri, 29 Sep 2006 15:52:46 +0200
>Nick Copeland wrote:
>>>rhodes, and rhodes-bass arent working, segfault?
>>Not the first complaint about these algorithms failing. To test it you 
>>minimally need read access to the whole tree where you installed and built 
>>bristol so that you can read the memories, then use the startBristol 
>>script in the bin directory: 'startBristol -rhodes'. That is supposed to 
>>work, and if that is how you get segmentation faults then I could do with 
>>the output from a gdb stack backtrace ('gdb <bristol> <core>' then type in 
>>"backtrace", or a core file sent directly to me).
>i looked now following your instructions, it is not a segfault, but 
>zombifying jack.
>i did:
>cd /software/nove/bristol/bristol-0.9.5/bin$
>and then:
>./startBristol -rhodes -jack
>the roads piano appears, it is connected to jack, but trying to play the 
>keys, no sound, than short time after rhodes stops:
>nowhiskey at murija2:~/software/nove/bristol/bristol-0.9.5/bin$ ./startBristol 
>-rhodes -jack
>spawning midi thread
>parent going into idle loop
>connected to :0.0 (81492f0)
>display is 1024 by 768 pixels
>Window is w 1024, h 768, d 24, 0 0 0
>Using DirectColor display
>masks are ff0000 ff0000 ff0000
>Initialise the rhodes link to bristol: 814dd50
>midi sequencer
>Opened listening control socket: 5028
>Client ID = 129
>Queue ID = 0
>Device name did not parse, defaults 128.0
>hostname is localhost, bristol
>port is 5028
>Connected to the bristol control socket: 5
>bristolengine already active
>Accepted connection from 0 (3) onto 2 (5)
>created 16 voices: allocated 16 to synth
>engine MIDI channel 0
>spawning audio thread
>registering jack interface
>Rescheduled thread: 95
>initialising one DX sound
>done create interface: 81490c0, 814dd50
>brightonWorldChanged(750 250 10 10)
>going operational
>Found port alsa_pcm:playback_1
>Found port alsa_pcm:playback_2
>Default connection bristol:out_left to alsa_pcm:playback_1
>Default connection bristol:out_right to alsa_pcm:playback_2
>Found port alsa_pcm:capture_1
>Found port alsa_pcm:capture_2
>Default connection alsa_pcm:capture_1 to bristol:in
>zombified - calling shutdown handler
>unregistering jack interface
>midi write error, fd 5, size 1
>midi write error, fd 5, size 12
>midi write error, fd 5, size 1
>return - no data in buffer
>socket closed
>request acked: -1
>nowhiskey at murija2:~/software/nove/bristol/bristol-0.9.5/bin$
>please give me a more precisely "howto" for using "gdb"
>>>copy in to /usr/local/bin or /usr/local/lib, so that i can put some 
>>>menu-entries, so being able to start from menu?
>>Hm, this is the second request for an install operation. Can you not build 
>>in the full path to the startBristol script, with options, as a menu 
>>command? Is the issue here that libraries cannot be found due to root 
>>permissions and security or that binaries cannot be found if the path is 
>>not configured correctly?
>this part i really dont understand, but i think it is a less problem, since 
>i can copy the hole build dir somewhere, and than make  the different 
>>Kind regards,
>>Don't just search. Find. Check out the new MSN Search! 

Express yourself instantly with MSN Messenger! Download today it's FREE! 

More information about the linux-audio-user mailing list