Menu
▾
▴
linuxsampler-devel — This list is for discussing LinuxSampler development issues and ideas
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(27) |
Nov
(120) |
Dec
(16) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(65) |
Feb
(2) |
Mar
(53) |
Apr
(15) |
May
|
Jun
(19) |
Jul
(8) |
Aug
(35) |
Sep
(17) |
Oct
(70) |
Nov
(87) |
Dec
(94) |
| 2004 |
Jan
(133) |
Feb
(28) |
Mar
(45) |
Apr
(30) |
May
(113) |
Jun
(132) |
Jul
(33) |
Aug
(29) |
Sep
(26) |
Oct
(11) |
Nov
(21) |
Dec
(60) |
| 2005 |
Jan
(108) |
Feb
(153) |
Mar
(108) |
Apr
(44) |
May
(72) |
Jun
(90) |
Jul
(99) |
Aug
(67) |
Sep
(117) |
Oct
(38) |
Nov
(40) |
Dec
(27) |
| 2006 |
Jan
(16) |
Feb
(18) |
Mar
(21) |
Apr
(71) |
May
(26) |
Jun
(48) |
Jul
(27) |
Aug
(40) |
Sep
(20) |
Oct
(118) |
Nov
(69) |
Dec
(35) |
| 2007 |
Jan
(76) |
Feb
(98) |
Mar
(26) |
Apr
(126) |
May
(94) |
Jun
(46) |
Jul
(9) |
Aug
(89) |
Sep
(18) |
Oct
(27) |
Nov
|
Dec
(49) |
| 2008 |
Jan
(117) |
Feb
(40) |
Mar
(18) |
Apr
(30) |
May
(40) |
Jun
(10) |
Jul
(30) |
Aug
(13) |
Sep
(29) |
Oct
(23) |
Nov
(22) |
Dec
(35) |
| 2009 |
Jan
(19) |
Feb
(39) |
Mar
(17) |
Apr
(2) |
May
(6) |
Jun
(6) |
Jul
(8) |
Aug
(11) |
Sep
(1) |
Oct
(46) |
Nov
(13) |
Dec
(5) |
| 2010 |
Jan
(21) |
Feb
(3) |
Mar
(2) |
Apr
(7) |
May
(1) |
Jun
(26) |
Jul
(3) |
Aug
(10) |
Sep
(13) |
Oct
(35) |
Nov
(10) |
Dec
(17) |
| 2011 |
Jan
(26) |
Feb
(27) |
Mar
(14) |
Apr
(32) |
May
(8) |
Jun
(11) |
Jul
(4) |
Aug
(7) |
Sep
(27) |
Oct
(25) |
Nov
(7) |
Dec
(2) |
| 2012 |
Jan
(20) |
Feb
(17) |
Mar
(59) |
Apr
(31) |
May
|
Jun
(6) |
Jul
(7) |
Aug
(10) |
Sep
(11) |
Oct
(2) |
Nov
(4) |
Dec
(17) |
| 2013 |
Jan
(17) |
Feb
(2) |
Mar
(3) |
Apr
(4) |
May
(8) |
Jun
(3) |
Jul
(2) |
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
(1) |
| 2014 |
Jan
(6) |
Feb
(26) |
Mar
(12) |
Apr
(14) |
May
(8) |
Jun
(7) |
Jul
(6) |
Aug
(6) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
(9) |
Feb
(5) |
Mar
(4) |
Apr
(9) |
May
(3) |
Jun
(2) |
Jul
(4) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(3) |
| 2016 |
Jan
(2) |
Feb
(4) |
Mar
(5) |
Apr
(4) |
May
(14) |
Jun
(31) |
Jul
(18) |
Aug
|
Sep
(10) |
Oct
(3) |
Nov
|
Dec
|
| 2017 |
Jan
(39) |
Feb
(5) |
Mar
(2) |
Apr
|
May
(52) |
Jun
(11) |
Jul
(36) |
Aug
(1) |
Sep
(7) |
Oct
(4) |
Nov
(10) |
Dec
(8) |
| 2018 |
Jan
(3) |
Feb
(4) |
Mar
|
Apr
(8) |
May
(28) |
Jun
(11) |
Jul
(2) |
Aug
(2) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
(25) |
| 2019 |
Jan
(12) |
Feb
(50) |
Mar
(14) |
Apr
(3) |
May
(8) |
Jun
(17) |
Jul
(10) |
Aug
(2) |
Sep
(21) |
Oct
(10) |
Nov
|
Dec
(28) |
| 2020 |
Jan
(4) |
Feb
(10) |
Mar
(7) |
Apr
(16) |
May
(10) |
Jun
(7) |
Jul
(2) |
Aug
(5) |
Sep
(3) |
Oct
(3) |
Nov
(2) |
Dec
(1) |
| 2021 |
Jan
|
Feb
(5) |
Mar
(13) |
Apr
(13) |
May
(7) |
Jun
|
Jul
(1) |
Aug
(11) |
Sep
(12) |
Oct
(7) |
Nov
(26) |
Dec
(41) |
| 2022 |
Jan
(23) |
Feb
|
Mar
(8) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
(3) |
Nov
(1) |
Dec
(1) |
| 2023 |
Jan
|
Feb
(5) |
Mar
(2) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(11) |
Sep
(5) |
Oct
(1) |
Nov
|
Dec
|
| 2024 |
Jan
(2) |
Feb
(4) |
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(10) |
Dec
|
| 2025 |
Jan
|
Feb
(4) |
Mar
(1) |
Apr
(2) |
May
|
Jun
(17) |
Jul
(1) |
Aug
(4) |
Sep
(7) |
Oct
(1) |
Nov
(9) |
Dec
|
|
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 01:55:10
|
Mark, This is great news! I'm almost ready to start celebrating :))) Memory stats could be looked at by tools like "top" but there is nothing currently in LS itself (as far as i know) that could output memory usage stats. I think it is a good idea and we should add a feature that would allow this. I'm not sure how it should look like exactly but i'll think about it. Can you do a "gigdump" on Scarbee J-Fingered Bass gig so we could have a bit more info to try to figure out why it doesn't work. Also, if you hear something strange that you haven't heard before and if GS doesn't sound the same, could you try against previous verion of LS (the one before optimization, the one from Rui's site should do). Another thing to try is to use the -no-tune flag to disable SSEMMX optimizations on the latest LS. HAPPY NEW YEAR!!! you have 6 minutes to go there on the west coast :) Regards, Vladimir. |
|
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: Mark K. <mar...@gm...> - 2005-01-01 01:30:14
|
On Fri, 31 Dec 2004 19:43:27 -0500, Vladimir Senkov <ha...@gm...> wrote: > Looks good! > but . . . i haven't actually tested with the GUI for a little while, > so i can only speak for LS itself. but since we didn't change anything > in lscp area for a while it should work. > if it doesn't, please let me know and i'll try to fix it asap. i still > have a few vacation days :) > > > OK, I'm building from CVS right now. Rui's page doesn't seem ot have > > been updated for a while so this seems best. When this finishes in a > > minute I would begin testing using the following set of tools: > > > > linuxsampler-cvs-20041231 > > libgig-1.0.0 > > liblscp-0.2.4 > > qsampler-0.0.4 > > > > Look good to you? > OK, I've done some very preliminary, initial tests with the toolset show above in comparison with GSt Ver. 2.50.48 running under Win XP. I'm using the Bardstown Bosendorfer piano gig. I have a short MIDI file in Pro Tools (on a separate, 3rd PC) driving both samplers and I've recorded the audio from each into Ardour on separate passes. So far I cannot hear any differences at all, but I'm using headphones and have a bit of a headache. (geez...New Years Eve and I ALREADY have a headache!) ;-) My MIDI file is very simple. The first number is the note-on velocity and the second is the note-off velocity. 16 notes - 1/1, 9/9, 17/17, ...118/118, 127/127 16 notes - 96/1, 96/9, 96/17, ...96/127 16 notes - 1/50, 9/50, 17/50, ...127/50 16 notes - 1/96. 9/96, 17/96, ...127/96 Is thi ssort of MIDI file appropriate for findign the release sample problem if it exists? I suppose my only comments at this point are: 1) While the Bardstown Piano advertises release samples it's not 100% clear that they are being used in this voice. I'd like to know how to be sure of this using gigdump or some other tool if possible. 2) LS is producing about 2db higher output than GSt when GSt has all settings at max level. (I need to check my hardware setting in hdspmixer to ensure I'm not doing something silly with levels.) On a good note I tested LS hard for the streaming problem I saw earlier today and that seems to have completely gone away, at least for single note testing. I can drag the note around in Pro Tools causing lots of real time events. All notes seem to be played and there were no lockups. I did notice some sonic problems with a few notes in the Bardstown piano that I have not heard before. I need to check and see if those are in the gig file itself and also present on the GSt side. Also, the Scarbee J-Fingered Bass gig still does not work correctly. All in all, very positive results! Congrats to the developers. I need to do some testing with more complicated MIDI files and multiple gig files loaded at the same time. I am a bit concerned about memory usage as reported by top while LS is running, ut possibly it's not really a problem. top is often confused about such things. Is there a way I can see the amount of memory LS is allocating to each gig file? It would be good to know this sort of thing I think. With best regards, Mark |
|
From: Vladimir S. <ha...@gm...> - 2005-01-01 00:43:38
|
Looks good! but . . . i haven't actually tested with the GUI for a little while, so i can only speak for LS itself. but since we didn't change anything in lscp area for a while it should work. if it doesn't, please let me know and i'll try to fix it asap. i still have a few vacation days :) > OK, I'm building from CVS right now. Rui's page doesn't seem ot have > been updated for a while so this seems best. When this finishes in a > minute I would begin testing using the following set of tools: > > linuxsampler-cvs-20041231 > libgig-1.0.0 > liblscp-0.2.4 > qsampler-0.0.4 > > Look good to you? |
|
From: Mark K. <mar...@gm...> - 2005-01-01 00:27:15
|
On Fri, 31 Dec 2004 17:14:24 -0500, Vladimir Senkov <ha...@gm...> wrote: > Mark, > > Happy new year!!!! And to you and all the LS Developers and users also! > > Older versions have known bugs. Streaming bug that you've seen just > now was one of the known bugs. > Please try the latest LS. The latest LS has only one known bug (as far > as i know): the release velocity bug. (i'm not completely sure it's > really gone but no one has reported it yet with the latest LS). > all other bugs are unknown at this point and i'd like to know about them! :) > > Regards, > Vladimir. > OK, I'm building from CVS right now. Rui's page doesn't seem ot have been updated for a while so this seems best. When this finishes in a minute I would begin testing using the following set of tools: linuxsampler-cvs-20041231 libgig-1.0.0 liblscp-0.2.4 qsampler-0.0.4 Look good to you? Have a great SAFE evening! - Mark |
|
From: Vladimir S. <ha...@gm...> - 2004-12-31 22:14:37
|
Mark, Happy new year!!!! Older versions have known bugs. Streaming bug that you've seen just now was one of the known bugs. Please try the latest LS. The latest LS has only one known bug (as far as i know): the release velocity bug. (i'm not completely sure it's really gone but no one has reported it yet with the latest LS). all other bugs are unknown at this point and i'd like to know about them! :) Regards, Vladimir. On Fri, 31 Dec 2004 14:07:21 -0800, Mark Knecht <mar...@gm...> wrote: > What LS should I be using for release velocity testing? > > While dragging notes around in Pro Tools I made this happen in an > older version of qsampler/LS: > > 14:04:19.646 ADD CHANNEL > 14:04:19.651 SET CHANNEL AUDIO_OUTPUT_TYPE 0 JACK > 14:04:19.656 SET CHANNEL MIDI_INPUT_TYPE 0 ALSA > 14:04:19.657 SET CHANNEL MIDI_INPUT_PORT 0 0 > 14:04:19.663 SET CHANNEL MIDI_INPUT_CHANNEL 0 0 > 14:04:19.670 LOAD ENGINE GigEngine 0 > Starting disk thread...OK > 14:04:19.871 LOAD INSTRUMENT NON_MODAL > '/mnt/audio1/Gigs/Pianos/Bardstown Audio/The Bosendorfer Imperial > Grand Version 2.2.gig' 0 0 > 14:04:19.905 SET CHANNEL VOLUME 0 1 > QFont::fromString: invalid description '(null)' > 14:04:19.943 Open session: "/home/mark/Bardstown.lscp". > 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 > 14:05:25.095 lscp_reset_channel: Timeout during receive operation (errno=-4) > No unused stream found (OrderID:69) - report if this happens, this is a bug! > No unused stream found (OrderID:70) - report if this happens, this is a bug! > No unused stream found (OrderID:71) - report if this happens, this is a bug! > No unused stream found (OrderID:72) - report if this happens, this is a bug! > No unused stream found (OrderID:73) - report if this h0x4561e7c0Disk > stream not available in time! > No debugger found > FATAL: exception not rethrown > 14:05:26.747 Client disconnecting... > 14:05:26.749 Client disconnected. > 14:05:26.751 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...> - 2004-12-31 22:07:28
|
What LS should I be using for release velocity testing? While dragging notes around in Pro Tools I made this happen in an older version of qsampler/LS: 14:04:19.646 ADD CHANNEL 14:04:19.651 SET CHANNEL AUDIO_OUTPUT_TYPE 0 JACK 14:04:19.656 SET CHANNEL MIDI_INPUT_TYPE 0 ALSA 14:04:19.657 SET CHANNEL MIDI_INPUT_PORT 0 0 14:04:19.663 SET CHANNEL MIDI_INPUT_CHANNEL 0 0 14:04:19.670 LOAD ENGINE GigEngine 0 Starting disk thread...OK 14:04:19.871 LOAD INSTRUMENT NON_MODAL '/mnt/audio1/Gigs/Pianos/Bardstown Audio/The Bosendorfer Imperial Grand Version 2.2.gig' 0 0 14:04:19.905 SET CHANNEL VOLUME 0 1 QFont::fromString: invalid description '(null)' 14:04:19.943 Open session: "/home/mark/Bardstown.lscp". 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 14:05:25.095 lscp_reset_channel: Timeout during receive operation (errno=-4) No unused stream found (OrderID:69) - report if this happens, this is a bug! No unused stream found (OrderID:70) - report if this happens, this is a bug! No unused stream found (OrderID:71) - report if this happens, this is a bug! No unused stream found (OrderID:72) - report if this happens, this is a bug! No unused stream found (OrderID:73) - report if this h0x4561e7c0Disk stream not available in time! No debugger found FATAL: exception not rethrown 14:05:26.747 Client disconnecting... 14:05:26.749 Client disconnected. 14:05:26.751 Server was stopped with exit status 0. |
|
From: Mark K. <mar...@gm...> - 2004-12-30 23:51:21
|
On Thu, 30 Dec 2004 19:20:20 +0100, Christian Schoenebeck <sch...@so...> wrote: > > Mark, could you please determine this? I mean if the release triggered sample > on Gst is selected by its releease velocity or by its previous note on > velocity? > > CU > Christian Of course, as it would happen, it appears that my Linux machine has taken a complete dump today. The machine was working but the gig library was incomplete, so I moved the 1394 drive to one of my Win XP boxes to copy the library. Upon returning the 1394 drive to the LS machine the machine has gone haywire. With the 1394 drive plugged in I get POST beep codes about memory or video problems. If the machine boots then video starts getting corrupted as soon as I plug the drive in. The drive is fine. It still works under Windows. Looks like a hardware problem has developed today. This will likely take me a day or two to work out, and being unemployed at this time I need to work it out in an inexpensive way. Sorry, Mark |
|
From: Garett S. <shu...@co...> - 2004-12-30 18:46:17
|
I wouldn't think that single or multi release samples would make a difference. It seems as though the amplitude in ls is high regardless. I have Post Pristine and experience the problem with that. I get very unusual behavior with Post Pristine when I hold down the sustain pedal. The noteoff event triggers the noteon event sample when the sustain pedal is down. On Dec 30, 2004, at 11:30 AM, Mark Knecht wrote: > Garett, > Yes, it makes sense to me technically, but not practically. I get > that if I could send note-off events only then I could trigger > note-off samples. (At least I think that's what you're saying. Correct > me if I'm wrong.) > > I think that I have no way to generate a string of note-off events. > It's no big deal to generate a number of note-on/note-off events by > editing in Pro Tools. I did this earlier when I helped with the > filters and what not. Now I'll just modify some of those files to set > the note-off events to a meaningful value for this test. > > I do not have the Scarbee RSP 73. I've heard good things about it. > I do have a few grand piano gig's (Bardstown, Post, Trachtman) that > have release samples, but I'm not at all sure how many samples they > have. > > It's my understanding that this test we are talking about only > makes a difference on gig files that have multi-velocity release > samples. Correct? If it works with gig files that have single velocity > release files then I should have no problem testing as I have a number > of those. > > - Mark > > > On Thu, 30 Dec 2004 11:10:56 -0700, Garett Shulman > <shu...@co...> wrote: >> Hey Mark, I don't think that the time between noteon and noteoff >> events >> makes a difference. In fact, the noteon event should be irrelevent >> (these seem to be playing pretty well). The noteoff event triggers a >> completely different sample than an equivelent noteon event on all of >> the patches I have. Do you happen to have Scarbee RSP 73? This gig >> uses >> noteoff triggered samples to simulate the sound of the damper striking >> the tine as the tine is silenced when the key is released. This should >> be quantifiable by comparing the amplitude of recordings you make from >> ls and gs in an audio editor (like snd or soundforge). I don't think >> you need to bother generating noteon events at all. Is this making >> sense? -Garett >> >> >> On Dec 30, 2004, at 10:10 AM, Mark Knecht wrote: >> >>> OK, I found out how to do it in Pro Tools. It's a little painful >>> though. >>> >>> I'll set up a test MIDI file and get ready to record some audio data. >>> However it seems that testing this in a quantifiable way could be >>> somewhat difficult. Does note-on velocity effect what GSt & LS are >>> supposed to do? Does the time between note-on and note-off make a >>> difference? (I assume it does...) >>> >>> What are the current ideas about how this should be looked at? >>> >>> >>> On Thu, 30 Dec 2004 08:52:48 -0800, Mark Knecht >>> <mar...@gm...> >>> wrote: >>>> Garett, >>>> I have both GSt and LS running side by side so I could do a >>>> comparison if: >>>> >>>> 1) I get LS updated to something new and groovy. >>>> >>>> and >>>> >>>> 2) I had access to an appropriate gig file. >>>> >>>> When you state 'voices based on noteoff velocity' what exactly do >>>> you >>>> mean? How can I control the note-off velocity? Does the note-off >>>> event >>>> carry velocity information? If so then how do I effect it? Edit MIDI >>>> files in Pro Tools possibly? I've called up Pro Tools and made a >>>> MIDI >>>> track but it only shows velocity on the initial note-on event. >>>> >>>> I don't know where Pro Tools keeps an event list editor. I'll check >>>> for that. >>>> >>>> - Mark >>>> >>>> >>>> On Thu, 30 Dec 2004 09:13:10 -0700, Garett Shulman >>>> <shu...@co...> wrote: >>>>> Hello Christian, On all of the patches I have that trigger voices >>>>> based >>>>> on noteoff velocity, the voices seem to playback with excessive >>>>> volume >>>>> (like the sound of the mute pad striking the tine on the rhodes >>>>> when >>>>> you >>>>> release a key). Unfortunatly, I don't have a windows box with gs to >>>>> compare to. I can try to produce a recording. Let me know if there >>>>> is >>>>> more specific information I can provide. I get around this problem >>>>> by >>>>> using an alsa sequencer filter that just sets noteoff velocity to >>>>> 1. >>>>> >>>>> In regards to the voice bound... Is it possible to set this at >>>>> runtime >>>>> or compiletime? >>>>> >>>>> -Garett >>>>> >>>>> Christian Schoenebeck wrote: >>>>> >>>>>> Es geschah am Mittwoch 29 Dezember 2004 06:26 als Garett Shulman >>>>>> schrieb: >>>>>> >>>>>> >>>>>>> BTW Mark, Scarbee RSP 73 works fine for me (except for the loud >>>>>>> release >>>>>>> triggered voices :) ) >>>>>>> >>>>>>> >>>>>> >>>>>> Hi Garett, >>>>>> >>>>>> could please explain once again what the problem with the release >>>>>> trigger >>>>>> dimension exactly was? >>>>>> >>>>>> Btw, maybe we should reduce the default upper limit of voices? >>>>>> Currently it's >>>>>> bound to 128 voices by default, some older boxes might not be able >>>>>> to deliver >>>>>> that amount. In future the voice limit, that is the amount of >>>>>> voices when >>>>>> voice stealing starts to chime in, should be estimated by >>>>>> benchmarking. >>>>>> >>>>>> CU >>>>>> Christian >>>>>> >>>>>> >>>>>> ------------------------------------------------------- >>>>>> 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 >>>>>> >>>>>> >>>>> >>>>> ------------------------------------------------------- >>>>> 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 >>>>> >>>> >> >> >> ------------------------------------------------------- >> 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: Mark K. <mar...@gm...> - 2004-12-30 18:32:42
|
On Thu, 30 Dec 2004 19:20:20 +0100, Christian Schoenebeck <SNIP> > At least that would explain why LS and GSt behave differently > regarding release triggered samples. > > Mark, could you please determine this? I mean if the release triggered sample > on Gst is selected by its releease velocity or by its previous note on > velocity? > > CU > Christian Christian, I can try. - Mark |
|
From: Mark K. <mar...@gm...> - 2004-12-30 18:30:23
|
Garett, Yes, it makes sense to me technically, but not practically. I get that if I could send note-off events only then I could trigger note-off samples. (At least I think that's what you're saying. Correct me if I'm wrong.) I think that I have no way to generate a string of note-off events. It's no big deal to generate a number of note-on/note-off events by editing in Pro Tools. I did this earlier when I helped with the filters and what not. Now I'll just modify some of those files to set the note-off events to a meaningful value for this test. I do not have the Scarbee RSP 73. I've heard good things about it. I do have a few grand piano gig's (Bardstown, Post, Trachtman) that have release samples, but I'm not at all sure how many samples they have. It's my understanding that this test we are talking about only makes a difference on gig files that have multi-velocity release samples. Correct? If it works with gig files that have single velocity release files then I should have no problem testing as I have a number of those. - Mark On Thu, 30 Dec 2004 11:10:56 -0700, Garett Shulman <shu...@co...> wrote: > Hey Mark, I don't think that the time between noteon and noteoff events > makes a difference. In fact, the noteon event should be irrelevent > (these seem to be playing pretty well). The noteoff event triggers a > completely different sample than an equivelent noteon event on all of > the patches I have. Do you happen to have Scarbee RSP 73? This gig uses > noteoff triggered samples to simulate the sound of the damper striking > the tine as the tine is silenced when the key is released. This should > be quantifiable by comparing the amplitude of recordings you make from > ls and gs in an audio editor (like snd or soundforge). I don't think > you need to bother generating noteon events at all. Is this making > sense? -Garett > > > On Dec 30, 2004, at 10:10 AM, Mark Knecht wrote: > > > OK, I found out how to do it in Pro Tools. It's a little painful > > though. > > > > I'll set up a test MIDI file and get ready to record some audio data. > > However it seems that testing this in a quantifiable way could be > > somewhat difficult. Does note-on velocity effect what GSt & LS are > > supposed to do? Does the time between note-on and note-off make a > > difference? (I assume it does...) > > > > What are the current ideas about how this should be looked at? > > > > > > On Thu, 30 Dec 2004 08:52:48 -0800, Mark Knecht <mar...@gm...> > > wrote: > >> Garett, > >> I have both GSt and LS running side by side so I could do a > >> comparison if: > >> > >> 1) I get LS updated to something new and groovy. > >> > >> and > >> > >> 2) I had access to an appropriate gig file. > >> > >> When you state 'voices based on noteoff velocity' what exactly do you > >> mean? How can I control the note-off velocity? Does the note-off event > >> carry velocity information? If so then how do I effect it? Edit MIDI > >> files in Pro Tools possibly? I've called up Pro Tools and made a MIDI > >> track but it only shows velocity on the initial note-on event. > >> > >> I don't know where Pro Tools keeps an event list editor. I'll check > >> for that. > >> > >> - Mark > >> > >> > >> On Thu, 30 Dec 2004 09:13:10 -0700, Garett Shulman > >> <shu...@co...> wrote: > >>> Hello Christian, On all of the patches I have that trigger voices > >>> based > >>> on noteoff velocity, the voices seem to playback with excessive > >>> volume > >>> (like the sound of the mute pad striking the tine on the rhodes when > >>> you > >>> release a key). Unfortunatly, I don't have a windows box with gs to > >>> compare to. I can try to produce a recording. Let me know if there is > >>> more specific information I can provide. I get around this problem by > >>> using an alsa sequencer filter that just sets noteoff velocity to 1. > >>> > >>> In regards to the voice bound... Is it possible to set this at > >>> runtime > >>> or compiletime? > >>> > >>> -Garett > >>> > >>> Christian Schoenebeck wrote: > >>> > >>>> Es geschah am Mittwoch 29 Dezember 2004 06:26 als Garett Shulman > >>>> schrieb: > >>>> > >>>> > >>>>> BTW Mark, Scarbee RSP 73 works fine for me (except for the loud > >>>>> release > >>>>> triggered voices :) ) > >>>>> > >>>>> > >>>> > >>>> Hi Garett, > >>>> > >>>> could please explain once again what the problem with the release > >>>> trigger > >>>> dimension exactly was? > >>>> > >>>> Btw, maybe we should reduce the default upper limit of voices? > >>>> Currently it's > >>>> bound to 128 voices by default, some older boxes might not be able > >>>> to deliver > >>>> that amount. In future the voice limit, that is the amount of > >>>> voices when > >>>> voice stealing starts to chime in, should be estimated by > >>>> benchmarking. > >>>> > >>>> CU > >>>> Christian > >>>> > >>>> > >>>> ------------------------------------------------------- > >>>> 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 > >>>> > >>>> > >>> > >>> ------------------------------------------------------- > >>> 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 > >>> > >> > > > ------------------------------------------------------- > 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: Christian S. <sch...@so...> - 2004-12-30 18:27:46
|
Es geschah am Donnerstag 30 Dezember 2004 19:10 als Garett Shulman schrieb: > Hey Mark, I don't think that the time between noteon and noteoff events > makes a difference. In fact, the noteon event should be irrelevent > (these seem to be playing pretty well). The noteoff event triggers a > completely different sample than an equivelent noteon event on all of Correct > the patches I have. Do you happen to have Scarbee RSP 73? This gig uses > noteoff triggered samples to simulate the sound of the damper striking > the tine as the tine is silenced when the key is released. This should > be quantifiable by comparing the amplitude of recordings you make from > ls and gs in an audio editor (like snd or soundforge). I don't think > you need to bother generating noteon events at all. Is this making > sense? -Garett Actually this is a good question. In regards of LS you are right, when the note-off arrives we play a completely independent sample and determine the right sample to play (together with its articulation information) by its key number, the positive release trigger dimension (release trigger dimension is a binary value, false = sample for note on, true = sample for note off) and its release trigger velocity (actually it depends on couple more things, but these can be ignored for our problem). But I'm not sure if this is correct. Maybe the original GSt uses the original note on velocity instead of the note off velocity? At least that would explain why LS and GSt behave differently regarding release triggered samples. Mark, could you please determine this? I mean if the release triggered sample on Gst is selected by its releease velocity or by its previous note on velocity? CU Christian |
|
From: Garett S. <shu...@co...> - 2004-12-30 18:09:35
|
Hey Mark, I don't think that the time between noteon and noteoff events makes a difference. In fact, the noteon event should be irrelevent (these seem to be playing pretty well). The noteoff event triggers a completely different sample than an equivelent noteon event on all of the patches I have. Do you happen to have Scarbee RSP 73? This gig uses noteoff triggered samples to simulate the sound of the damper striking the tine as the tine is silenced when the key is released. This should be quantifiable by comparing the amplitude of recordings you make from ls and gs in an audio editor (like snd or soundforge). I don't think you need to bother generating noteon events at all. Is this making sense? -Garett On Dec 30, 2004, at 10:10 AM, Mark Knecht wrote: > OK, I found out how to do it in Pro Tools. It's a little painful > though. > > I'll set up a test MIDI file and get ready to record some audio data. > However it seems that testing this in a quantifiable way could be > somewhat difficult. Does note-on velocity effect what GSt & LS are > supposed to do? Does the time between note-on and note-off make a > difference? (I assume it does...) > > What are the current ideas about how this should be looked at? > > > On Thu, 30 Dec 2004 08:52:48 -0800, Mark Knecht <mar...@gm...> > wrote: >> Garett, >> I have both GSt and LS running side by side so I could do a >> comparison if: >> >> 1) I get LS updated to something new and groovy. >> >> and >> >> 2) I had access to an appropriate gig file. >> >> When you state 'voices based on noteoff velocity' what exactly do you >> mean? How can I control the note-off velocity? Does the note-off event >> carry velocity information? If so then how do I effect it? Edit MIDI >> files in Pro Tools possibly? I've called up Pro Tools and made a MIDI >> track but it only shows velocity on the initial note-on event. >> >> I don't know where Pro Tools keeps an event list editor. I'll check >> for that. >> >> - Mark >> >> >> On Thu, 30 Dec 2004 09:13:10 -0700, Garett Shulman >> <shu...@co...> wrote: >>> Hello Christian, On all of the patches I have that trigger voices >>> based >>> on noteoff velocity, the voices seem to playback with excessive >>> volume >>> (like the sound of the mute pad striking the tine on the rhodes when >>> you >>> release a key). Unfortunatly, I don't have a windows box with gs to >>> compare to. I can try to produce a recording. Let me know if there is >>> more specific information I can provide. I get around this problem by >>> using an alsa sequencer filter that just sets noteoff velocity to 1. >>> >>> In regards to the voice bound... Is it possible to set this at >>> runtime >>> or compiletime? >>> >>> -Garett >>> >>> Christian Schoenebeck wrote: >>> >>>> Es geschah am Mittwoch 29 Dezember 2004 06:26 als Garett Shulman >>>> schrieb: >>>> >>>> >>>>> BTW Mark, Scarbee RSP 73 works fine for me (except for the loud >>>>> release >>>>> triggered voices :) ) >>>>> >>>>> >>>> >>>> Hi Garett, >>>> >>>> could please explain once again what the problem with the release >>>> trigger >>>> dimension exactly was? >>>> >>>> Btw, maybe we should reduce the default upper limit of voices? >>>> Currently it's >>>> bound to 128 voices by default, some older boxes might not be able >>>> to deliver >>>> that amount. In future the voice limit, that is the amount of >>>> voices when >>>> voice stealing starts to chime in, should be estimated by >>>> benchmarking. >>>> >>>> CU >>>> Christian >>>> >>>> >>>> ------------------------------------------------------- >>>> 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 >>>> >>>> >>> >>> ------------------------------------------------------- >>> 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: Mark K. <mar...@gm...> - 2004-12-30 17:59:55
|
Garett, I have both GSt and LS running side by side so I could do a comparison if: 1) I get LS updated to something new and groovy. and 2) I had access to an appropriate gig file. When you state 'voices based on noteoff velocity' what exactly do you mean? How can I control the note-off velocity? Does the note-off event carry velocity information? If so then how do I effect it? Edit MIDI files in Pro Tools possibly? I've called up Pro Tools and made a MIDI track but it only shows velocity on the initial note-on event. I don't know where Pro Tools keeps an event list editor. I'll check for that. - Mark On Thu, 30 Dec 2004 09:13:10 -0700, Garett Shulman <shu...@co...> wrote: > Hello Christian, On all of the patches I have that trigger voices based > on noteoff velocity, the voices seem to playback with excessive volume > (like the sound of the mute pad striking the tine on the rhodes when you > release a key). Unfortunatly, I don't have a windows box with gs to > compare to. I can try to produce a recording. Let me know if there is > more specific information I can provide. I get around this problem by > using an alsa sequencer filter that just sets noteoff velocity to 1. > > In regards to the voice bound... Is it possible to set this at runtime > or compiletime? > > -Garett > > Christian Schoenebeck wrote: > > >Es geschah am Mittwoch 29 Dezember 2004 06:26 als Garett Shulman schrieb: > > > > > >>BTW Mark, Scarbee RSP 73 works fine for me (except for the loud release > >>triggered voices :) ) > >> > >> > > > >Hi Garett, > > > >could please explain once again what the problem with the release trigger > >dimension exactly was? > > > >Btw, maybe we should reduce the default upper limit of voices? Currently it's > >bound to 128 voices by default, some older boxes might not be able to deliver > >that amount. In future the voice limit, that is the amount of voices when > >voice stealing starts to chime in, should be estimated by benchmarking. > > > >CU > >Christian > > > > > >------------------------------------------------------- > >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 > > > > > > ------------------------------------------------------- > 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: Mark K. <mar...@gm...> - 2004-12-30 17:54:15
|
OK, I found out how to do it in Pro Tools. It's a little painful though. I'll set up a test MIDI file and get ready to record some audio data. However it seems that testing this in a quantifiable way could be somewhat difficult. Does note-on velocity effect what GSt & LS are supposed to do? Does the time between note-on and note-off make a difference? (I assume it does...) What are the current ideas about how this should be looked at? On Thu, 30 Dec 2004 08:52:48 -0800, Mark Knecht <mar...@gm...> wrote: > Garett, > I have both GSt and LS running side by side so I could do a comparison if: > > 1) I get LS updated to something new and groovy. > > and > > 2) I had access to an appropriate gig file. > > When you state 'voices based on noteoff velocity' what exactly do you > mean? How can I control the note-off velocity? Does the note-off event > carry velocity information? If so then how do I effect it? Edit MIDI > files in Pro Tools possibly? I've called up Pro Tools and made a MIDI > track but it only shows velocity on the initial note-on event. > > I don't know where Pro Tools keeps an event list editor. I'll check for that. > > - Mark > > > On Thu, 30 Dec 2004 09:13:10 -0700, Garett Shulman > <shu...@co...> wrote: > > Hello Christian, On all of the patches I have that trigger voices based > > on noteoff velocity, the voices seem to playback with excessive volume > > (like the sound of the mute pad striking the tine on the rhodes when you > > release a key). Unfortunatly, I don't have a windows box with gs to > > compare to. I can try to produce a recording. Let me know if there is > > more specific information I can provide. I get around this problem by > > using an alsa sequencer filter that just sets noteoff velocity to 1. > > > > In regards to the voice bound... Is it possible to set this at runtime > > or compiletime? > > > > -Garett > > > > Christian Schoenebeck wrote: > > > > >Es geschah am Mittwoch 29 Dezember 2004 06:26 als Garett Shulman schrieb: > > > > > > > > >>BTW Mark, Scarbee RSP 73 works fine for me (except for the loud release > > >>triggered voices :) ) > > >> > > >> > > > > > >Hi Garett, > > > > > >could please explain once again what the problem with the release trigger > > >dimension exactly was? > > > > > >Btw, maybe we should reduce the default upper limit of voices? Currently it's > > >bound to 128 voices by default, some older boxes might not be able to deliver > > >that amount. In future the voice limit, that is the amount of voices when > > >voice stealing starts to chime in, should be estimated by benchmarking. > > > > > >CU > > >Christian > > > > > > > > >------------------------------------------------------- > > >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 > > > > > > > > > > ------------------------------------------------------- > > 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...> - 2004-12-30 16:12:59
|
Hello Christian, On all of the patches I have that trigger voices based on noteoff velocity, the voices seem to playback with excessive volume (like the sound of the mute pad striking the tine on the rhodes when you release a key). Unfortunatly, I don't have a windows box with gs to compare to. I can try to produce a recording. Let me know if there is more specific information I can provide. I get around this problem by using an alsa sequencer filter that just sets noteoff velocity to 1. In regards to the voice bound... Is it possible to set this at runtime or compiletime? -Garett Christian Schoenebeck wrote: >Es geschah am Mittwoch 29 Dezember 2004 06:26 als Garett Shulman schrieb: > > >>BTW Mark, Scarbee RSP 73 works fine for me (except for the loud release >>triggered voices :) ) >> >> > >Hi Garett, > >could please explain once again what the problem with the release trigger >dimension exactly was? > >Btw, maybe we should reduce the default upper limit of voices? Currently it's >bound to 128 voices by default, some older boxes might not be able to deliver >that amount. In future the voice limit, that is the amount of voices when >voice stealing starts to chime in, should be estimated by benchmarking. > >CU >Christian > > >------------------------------------------------------- >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: Christian S. <sch...@so...> - 2004-12-30 02:09:41
|
Es geschah am Mittwoch 29 Dezember 2004 06:26 als Garett Shulman schrieb: > BTW Mark, Scarbee RSP 73 works fine for me (except for the loud release > triggered voices :) ) Hi Garett, could please explain once again what the problem with the release trigger dimension exactly was? Btw, maybe we should reduce the default upper limit of voices? Currently it's bound to 128 voices by default, some older boxes might not be able to deliver that amount. In future the voice limit, that is the amount of voices when voice stealing starts to chime in, should be estimated by benchmarking. CU Christian |
|
From: Garett S. <shu...@co...> - 2004-12-29 20:07:45
|
Hello, I have found that if I create an alsa audio output device and
then try to increase the channels I get the following segfault. However
I can create an alsa audio output device with more than the default
channels (like 4 for example), then set the channels down to 2, then
set the channels back to 4. But, if I try to then set the channels to 6
I get the segfault. This is not an issue for me as I really have no
need to change the number of channel after I have created the device.
HTH. Let me know if there is more info you might need. -Garett
SET AUDIO_OUTPUT_DEVICE_PARAMETER 0 CHANNELS=6
>>> FATAL ERROR: Segmentation fault (SIGSEGV) occured! <<<
Showing stack trace...
No debugger found
Attaching to program: /usr/local/bin/linuxsampler, process 26949
Reading symbols from
/usr/local/lib/linuxsampler/liblinuxsampler.so.0...done.
Loaded symbols for /usr/local/lib/linuxsampler/liblinuxsampler.so.0
Reading symbols from /usr/local/lib/linuxsampler/libgig.so.0...done.
Loaded symbols for /usr/local/lib/linuxsampler/libgig.so.0
Reading symbols from /usr/lib/libjack-0.71.2.so.0...done.
Loaded symbols for /usr/lib/libjack-0.71.2.so.0
Reading symbols from /lib/librt.so.1...done.
Loaded symbols for /lib/librt.so.1
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/libpthread.so.0...done.
[New Thread 16384 (LWP 26947)]
[New Thread 32769 (LWP 26948)]
[New Thread 16386 (LWP 26949)]
[New Thread 32771 (LWP 26951)]
[New Thread 49156 (LWP 26952)]
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /usr/lib/libstdc++.so.5...done.
Loaded symbols for /usr/lib/libstdc++.so.5
Reading symbols from /lib/libm.so.6...done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
0x403ecc36 in nanosleep () from /lib/libc.so.6
(gdb) --- Stacktrace
#0 0x403ecc36 in nanosleep () from /lib/libc.so.6
#1 0x00000000 in ?? ()
--- Symbols
#0 0x00000000 in ?? ()
> > > >No symbol table info available.
---
Error snd_pcm_writei failed: Interrupted system call
Alsa: Audio output error, exiting.
Detaching from program: /usr/local/bin/linuxsampler, process 26949
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "/usr/local/lib/python2.3/site-packages/sampler.py", line 64, in
set_audio_out_channels
print sampler.read_until("\n")
File "/usr/lib/python2.3/telnetlib.py", line 324, in read_until
return self.read_very_lazy()
File "/usr/lib/python2.3/telnetlib.py", line 400, in read_very_lazy
raise EOFError, 'telnet connection closed'
EOFError: telnet connection closed
|
|
From: Garett S. <shu...@co...> - 2004-12-29 05:25:58
|
Hello, I checked out ls from cvs and built it about 20 minutes ago. I will try to give it a more thurough workout, but so far I have not seen the disk stream problem at all. I would get: "No unused stream found (OrderID:34) - report if this happens, this is a bug!" very consistantly on some of my patches with the last checkout and have not seen one yet with the new checkout. When using the sustain pedal to play > 50 voices I did get a couple of: "0x4046e1e0Disk stream not available in time!" but upon releasing the sustain pedal ls stopped producing errors and did not drop voices as it had before. Nice work! BTW Mark, Scarbee RSP 73 works fine for me (except for the loud release triggered voices :) ) -Garett Mark Knecht wrote: >On Wed, 29 Dec 2004 01:13:35 +0100, Christian Schoenebeck ><sch...@so...> wrote: > > >>Looks good! I will do a final test now and will commit it afterwards. Seems we >>reduced our release critical bug list to two remaing items: >> >> * the disk stream bug with error message "No unused stream found" >> >> * release velocity bug >> >>Thanks! >> >>CU >>Christian >> >> > >Hi Christian (and everyone else) > >I wonder if the bug I reported long ago about the Scarbee libraries >has ever been looked at? I understand that since this is a commercial >library that most folks won't have it, but I think the bug may be >important. It was our guess at the time that the files were encrypted >or compressed in some manner. The last time I tried these libraries >under LS (maybe 5-6 months ago) the problem was still there. > >Since they are well respected commercial libraries used by many on the >Northern sounds site I would hope that you all would see the >importance of spending some time on these when you get these other >things behind you. > >To me this is a critical bug. > >Thanks, >Mark > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://productguide.itmanagersjournal.com/ >_______________________________________________ >Linuxsampler-devel mailing list >Lin...@li... >https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel > > |
|
From: Mark K. <mar...@gm...> - 2004-12-29 00:26:39
|
On Wed, 29 Dec 2004 01:13:35 +0100, Christian Schoenebeck <sch...@so...> wrote: > Looks good! I will do a final test now and will commit it afterwards. Seems we > reduced our release critical bug list to two remaing items: > > * the disk stream bug with error message "No unused stream found" > > * release velocity bug > > Thanks! > > CU > Christian Hi Christian (and everyone else) I wonder if the bug I reported long ago about the Scarbee libraries has ever been looked at? I understand that since this is a commercial library that most folks won't have it, but I think the bug may be important. It was our guess at the time that the files were encrypted or compressed in some manner. The last time I tried these libraries under LS (maybe 5-6 months ago) the problem was still there. Since they are well respected commercial libraries used by many on the Northern sounds site I would hope that you all would see the importance of spending some time on these when you get these other things behind you. To me this is a critical bug. Thanks, Mark |
|
From: Vladimir S. <ha...@gm...> - 2004-12-29 00:23:28
|
Cool! Hopefully we'll find an instrument to reproduce the velocity bug problem and then we'll be down to one, the notorious streaming bug. BTW, i haven't seen it anymore after last night checkins. Probably just bad luck. Has anyone seen it recently? With what instruments? Regards, Vladimir. On Wed, 29 Dec 2004 01:13:35 +0100, Christian Schoenebeck <sch...@so...> wrote: > Looks good! I will do a final test now and will commit it afterwards. Seems we > reduced our release critical bug list to two remaing items: > > * the disk stream bug with error message "No unused stream found" > > * release velocity bug > > Thanks! > > CU > Christian > > Es geschah am Dienstag 28 Dezember 2004 12:45 als v-...@vi... schrieb: > > Hello, > > > > I think I have now fixed the bug with samples playing back too long. The > > problem was: When Render() got close to a sample end, silence was added. > > The voice was meant to be killed when all samples had been played. But, as > > the sample end was pushed forward for every silence addition, the end was > > never reached. I added a new counter for "real" sample words left to be > > read, that is, samples not including the added silence. > > > > /Andreas > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Linuxsampler-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel > -- Regards, Vladimir |
|
From: Christian S. <sch...@so...> - 2004-12-29 00:17:09
|
Looks good! I will do a final test now and will commit it afterwards. Seems we reduced our release critical bug list to two remaing items: * the disk stream bug with error message "No unused stream found" * release velocity bug Thanks! CU Christian Es geschah am Dienstag 28 Dezember 2004 12:45 als v-...@vi... schrieb: > Hello, > > I think I have now fixed the bug with samples playing back too long. The > problem was: When Render() got close to a sample end, silence was added. > The voice was meant to be killed when all samples had been played. But, as > the sample end was pushed forward for every silence addition, the end was > never reached. I added a new counter for "real" sample words left to be > read, that is, samples not including the added silence. > > /Andreas |
|
From: <v-...@vi...> - 2004-12-28 11:52:26
|
Hello, I think I have now fixed the bug with samples playing back too long. The problem was: When Render() got close to a sample end, silence was added. The voice was meant to be killed when all samples had been played. But, as the sample end was pushed forward for every silence addition, the end was never reached. I added a new counter for "real" sample words left to be read, that is, samples not including the added silence. /Andreas |
|
From: Vladimir S. <ha...@gm...> - 2004-12-28 09:52:54
|
Hi All, I've got the "streaming bug" happening here very often. At first this made me very happy only i foud out later that it was caused by a combination of my scripts that caused "LOAD ENGINE" to get executed more than once. We had issues there. Not everything was destroyed and recreated back properly. I think i've fixed most of that now, just checked in. So now i'm back at square one. Problem doesn't happen anymore :( I'm pretty sure everybody else who had this problem (including myself previously) had something else (other than LOAD ENGINE) causing it. So there probably more bugs there somewhere. Please give it a try and report results. I'll keep chasing it for the next few days (i'm on vacation here) but if nothing shows up we'll probably have to add some debugging or something. If anyone knows how to reproduce this please let me know :) -- Regards, Vladimir |
161 messages has been excluded from this view by a project administrator.
