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

Nick Copeland wrote:
> 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@email-addr-hidden:~/software/nove/bristol/bristol-0.9.5/bin$ limit
> coredumpsize unlimited

as root, or as a user:

bash: limit: command not found

> nowhiskey@email-addr-hidden:~/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@email-addr-hidden:~/software/nove/bristol/bristol-0.9.5/bin$ cd /tmp
> nowhiskey@email-addr-hidden:/tmp$
> ~/software/nove/bristol/bristol-0.9.5/startBristol -rhodes -jack

not sure if this is right:

nowhiskey@email-addr-hidden:/tmp$
/home/nowhiskey/software/nove/bristol/bristol-0.9.5/bin/startBristol
-rhodes -jack
spawning midi thread
parent going into idle loop
midi sequencer
Opened listening control socket: 5028
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
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
cleanupBrighton(0)
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@email-addr-hidden:/tmp$

cheers,
doc
>
> The coredump as an enclosure, or the stack backtrace from GDB will
> help to track down the cause of the problem.
>
> Regards,
>
> Nick.
>
Received on Fri Sep 29 20:15:05 2006