Hi, I'm using the 64 studio 1.0 distro.
with the command:
startBristol -jack -b3 -midi alsa
I get the following, and was wondering what I might be doing wrong.
larry@64studio:~$ startBristol -jack -b3 -midi alsa
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 (5cc430)
display is 1280 by 1024 pixels
Window is w 1280, h 1024, d 24, 0 0 0
Using TrueColor display
masks are ff0000 ff0000 ff0000
flags are 80000000
Returning socket 3
Opened listening control socket: 5028
ALSA lib rawmidi_hw.c:233:(snd_rawmidi_hw_open) open /dev/snd/midiC0D0
failed: Device or resource busy
Could not open the MIDI interface hw:0,0.
Error opening midi device hw:0,0, exiting midi thread
Initialise the hammondB3 link to bristol: 5d15b0
starting upper manual connection
hostname is localhost, bristol
port is 5028
connfailed
opening link to engine: -1
hostname is localhost, bristol
port is 5028
connfailed
cleanupBristol(-4)
larry@64studio:~$ parent exiting
Larry Troxler
