Menu
▾
▴
linuxsampler-devel
|
From: Mark K. <mar...@gm...> - 2005-01-01 18:49:05
|
I have qsampler set up with three instruments - piano, bass and drums. Piano and drums are working well. Bass MIDI is muted in Pro Tools. The instant I turned on the bass MIDI channel the segfault occured: 10:41:17.396 Save session: "/home/mark/Chick.lscp". gig::Voice: No Region defined for MIDI key 52 Triggering new voice failed! gig::Voice: No Region defined for MIDI key 52 Triggering new voice failed! gig::Voice: No Region defined for MIDI key 52 Triggering new voice failed! gig::Voice: No Region defined for MIDI key 88 Triggering new voice failed! gig::Voice: No Region defined for MIDI key 52 Triggering new voice failed! gig::Voice: No Region defined for MIDI key 52 Triggering new voice failed! gig::Voice: No Region defined for MIDI key 52 Triggering new voice failed! gig::Voice: No Region defined for MIDI key 52 Triggering new voice failed! gig::Voice: No Region defined for MIDI key 55 Triggering new voice failed! gig::Voice: No Region defined for MIDI key 52 Triggering new voice failed! gig::Voice: No Region defined for MIDI key 52 Triggering new voice failed! gig::Voice: No Region defined for MIDI key 55 Triggering new voice failed! gig::Voice: No Region defined for MIDI key 55 Triggering new voice failed! gig::Voice: No Region defined for MIDI key 52 Triggering new voice failed! gig::Voice: No Region defined for MIDI key 52 Triggering new voice failed! gig::Voice: No Region defined for MIDI key 55 Triggering new voice failed! gig::Voice: No Region defined for MIDI key 55 Triggering new voice failed! >>> FATAL ERROR: Segmentation fault (SIGSEGV) occured! <<< Showing stack trace... No debugger found Killing LinuxSampler... lscp_client_recv: recv: Connection reset by peer lscp_client_call: send: Broken pipe lscp_client_call: send: Broken pipe lscp_client_call: send: Broken pipe lscp_client_call: send: Broken pipe lscp_client_call: send: Broken pipe lscp_client_call: send: Broken pipe lscp_client_call: send: Broken pipe lscp_client_call: send: Broken pipe 10:44:09.597 Client disconnecting... 10:44:09.615 Client disconnected. 10:44:09.617 Server was stopped with exit status 0. I do not know if the 'No region defined' messages were for the piano/drum channels or for the bass. How can I provide better info? This is a PlanetCCRMA FC2 box. gdb is not currently installed so I'll look into that. How do I compile LS/qsampler to give you better info? Thanks, Mark |
|
From: Mark K. <mar...@gm...> - 2005-01-01 19:10:20
|
On Sat, 1 Jan 2005 10:48:59 -0800, Mark Knecht <mar...@gm...> wrote: > I have qsampler set up with three instruments - piano, bass and drums. > Piano and drums are working well. Bass MIDI is muted in Pro Tools. The > instant I turned on the bass MIDI channel the segfault occured: > <SNIP> > >>> FATAL ERROR: Segmentation fault (SIGSEGV) occured! <<< > Showing stack trace... > No debugger found > Killing LinuxSampler... > lscp_client_recv: recv: Connection reset by peer > lscp_client_call: send: Broken pipe > lscp_client_call: send: Broken pipe > lscp_client_call: send: Broken pipe > lscp_client_call: send: Broken pipe > lscp_client_call: send: Broken pipe > lscp_client_call: send: Broken pipe > lscp_client_call: send: Broken pipe > lscp_client_call: send: Broken pipe > 10:44:09.597 Client disconnecting... > 10:44:09.615 Client disconnected. > 10:44:09.617 Server was stopped with exit status 0. > > I do not know if the 'No region defined' messages were for the > piano/drum channels or for the bass. The 'no region defined' messages are not part of this problem. I have redone the crash using only the bass MIDI channel. I get the crash with none of those message. The appear to be for the drum channel. (I think.I'll check later.) I wonder if this could be something like the 'malformed MIDI' issue that was reported by Garett yesterday? I'll see if amidirecord can capture the incoming MIDI that causes the crash. - Mark |
|
From: Mark K. <mar...@gm...> - 2005-01-01 19:18:34
|
On Sat, 1 Jan 2005 11:10:14 -0800, Mark Knecht <mar...@gm...> wrote:
>
> I wonder if this could be something like the 'malformed MIDI' issue
> that was reported by Garett yesterday? I'll see if amidirecord can
> capture the incoming MIDI that causes the crash.
>
> - Mark
>
And the winner is....... (drum roll) Control Change or Program Change?
[mark@Godzilla mark]$ arecordmidi --port 64:0 --dump
Chick-bass-midi.mid Waiting for data. Press Ctrl+C to end
_______Tick Event_________________ Ch _Data__
53411 Control change 1 7 96
53411 Program change 1 32
53591 Note on 1 50 76
53855 Control change 1 64 127
53981 Note on 1 50 0
54031 Control change 1 64 0
54037 Note on 1 57 70
54174 Control change 1 64 127
54392 Control change 1 64 0
54408 Note on 1 64 86
54410 Note on 1 57 0
54704 Control change 1 64 127
54816 Note on 1 64 0
54950 Note on 1 57 63
Pro Tools does not seem to have a way to not send these values. It
filters on the input side by not on the transmit side. I don't know
how to filter this on the LS machine. Since Garett reported the
malformed MIDI messages issue WRT a MIDI filter maybe that's not the
issue at all, but rather he just received these same sort of messages
also?
This MIDI file is a commercially available file that works fine with GSt.
Cheers,
Mark
|
|
From: Garett S. <shu...@co...> - 2005-01-01 19:43:58
|
I do get the No Region defined message quite often when I hit a key that... has not region defined. :) However, I haven't seen a segfault coralated with this. The malformed midi message was created by code similar to the following ev1->data.note.channel=ev2->data.control.value where ev1 is a noteon event and ev2 is a controller (sustain pedal) event. So I think that the channel value might be out of bounds. This code is pretty nonsensical and was written in error. However it did cause ls to segfault. Vlad, I have never tried to gdb over irc. I would be happy to learn how this is done if you think it would help. I'm pretty sharp with gdb and might just be able to get you the info you need myself (although I haven't familiarized myself with the ls code at all). Also, I could just make you a temporary account on my box and you could gdb through ssh. I tried the lastest cvs ls and have not seen a disk stream error yet with > 2 channels. Right on! Also, in regards to running ls as root... I just realized this morning that the voice dropping I had mentioned to the list last week was caused because I had not chmod +s linuxsampler . When I do not run ls as root on my system I get lots of audio artifacts and lots of voice dropping. -Garett Mark Knecht wrote: >I have qsampler set up with three instruments - piano, bass and drums. >Piano and drums are working well. Bass MIDI is muted in Pro Tools. The >instant I turned on the bass MIDI channel the segfault occured: > >10:41:17.396 Save session: "/home/mark/Chick.lscp". >gig::Voice: No Region defined for MIDI key 52 >Triggering new voice failed! >gig::Voice: No Region defined for MIDI key 52 >Triggering new voice failed! >gig::Voice: No Region defined for MIDI key 52 >Triggering new voice failed! >gig::Voice: No Region defined for MIDI key 88 >Triggering new voice failed! >gig::Voice: No Region defined for MIDI key 52 >Triggering new voice failed! >gig::Voice: No Region defined for MIDI key 52 >Triggering new voice failed! >gig::Voice: No Region defined for MIDI key 52 >Triggering new voice failed! >gig::Voice: No Region defined for MIDI key 52 >Triggering new voice failed! >gig::Voice: No Region defined for MIDI key 55 >Triggering new voice failed! >gig::Voice: No Region defined for MIDI key 52 >Triggering new voice failed! >gig::Voice: No Region defined for MIDI key 52 >Triggering new voice failed! >gig::Voice: No Region defined for MIDI key 55 >Triggering new voice failed! >gig::Voice: No Region defined for MIDI key 55 >Triggering new voice failed! >gig::Voice: No Region defined for MIDI key 52 >Triggering new voice failed! >gig::Voice: No Region defined for MIDI key 52 >Triggering new voice failed! >gig::Voice: No Region defined for MIDI key 55 >Triggering new voice failed! >gig::Voice: No Region defined for MIDI key 55 >Triggering new voice failed! > > >>>>FATAL ERROR: Segmentation fault (SIGSEGV) occured! <<< >>>> >>>> >Showing stack trace... >No debugger found >Killing LinuxSampler... >lscp_client_recv: recv: Connection reset by peer >lscp_client_call: send: Broken pipe >lscp_client_call: send: Broken pipe >lscp_client_call: send: Broken pipe >lscp_client_call: send: Broken pipe >lscp_client_call: send: Broken pipe >lscp_client_call: send: Broken pipe >lscp_client_call: send: Broken pipe >lscp_client_call: send: Broken pipe >10:44:09.597 Client disconnecting... >10:44:09.615 Client disconnected. >10:44:09.617 Server was stopped with exit status 0. > >I do not know if the 'No region defined' messages were for the >piano/drum channels or for the bass. > >How can I provide better info? This is a PlanetCCRMA FC2 box. gdb is >not currently installed so I'll look into that. How do I compile >LS/qsampler to give you better info? > >Thanks, >Mark > > >------------------------------------------------------- >The SF.Net email is sponsored by: Beat the post-holiday blues >Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. >It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt >_______________________________________________ >Linuxsampler-devel mailing list >Lin...@li... >https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel > > |
|
From: Vladimir S. <ha...@gm...> - 2005-01-01 20:46:54
|
Garett, > Vlad, I have never tried to gdb over irc. I would be happy to learn how > this is done if you think it would help. I'm pretty sharp with gdb and > might just be able to get you the info you need myself (although I > haven't familiarized myself with the ls code at all). Also, I could just > make you a temporary account on my box and you could gdb through ssh. sounds good. i'll be on irc.freenode.org #linuxsampler we can discuss this in detail. if you have time and desire, i'd be glad to hook you up with everything especially since you are already sharp with gdb. then in addition to your great testing and bugreports you'll be fixing bugs, adding features in no time! > I tried the lastest cvs ls and have not seen a disk stream error yet > with > 2 channels. Right on! good. > Also, in regards to running ls as root... I just realized this morning > that the voice dropping I had mentioned to the list last week was caused > because I had not chmod +s linuxsampler . > When I do not run ls as root on my system I get lots of audio artifacts > and lots of voice dropping. it might be an indication that your system doesn't have much free ram. One of the major differences between LS root vs non-root is memory can't be locked if it's not root. so it's probably getting swapped out and then there will definitely be issues. you can test that theory by doing swapoff -a and running non-root. I do that sometimes when i'm debugging a hang and i don't want LS to hang the whole system hard :) Regards, Vladimir. |
|
From: Mark K. <mar...@gm...> - 2005-01-01 20:25:15
|
On Sat, 1 Jan 2005 11:18:27 -0800, Mark Knecht <mar...@gm...> wrote:
> On Sat, 1 Jan 2005 11:10:14 -0800, Mark Knecht <mar...@gm...> wrote:
> >
> > I wonder if this could be something like the 'malformed MIDI' issue
> > that was reported by Garett yesterday? I'll see if amidirecord can
> > capture the incoming MIDI that causes the crash.
> >
> > - Mark
> >
>
> And the winner is....... (drum roll) Control Change or Program Change?
OK, so I've spent some more time looking at the MIDI files in Pro
Tools. The big difference between the bass channel that causes the
segfault and the other two channels is that the bass channel uses
sustain pedal events for almost every note.
222069 Control change 1 7 96
222070 Program change 1 32
222237 Note on 1 50 76
222501 Control change 1 64 127
222628 Note on 1 50 0
222677 Control change 1 64 0
222683 Note on 1 57 70
222821 Control change 1 64 127
223038 Control change 1 64 0
223054 Note on 1 64 86
223056 Note on 1 57 0
223351 Control change 1 64 127
223461 Note on 1 64 0
223597 Note on 1 57 63
223612 Control change 1 64 0
223776 Control change 1 64 127
224017 Note on 1 57 0
224039 Note on 1 50 73
224050 Control change 1 64 0
224292 Control change 1 64 127
Possibly LS is having trouble keeping up with that many controller
changes happening in real-time?
Jsut a guess.
- Mark
|
|
From: Mark K. <mar...@gm...> - 2005-01-01 21:26:02
|
On Sat, 1 Jan 2005 12:25:08 -0800, Mark Knecht <mar...@gm...> wrote:
> On Sat, 1 Jan 2005 11:18:27 -0800, Mark Knecht <mar...@gm...> wrote:
> > On Sat, 1 Jan 2005 11:10:14 -0800, Mark Knecht <mar...@gm...> wrote:
> > >
> > > I wonder if this could be something like the 'malformed MIDI' issue
> > > that was reported by Garett yesterday? I'll see if amidirecord can
> > > capture the incoming MIDI that causes the crash.
> > >
> > > - Mark
> > >
> >
> > And the winner is....... (drum roll) Control Change or Program Change?
>
> OK, so I've spent some more time looking at the MIDI files in Pro
> Tools. The big difference between the bass channel that causes the
> segfault and the other two channels is that the bass channel uses
> sustain pedal events for almost every note.
>
> 222069 Control change 1 7 96
> 222070 Program change 1 32
> 222237 Note on 1 50 76
> 222501 Control change 1 64 127
> 222628 Note on 1 50 0
> 222677 Control change 1 64 0
> 222683 Note on 1 57 70
> 222821 Control change 1 64 127
> 223038 Control change 1 64 0
> 223054 Note on 1 64 86
> 223056 Note on 1 57 0
> 223351 Control change 1 64 127
> 223461 Note on 1 64 0
> 223597 Note on 1 57 63
> 223612 Control change 1 64 0
> 223776 Control change 1 64 127
> 224017 Note on 1 57 0
> 224039 Note on 1 50 73
> 224050 Control change 1 64 0
> 224292 Control change 1 64 127
>
> Possibly LS is having trouble keeping up with that many controller
> changes happening in real-time?
>
> Jsut a guess.
>
> - Mark
>
I exported the MIDI file from Pro Tools and brought it over to Linux.
Using aplaymidi I tried playing it thus bypassing the hardware aspects
of this problem. Same segfault results (I think) but a little more
info.
Again, if I knew how to build LS to give more debug info maybe this
would look better. I don't know...
13:19:51.178 Client connecting...
13:19:51.180 Server is starting...
13:19:51.181 linuxsampler
13:19:51.208 Server was started with PID=18051.
lscp_client_create: cmd: connect: Connection refused
LinuxSampler 0.2
Copyright (C) 2003, 2004 by Benno Senoner and Christian Schoenebeck
Detected features: MMX SSE
Creating Sampler...OK
Registered MIDI input drivers: ALSA
Registered audio output drivers: ALSA,JACK
Starting LSCP network server (on TCP port 8888)...OK
13:19:53.420 Client connecting...
13:19:53.421 Client receive timeout is set to 6000 msec.
13:19:53.422 Client connected.
13:19:53.423 New session: "Untitled1".
LinuxSampler initialization completed.
LSCPServer: Client connection established on socket:4.
13:19:58.297 ADD CHANNEL
13:19:58.301 SET CHANNEL AUDIO_OUTPUT_TYPE 0 Jack
13:19:58.356 SET CHANNEL MIDI_INPUT_TYPE 0 Alsa
13:19:58.391 SET CHANNEL MIDI_INPUT_PORT 0 0
13:19:58.396 SET CHANNEL MIDI_INPUT_CHANNEL 0 0
13:19:58.400 LOAD ENGINE GigEngine 0
Starting disk thread...OK
13:19:58.785 LOAD INSTRUMENT NON_MODAL
'/mnt/audio1/Gigs/Pianos/Bardstown Audio/The Bosendorfer Imperial
Grand Version 2.2.gig' 0 0
13:19:58.812 SET CHANNEL VOLUME 0 0.4
13:19:58.822 ADD CHANNEL
13:19:58.827 SET CHANNEL AUDIO_OUTPUT_TYPE 1 Jack
13:19:58.830 SET CHANNEL MIDI_INPUT_TYPE 1 Alsa
13:19:58.835 SET CHANNEL MIDI_INPUT_PORT 1 0
13:19:58.840 SET CHANNEL MIDI_INPUT_CHANNEL 1 9
13:19:58.844 LOAD ENGINE GigEngine 1
Starting disk thread...OK
13:19:59.003 LOAD INSTRUMENT NON_MODAL
'/mnt/audio1/Gigs/Drums/Wizzo/Ambience Kit XXL.gig' 0 1
13:19:59.028 SET CHANNEL VOLUME 1 0.4
13:19:59.078 ADD CHANNEL
13:19:59.090 SET CHANNEL AUDIO_OUTPUT_TYPE 2 Jack
13:19:59.101 SET CHANNEL MIDI_INPUT_TYPE 2 Alsa
13:19:59.113 SET CHANNEL MIDI_INPUT_PORT 2 0
13:19:59.125 SET CHANNEL MIDI_INPUT_CHANNEL 2 1
13:19:59.136 LOAD ENGINE GigEngine 2
Loading gig file '/mnt/audio1/Gigs/Pianos/Bardstown Audio/The
Bosendorfer Imperial Grand Version 2.2.gig'...Starting disk
thread...Loading gig file '/mnt/audio1/Gigs/Drums/Wizzo/Ambience Kit
XXL.gig'...OK
13:19:59.381 LOAD INSTRUMENT NON_MODAL '/mnt/audio1/Gigs/Bass/East
West Bass/Fender/2PU SJZHRD B.gig' 0 2
13:19:59.418 SET CHANNEL VOLUME 2 0.4
Loading gig file '/mnt/audio1/Gigs/Bass/East West Bass/Fender/2PU
SJZHRD B.gig'...OK
Loading gig instrument...OK
Loading gig instrument...OK
Loading gig instrument...OK
Caching initial samples...OK
Caching initial samples...OK
OK
13:20:42.043 Open session: "/home/mark/Chick.lscp".
OK
Caching initial samples...>>> FATAL ERROR: Segmentation fault
(SIGSEGV) occured! <<<
Showing stack trace...
No debugger found
Using host libthread_db library "/lib/tls/libthread_db.so.1".
Attaching to program: /usr/bin/linuxsampler, process 18051
Reading symbols from /usr/lib/linuxsampler/liblinuxsampler.so.0...done.
Loaded symbols for /usr/lib/linuxsampler/liblinuxsampler.so.0
Reading symbols from /usr/lib/linuxsampler/libgig.so.0...done.
Loaded symbols for /usr/lib/linuxsampler/libgig.so.0
Reading symbols from /usr/lib/libjack.so.0...done.
Loaded symbols for /usr/lib/libjack.so.0
Reading symbols from /usr/lib/libasound.so.2...done.
Loaded symbols for /usr/lib/libasound.so.2
Reading symbols from /lib/libdl.so.2...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/tls/libpthread.so.0...done.
[Thread debugging using libthread_db enabled]
[New Thread -1209162112 (LWP 18051)]
[New Thread -1427514448 (LWP 18063)]
[Thread debugging using libthread_db enabled]
[New Thread -1209162112 (LWP 18051)]
[New Thread -1427514448 (LWP 18063)]
[Thread debugging using libthread_db enabled]
[New Thread -1209162112 (LWP 18051)]
[New Thread -1427514448 (LWP 18063)]
[New Thread -1365836880 (LWP 18060)]
[New Thread -1344386128 (LWP 18058)]
[New Thread -1284338768 (LWP 18056)]
[New Thread -1226388560 (LWP 18054)]
[New Thread -1217995856 (LWP 18053)]
[New Thread -1209164880 (LWP 18052)]
Loaded symbols for /lib/tls/libpthread.so.0
Reading symbols from /usr/lib/libstdc++.so.5...done.
Loaded symbols for /usr/lib/libstdc++.so.5
Reading symbols from /lib/tls/libm.so.6...done.
Loaded symbols for /lib/tls/libm.so.6
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/tls/libc.so.6...done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
0xffffe410 in ?? ()
(gdb) --- Stacktrace
#0 0xffffe410 in ?? ()
#1 0xbffffa58 in ?? ()
#2 0x4561dfdc in ?? () from /lib/tls/libc.so.6
#3 0xbffff8b4 in ?? ()
#4 0x4558c7f6 in __nanosleep_nocancel () from /lib/tls/libc.so.6
#5 0x4558c61f in sleep () from /lib/tls/libc.so.6
#6 0x0804961c in main (argc=-516, argv=0x0) at linuxsampler.cpp:118
--- Symbols
#4 0x4558c7f6 in __nanosleep_nocancel () from /lib/tls/libc.so.6
> > > >No symbol table info available.
#5 0x4558c61f in sleep () from /lib/tls/libc.so.6
No symbol table info available.
#6 0x0804961c in main (argc=-516, argv=0x0) at linuxsampler.cpp:118
118 sleep(1);
sFeatures = {static npos = 4294967295,
_M_dataplus = {<std::allocator<char>> = {<No data fields>},
_M_p = 0x804ce5c "CHANNELS"}, static _S_empty_rep_storage = {0, 0, 0, 0}}
sact = {__sigaction_handler = {sa_handler = 0x8049780 <signal_handler(int)>,
sa_sigaction = 0x8049780 <signal_handler(int)>}, sa_mask = {__val = {
0 <repeats 32 times>}}, sa_flags = 0, sa_restorer = 0}
---
Detaching from program: /usr/bin/linuxsampler, process 18051
Killing LinuxSampler...
13:21:28.916 Client disconnecting...
13:21:28.918 Client disconnected.
13:21:28.920 Server was stopped with exit status 0.
|
|
From: Vladimir S. <ha...@gm...> - 2005-01-01 21:42:54
|
Mark,
Interesing, from the output it looks like it crashed while loading
sample, even before the midi was sent to it. Or did i misunderstand
it?
I'm wondering if this could be reproduce with the single channel (bass
channel) just to simplify?
Also, if it does happen after MIDI is sent, i wonder if the same thing
happens if you load any other instrument (not bass) into this channel
and play the same MIDI to it.
In other words, it would be good to know if this is instrument specific or not.
It would be nice if it isn't. This way i'll be able to reproduce it
here and hopefully fix it (if you could send me the MIDI file).
Regards,
Vladimir.
On Sat, 1 Jan 2005 13:25:54 -0800, Mark Knecht <mar...@gm...> wrote:
> On Sat, 1 Jan 2005 12:25:08 -0800, Mark Knecht <mar...@gm...> wrote:
> > On Sat, 1 Jan 2005 11:18:27 -0800, Mark Knecht <mar...@gm...> wrote:
> > > On Sat, 1 Jan 2005 11:10:14 -0800, Mark Knecht <mar...@gm...> wrote:
> > > >
> > > > I wonder if this could be something like the 'malformed MIDI' issue
> > > > that was reported by Garett yesterday? I'll see if amidirecord can
> > > > capture the incoming MIDI that causes the crash.
> > > >
> > > > - Mark
> > > >
> > >
> > > And the winner is....... (drum roll) Control Change or Program Change?
> >
> > OK, so I've spent some more time looking at the MIDI files in Pro
> > Tools. The big difference between the bass channel that causes the
> > segfault and the other two channels is that the bass channel uses
> > sustain pedal events for almost every note.
> >
> > 222069 Control change 1 7 96
> > 222070 Program change 1 32
> > 222237 Note on 1 50 76
> > 222501 Control change 1 64 127
> > 222628 Note on 1 50 0
> > 222677 Control change 1 64 0
> > 222683 Note on 1 57 70
> > 222821 Control change 1 64 127
> > 223038 Control change 1 64 0
> > 223054 Note on 1 64 86
> > 223056 Note on 1 57 0
> > 223351 Control change 1 64 127
> > 223461 Note on 1 64 0
> > 223597 Note on 1 57 63
> > 223612 Control change 1 64 0
> > 223776 Control change 1 64 127
> > 224017 Note on 1 57 0
> > 224039 Note on 1 50 73
> > 224050 Control change 1 64 0
> > 224292 Control change 1 64 127
> >
> > Possibly LS is having trouble keeping up with that many controller
> > changes happening in real-time?
> >
> > Jsut a guess.
> >
> > - Mark
> >
>
> I exported the MIDI file from Pro Tools and brought it over to Linux.
> Using aplaymidi I tried playing it thus bypassing the hardware aspects
> of this problem. Same segfault results (I think) but a little more
> info.
>
> Again, if I knew how to build LS to give more debug info maybe this
> would look better. I don't know...
>
> 13:19:51.178 Client connecting...
> 13:19:51.180 Server is starting...
> 13:19:51.181 linuxsampler
> 13:19:51.208 Server was started with PID=18051.
> lscp_client_create: cmd: connect: Connection refused
> LinuxSampler 0.2
> Copyright (C) 2003, 2004 by Benno Senoner and Christian Schoenebeck
> Detected features: MMX SSE
> Creating Sampler...OK
> Registered MIDI input drivers: ALSA
> Registered audio output drivers: ALSA,JACK
> Starting LSCP network server (on TCP port 8888)...OK
> 13:19:53.420 Client connecting...
> 13:19:53.421 Client receive timeout is set to 6000 msec.
> 13:19:53.422 Client connected.
> 13:19:53.423 New session: "Untitled1".
> LinuxSampler initialization completed.
> LSCPServer: Client connection established on socket:4.
> 13:19:58.297 ADD CHANNEL
> 13:19:58.301 SET CHANNEL AUDIO_OUTPUT_TYPE 0 Jack
> 13:19:58.356 SET CHANNEL MIDI_INPUT_TYPE 0 Alsa
> 13:19:58.391 SET CHANNEL MIDI_INPUT_PORT 0 0
> 13:19:58.396 SET CHANNEL MIDI_INPUT_CHANNEL 0 0
> 13:19:58.400 LOAD ENGINE GigEngine 0
> Starting disk thread...OK
> 13:19:58.785 LOAD INSTRUMENT NON_MODAL
> '/mnt/audio1/Gigs/Pianos/Bardstown Audio/The Bosendorfer Imperial
> Grand Version 2.2.gig' 0 0
> 13:19:58.812 SET CHANNEL VOLUME 0 0.4
> 13:19:58.822 ADD CHANNEL
> 13:19:58.827 SET CHANNEL AUDIO_OUTPUT_TYPE 1 Jack
> 13:19:58.830 SET CHANNEL MIDI_INPUT_TYPE 1 Alsa
> 13:19:58.835 SET CHANNEL MIDI_INPUT_PORT 1 0
> 13:19:58.840 SET CHANNEL MIDI_INPUT_CHANNEL 1 9
> 13:19:58.844 LOAD ENGINE GigEngine 1
> Starting disk thread...OK
> 13:19:59.003 LOAD INSTRUMENT NON_MODAL
> '/mnt/audio1/Gigs/Drums/Wizzo/Ambience Kit XXL.gig' 0 1
> 13:19:59.028 SET CHANNEL VOLUME 1 0.4
> 13:19:59.078 ADD CHANNEL
> 13:19:59.090 SET CHANNEL AUDIO_OUTPUT_TYPE 2 Jack
> 13:19:59.101 SET CHANNEL MIDI_INPUT_TYPE 2 Alsa
> 13:19:59.113 SET CHANNEL MIDI_INPUT_PORT 2 0
> 13:19:59.125 SET CHANNEL MIDI_INPUT_CHANNEL 2 1
> 13:19:59.136 LOAD ENGINE GigEngine 2
> Loading gig file '/mnt/audio1/Gigs/Pianos/Bardstown Audio/The
> Bosendorfer Imperial Grand Version 2.2.gig'...Starting disk
> thread...Loading gig file '/mnt/audio1/Gigs/Drums/Wizzo/Ambience Kit
> XXL.gig'...OK
> 13:19:59.381 LOAD INSTRUMENT NON_MODAL '/mnt/audio1/Gigs/Bass/East
> West Bass/Fender/2PU SJZHRD B.gig' 0 2
> 13:19:59.418 SET CHANNEL VOLUME 2 0.4
> Loading gig file '/mnt/audio1/Gigs/Bass/East West Bass/Fender/2PU
> SJZHRD B.gig'...OK
> Loading gig instrument...OK
> Loading gig instrument...OK
> Loading gig instrument...OK
> Caching initial samples...OK
> Caching initial samples...OK
> OK
> 13:20:42.043 Open session: "/home/mark/Chick.lscp".
> OK
> Caching initial samples...>>> FATAL ERROR: Segmentation fault
> (SIGSEGV) occured! <<<
> Showing stack trace...
> No debugger found
> Using host libthread_db library "/lib/tls/libthread_db.so.1".
> Attaching to program: /usr/bin/linuxsampler, process 18051
> Reading symbols from /usr/lib/linuxsampler/liblinuxsampler.so.0...done.
> Loaded symbols for /usr/lib/linuxsampler/liblinuxsampler.so.0
> Reading symbols from /usr/lib/linuxsampler/libgig.so.0...done.
> Loaded symbols for /usr/lib/linuxsampler/libgig.so.0
> Reading symbols from /usr/lib/libjack.so.0...done.
> Loaded symbols for /usr/lib/libjack.so.0
> Reading symbols from /usr/lib/libasound.so.2...done.
> Loaded symbols for /usr/lib/libasound.so.2
> Reading symbols from /lib/libdl.so.2...done.
> Loaded symbols for /lib/libdl.so.2
> Reading symbols from /lib/tls/libpthread.so.0...done.
> [Thread debugging using libthread_db enabled]
> [New Thread -1209162112 (LWP 18051)]
> [New Thread -1427514448 (LWP 18063)]
> [Thread debugging using libthread_db enabled]
> [New Thread -1209162112 (LWP 18051)]
> [New Thread -1427514448 (LWP 18063)]
> [Thread debugging using libthread_db enabled]
> [New Thread -1209162112 (LWP 18051)]
> [New Thread -1427514448 (LWP 18063)]
> [New Thread -1365836880 (LWP 18060)]
> [New Thread -1344386128 (LWP 18058)]
> [New Thread -1284338768 (LWP 18056)]
> [New Thread -1226388560 (LWP 18054)]
> [New Thread -1217995856 (LWP 18053)]
> [New Thread -1209164880 (LWP 18052)]
> Loaded symbols for /lib/tls/libpthread.so.0
> Reading symbols from /usr/lib/libstdc++.so.5...done.
> Loaded symbols for /usr/lib/libstdc++.so.5
> Reading symbols from /lib/tls/libm.so.6...done.
> Loaded symbols for /lib/tls/libm.so.6
> Reading symbols from /lib/libgcc_s.so.1...done.
> Loaded symbols for /lib/libgcc_s.so.1
> Reading symbols from /lib/tls/libc.so.6...done.
> Loaded symbols for /lib/tls/libc.so.6
> Reading symbols from /lib/ld-linux.so.2...done.
> Loaded symbols for /lib/ld-linux.so.2
> 0xffffe410 in ?? ()
> (gdb) --- Stacktrace
> #0 0xffffe410 in ?? ()
> #1 0xbffffa58 in ?? ()
> #2 0x4561dfdc in ?? () from /lib/tls/libc.so.6
> #3 0xbffff8b4 in ?? ()
> #4 0x4558c7f6 in __nanosleep_nocancel () from /lib/tls/libc.so.6
> #5 0x4558c61f in sleep () from /lib/tls/libc.so.6
> #6 0x0804961c in main (argc=-516, argv=0x0) at linuxsampler.cpp:118
> --- Symbols
> #4 0x4558c7f6 in __nanosleep_nocancel () from /lib/tls/libc.so.6
> > > > >No symbol table info available.
> #5 0x4558c61f in sleep () from /lib/tls/libc.so.6
> No symbol table info available.
> #6 0x0804961c in main (argc=-516, argv=0x0) at linuxsampler.cpp:118
> 118 sleep(1);
> sFeatures = {static npos = 4294967295,
> _M_dataplus = {<std::allocator<char>> = {<No data fields>},
> _M_p = 0x804ce5c "CHANNELS"}, static _S_empty_rep_storage = {0, 0, 0, 0}}
> sact = {__sigaction_handler = {sa_handler = 0x8049780 <signal_handler(int)>,
> sa_sigaction = 0x8049780 <signal_handler(int)>}, sa_mask = {__val = {
> 0 <repeats 32 times>}}, sa_flags = 0, sa_restorer = 0}
> ---
> Detaching from program: /usr/bin/linuxsampler, process 18051
> Killing LinuxSampler...
> 13:21:28.916 Client disconnecting...
> 13:21:28.918 Client disconnected.
> 13:21:28.920 Server was stopped with exit status 0.
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Linuxsampler-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
>
--
Regards,
Vladimir
|
|
From: Mark K. <mar...@gm...> - 2005-01-01 22:08:27
|
On Sat, 1 Jan 2005 16:42:43 -0500, Vladimir Senkov <ha...@gm...> wrote: > Mark, > > Interesing, from the output it looks like it crashed while loading > sample, even before the midi was sent to it. Or did i misunderstand > it? No, the samples all load fine. It crashes when it receives the MIDI. > I'm wondering if this could be reproduce with the single channel (bass > channel) just to simplify? Good question. I tried it and got the same results. > Also, if it does happen after MIDI is sent, i wonder if the same thing > happens if you load any other instrument (not bass) into this channel > and play the same MIDI to it. I tried a different gig file and it does not crash with that file so this is related to the specific gig file that's loaded? I loaded both the piano and then a drone file on that channel and it didn't crash. Then I reloaded the bass gig that's been failing and it failed again. Good questions Vladimir! Leading us in the right direction. gigdump on the file doesn't look very strange. It's a cheap little bass gig file. I never use it under GSt but I'm force to try here since LS won't handle Scarbee yet. It's about 4MB. I could provide it for development/test purposes by email to one of you guys if you promise to erase it later. > In other words, it would be good to know if this is instrument specific or not. > It would be nice if it isn't. This way i'll be able to reproduce it > here and hopefully fix it (if you could send me the MIDI file). > > Regards, > Vladimir. |
|
From: Mark K. <mar...@gm...> - 2005-01-01 22:10:24
Attachments:
EW-Bass.txt
|
gigdump results attached. |
Thanks for helping keep SourceForge clean.
X