15 Apr
2007
15 Apr
'07
1 p.m.
Anyone been successful at running Bristol on FC6 x86_64 ?
I get is the following (complete console output available):
# bristol -jack -mini
[...]
/usr/share/bristol/bin/startBristol: line 302: 22346 Erreur de
segmentation $BRISTOL/bin/brighton $* -engine
And although that par tof the program has bailed out, there's still in
'ps aux':
/usr/share/bristol/bin/bristol -rate 48000 -count 102
And jack has bristol entries for both audio and MIDI. Hey, if I
actually try this with a MIDI keyboard...
Nope. No sound. Anyways, there's no GUI to change sound parameters.
Anyone been successful at running Bristol on FC6 x86_64 ?
15 Apr
15 Apr
1:15 p.m.
On 4/15/07, lanas <lanas(a)securenet.net> wrote:
Anyone been successful at running Bristol on FC6 x86_64 ?
Well, my first attempt at compiling it for x86_64 showed a few dozen casting
issues of the form:
audioGUI.c: In function 'getControllerName':
audioGUI.c:160: warning: cast to pointer from integer of different size
audioGUI.c:163: warning: cast to pointer from integer of different size
These are probably responsible for your segfault. Bristol - at least the
version I'm looking at - was last worked on in 2002. Perhaps there's a later
version in a cvs or svn tree somewhere?
Finding all the spots where these casts occur and redefining the integers as
"size_t" will address this particular issue.
I get is the following (complete console output available):
>
>
> # bristol -jack -mini
>
> [...]
> /usr/share/bristol/bin/startBristol: line 302: 22346 Erreur de
> segmentation $BRISTOL/bin/brighton $* -engine
>
> And although that par tof the program has bailed out, there's still in
> 'ps aux':
>
> /usr/share/bristol/bin/bristol -rate 48000 -count 102
>
> And jack has bristol entries for both audio and MIDI. Hey, if I
> actually try this with a MIDI keyboard...
>
> Nope. No sound. Anyways, there's no GUI to change sound parameters.
Anyone been successful at running Bristol on FC6 x86_64 ?
>
>
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
>
--
Mike Taht
PostCards From the Bleeding Edge
http://the-edge.blogspot.com
1:47 p.m.
On 4/15/07, Mike Taht <mike.taht(a)gmail.com> wrote:
On 4/15/07, lanas <lanas(a)securenet.net> wrote:
OK, found the latest and greatest on
https://sourceforge.net/project/showfiles.php?group_id=157415
I only got one casting error while building the latest version, (0.9.6), but
it bombed out on linking... fixing now...
Finding all the spots where these casts occur and redefining the integers as
Anyone been successful at running Bristol on FC6 x86_64 ?
Well, my first attempt at compiling it for x86_64 showed a few dozen
casting issues of the form:
audioGUI.c: In function 'getControllerName':
audioGUI.c:160: warning: cast to pointer from integer of different size
audioGUI.c:163: warning: cast to pointer from integer of different size
These are probably responsible for your segfault. Bristol - at least the
version I'm looking at - was last worked on in 2002. Perhaps there's a later
version in a cvs or svn tree somewhere?
"size_t" will address this particular
issue.
I get is the following (complete console output available):
--
Mike Taht
PostCards From the Bleeding Edge
http://the-edge.blogspot.com
# bristol -jack -mini
[...]
/usr/share/bristol/bin/startBristol: line 302: 22346 Erreur de
segmentation $BRISTOL/bin/brighton $* -engine
And although that par tof the program has bailed out, there's still in
'ps aux':
/usr/share/bristol/bin/bristol -rate 48000 -count 102
And jack has bristol entries for both audio and MIDI. Hey, if I
actually try this with a MIDI keyboard...
Nope. No sound. Anyways, there's no GUI to change sound parameters.
Anyone been successful at running Bristol on FC6 x86_64 ?
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
--
Mike Taht
PostCards From the Bleeding Edge
http://the-edge.blogspot.com
3:47 p.m.
On 4/15/07, Mike Taht <mike.taht(a)gmail.com> wrote:
A crude patch to convince bristol to compile and run on x86_64 FC6 can be
fetched from http://www.taht.net/~mtaht/bristol_for_x86_64.patch
It applies against bristol-0.9.6-121.src.031407.tgz from sourceforge.
Basically there were issues with altering an environment variable in place,
and issues finding the right lib dirs for x86_64.
The patch is not pretty, but seems to work in my 5 minutes of
experimentation (how to get it to talk to my midi keyboard via jack's
connections?)
Bristol, on the other hand, is quite pretty. I confess, now, that at least
part of my scorn for the VST UIs on other platforms was mere jealousy, as I
didn't have them for Linux. Nice stuff.
On 4/15/07, lanas <lanas(a)securenet.net > wrote:
OK, found the latest and greatest on
https://sourceforge.net/project/showfiles.php?group_id=157415
I only got one casting error while building the latest version, ( 0.9.6),
but it bombed out on linking... fixing now...
Finding all the spots where these casts occur and redefining the integers
--
Mike Taht
PostCards From the Bleeding Edge
http://the-edge.blogspot.com
Anyone been successful at running Bristol on FC6 x86_64 ?
Well, my first attempt at compiling it for x86_64 showed a few dozen
casting issues of the form:
audioGUI.c: In function 'getControllerName':
audioGUI.c:160: warning: cast to pointer from integer of different size
audioGUI.c:163: warning: cast to pointer from integer of different size
These are probably responsible for your segfault. Bristol - at least the
version I'm looking at - was last worked on in 2002. Perhaps there's a later
version in a cvs or svn tree somewhere?
as "size_t" will address this
particular issue.
I get is the following (complete console output available):
--
Mike Taht
PostCards From the Bleeding Edge
http://the-edge.blogspot.com
# bristol -jack -mini
[...]
/usr/share/bristol/bin/startBristol: line 302: 22346 Erreur de
segmentation $BRISTOL/bin/brighton $* -engine
And although that par tof the program has bailed out, there's still in
'ps aux':
/usr/share/bristol/bin/bristol -rate 48000 -count 102
And jack has bristol entries for both audio and MIDI. Hey, if I
actually try this with a MIDI keyboard...
Nope. No sound. Anyways, there's no GUI to change sound parameters.
Anyone been successful at running Bristol on FC6 x86_64 ?
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
--
Mike Taht
PostCards From the Bleeding Edge
http://the-edge.blogspot.com 
17 Apr
17 Apr
7:50 p.m.
New subject: problems with Bristol on x86_64 was Re: Bristol on FC6 x86_64 ?
Greetings:
I built Bristol on a 64Studio system today, but I have troubles:
dlphilp@64studio:~/bristol-0.9.6/bin$ ./startBristol -jack -dx
./startBristol: line 202: [: too many arguments
Bristol is about to start.
This program is totally unrelated to ANY of the companies that produced
the original intruments emulated by bristol, and none of the original
manufacturers in ANY way endorse this product.
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 (66c440)
display is 1280 by 1024 pixels
Window is w 1280, h 1024, d 24, 0 0 0
Using DirectColor display
masks are ff0000 ff0000 ff0000
connected to :0.0 (5cc430)
display is 1280 by 1024 pixels
Window is w 1280, h 1024, d 24, 0 0 0
Using DirectColor display
masks are ff0000 ff0000 ff0000
flags are 8a000000
midi sequencer
Problem with bind
Could not open control listening socket: 0
No controlling socket available: anticipating MIDI
Error opening control device, exiting midi thread
Initialise the dx link to bristol: 672d10
Initialise the dx link to bristol: 5d1460
hostname is localhost, bristol
port is 5028
Connected to the bristol control socket: 5
acceptConnection(0)
bristolengine already active
Accepted connection from 0 (3) onto 2 (5)
bristolSystem(127, 0, 64) 10
flags are 2010
configured 16 voices
message from 2, 0
hostname is localhost, bristol
port is 5028
connfailed
opening link to engine: -1
hostname is localhost, bristol
port is 5028
connfailed
cleanupBristol(-4)
bristolSystem(127, 0, 14) 0
flags are 700
2: 2 2
configuring midi channel to 0
bristolSystem(127, 0, 2) 0
flags are 100
going to attempt engine kickoff: 2000 (-1)
spawning audio thread
Could not reschedule thread to 1
init audio thread, 581ca0
bufsize is now 1024
bristolAudioOpen(/dev/audio, 44100, 1024, 8a000004)
audioOpen(0054f8a0, 0, 1024): /dev/audio
flags are now 2
Failed to open audio device "/dev/audio", flags 2
Problem opening audio device /dev/audio, exiting audio thread
bristolSystem(127, 0, 12) 3
flags are 603
1: 2 2
initialising one DX sound
return - no data in buffer
cleanupBrighton(0)
cleared sigpipe handler
cleanupBrighton(0)
midi write error, fd 5, size 1
midi write error, fd 5, size 12
midi write error, fd 5, size 1
return - no data in buffer
socket closed
parent exiting
request acked: -1
What's up with all that ? I've tried various other options, always with
the same results.
CPU is an AMD64 3200+.
Best,
dp
18 Apr
18 Apr
12:52 a.m.
New subject: problems with Bristol on x86_64 SOLVED
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, Apr 17, 2007 at 08:44:10PM -0400, Dave Phillips wrote:
Dave Phillips wrote:
What were the correct command line flags?
- -ken
Greetings:
I built Bristol on a 64Studio system today, but I have troubles:
[snip]
Never mind, I realized the command line flags weren't correct.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFGJYfVe8HF+6xeOIcRAv4MAKCpOOTwqjFPogJzUJ6XJbxnamdLywCggTT+
Og6Zxi3oHaEOhMsbuB1bsCQ=
=Yw/c
-----END PGP SIGNATURE-----
10:46 a.m.
New subject: problems with Bristol on x86_64 SOLVED
Ken Restivo wrote:
What were the correct command line flags?
Oops, sorry:
startBristol -dx -audio jack
Just using the -jack flag didn't work. With this command line the synth
starts fine and is easily connected in QJackCtl. The audio connection
gets made by default, MIDI can hook up any way I like.
Best,
dp
1:01 a.m.
New subject: problems with Bristol on x86_64 SOLVED
Dave Phillips wrote:
Dave Phillips wrote:
Hello Dave,
I'm also using Bristol on 64studio (version 1.0).
What synths are you using with Bristol? Maybe if you play with it a bit
in the near future, we can compare notes - I'm using the Hammond B3.
I don't have time tonight to dig up the details, but I do know I had to
hack a bit with the build process to put everything in the standard
bin,usr/lib, and home directories.
Also, I haven't figured out how to assign MIDI controllers to the
graphics controls, if there is a way. I may actually modify the source
to hardwire the MIDI controls I need. Even MIDI volume wasn't working on
me with the Hammond.
Larry
Greetings:
I built Bristol on a 64Studio system today, but I have troubles:
[snip]
Never mind, I realized the command line flags weren't correct.
Best,
dp
5:14 a.m.
New subject: problems with Bristol on x86_64 SOLVED
Hi,
Actualy I don't use Bristol because I used to play real time, and without
any midi control, it's a bit difficult. So If you know how to assign Midi
controllers I would like too :)
thanks
Erwan
2007/4/18, Larry Troxler <lt(a)westnet.com>om>:
Dave Phillips wrote:
Dave Phillips wrote:
Hello Dave,
I'm also using Bristol on 64studio (version 1.0).
What synths are you using with Bristol? Maybe if you play with it a bit
in the near future, we can compare notes - I'm using the Hammond B3.
I don't have time tonight to dig up the details, but I do know I had to
hack a bit with the build process to put everything in the standard
bin,usr/lib, and home directories.
Also, I haven't figured out how to assign MIDI controllers to the
graphics controls, if there is a way. I may actually modify the source
to hardwire the MIDI controls I need. Even MIDI volume wasn't working on
me with the Hammond.
Larry
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
Greetings:
I built Bristol on a 64Studio system today, but I have troubles:
[snip]
Never mind, I realized the command line flags weren't correct.
Best,
dp
6:29 a.m.
New subject: problems with Bristol on x86_64 SOLVED
Hi All,
to hack a bit with the build process to put everything
in the standard
bin,usr/lib, and home directories.
There is an enhancement request open to put the source code under the GNU
tools including install option. Its not top of my list but it is there.
Also, I haven't figured out how to assign MIDI
controllers to the graphics
controls
The engine and GUI are separate elements. You need to aconnect the engine,
bristol, to a keyboard to be able play it. You also need to connect the GUI,
brighton, to a MIDI controller to be able to drive the GUI. This is also
with aconnect and both bristol and brighton should be visible. Then, place
the mouse over the GUI device you want to control and press the middle mouse
button, then joggle the MIDI control you want to drive it from.
Even MIDI volume wasn't working on me with the
Hammond.
There are a few things here. MIDI volume is a GM2 controller however these
go through the GUI, not through the engine, so it would still need to be
connected up to the GUI for them to possibly work. If you are actually after
a swell pedal I will check the code. The engine does have access to all the
MIDI controllers but only responds, per default, to few of them (pitchbend,
modwheel, and some pressure tracking). It would make sense for some of the
synths to respond to typical input devices such as the pedal in the case of
the b3.
Regards,
Nick.
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
10:15 a.m.
New subject: problems with Bristol on x86_64 SOLVED
Nick Copeland wrote:
Hi Nick,
That's great news. I do see two different MIDI ports in the jack control
MIDI connections window. However, they both have the same name. They
are, for example, 131:0 (Bristol / To Bristol) and 133:0 (Bristol / To
Bristol). I had always thought that the second port was the lower manual
of the Hammond, but is this really the GUI port?
Is there a way to specify the port's name? Otherwise I don't see how I
can set up an automatic connection two the second port.
Larry
Also, I
haven't figured out how to assign MIDI controllers to the
graphics controls
The engine and GUI are separate elements. You need to aconnect the
engine, bristol, to a keyboard to be able play it. You also need to
connect the GUI, brighton, to a MIDI controller to be able to drive the
GUI. This is also with aconnect and both bristol and brighton should be
visible. Then, place the mouse over the GUI device you want to control
and press the middle mouse button, then joggle the MIDI control you want
to drive it from.
12:46 p.m.
New subject: problems with Bristol on x86_64 SOLVED
they both have the same name. They are, for example,
131:0 (Bristol / To
Bristol) and 133:0 (Bristol / To Bristol).
That may be my fault. The two interfaces are for the engine and GUI
respectively, for the engine to accept note events and for the GUI also to
accept controller mappings. They should have different names but perhaps I
need to check what I am passing in the library.
I had always thought that the second port was the lower
manual of the
Hammond, but is this really the GUI port?
Yeah, it should be the GUI. The dual manual synths (Hammond, Prophet-10 and
OB-Xa) all take a MIDI channel for one manual and the same channel '+ 1' for
the second manual or layer. This behaviour cannot be changed at the moment,
at least not without a compiler.
Regards,
Nick.
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
19 Apr
19 Apr
1:16 a.m.
New subject: problems with Bristol on x86_64 SOLVED
Nick Copeland wrote:
The dual manual synths (Hammond, Prophet-10
and OB-Xa) all take a MIDI channel for one manual and the same channel
'+ 1' for the second manual or layer. This behaviour cannot be changed
at the moment, at least not without a compiler.
Regards,
Nick.
Ah, thanks, I didn't know that. My own opinion is that this behavior is
fine, and better than using two different ports anyway.
Larry
20 Apr
20 Apr
4:08 p.m.
Le Sun, 15 Apr 2007 10:47:19 -0700,
"Mike Taht" <mike.taht(a)gmail.com> a écrit :
http://www.taht.net/~mtaht/bristol_for_x86_64.patch It
applies
against bristol-0.9.6-121.src.031407.tgz from sourceforge.
Hi,
I get bristol running now, but how do you build it with the jack
option ? I get this:
./startBristol -jack -mini
jack driver requested, jackd not running
private jack configuration found in ~/.jackdrc
Requested Jack drivers, not compiled into bristol
In build I've changed 'no' to:
JACKPKG=yes
But still, it's the same. With alsa I get the GUI running.
Cheers,
Al
5:57 p.m.
On Fri, 2007-04-20 at 14:11 -0400, lanas wrote:
Le Sun, 15 Apr 2007 10:47:19 -0700,
"Mike Taht" <mike.taht(a)gmail.com> a écrit :
You probably don't have the jack headers and development files, maybe
sure you "yum install jack-audio-connection-kit-devel" before building.
-- Fernando
http://www.taht.net/~mtaht/bristol_for_x86_64.patch It applies
against bristol-0.9.6-121.src.031407.tgz from sourceforge.
Hi,
I get bristol running now, but how do you build it with the jack
option ? I get this:
./startBristol -jack -mini
jack driver requested, jackd not running
private jack configuration found in ~/.jackdrc
Requested Jack drivers, not compiled into bristol
In build I've changed 'no' to:
JACKPKG=yes
But still, it's the same. With alsa I get the GUI running.
6480
days inactive
6485
days old
linux-audio-user@lists.linuxaudio.org
15 comments
8 participants
participants (8)
-
Dave Phillips -
Fernando Lopez-Lezcano -
Ken Restivo -
lanas -
Larry Troxler -
Mike Taht -
Mysth-R -
Nick Copeland