#11 bristol doesn't start or crash immediately

admin
closed
Nick Copeland
5
2008-01-28
2008-01-17
Anonymous
No

hi,
I compiled bristol-0.10.12 on my mandriva 2008 but as soon as I start it, it crashes immediately or after I press the first note. this is my output
7148 ? I started jack 0:01 /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p64 -n2 -P -m -H -M

and then
startBristol -jack
spawning midi thread
connected to :0.0
display is 1280 by 800 pixels
Window is w 1280, h 800, d 16, 0 0 0
Using DirectColor display
alloc color by name Blue
midi sequencer
Opened listening control socket: 5028
Client ID = 129
Queue ID = 0
Registering 0 1
Registered 129 0
Device name "bristol" did not parse, defaults 128.0
Initialise the hammondB3 link to bristol: 811e9e8
parent going into idle loop
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
Did not need to reschedule thread
initialising one hammond sound
micro first 0.000000 last 0.000000 (hammond)
veloc first 0.00 last 1.00
Found port system:playback_1
Found port system:playback_2
Bristol Defaulted Conn: bristol:out_left to system:playback_1
Bristol Defaulted Conn: bristol:out_right to system:playback_2
hostname is localhost, bristol
port is 5028
connect failed: Connection refused
connfailed
hostname is localhost, bristol
port is 5028
connect failed: Connection refused
connfailed
cleanupBrighton(0)
cleared sigpipe handler
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
/usr/bin/startBristol: line 311: 7549 Segmentation fault bristol -rate ${RATE} -count ${COUNT} $*

if I start it with a rhodes, I don't see it into the connect window of qjackctl and as soon as I press a note, it crashes
startBristol -jack -rhodes
spawning midi thread
connected to :0.0
display is 1280 by 800 pixels
Window is w 1280, h 800, d 16, 0 0 0
Using DirectColor display
alloc color by name Blue
midi sequencer
Opened listening control socket: 5028
Client ID = 129
Queue ID = 0
Registering 0 1
Registered 129 0
Device name "bristol" did not parse, defaults 128.0
parent going into idle loop
Initialise the rhodes link to bristol: 811e9e8
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
Did not need to reschedule thread
initialising one Rhodes sound
micro first 0.000000 last 0.000000 (dx)
veloc first 0.00 last 1.00
done create interface: 81160d0, 811e9e8
Client ID = 130
Queue ID = 1
Registering 0 1
Registered 130 0
Device name "brighton" did not parse, defaults 128.0
opened GUI midi handle: 1, fd 39
Read Configuration: rhodes
brightonWorldChanged(750 250 10 10)
going operational
Attempt to read dx into rhodes algorithm
Active count changed. Overriding
bristolMidiSendNRP(0, 0, 16382, 0)
bristolMidiSendNRP(0, 0, 16381, 0)
bristolMidiSendRP(0, 0, 0, 2)
Found port system:playback_1
Found port system:playback_2
Bristol Defaulted Conn: bristol:out_left to system:playback_1
Bristol Defaulted Conn: bristol:out_right to system:playback_2
cleared sigpipe handler
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
/usr/bin/startBristol: line 311: 7616 Segmentation fault bristol -rate ${RATE} -count ${COUNT} $*

Discussion

  • Nick Copeland
    Nick Copeland
    2008-01-17

    • labels: 977291 -->
     
  • Nick Copeland
    Nick Copeland
    2008-01-17

    Logged In: YES
    user_id=1426398
    Originator: NO

    This is almost certainly a duplicate of the case 'Bristol segfaults with jack buffer size mismatches". That is kind of not what I anticipated for 0.10.12 though - it should report different buffer sizes and exit a little more gracefully.

    You might want to test this with 'startBristol -jack -count 64' though.

    I will run these buffer sizes through my system though. Out of interest, is this a 64 bit system? Perhaps there is a separate issue with jack interoperability on 32 vs 64 bit systems?

     
  • Nick Copeland
    Nick Copeland
    2008-01-17

    • labels: --> Bristol Engine
    • milestone: --> admin
    • assigned_to: nobody --> ncopeland
     
  • Nick Copeland
    Nick Copeland
    2008-01-20

    Logged In: YES
    user_id=1426398
    Originator: NO

    The problem has not been reproducable with jack 0.103.0 (have not tried 0.109.0 yet). Even if the size mismatches then bristol will just give a big error message and exit - that is not visible in these debug outputs, something which implies the startBristol script has successfully found the -p64 and -r48000 from the active jackd as it is supposed to (and tested this again to make sure).

    You may want to try complete reinstall:

    make uninstall
    make distclean
    autoreconf --install --force && ./configure && make install

     
  • Nick Copeland
    Nick Copeland
    2008-01-23

    Logged In: YES
    user_id=1426398
    Originator: NO

    This is being closed as a duplicate of the stated case, and since it cannot be reproduced with jackd 0.103 or 0.109

     
  • Nick Copeland
    Nick Copeland
    2008-01-23

    • status: open --> pending
     
  • Nick Copeland
    Nick Copeland
    2008-01-28

    • status: pending --> closed