4 - Toutes les autres applications, les émulateurs...

startBristol
        You may want to make bristolengine a suid-root executable
spawning midi thread
Could not reschedule thread to 2
parent going into idle loop
connected to :0.0 (80f82f0)
display is 1680 by 1050 pixels
Window is w 1680, h 1050, d 24, 0 0 0
Using DirectColor display
masks are ff0000 ff0000 ff0000
INIT: 80f8008
Initialise the mini link to bristol: 80fcc18
        flags are 8a000000
midi sequencer
Returning socket 3
Opened listening control socket: 5028
Client ID = 128
Queue ID = 0
Device name did not parse, defaults 128.0
Found 1 descriptor
hostname is localhost, bristol
port is 5028
Connected to the bristol control socket: 5
bristolengine already active
80d4e80 80000000 0
acceptConnection(0)
Accepted connection from 0 (3) onto 2 (5)
bristolSystem(127, 0, 64) 10
        flags are 2010
configured 16 voices
message from 2, 0
bristolSystem(127, 0, 14) 0
        flags are 700
2:      2 2
configuring midi channel to 0
bristolSystem(127, 0, 2) 0
        flags are 100
going to attempt engine kickoff: 2000 (-1)
spawning audio thread
Could not reschedule thread to 1
init audio thread, 80c5c40
bufsize is now 1024
bristolAudioOpen(/dev/audio, 44100, 1024, 8a000004)
audioOpen(080944a0, 0, 1024): /dev/audio
flags are now 2
Failed to open audio device "/dev/audio", flags 2
Problem opening audio device /dev/audio, exiting audio thread
bristolSystem(127, 0, 12) 0
        flags are 600
1:      2 2
initialising one bristolmini
return - no data in buffer
cleanupBristol(0)
/usr/bin/startBristol: line 130: 17139 Erreur de segmentation  (core dumped) bristolengine -preload 4 -bufsize 1024 $audioflags $midiflags $*