Menu
▾
▴
linuxsampler-devel
|
From: <v-...@vi...> - 2004-12-28 11:52:26
Attachments:
sampleend.patch.gz
|
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: 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: 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: 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: 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: 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-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: 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 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: 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: 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 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: Andreas P. <and...@lk...> - 2005-06-11 14:55:10
|
Hi, I have know examined and hopefully corrected this old issue: On 2004-12-30 19:20, Christian Schoenebeck wrote: > 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? I did some measurements which show that the volume of the release triggered sample is derived from three values: the previous note-on velocity, the time from note-on to note-off (the note length) and the value of the "Release trigger decay" parameter in the gig file. The MIDI note-off velocity seems to be ignored. I have committed a fix for this. /Andreas |
|
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: 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 >> |
Thanks for helping keep SourceForge clean.
X