Terrible problems on Ubuntu Hardy

Help
hello45044
2008-09-23
2013-05-23
  • hello45044
    hello45044
    2008-09-23

    I compiled Bristol 0.20.7 from source with ALSA support, on Ubuntu Hardy 8.04 32bit. I am having all kinds of problems running it, and am getting very frustrated. Can anyone help?

    [code]michael@cortana:~$ startBristol -alsa -mini
    spawning midi thread
    Fixing samplerate at 44100
            /home/michael/.bristol/memory/profiles/midicontrollermap
    attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
            /home/michael/.bristol/memory/profiles/midicontrollermap
    attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
            /home/michael/.bristol/memory/profiles/midicontrollermap
    attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
            /home/michael/.bristol/memory/profiles/midicontrollermap
    attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
            /home/michael/.bristol/memory/profiles/midicontrollermap
    attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
            /home/michael/.bristol/memory/profiles/midicontrollermap
    attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
            /home/michael/.bristol/memory/profiles/midicontrollermap
    attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
            /home/michael/.bristol/memory/profiles/midicontrollermap
    attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
            /home/michael/.bristol/memory/profiles/midicontrollermap
    attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
            /home/michael/.bristol/memory/profiles/midicontrollermap
    attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
            /home/michael/.bristol/memory/profiles/midicontrollermap
    attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
            /home/michael/.bristol/memory/profiles/midicontrollermap
    attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
            /home/michael/.bristol/memory/profiles/midicontrollermap
    attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
            /home/michael/.bristol/memory/profiles/midicontrollermap
    attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
            /home/michael/.bristol/memory/profiles/midicontrollermap
    attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
            /home/michael/.bristol/memory/profiles/midicontrollermap
    attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
            /home/michael/.bristol/memory/profiles/midicontrollermap
    attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
    parent going into idle loop
    Init waiting for midi thread OK status
            /home/michael/.bristol/memory/profiles/midicontrollermap
    attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
    Opened listening control socket: 5028
    midiOpen: hw:0,0(40)
    ALSA lib rawmidi_hw.c:233:(snd_rawmidi_hw_open) open /dev/snd/midiC0D0 failed: No such file or directory
    Could not open the MIDI interface.
    Error opening midi device hw:0,0, exiting midi thread
    bristol version 0.20.7
    connected to :0.0
    display is 1600 by 1200 pixels
    Window is w 1600, h 1200, d 24, 0 0 0
    Using DirectColor display
    alloc color by name Blue
    Initialise the mini link to bristol: 8137348
    hostname is localhost, bristol
    TCP port: 5028
    connect failed: Connection refused
    connfailed
    opening link to engine: -1
    hostname is localhost, bristol
    TCP port: 5028
    connect failed: Connection refused
    connfailed
    cleanupBrighton(-4)[/code]

     
    • hello45044
      hello45044
      2008-09-23

      Darn I'm used to using code tags. :)

       
    • Nick Copeland
      Nick Copeland
      2008-09-24

      From the error message is looks like there is an issue with the ALSA interface. It is difficult to say what from here but the obvious choice would be that some audio server already has the audio interface open. Do you have any window system sound server activated? If so, you may need to turn it off first.

      You may also want to put in the out from the ./configure - the last few lines will show which options have been included in the build process, just to make sure that ALSA is available.

      To check your alsa drivers try a 'cat /proc/asound/version' and 'cat /proc/asound/devices'

       
      • hello45044
        hello45044
        2008-09-24

        I tried closing out of Firefox, stopping Timidity, stopping pulseaudio, and restarting ALSA. And I know for sure ALSA support was enabled by the configure script because I had to go and install the development libraries for ALSA to get the script to say ALSA Enabled. This is what it gives me now.

        michael@cortana:~$ startBristol -mini -alsa
        spawning midi thread
        parent going into idle loop
        Init waiting for midi thread OK status
        Fixing samplerate at 44100
                /home/michael/.bristol/memory/profiles/midicontrollermap
        attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
                /home/michael/.bristol/memory/profiles/midicontrollermap
        attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
                /home/michael/.bristol/memory/profiles/midicontrollermap
        attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
                /home/michael/.bristol/memory/profiles/midicontrollermap
        attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
                /home/michael/.bristol/memory/profiles/midicontrollermap
        attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
                /home/michael/.bristol/memory/profiles/midicontrollermap
        attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
                /home/michael/.bristol/memory/profiles/midicontrollermap
        attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
                /home/michael/.bristol/memory/profiles/midicontrollermap
        attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
                /home/michael/.bristol/memory/profiles/midicontrollermap
        attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
                /home/michael/.bristol/memory/profiles/midicontrollermap
        attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
                /home/michael/.bristol/memory/profiles/midicontrollermap
        attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
                /home/michael/.bristol/memory/profiles/midicontrollermap
        attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
                /home/michael/.bristol/memory/profiles/midicontrollermap
        attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
                /home/michael/.bristol/memory/profiles/midicontrollermap
        attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
                /home/michael/.bristol/memory/profiles/midicontrollermap
        attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
                /home/michael/.bristol/memory/profiles/midicontrollermap
        attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
                /home/michael/.bristol/memory/profiles/midicontrollermap
        attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
                /home/michael/.bristol/memory/profiles/midicontrollermap
        attempt    /usr/local/share/bristol/memory/profiles/midicontrollermap
        Opened listening control socket: 5028
        midiOpen: hw:0,0(40)
        opened midi device: 0/1
        Got midi thread OK status
        bristol version 0.20.7
        connected to :0.0
        display is 1600 by 1200 pixels
        Window is w 1600, h 1200, d 24, 0 0 0
        Using DirectColor display
        alloc color by name Blue
        Initialise the mini link to bristol: 8137348
        hostname is localhost, bristol
        TCP port: 5028
        Connected to the bristol control socket: 4
        bristolengine already active
        Accepted connection from 0 (3) onto 2 (4)
        created 32 voices: allocated 32 to synth
        spawning audio thread
        bristolAudioOpen(plughw:0,0, 44100, 256, 1010008)
        audioOpen(b7e3f1a0, 0, 1024): plughw:0,0
        opening device plughw:0,0, flags 0000000d
        open playback on plughw:0,0, pre 8
        Could not set playback rate to 44100
        Problem opening audio device plughw:0,0, exiting audio thread
        could not get thread schedule
        initialising one bristolmini
        Null palette
        Terminate MIDI signalling
        Midi read retry (6740)
        Midi read retry (6740)
        Midi read retry (6740)
        return - no data in buffer
        cleanupBrighton(0)
        Midi read retry (6740)
        Midi read retry (6740)
        Midi read retry (6740)
        return - no data in buffer
        socket closed
        request acked: -1

         
    • Nick Copeland
      Nick Copeland
      2008-09-24

      Can you try this with just

      startBristol -mini

      and see what the difference is? I tried '-mini -alsa' on my system Ubuntu 7.10 and it fails similarly. Perhaps my default ALSA settings (alsa is the default but it selects even more defaults when default as a flag) are wrong now.

      If the line here works without the -alsa flag then either you can use that and I can fix the difference later.

      Regards,

      Nick

       
    • Nick Copeland
      Nick Copeland
      2008-09-24

      Perhaps you might also try

      startBristol -b3

      That would rule out any issues with just the mini emulator or perhps with the new filters (since the B3 does not use them). There was another thing that may be happening - if you start the application and the GUI fails for whatever reason then it may leave the engine in an idle state. When you start it again there may be unexpected effects. This should not happen any more since 'active sensing' was introduced in the release you have such that the engine should exit if it detects the GUI has also stopped working but it is worth checking:

      ps aux | grep bristol

      If you see the bristol engine running then kill it with a '-9' and startBristol again to see if there is any difference. If either of the above work then I probably have a bug I need to resolve.

      Regards,

      Nick.