Problem with the mixer memory during compilation will not have any affect on
the rest of the functionality, especially not on the audio drivers since the
mixer is GUI only at the moment, there is no code resident in the bristol
audio process.
I cannot state what would happen with different versions of the jack
drivers. Bristol compiles with the headers you have installed on the system.
It uses structures defined in those headers. The library you have installed
uses structures defined from a different version - if the structures are
formatted differently then anything can happen including segfaults and all.
Personally I doubt if there were that many changes between 102 and 101
however I would probably not advise using different versions anyway.
Is there any chance you could get me a copy of the core file?
Regards,
Nick.
From: Larry Troxler <lt@xxxxxxxxxxx>
Reply-To: A list for linux audio users
<linux-audio-user@xxxxxxxxxxxxxxxxxx>
To: A list for linux audio users <linux-audio-user@xxxxxxxxxxxxxxxxxx>
Subject: RE: Problem starting bristol with jack
Date: Sat, 10 Feb 2007 18:33:27 -0500 (EST)
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).
Well I recompiled from the latest sources (version 0.9.6), and I have a
somewhat different problem now:
<snip output>
spawning audio thread
registering jack interface
Rescheduled thread: 95
initialising one arp2600
return - no data in buffer
exit algo: 0, 5dba20, 0
/home/larry/bin/startBristol: line 302: 8511 Segmentation fault brighton $
* -engine
<snip output>
First, let me say that a complication is that my jack headers don't
exactly match my libjack version. My libjack is 0.102 (installed as a
debian package), and the headers are 0.101. Debian/64studio seems to have
packages available for libjack 0.102 but the libjack-devel is only at
0.101. Hence to attempt to get going with compiling apps, I simply
downloaded the 0.101 devel package and unpacked it. Dangerous, I know, but
I'm not sure that this is the cause of my problem, because I got a warning
during compilation that seems odd:
In brightonMixerMemory.c, there is a waring about a cast from pointer to
integer of different size (remember that I'm running 64 bits). Is this a
cause for alarm? Perhaps brighton doesn't work in 64 bits? Or do I need to
look elsewhere?
Regards
Larry
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
