64Studio, Bristol 0.9.6, building and run err

Karol K.
  • Karol K.

    Karol K. - 2008-10-31

    Hi there :-)

    I just installed 64Studio and have a problem with Bristol package. I followd the tutoriald served at Studio webpage(which can be found here: http://64studio.com/howto_bristol\) and followed errors aoocured.
    First is the build problem. I had a alsa-libs installed(default installation), but script throw a bug. I edited it, commented out the error signal:

            if [ $ADLIB -eq -1 ]; then
                    echo "Could not find ALSA headers (alsa-lib package)"1
    #               fatal=1

    And it builds with no errors. :-]
    (installng alsa-lib makes no effect. It is installed already)

    Next, following the tips, I run from bin directory:
    ./startBristol -audio jack -pro5
    and I get output:

    64studio:/home/krl/Desktop/bristol-0.9.6/bin# ; not implemented
    ./startBristol -audio jack -pro5

    Bristol is about to start.

    This program is totally unrelated to ANY of the companies that produced
    the original instruments emulated by bristol, and none of the original
    manufacturers in ANY way endorse this product.

    ./startBristol: line 299: brighton: command not found
    64studio:/home/krl/Desktop/bristol-0.9.6/bin# spawning midi thread
    Could not reschedule thread to 2
    parent going into idle loop
            flags are ca000000
    midi sequencer
    Problem with bind
    Could not open control listening socket: 0
    No controlling socket available: anticipating MIDI
    Error opening control device, exiting midi thread
    Xlib: connection to ":0.0" refused by server
    Xlib: No protocol specified

    cannot connect to :0.0
    brightonOpenDisplay(): cannot open :0.0
    /usr/bin/bristol: line 130: 11796 Naruszenie ochrony pamięci   bristol.real $* -engine
    parent exiting

    Naruszenie ochrony pamięci - segfault.

    Note, that there is Jack and a sequencer running in the background already.

    Any suggests? :)

    • Nick Copeland

      Nick Copeland - 2008-10-31

      I think I am going to have to be really, really lazy on this one. Can you try 0.20.8 rather than 0.9.6 and see how that works? There have been changes to the build process since GNU autotools was finally implemented and you probably have an issue with the early releases seeing as you do have ALSA lib and the rest already installed.

      Also, -audio jack is not advised, you probably want to try just the -jack option. If you use -audio or -midi then I clear out a lot of defaults for the audio or midi interfaces and allow the user to be very specific about options. That is admittedly sometimes counterproductive but it helps with some specific configurations.

      Kind regards,


    • Nick Copeland

      Nick Copeland - 2008-10-31

      OK, having just passed the buck totally with that reply I also wanted to say that trying -pro1 might be even more interesting than -pro5. The pro5 was a very early algorithm, the pro1 a lot more recent and I think it is a better emulator than the pro5. Both a polyphonic unless otherwise requested. I only bring this up now since the pro1 is only really emulated in the 0.20.8 release but its filters are far warmer and it overdrives with a rich sound rather than being dirty.



Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks