Greetings all, I've only just discovered
  http://bristol.sourceforge.net/
which looks great; so I downloaded bristol-0.40.6.tar.gz and
compiled and installed it OK.  Now starting it up with
  startBristol -juno
I get a real-looking keyboard on the screen, and can play it fine
through the audio card! :-)  But it displays an error message:
  Registered 129 0
  Device name "bristol" did not parse, defaults 128.0
  could not reschedule thread
  parent going into idle loop
  Got midi thread OK status
and other similar messages, and ALSA can't see the bristol at all:
 $> aplaymidi -l
  Port    Client name           Port name
  14:0    Midi Through          Midi Through Port-0
  20:0    Roland XV-2020        Roland XV-2020 MIDI 1
 128:0    TiMidity              TiMidity port 0
 128:1    TiMidity              TiMidity port 1
 128:2    TiMidity              TiMidity port 2
 128:3    TiMidity              TiMidity port 3

But... I want to feed MIDI into it, e.g from aplaymidi --port=NN:N
so I tried
  startBristol -midi alsa -juno
but get
  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/-4, exiting midi thread
and the program exits. I also tried -mididev 14 etc without success.
How do I get this thing listening to my MIDI ?

Can't wait to get it working... seeking other bristol users,

Regards,  Peter

-- 
Peter Billam       www.pjb.com.au    www.pjb.com.au/comp/contact.html

Peter Billam wrote:
>   startBristol -midi alsa -juno

    startBristol -midi seq juno


HTH
Clemens

On 2009-11-02, Clemens Ladisch <clemens@ladisch.de> wrote:
>     startBristol -midi seq juno
> HTH
> Clemens

Thanks!  It didn't actually help, it was just the same as -midi alsa,
but I just got an email from Bristol author Nick Copeland saying:

> You should be able to do the following:
>   aconnect -io
> This should list bristol and brighton as available input and output.
> It should have been given the ID 129 and 130 but I will be honest
> - I don't understand why they do not appear to aplaymidi. In my
> opinion it is  due to missing some ALSA capability flags although
> I have tested with other combinations and the issue still shows
> up here on my system too. At the same time I did get the following
> to work, with certain limitations:
>   aplaymidi -p 129:0 bluegrass.mid
> This did work even though the ports to not appear as available to 
> aplaymidi.

and it works!
  box8 (debian) ~> startBristol -juno
  ... meanwhile in another xterm ...
  box8 (debian) ~> aconnect -io
  client 0: 'System' [type=kernel]
      0 'Timer           '
      1 'Announce        '
  client 14: 'Midi Through' [type=kernel]
      0 'Midi Through Port-0'
  client 20: 'Roland XV-2020' [type=kernel]
      0 'Roland XV-2020 MIDI 1'
  client 128: 'TiMidity' [type=user]
      0 'TiMidity port 0 '
      1 'TiMidity port 1 '
      2 'TiMidity port 2 '
      3 'TiMidity port 3 '
  client 129: 'bristol' [type=user]
      0 'bristol input   '
  client 130: 'brighton' [type=user]
      0 'brighton input  '
even though ports 129 and 130 don't show up in aplaymidi -l ?!

Now, off we go.. so much to explore..
The bristol site again:  http://bristol.sourceforge.net

Regards,  Peter

-- 
Peter Billam       www.pjb.com.au    www.pjb.com.au/comp/contact.html