Menu
▾
▴
linuxsampler-devel
|
From: Mark K. <mar...@gm...> - 2005-01-01 01:51:25
|
Hi, I am getting these sort of error messages quite a lot: 17:49:01.109 Client connecting... 17:49:01.111 Client receive timeout is set to 500 msec. 17:49:01.112 Client connected. 17:49:01.113 New session: "Untitled1". 17:49:09.943 lscp_get_available_engines: Timeout during receive operation (errno=-4) 17:49:10.444 lscp_get_available_audio_drivers: Timeout during receive operation (errno=-4) 17:49:10.945 lscp_get_available_midi_drivers: Timeout during receive operation (errno=-4) 17:49:27.267 lscp_add_channel: Timeout during receive operation (errno=-4) 17:49:27.268 Could not create the new channel. Sorry. 17:49:29.262 Some channel settings could not be set. Sorry. QFont::fromString: invalid description '(null)' I'm trying to load the Bardstown piano which has been working. What's timing out? - Mark |
|
From: Vladimir S. <ha...@gm...> - 2005-01-01 02:04:44
|
Mark, Sorry i got my internal clock all messed up :) you of course have plenty of time before the new year :) This error means that the GUI is not getting response from the server fast enough. It expects to get something in 500msecs. The timeout is configurable, so try setting it higher, maybe a couple of seconds. Server must be busy or maybe it's stuck/hung. But if everything works fine eventually the server is probably just busy with something else and responds after a bit of a delay. Regards, Vladimir. On Fri, 31 Dec 2004 17:51:17 -0800, Mark Knecht <mar...@gm...> wrote: > Hi, > I am getting these sort of error messages quite a lot: > > 17:49:01.109 Client connecting... > 17:49:01.111 Client receive timeout is set to 500 msec. > 17:49:01.112 Client connected. > 17:49:01.113 New session: "Untitled1". > 17:49:09.943 lscp_get_available_engines: Timeout during receive > operation (errno=-4) > 17:49:10.444 lscp_get_available_audio_drivers: Timeout during receive > operation (errno=-4) > 17:49:10.945 lscp_get_available_midi_drivers: Timeout during receive > operation (errno=-4) > 17:49:27.267 lscp_add_channel: Timeout during receive operation (errno=-4) > 17:49:27.268 Could not create the new channel. Sorry. > 17:49:29.262 Some channel settings could not be set. Sorry. > QFont::fromString: invalid description '(null)' > > I'm trying to load the Bardstown piano which has been working. What's > timing out? > > - 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 > -- Regards, Vladimir |
|
From: Vladimir S. <ha...@gm...> - 2005-01-01 02:20:58
|
i've just remembered that the gui probably hasn't implemented the "background gig loading" feature. so you have to set the timeout to something really high for the time being. 30 seconds (or however long it takes to load the biggest gig) should do it. |
|
From: Mark K. <mar...@gm...> - 2005-01-01 02:26:52
|
On Fri, 31 Dec 2004 21:20:42 -0500, Vladimir Senkov <ha...@gm...> wrote: > i've just remembered that the gui probably hasn't implemented the > "background gig loading" feature. so you have to set the timeout to > something really high for the time being. 30 seconds (or however long > it takes to load the biggest gig) should do it. > Right. I set it to 6 seconds and seem to get the gigs loaded. However, when I start Pro Tools playing against 3 gig files - a jazz piece with piano, bass and drums, it plays for 10 seconds and then has problems and disappears from QJC's connections window: 18:21:30.595 Channel 0 reset. 18:21:55.123 Channel 1 created. Starting disk thread...OK Loading gig file '/mnt/audio1/Gigs/Pianos/Bardstown Audio/The Bosendorfer Imperial Grand Version 2.2.gig'...OK Loading gig instrument...OK Caching initial samples...OK 18:22:45.352 Channel 1 reset. 18:22:59.075 Channel 2 created. Starting disk thread...OK Loading gig file '/mnt/audio1/Gigs/Bass/East West Bass/Fender/2PU SJZHRD B.gig'...OK Loading gig instrument...OK Caching initial samples...OK 18:22:59.971 Channel 2 reset. 18:23:17.008 Channel 3 created. Starting disk thread...OK Loading gig file '/mnt/audio1/Gigs/Drums/Wizzo/Ambience Kit XXL.gig'...OK Loading gig instrument...OK Caching initial samples...OK gig::Synthesizer: Invalid Synthesis Mode: 241 18:24:11.520 Client disconnecting... 18:24:11.539 Client disconnected. 18:24:11.540 Server was stopped with exit status -1. |
|
From: Vladimir S. <ha...@gm...> - 2005-01-01 02:35:12
|
Mark, This is definitely a bug: gig::Synthesizer: Invalid Synthesis Mode: 241 and it causes the server to terminate. do you consistently get it every time? If so, i'd like to figure out the minimal set of variables to get this to reproduce it. i should be able to fix it easily then. Regards, Vladimir. |
|
From: Vladimir S. <ha...@gm...> - 2005-01-01 02:54:13
|
Mark, i think i just found a bug by looking at the code for a few minutes. I'm going to fix it now and let you know, so don't worry about reproducing. On Fri, 31 Dec 2004 21:34:54 -0500, Vladimir Senkov <ha...@gm...> wrote: > Mark, > > This is definitely a bug: > gig::Synthesizer: Invalid Synthesis Mode: 241 > and it causes the server to terminate. > do you consistently get it every time? > If so, i'd like to figure out the minimal set of variables to get this > to reproduce it. i should be able to fix it easily then. > > Regards, > Vladimir. > -- Regards, Vladimir |
|
From: Vladimir S. <ha...@gm...> - 2005-01-01 03:07:34
|
Mark, i've submitted a fix. please take an update from CVS, rebuild and try in again, i think it should take care of this problem. On Fri, 31 Dec 2004 21:54:02 -0500, Vladimir Senkov <ha...@gm...> wrote: > Mark, i think i just found a bug by looking at the code for a few minutes. > I'm going to fix it now and let you know, so don't worry about reproducing. > > On Fri, 31 Dec 2004 21:34:54 -0500, Vladimir Senkov <ha...@gm...> wrote: > > Mark, > > > > This is definitely a bug: > > gig::Synthesizer: Invalid Synthesis Mode: 241 > > and it causes the server to terminate. > > do you consistently get it every time? > > If so, i'd like to figure out the minimal set of variables to get this > > to reproduce it. i should be able to fix it easily then. > > > > Regards, > > Vladimir. > > > > > -- > Regards, > Vladimir > -- Regards, Vladimir |
|
From: Mark K. <mar...@gm...> - 2005-01-01 03:28:23
|
Building now. Won't have much more time to test tonight but will start with it first thing tomorrow. Thanks! And again, have a very fun and safe New Year's Eve! - Mark On Fri, 31 Dec 2004 22:07:20 -0500, Vladimir Senkov <ha...@gm...> wrote: > Mark, i've submitted a fix. please take an update from CVS, rebuild > and try in again, i think it should take care of this problem. > > > On Fri, 31 Dec 2004 21:54:02 -0500, Vladimir Senkov <ha...@gm...> wrote: > > Mark, i think i just found a bug by looking at the code for a few minutes. > > I'm going to fix it now and let you know, so don't worry about reproducing. > > > > On Fri, 31 Dec 2004 21:34:54 -0500, Vladimir Senkov <ha...@gm...> wrote: > > > Mark, > > > > > > This is definitely a bug: > > > gig::Synthesizer: Invalid Synthesis Mode: 241 > > > and it causes the server to terminate. > > > do you consistently get it every time? > > > If so, i'd like to figure out the minimal set of variables to get this > > > to reproduce it. i should be able to fix it easily then. > > > > > > Regards, > > > Vladimir. > > > > > > > > > -- > > Regards, > > Vladimir > > > > -- > Regards, > Vladimir > > ------------------------------------------------------- > 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: Garett S. <shu...@co...> - 2005-01-01 04:48:13
|
Hello Vladimir, I began to notice the invalid synthesis mode error when I would create a channel using one instrument from a gig file, then remove the channel and add another channel with a different instrument from the same gig. After building ls from cvs 15 minutes ago the problem has not appeared. Also, I have been getting disk stream errors when I load 3 or more channels at once. Whichever channel I am playing will eventually (after a minute or two) begin to show disk stream errors. If I begin playing on another channel it will get disk stream errors until there are only two channels that do not have disk stream errors. These two channels will work correctly until another channel is added. Also, I guess this is not necessarily a bug, but I have gotten segfaults from malformed midi messages. Vladimir Senkov wrote: >Mark, i've submitted a fix. please take an update from CVS, rebuild >and try in again, i think it should take care of this problem. > > >On Fri, 31 Dec 2004 21:54:02 -0500, Vladimir Senkov <ha...@gm...> wrote: > > >>Mark, i think i just found a bug by looking at the code for a few minutes. >>I'm going to fix it now and let you know, so don't worry about reproducing. >> >>On Fri, 31 Dec 2004 21:34:54 -0500, Vladimir Senkov <ha...@gm...> wrote: >> >> >>>Mark, >>> >>>This is definitely a bug: >>>gig::Synthesizer: Invalid Synthesis Mode: 241 >>>and it causes the server to terminate. >>>do you consistently get it every time? >>>If so, i'd like to figure out the minimal set of variables to get this >>>to reproduce it. i should be able to fix it easily then. >>> >>>Regards, >>>Vladimir. >>> >>> >>> >>-- >>Regards, >>Vladimir >> >> >> > > > > |
|
From: Vladimir S. <ha...@gm...> - 2005-01-01 04:57:41
|
Hello Garett, Happy new year!!! it's coming up here in 8 minutes :) > Hello Vladimir, I began to notice the invalid synthesis mode error when > I would create a channel using one instrument from a gig file, then > remove the channel and add another channel with a different instrument > from the same gig. After building ls from cvs 15 minutes ago the problem > has not appeared. cool. please let the mailing list know when you experience problems this way someone will fix it sooner :) i'm glad the fix seems to work. i'm surprised i haven't seen this problem myself, it was kind of a trivial bug, variable was not properly initialized. > Also, I have been getting disk stream errors when I load 3 or more > channels at once. Whichever channel I am playing will eventually (after > a minute or two) begin to show disk stream errors. If I begin playing on > another channel it will get disk stream errors until there are only two > channels that do not have disk stream errors. These two channels will > work correctly until another channel is added. Ok, so unfortunately disk streaming problems are not over yet. I suspected that. I'll try to reproduce the problem using the description you provided. If there is any more minimalistic step by step reproduction sequence please let me know. > Also, I guess this is not necessarily a bug, but I have gotten segfaults > from malformed midi messages. definitely a bug, we should never segfault. could you send those messages in a midi file? Regards, Vladimir. |
|
From: Garett S. <shu...@co...> - 2005-01-01 05:16:17
|
Vladimir Senkov wrote: Happy new Year! >Hello Garett, > >Happy new year!!! >it's coming up here in 8 minutes :) > > > >>Hello Vladimir, I began to notice the invalid synthesis mode error when >>I would create a channel using one instrument from a gig file, then >>remove the channel and add another channel with a different instrument >>from the same gig. After building ls from cvs 15 minutes ago the problem >>has not appeared. >> >> > >cool. please let the mailing list know when you experience problems >this way someone will fix it sooner :) >i'm glad the fix seems to work. i'm surprised i haven't seen this >problem myself, it was kind of a trivial bug, variable was not >properly initialized. > > > I was preparing an email to the list but you just solve these problems too fast! :) >>Also, I have been getting disk stream errors when I load 3 or more >>channels at once. Whichever channel I am playing will eventually (after >>a minute or two) begin to show disk stream errors. If I begin playing on >>another channel it will get disk stream errors until there are only two >>channels that do not have disk stream errors. These two channels will >>work correctly until another channel is added. >> >> > >Ok, so unfortunately disk streaming problems are not over yet. I suspected that. >I'll try to reproduce the problem using the description you provided. >If there is any more minimalistic step by step reproduction sequence >please let me know. > > > >>Also, I guess this is not necessarily a bug, but I have gotten segfaults >>from malformed midi messages. >> >> > >definitely a bug, we should never segfault. could you send those >messages in a midi file? > > the midi messages where malformed in an alsa sequencer filter program. I will try to figure out what the messages contained tomorrow. > >Regards, >Vladimir. > > >------------------------------------------------------- >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 05:43:47
|
Garett, > I was preparing an email to the list but you just solve these problems > too fast! :) only simple ones :) > >>Also, I guess this is not necessarily a bug, but I have gotten segfaults > >>from malformed midi messages. > >> > >> > > > >definitely a bug, we should never segfault. could you send those > >messages in a midi file? > > > > > the midi messages where malformed in an alsa sequencer filter program. > I will try to figure out what the messages contained tomorrow. one other option is online over the irc gdb session :) this way you might not have to figure out the messages . . . might be easier if the problem is simple enough. Another option is build with increased logging level . . might or might not show anything. The best way is online/irc gdb session imho. Regards, Vladimir. |
|
From: Vladimir S. <ha...@gm...> - 2005-01-01 08:02:45
|
Everybody, While looking at this problem i discovered that we have somewhat of a design problem or maybe i just don't understand the design. Today we have a diskthread for each channel. So while there are limits to numbers of streams and voices those limits seem to only apply per channel. And there is some code in the disk thread that assumes that there is only one diskthread. So . . . i'm not sure if i should fix the diskthread not to assume that it is the only one or if i should make diskthread unique per sampler rather than per channel? I suppose if instruments "live" on different drives (for example) it could make more sense to have separate diskthread for each channel. but what about the limits? we should probably rethink limits anyways, so for for now i'll see if there is an easy way to fix diskthread not to assume that it's the only instance. Regards, Vladimir. > Also, I have been getting disk stream errors when I load 3 or more > channels at once. Whichever channel I am playing will eventually (after > a minute or two) begin to show disk stream errors. If I begin playing on > another channel it will get disk stream errors until there are only two > channels that do not have disk stream errors. These two channels will > work correctly until another channel is added. |
|
From: Vladimir S. <ha...@gm...> - 2005-01-01 08:25:23
|
Ok, so i've submitted a fix that should take care of the issue with streams leaking out when multiple channels are used. i know there are definitely some issues there still, but hopefully those will not surface during "normal" use. For example, one issue is this: CREATE AUDIO_OUTPUT_DEVICE ALSA CARD='0,0' SAMPLERATE=48000 ADD CHANNEL LOAD ENGINE GigEngine 0 SET CHANNEL AUDIO_OUTPUT_DEVICE 0 0 CREATE MIDI_INPUT_DEVICE ALSA SET CHANNEL MIDI_INPUT 0 0 0 0 SET MIDI_INPUT_PORT_PARAMETER 0 0 ALSA_SEQ_BINDINGS='128:0' LOAD INSTRUMENT 'test.gig' 0 0 SET CHANNEL VOLUME 0 0.15 everything works fine so far but if i just do this one command again: SET CHANNEL AUDIO_OUTPUT_DEVICE 0 0 then something gets connected incorrectly, some state gets corrupted somewhere and if i try to trigger any voices after that LS crashes. I haven't had a chance to look at the crash yet . . . martini is kicking in now and i'm going to go relax or something :) hopefully we'll clean up most of the bugs during this year :))) good night everybody and happy new year :) On Sat, 1 Jan 2005 03:02:34 -0500, Vladimir Senkov <ha...@gm...> wrote: > Everybody, > > While looking at this problem i discovered that we have somewhat of a > design problem or maybe i just don't understand the design. > Today we have a diskthread for each channel. > So while there are limits to numbers of streams and voices those > limits seem to only apply per channel. > And there is some code in the disk thread that assumes that there is > only one diskthread. > So . . . i'm not sure if i should fix the diskthread not to assume > that it is the only one or if i should make diskthread unique per > sampler rather than per channel? > > I suppose if instruments "live" on different drives (for example) it > could make more sense to have separate diskthread for each channel. > but what about the limits? we should probably rethink limits anyways, > so for for now i'll see if there is an easy way to fix diskthread not > to assume that it's the only instance. > > Regards, > Vladimir. > > > Also, I have been getting disk stream errors when I load 3 or more > > channels at once. Whichever channel I am playing will eventually (after > > a minute or two) begin to show disk stream errors. If I begin playing on > > another channel it will get disk stream errors until there are only two > > channels that do not have disk stream errors. These two channels will > > work correctly until another channel is added. > -- Regards, Vladimir |
Thanks for helping keep SourceForge clean.
X