18 Sep
2006
18 Sep
'06
6:06 p.m.
Bristol has been updated with a user configurable ARP 2600 synth. It has the
usual pre-patching as the original and, additionally, outputs can be
redirected to arbitrary inputs. This was a few changes to bristol to adjust
the engine buffer management for data that may feed back on itself, and
additionally a few extra operators for electroswitches, reverb and ring-mod,
etc. The envelope follower has not been tested at all and not all the patch
possibilities either as there are honestly too many to go through - about
600 possibilities with just a single cable.
The biggest changes were in the GUI. To support the user patches an extra
layer was added for their representation, then this was converted into a
transparency layer so the cables can be layered over the GUI to allow
control of the parameters without them 'getting in the way', then the cables
were coloured perhaps somewhat randomly - yellow patches carry signal left
to right, red cables carry signal right to left when see from the user
interface.
Once that was done I put in a cheesy watermarked logo - you can clear it
with the 'l' key or use the '-logo' option on the command line, but the
effect was too good to miss out on. The transparency can be toggled with the
't' key to allow you to foreground and background the layer, and
'o'/'O'
will adjust the depth of opacity. Load memory number 17, and play with the
'o' and 't' keys to get a feel for how the interface works. To patch,
select
an output (the jack sockets light up for outputs) and then select an input
(these are just 'momentary'). This will direct the new engine routing
algorithm for each voice and then paint in the GUI. To clear a patch just
select either jack socket at the cable ends.
The net output of the synth is reminiscent of the sounds from the BBC
Radiophonic Workshop's greatest ever hit - the theme tune to 'Dr Who'. If
you don't know what that is don't worry, it's perhaps a bit obscure. The
original was composed on the elder brother of this synth - the ARP 2500 of
which the BBC had a few, so the results came as a pleasant surprise.
Graphics can be seen on the sourceforge homepage. Downloads as well of
course.
https://sourceforge.net/project/screenshots.php?group_id=157415
Regards,
Nick.
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
19 Sep
19 Sep
5:20 a.m.
-downloaded 0.9.5-60
-read the directions
-built it on FC5
-tested a few of the synth models using jack and an external midi keyboard
-so far, so good
-need to spend some time testing your newest models
-thanks
Tracey
4:53 p.m.
Hi:
I had big fun with Bristol last night in my FC3/CCRMA machine. The ARP
2600 is fantastic, as are the Korgs.
Are there plans for other synth emulations ? I think you should do a
Synthi AKS, now
that you have some sort of patching capabilities....
cheers,
ernst
On 9/19/06, Tracey Hytry <shakti(a)bayarea.net> wrote:
-downloaded 0.9.5-60
-read the directions
-built it on FC5
-tested a few of the synth models using jack and an external midi keyboard
-so far, so good
-need to spend some time testing your newest models
-thanks
Tracey
--
"Both Rob and I see sound as shapes.
I only have to do this (makes a fist)
and he knows what sound I mean". - Autechre
:::::::::::::::::::::::::::::::::::::::::::
Ernie Dulanowsky CCNA CWLSS
www.pulsewidth.ca
> test_tones on www.cjtr.ca <<
21 Sep
21 Sep
3:05 p.m.
I get this
cc -g -fPIC -D_BRISTOL_JACK -I../include -I. -I/usr/local/include
-I/usr/include/jack bristoljack.o bristolmixer.o bristolprophet52.o
bristolobx.o bristolpoly.o bristolvox.o vox.o sdco.o sdcoutils.o
bristolsampler.o vibrachorus.o thesermon.o bristolexplorer.o filter2.o
lfo.o bristoldx.o hpf.o junodco.o bristoljuno.o dimensionD.o expdco.o
bristolsystem.o bristolhammond.o bristolprophet.o prophetdco.o filter.o
noise.o hammond.o audioEngine.o resonator.o dxop.o midihandlers.o
bristolmm.o midinote.o envelope.o dca.o rotary.o bristolmain.o dco.o
midithread.o audiothread.o soundManager.o -o bristol -L/usr/lib
-L/usr/local/lib -L../../slab/libslabaudio -L../libbristol
-L../libbristolmidi -L../libbristol -L/usr/lib/jack -Xlinker -Bdynamic
-lc -lm -lpthread -lasound -lbristol -lbristolmidi -lslabaudio -ljack
audiothread.o:(.data.rel+0x4c): undefined reference to `arpdcoinit'
audiothread.o:(.data.rel+0x50): undefined reference to `ringmodinit'
audiothread.o:(.data.rel+0x54): undefined reference to `eswitchinit'
audiothread.o:(.data.rel+0x58): undefined reference to `reverbinit'
audiothread.o:(.data.rel+0x5c): undefined reference to `followerinit'
audiothread.o:(.data.rel+0xcc): undefined reference to `bristolPoly6Init'
audiothread.o:(.data.rel+0xd0): undefined reference to `bristolAxxeInit'
audiothread.o:(.data.rel+0xd4): undefined reference to `bristolOdysseyInit'
audiothread.o:(.data.rel+0xd8): undefined reference to
`bristolMemoryMoogInit'
audiothread.o:(.data.rel+0xdc): undefined reference to `bristolArp2600Init'
collect2: ld returned 1 exit status
make[1]: *** [bristol] Error 1
make[1]: Leaving directory
`/var/tmp/portage/bristol-0.9.5.60/work/bristol-0.9.5/src/bristol/bristol'
make: *** [all] Error 2
Greetz
Frieder
3:50 p.m.
Frieder Bürzele wrote:
I get this
cc -g -fPIC -D_BRISTOL_JACK -I../include -I. -I/usr/local/include
-I/usr/include/jack bristoljack.o bristolmixer.o bristolprophet52.o
bristolobx.o bristolpoly.o bristolvox.o vox.o sdco.o sdcoutils.o
bristolsampler.o vibrachorus.o thesermon.o bristolexplorer.o filter2.o
lfo.o bristoldx.o hpf.o junodco.o bristoljuno.o dimensionD.o expdco.o
bristolsystem.o bristolhammond.o bristolprophet.o prophetdco.o
filter.o noise.o hammond.o audioEngine.o resonator.o dxop.o
midihandlers.o bristolmm.o midinote.o envelope.o dca.o rotary.o
bristolmain.o dco.o midithread.o audiothread.o soundManager.o -o
bristol -L/usr/lib -L/usr/local/lib -L../../slab/libslabaudio
-L../libbristol -L../libbristolmidi -L../libbristol -L/usr/lib/jack
-Xlinker -Bdynamic -lc -lm -lpthread -lasound -lbristol -lbristolmidi
-lslabaudio -ljack
audiothread.o:(.data.rel+0x4c): undefined reference to `arpdcoinit'
audiothread.o:(.data.rel+0x50): undefined reference to `ringmodinit'
audiothread.o:(.data.rel+0x54): undefined reference to `eswitchinit'
audiothread.o:(.data.rel+0x58): undefined reference to `reverbinit'
audiothread.o:(.data.rel+0x5c): undefined reference to `followerinit'
audiothread.o:(.data.rel+0xcc): undefined reference to `bristolPoly6Init'
audiothread.o:(.data.rel+0xd0): undefined reference to `bristolAxxeInit'
audiothread.o:(.data.rel+0xd4): undefined reference to
`bristolOdysseyInit'
audiothread.o:(.data.rel+0xd8): undefined reference to
`bristolMemoryMoogInit'
audiothread.o:(.data.rel+0xdc): undefined reference to
`bristolArp2600Init'
collect2: ld returned 1 exit status
make[1]: *** [bristol] Error 1
make[1]: Leaving directory
`/var/tmp/portage/bristol-0.9.5.60/work/bristol-0.9.5/src/bristol/bristol'
make: *** [all] Error 2
Greetz
Frieder
sorry for the noise it was my fault
24 Sep
24 Sep
11:42 a.m.
Was this from the 'build' script in the 'src' directory or from a make in
the engine directory? You can use the makefile directly, but the wrapper in
the src directory will build all the dependent libraries first. This is
still strange output though, the unresolved calls should be for sourcecode
resident in this directory.
Regards,
Nick.
From: Frieder Bürzele <linux-stuff(a)arcor.de>
Reply-To: A list for linux audio users
<linux-audio-user(a)music.columbia.edu>
To: A list for linux audio users <linux-audio-user(a)music.columbia.edu>
Subject: Re: [linux-audio-user] ANN: bristol 0.9.5-60
Date: Thu, 21 Sep 2006 19:34:54 +0200
Frieder Bürzele wrote:
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
I get this
cc -g -fPIC -D_BRISTOL_JACK -I../include -I. -I/usr/local/include
-I/usr/include/jack bristoljack.o bristolmixer.o bristolprophet52.o
bristolobx.o bristolpoly.o bristolvox.o vox.o sdco.o sdcoutils.o
bristolsampler.o vibrachorus.o thesermon.o bristolexplorer.o filter2.o
lfo.o bristoldx.o hpf.o junodco.o bristoljuno.o dimensionD.o expdco.o
bristolsystem.o bristolhammond.o bristolprophet.o prophetdco.o filter.o
noise.o hammond.o audioEngine.o resonator.o dxop.o midihandlers.o
bristolmm.o midinote.o envelope.o dca.o rotary.o bristolmain.o dco.o
midithread.o audiothread.o soundManager.o -o bristol -L/usr/lib
-L/usr/local/lib -L../../slab/libslabaudio -L../libbristol
-L../libbristolmidi -L../libbristol -L/usr/lib/jack -Xlinker -Bdynamic -lc
-lm -lpthread -lasound -lbristol -lbristolmidi -lslabaudio -ljack
audiothread.o:(.data.rel+0x4c): undefined reference to `arpdcoinit'
audiothread.o:(.data.rel+0x50): undefined reference to `ringmodinit'
audiothread.o:(.data.rel+0x54): undefined reference to `eswitchinit'
audiothread.o:(.data.rel+0x58): undefined reference to `reverbinit'
audiothread.o:(.data.rel+0x5c): undefined reference to `followerinit'
audiothread.o:(.data.rel+0xcc): undefined reference to `bristolPoly6Init'
audiothread.o:(.data.rel+0xd0): undefined reference to `bristolAxxeInit'
audiothread.o:(.data.rel+0xd4): undefined reference to
`bristolOdysseyInit'
audiothread.o:(.data.rel+0xd8): undefined reference to
`bristolMemoryMoogInit'
audiothread.o:(.data.rel+0xdc): undefined reference to
`bristolArp2600Init'
collect2: ld returned 1 exit status
make[1]: *** [bristol] Error 1
make[1]: Leaving directory
`/var/tmp/portage/bristol-0.9.5.60/work/bristol-0.9.5/src/bristol/bristol'
make: *** [all] Error 2
Greetz
Frieder
sorry for the noise it was my fault
25 Sep
25 Sep
10:07 p.m.
Nick Copeland wrote:
Was this from the 'build' script in the
'src' directory or from a make
in the engine directory? You can use the makefile directly, but the
wrapper in the src directory will build all the dependent libraries
first. This is still strange output though, the unresolved calls
should be for sourcecode resident in this directory.
Regards,
Nick.
I bumped a gentoo ebuild to the new bristol version, but forgot to
delete the makefile patch
which was needed for the old bristol version
Frieder
From: Frieder Bürzele
<linux-stuff(a)arcor.de>
Reply-To: A list for linux audio users
<linux-audio-user(a)music.columbia.edu>
To: A list for linux audio users <linux-audio-user(a)music.columbia.edu>
Subject: Re: [linux-audio-user] ANN: bristol 0.9.5-60
Date: Thu, 21 Sep 2006 19:34:54 +0200
Frieder Bürzele wrote:
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's
FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
I get this
cc -g -fPIC -D_BRISTOL_JACK -I../include -I. -I/usr/local/include
-I/usr/include/jack bristoljack.o bristolmixer.o bristolprophet52.o
bristolobx.o bristolpoly.o bristolvox.o vox.o sdco.o sdcoutils.o
bristolsampler.o vibrachorus.o thesermon.o bristolexplorer.o
filter2.o lfo.o bristoldx.o hpf.o junodco.o bristoljuno.o
dimensionD.o expdco.o bristolsystem.o bristolhammond.o
bristolprophet.o prophetdco.o filter.o noise.o hammond.o
audioEngine.o resonator.o dxop.o midihandlers.o bristolmm.o
midinote.o envelope.o dca.o rotary.o bristolmain.o dco.o
midithread.o audiothread.o soundManager.o -o bristol -L/usr/lib
-L/usr/local/lib -L../../slab/libslabaudio -L../libbristol
-L../libbristolmidi -L../libbristol -L/usr/lib/jack -Xlinker
-Bdynamic -lc -lm -lpthread -lasound -lbristol -lbristolmidi
-lslabaudio -ljack
audiothread.o:(.data.rel+0x4c): undefined reference to `arpdcoinit'
audiothread.o:(.data.rel+0x50): undefined reference to `ringmodinit'
audiothread.o:(.data.rel+0x54): undefined reference to `eswitchinit'
audiothread.o:(.data.rel+0x58): undefined reference to `reverbinit'
audiothread.o:(.data.rel+0x5c): undefined reference to `followerinit'
audiothread.o:(.data.rel+0xcc): undefined reference to
`bristolPoly6Init'
audiothread.o:(.data.rel+0xd0): undefined reference to
`bristolAxxeInit'
audiothread.o:(.data.rel+0xd4): undefined reference to
`bristolOdysseyInit'
audiothread.o:(.data.rel+0xd8): undefined reference to
`bristolMemoryMoogInit'
audiothread.o:(.data.rel+0xdc): undefined reference to
`bristolArp2600Init'
collect2: ld returned 1 exit status
make[1]: *** [bristol] Error 1
make[1]: Leaving directory
`/var/tmp/portage/bristol-0.9.5.60/work/bristol-0.9.5/src/bristol/bristol'
make: *** [all] Error 2
Greetz
Frieder
sorry for the noise it was my fault 
24 Sep
24 Sep
9:36 p.m.
Hello,
thanks for the new version, have to check out.
The net output of the synth is reminiscent of the
sounds from the BBC
Radiophonic Workshop's greatest ever hit - the theme tune to 'Dr Who'.
If you don't know what that is don't worry, it's perhaps a bit obscure.
The original was composed on the elder brother of this synth - the ARP
2500 of which the BBC had a few, so the results came as a pleasant
surprise.
?
The theme was produced around 1963 before the ARP was available, it was
realized by the incredible Delia Derbyshire with the help of some
oscillators, filters and in the first place, tape splicing techniques.
Maybe later renditions are created with an ARP but more likly on a
Synthi 100 (the model at BBC was dubbed Delaware) which is actually a
modular synth.
Check out
http://www.delia-derbyshire.org/
EMS Synthis with patch cords are the Synthi Logic and Synthi E
http://www.emsrehberg.de/SYNTHI__s/synthi__s.html
but I guess most of the wirednes of the Synthis came from the
patchmatrix which might introduce lot of crosstalk.
When you simulate the MS20 filter I think you are rather close to the
EMS one. In a simular league the WASP might be too..
Cheers,
Malte
--
Malte Steiner
media art + development
-www.block4.com-
next events:
elektronengehirn exhibition, lecture + concert @ Piksel 2006, Bergen,
Norway 12.-15. october
more at blog 4, also available as rss feed:
http://java.block4.com/blog4/
29 Sep
29 Sep
11:07 a.m.
Nick Copeland wrote:
Bristol has been updated with a user configurable ARP
2600 synth. It
has the usual pre-patching as the original and, additionally, outputs
can be redirected to arbitrary inputs. This was a few changes to
bristol to adjust the engine buffer management for data that may feed
back on itself, and additionally a few extra operators for
electroswitches, reverb and ring-mod, etc. The envelope follower has
not been tested at all and not all the patch possibilities either as
there are honestly too many to go through - about 600 possibilities
with just a single cable.
The biggest changes were in the GUI. To support the user patches an
extra layer was added for their representation, then this was
converted into a transparency layer so the cables can be layered over
the GUI to allow control of the parameters without them 'getting in
the way', then the cables were coloured perhaps somewhat randomly -
yellow patches carry signal left to right, red cables carry signal
right to left when see from the user interface.
Once that was done I put in a cheesy watermarked logo - you can clear
it with the 'l' key or use the '-logo' option on the command line, but
the effect was too good to miss out on. The transparency can be
toggled with the 't' key to allow you to foreground and background the
layer, and 'o'/'O' will adjust the depth of opacity. Load memory
number 17, and play with the 'o' and 't' keys to get a feel for how
the interface works. To patch, select an output (the jack sockets
light up for outputs) and then select an input (these are just
'momentary'). This will direct the new engine routing algorithm for
each voice and then paint in the GUI. To clear a patch just select
either jack socket at the cable ends.
The net output of the synth is reminiscent of the sounds from the BBC
Radiophonic Workshop's greatest ever hit - the theme tune to 'Dr Who'.
If you don't know what that is don't worry, it's perhaps a bit
obscure. The original was composed on the elder brother of this synth
- the ARP 2500 of which the BBC had a few, so the results came as a
pleasant surprise.
Graphics can be seen on the sourceforge homepage. Downloads as well of
course.
https://sourceforge.net/project/screenshots.php?group_id=157415
Regards,
Nick.
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's
FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
hi, very nice application, since bristol is now jack-capable.
in my case rhodes, and rhodes-bass arent working, segfault?
but the question that i have is, what i should copy in to usr/local/bin
or /usr/local/lib, so that i can put some menu-entries, so being able to
start from menu?
cheers,
doc
11:22 a.m.
rhodes, and rhodes-bass arent working, segfault?
Not the first complaint about these algorithms failing. To test it you
minimally need read access to the whole tree where you installed and built
bristol so that you can read the memories, then use the startBristol script
in the bin directory: 'startBristol -rhodes'. That is supposed to work, and
if that is how you get segmentation faults then I could do with the output
from a gdb stack backtrace ('gdb <bristol> <core>' then type in
"backtrace",
or a core file sent directly to me).
copy in to /usr/local/bin or /usr/local/lib, so that i
can put some
menu-entries, so being able to start from menu?
Hm, this is the second request for an install operation. Can you not build
in the full path to the startBristol script, with options, as a menu
command? Is the issue here that libraries cannot be found due to root
permissions and security or that binaries cannot be found if the path is not
configured correctly?
Kind regards,
nick.
_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
11:50 a.m.
Nick Copeland wrote:
i looked now following your instructions, it is not a segfault,
but
zombifying jack.
i did:
cd /software/nove/bristol/bristol-0.9.5/bin$
and then:
./startBristol -rhodes -jack
the roads piano appears, it is connected to jack, but trying to play the
keys, no sound, than short time after rhodes stops:
nowhiskey@murija2:~/software/nove/bristol/bristol-0.9.5/bin$
./startBristol -rhodes -jack
spawning midi thread
parent going into idle loop
connected to :0.0 (81492f0)
display is 1024 by 768 pixels
Window is w 1024, h 768, d 24, 0 0 0
Using DirectColor display
masks are ff0000 ff0000 ff0000
Initialise the rhodes link to bristol: 814dd50
midi sequencer
Opened listening control socket: 5028
Client ID = 129
Queue ID = 0
Device name did not parse, defaults 128.0
hostname is localhost, bristol
port is 5028
Connected to the bristol control socket: 5
bristolengine already active
Accepted connection from 0 (3) onto 2 (5)
created 16 voices: allocated 16 to synth
engine MIDI channel 0
spawning audio thread
registering jack interface
Rescheduled thread: 95
initialising one DX sound
done create interface: 81490c0, 814dd50
brightonWorldChanged(750 250 10 10)
going operational
Found port alsa_pcm:playback_1
Found port alsa_pcm:playback_2
Default connection bristol:out_left to alsa_pcm:playback_1
Default connection bristol:out_right to alsa_pcm:playback_2
Found port alsa_pcm:capture_1
Found port alsa_pcm:capture_2
Default connection alsa_pcm:capture_1 to bristol:in
zombified - calling shutdown handler
unregistering jack interface
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
request acked: -1
nowhiskey@murija2:~/software/nove/bristol/bristol-0.9.5/bin$
------------
please give me a more precisely "howto" for using "gdb"
this part i really dont understand, but i think it is a less problem,
since i can copy the hole build dir somewhere, and than make the
different menu-entries.
cheers,
doc
rhodes, and
rhodes-bass arent working, segfault?
Not the first complaint about these algorithms failing. To test it you
minimally need read access to the whole tree where you installed and
built bristol so that you can read the memories, then use the
startBristol script in the bin directory: 'startBristol -rhodes'. That
is supposed to work, and if that is how you get segmentation faults
then I could do with the output from a gdb stack backtrace ('gdb
<bristol> <core>' then type in "backtrace", or a core file sent
directly to me). copy in to /usr/local/bin or /usr/local/lib, so
that i can put some
menu-entries, so being able to start from menu?
Hm, this is the second request for an install operation. Can you not
build in the full path to the startBristol script, with options, as a
menu command? Is the issue here that libraries cannot be found due to
root permissions and security or that binaries cannot be found if the
path is not configured correctly?
Kind regards,
nick.
_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
12:09 p.m.
The 'zombied' message from jack and the 'midi write error' from brighton
indicate that bristol, the engine, has ungracefully exit, most typically a
segfault. Depending on your shell and write permissions on the 'bin'
directory you may be able to do the following:
nowhiskey@murija2:~/software/nove/bristol/bristol-0.9.5/bin$ limit
coredumpsize unlimited
nowhiskey@murija2:~/software/nove/bristol/bristol-0.9.5/bin$ ./startBristol
-rhodes -jack
Now do whatever until the error occurs and if you now close the synth window
from the title bar you will get a core dump IF you have write permissions in
the current directory. If you do not want to have write permissions on the
bristol/bin directory then try the following:
nowhiskey@murija2:~/software/nove/bristol/bristol-0.9.5/bin$ cd /tmp
nowhiskey@murija2:/tmp$ ~/software/nove/bristol/bristol-0.9.5/startBristol
-rhodes -jack
The coredump as an enclosure, or the stack backtrace from GDB will help to
track down the cause of the problem.
Regards,
Nick.
From: Dragan Noveski <perodog(a)gmx.net>
Reply-To: A list for linux audio users
<linux-audio-user(a)music.columbia.edu>
To: A list for linux audio users <linux-audio-user(a)music.columbia.edu>
Subject: Re: [linux-audio-user] ANN: bristol 0.9.5-60
Date: Fri, 29 Sep 2006 15:52:46 +0200
Nick Copeland wrote:
i looked now following
your instructions, it is not a segfault, but
zombifying jack.
i did:
cd /software/nove/bristol/bristol-0.9.5/bin$
and then:
./startBristol -rhodes -jack
the roads piano appears, it is connected to jack, but trying to play the
keys, no sound, than short time after rhodes stops:
nowhiskey@murija2:~/software/nove/bristol/bristol-0.9.5/bin$ ./startBristol
-rhodes -jack
spawning midi thread
parent going into idle loop
connected to :0.0 (81492f0)
display is 1024 by 768 pixels
Window is w 1024, h 768, d 24, 0 0 0
Using DirectColor display
masks are ff0000 ff0000 ff0000
Initialise the rhodes link to bristol: 814dd50
midi sequencer
Opened listening control socket: 5028
Client ID = 129
Queue ID = 0
Device name did not parse, defaults 128.0
hostname is localhost, bristol
port is 5028
Connected to the bristol control socket: 5
bristolengine already active
Accepted connection from 0 (3) onto 2 (5)
created 16 voices: allocated 16 to synth
engine MIDI channel 0
spawning audio thread
registering jack interface
Rescheduled thread: 95
initialising one DX sound
done create interface: 81490c0, 814dd50
brightonWorldChanged(750 250 10 10)
going operational
Found port alsa_pcm:playback_1
Found port alsa_pcm:playback_2
Default connection bristol:out_left to alsa_pcm:playback_1
Default connection bristol:out_right to alsa_pcm:playback_2
Found port alsa_pcm:capture_1
Found port alsa_pcm:capture_2
Default connection alsa_pcm:capture_1 to bristol:in
zombified - calling shutdown handler
unregistering jack interface
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
request acked: -1
nowhiskey@murija2:~/software/nove/bristol/bristol-0.9.5/bin$
------------
please give me a more precisely "howto" for using "gdb"
this part i really dont understand, but i think it is a less problem, since
i can copy the hole build dir somewhere, and than make the different
menu-entries.
cheers,
doc
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
rhodes,
and rhodes-bass arent working, segfault?
Not the first complaint about these algorithms failing. To test it you
minimally need read access to the whole tree where you installed and built
bristol so that you can read the memories, then use the startBristol
script in the bin directory: 'startBristol -rhodes'. That is supposed to
work, and if that is how you get segmentation faults then I could do with
the output from a gdb stack backtrace ('gdb <bristol> <core>' then
type in
"backtrace", or a core file sent directly to me). copy in to /usr/local/bin or /usr/local/lib, so
that i can put some
menu-entries, so being able to start from menu?
Hm, this is the second request for an install operation. Can you not build
in the full path to the startBristol script, with options, as a menu
command? Is the issue here that libraries cannot be found due to root
permissions and security or that binaries cannot be found if the path is
not configured correctly?
Kind regards,
nick.
_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
12:33 p.m.
Nick Copeland wrote:
The 'zombied' message from jack and the
'midi write error' from
brighton indicate that bristol, the engine, has ungracefully exit,
most typically a segfault. Depending on your shell and write
permissions on the 'bin' directory you may be able to do the following:
nowhiskey@murija2:~/software/nove/bristol/bristol-0.9.5/bin$ limit
coredumpsize unlimited
as root, or as a user:
bash: limit: command not found
nowhiskey@murija2:~/software/nove/bristol/bristol-0.9.5/bin$
./startBristol -rhodes -jack
Now do whatever until the error occurs and if you now close the synth
window from the title bar you will get a core dump IF you have write
permissions in the current directory. If you do not want to have write
permissions on the bristol/bin directory then try the following:
nowhiskey@murija2:~/software/nove/bristol/bristol-0.9.5/bin$ cd /tmp
nowhiskey@murija2:/tmp$
~/software/nove/bristol/bristol-0.9.5/startBristol -rhodes -jack
not sure if this is right:
nowhiskey@murija2:/tmp$
/home/nowhiskey/software/nove/bristol/bristol-0.9.5/bin/startBristol
-rhodes -jack
spawning midi thread
parent going into idle loop
midi sequencer
Opened listening control socket: 5028
connected to :0.0 (81492f0)
display is 1024 by 768 pixels
Window is w 1024, h 768, d 24, 0 0 0
Using DirectColor display
masks are ff0000 ff0000 ff0000
Initialise the rhodes link to bristol: 814dd50
Client ID = 129
Queue ID = 0
Device name did not parse, defaults 128.0
hostname is localhost, bristol
port is 5028
Connected to the bristol control socket: 5
bristolengine already active
Accepted connection from 0 (3) onto 2 (5)
created 16 voices: allocated 16 to synth
engine MIDI channel 0
spawning audio thread
registering jack interface
Rescheduled thread: 95
initialising one DX sound
done create interface: 81490c0, 814dd50
brightonWorldChanged(750 250 10 10)
going operational
Found port alsa_pcm:playback_1
Found port alsa_pcm:playback_2
Default connection bristol:out_left to alsa_pcm:playback_1
Default connection bristol:out_right to alsa_pcm:playback_2
Found port alsa_pcm:capture_1
Found port alsa_pcm:capture_2
Default connection alsa_pcm:capture_1 to bristol:in
zombified - calling shutdown handler
unregistering jack interface
midi write error, fd 5, size 1
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
request acked: -1
nowhiskey@murija2:/tmp$
cheers,
doc
The coredump as an enclosure, or the stack backtrace from GDB will
help to track down the cause of the problem.
Regards,
Nick.
11:48 a.m.
On Mon, Sep 18, 2006 at 10:03:49PM +0200, Nick Copeland wrote:
The net output of the synth is reminiscent of the
sounds from the BBC
Radiophonic Workshop's greatest ever hit - the theme tune to 'Dr Who'. If
you don't know what that is don't worry, it's perhaps a bit obscure. The
original was composed on the elder brother of this synth - the ARP 2500 of
which the BBC had a few, so the results came as a pleasant surprise.
Can it process external inputs? Or patch e.g. the hammond output into
the ARP input?
If so, feed an organ sound into an ARP patch for some Won't Get Fooled
Again fun :)
--
Paul Winkler
http://www.slinkp.com
12:02 p.m.
Can [the ARP 2600] process external inputs?
It is coded to do so, however this is one part that has not been tested, at
all, so your millage will not exactly vary as it will probably be more like
petrol into a diesel tank. I also think you will get different results from
jack vs alsa drivers as they are organised differently within bristol.
feed an organ sound into an ARP patch for some
Won't Get Fooled Again fun
:)
That is currently not possible but is on the list of enhancements.
Eventually bristol may register each synth as separate IO into jack, so you
can then tie it all together as you like. The dirty workaround of invoking
two bristol into jack will also fail as the name space 'bristol' may clash?
I was considering putting the pid into the registration to avoid this issue,
but that remains mildly ugly.
Regards,
Nick.
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
2 Oct
2 Oct
10:21 a.m.
On 9/29/06, Nick Copeland <nickycopeland(a)hotmail.com> wrote:
Why not put the synth name in the IO port name? Unless you already
do, in which case I'm not sure what you mean by a namespace clash.
Can [the ARP
2600] process external inputs?
It is coded to do so, however this is one part that has not been tested, at
all, so your millage will not exactly vary as it will probably be more like
petrol into a diesel tank. I also think you will get different results from
jack vs alsa drivers as they are organised differently within bristol.
feed an organ sound into an ARP patch for some
Won't Get Fooled Again fun
:)
That is currently not possible but is on the list of enhancements.
Eventually bristol may register each synth as separate IO into jack, so you
can then tie it all together as you like. The dirty workaround of invoking
two bristol into jack will also fail as the name space 'bristol' may clash?
I was considering putting the pid into the registration to avoid this issue,
but that remains mildly ugly.
Regards,
Nick.
11:11 a.m.
Why not put the synth name in the IO port name? Unless
you already
do, in which case I'm not sure what you mean by a namespace clash.
There are problems here due to the engine being multitimbral, so a few
examples:
1. Single engine, multiple emulations (multitimbral Hammond and ARP 2600):
If the bristol engine first registers with the synth name then it starts
using Hammond for its IO. Then the signal from ARP 2600, which is started
afterwards, will come from the outputs named Hammond which is rather
ambiguous. This could almost be resolved with registering separate IO for
each emulation, but there there is case 2:
2. Single engine, multiple emulations (Prophet-5 and another Prophet-5):
These might be two different invocations of the same synth, however at the
same time this is pretty much how the Prophet-10 works (and the OBXa, and
the B3 kind of). This causes other issues with available namespace inside
the single registration. Why should a user not be able to have two Mini Moog
operating simultaneously using either methods described above? Neither
solution to case 1 or case 2 address this possibility.
2. Multiple Engines
Each engine would be affected by both of the above issues. Bristol was
designed to be able to produce all emulations simultenously.
The current 'workaround', which has not been uploaded yet, is that bristol
will register as itself. If that fails it will attempt to register
'bristol_<pid>'. This may cause other issues regarding LASH understanding
the use of a PID in connection settings as the PID will invariably change
between invocations? LASH support it not actually there yet, but it is on
the horizon so obviously needs to be considered whilst solving this problem.
All output from each synth us still currently collapsed by bristol onto the
same stereo outputs, this may give issues with mixing, obviously.
I am open to suggestions. Should the user give an optional registration
name? Even that goes against the grain of usability.
Regards,
Nick.
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
6759
days inactive
6773
days old
linux-audio-user@lists.linuxaudio.org
16 comments
8 participants
participants (8)
-
Dragan Noveski -
Ernie Dulanowsky -
Frieder Bürzele -
Malte Steiner -
Nick Copeland -
Paul Coccoli -
Paul Winkler -
Tracey Hytry