[linux-audio-user] Problem starting bristol with jack

[Larry Troxler]

Hi Nick, I don't know how to find the version of the executables (which 
command line option?), but the version of the Debian package is 0.9.1-13.

Using startBristol -jack -b3 gives the same behavior.

This is on a 64 bit AMD SMP kernel.

Larry


On Thu, 8 Feb 2007, Nick Copeland wrote:

> Hi Larry
>
> Have you tried with just the following?
>
> startBristol -jack -b3
>
> It looks like the engine has failed to start due to the midi selection (the 
> default midi options are the ALSA seq so I would advise not changing that). 
> This causes the GUI to fail as well since the engine is not available. What 
> version of bristol is this? I am surprised by the error message regarding 
> 'suid root' as I thought this was dropped in the -69 release on sourceforge - 
> it should now rely on PAM RT permissions or be started as root, so the 
> message is superfluous and you only need suid permissions if you want to use 
> bristol dedicated to the audio device with RT scheduling.
>
> Regards,
>
> Nick.
>
>
>> From: Larry Troxler <lt at westnet.com>
>> Reply-To: A list for linux audio users 
>> <linux-audio-user at music.columbia.edu>
>> To: linux-audio-user at music.columbia.edu
>> Subject: [linux-audio-user] Problem starting bristol with jack
>> Date: Wed, 7 Feb 2007 20:36:46 -0500 (EST)
>> 
>> 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 at 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 at 64studio:~$ parent exiting
>> 
>> 
>> Larry Troxler
>
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today it's FREE! 
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>

Larry Troxler