Menu
▾
▴
linuxsampler-devel
|
From: Peter R. <pet...@de...> - 2004-01-12 07:49:24
|
Bruce Richardson once explained on the NS forum that GigaStudio also has a clever mechanism for releasing (I guess "old") notes whose volume is nearly zero. That might be an interesting alternative (or addition) to a scheme of stopping oldest notes (which might be looping at max volume). Cheers, Peter Roos -----Original Message----- From: Mark Knecht [mailto:mar...@co...] Sent: Monday, January 12, 2004 1:51 To: Christian Schoenebeck Cc: Linux-Sampler Subject: Re: [Linuxsampler-devel] Roadmap (was: Latest CVS commit) On Sun, 2004-01-11 at 15:55, Christian Schoenebeck wrote: > > * Is Delay a minimum note-off->release delay, > > the maximum duration of the sustain state, > > or what? (Both seem useful to me...) > > That 2nd "D" is actually Decay2. It's an exponential fall from the last Decay1 > level to the first level of the Release stage. Decay2 will only become > applied in case this "infinite sustain" is disabled, but I'm not that sure. > Maybe Mark can confirm that? I believe this is a correct description. With Infinite Sustain enabled Decay 2 is not used. With Infinite Sustain disabled, Decay 2 begins at the end of Decay 1. This appears (in my mind) to create a first, normally faster decay region like everyone is used to. After that first decay period, Decay 2 kicks in and GSt will then does a second decay period that takes you down to 0 volume. I think the intention here is to ensure that all notes eventually go to zero even if their keys are never released. This does raise one unsolved issue I've seen with LS. To date I think LS has no mechanism for releasing the oldest notes when it reaches its maximum note count. Press sustain and start hitting keys. Eventually you get messages about not being able to play notes. LS needs to be able to release the oldest notes to that new notes can be played. Generally it will be better to get a release or something from very old notes going away vs. not playing the newest notes. Cheers, Mark ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Linuxsampler-devel mailing list Lin...@li... https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel |
|
From: Mark K. <mar...@co...> - 2004-01-12 14:29:59
|
On Sun, 2004-01-11 at 23:54, Peter Roos wrote: > Bruce Richardson once explained on the NS forum that GigaStudio also has a > clever mechanism for releasing (I guess "old") notes whose volume is nearly > zero. That might be an interesting alternative (or addition) to a scheme of > stopping oldest notes (which might be looping at max volume). > > Cheers, > > Peter Roos > Peter, Good to have you here and thanks for the pointer. I'll have to go look for Bruce's description. He's generally quite a good guy to get info from. Thanks, Mark |
|
From: Peter E. R. <pet...@de...> - 2004-01-12 14:40:27
|
I believe the same functionality was already mentioned here in the ongoing discussions yesterday and today. Maybe it is an option to distinguish between SAME note stealing and DIFFERENT note stealing, also... ;-) I think this is related to GigaStudio's block chord note stealing. And, I believe this is probably already on the developers minds: treat the notes differently based on where they are in the ADSR in the note stealing process. I guess this can a rather intricate set of rules. Bruce is quite close to the developers, so some of his notes surely go beyond being educated guesses. Regards, Peter -----Original Message----- From: lin...@li... [mailto:lin...@li...] On Behalf Of Mark Knecht Sent: Monday, January 12, 2004 15:30 Cc: 'Linux-Sampler' Subject: RE: [Linuxsampler-devel] Roadmap (was: Latest CVS commit) On Sun, 2004-01-11 at 23:54, Peter Roos wrote: > Bruce Richardson once explained on the NS forum that GigaStudio also has a > clever mechanism for releasing (I guess "old") notes whose volume is nearly > zero. That might be an interesting alternative (or addition) to a scheme of > stopping oldest notes (which might be looping at max volume). > > Cheers, > > Peter Roos > Peter, Good to have you here and thanks for the pointer. I'll have to go look for Bruce's description. He's generally quite a good guy to get info from. Thanks, Mark ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Linuxsampler-devel mailing list Lin...@li... https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel |
|
From: David O. <da...@ol...> - 2004-01-12 14:56:31
|
On Monday 12 January 2004 15.40, Peter E. Roos wrote: > I believe the same functionality was already mentioned here in the > ongoing discussions yesterday and today. > > Maybe it is an option to distinguish between SAME note stealing and > DIFFERENT note stealing, also... ;-) Yes, that can differ a lot between instruments. Many real instruments=20 respond to "retrigging" by adding overtones that are not there when=20 starting a note from silence. Physical modelling can simulate that=20 using a single "voice" per key/string/whatever, but a sampler or=20 other wavetable synth generally has to fake it one way or another. That said, it's not really about stealing, in the same sense as the=20 "out of voices emergency solution" - although with certain patches,=20 you *could* end up stealing your own voice, sort of. It think the=20 normal behavior would be things like: =09* Explicitly make your voice stop playing, and then =09 start playing a new waveform. (Causes some delay.) =09* Do something funny with the envelope, but just let =09 the oscillator run. =09* Set the old voice in release state, and then start =09 a new voice, leaving the old voice to die alone. =09 (This is effectively what you do if you want the =09 first alternative, but without the note-on delay.) > I think this is related to GigaStudio's block chord note stealing. Can you expand on that? > And, I believe this is probably already on the developers minds: > treat the notes differently based on where they are in the ADSR in > the note stealing process. Though checking the EG isn't enough, as the waveform may affect the=20 output level more than the EG sometimes. I use simple peak level meters in Audiality, but I don't know if=20 that's a suficient or effective solution. They just happened to be=20 there when I hacked the voice stealing code... (The meters were=20 thrown in for some audio debugging eyecandy that you can see in debug=20 builds of Kobo Deluxe. :-)=20 > I guess this can a rather intricate set of rules. To say the least... It's hard enough to figure out what *actually* is=20 the least audible voice - and that's just the beginning! //David Olofson - Programmer, Composer, Open Source Advocate =2E- Audiality -----------------------------------------------. | Free/Open Source audio engine for games and multimedia. | | MIDI, modular synthesis, real time effects, scripting,... | `-----------------------------------> http://audiality.org -' --- http://olofson.net --- http://www.reologica.se --- |
|
From: Mark K. <mar...@co...> - 2004-01-12 15:28:36
|
On Mon, 2004-01-12 at 06:56, David Olofson wrote: > > I think this is related to GigaStudio's block chord note stealing. > > Can you expand on that? > > GSt has a setting for the number of notes to use in 'Block Chord Stealing'. I've personally never known how to best set it, so I think I have it at about 10 notes or so, but that's just superstition. I've not bothered to look in the help files to see what it really does. - Mark |
|
From: Mark K. <mar...@co...> - 2004-01-13 01:08:43
|
On Mon, 2004-01-12 at 06:56, David Olofson wrote: > > I think this is related to GigaStudio's block chord note stealing. > > Can you expand on that? > > Dave, From GSt's help on the subject we're given just a few items to set up - Master Attenuation - Polyphony (up to the max you bought - 32, 96 or 160) - Transition Voices Transition Voices - Alter Transition Voices to steal notes from block chords Select the maximum number of voices that can be stolen from the decay portion of a sound to support polyphony. While a higher setting provides better block chord coverage, a lower setting increases overall polyphony. If you hear pops while playing a high-polyphony passage, try increasing this setting. - Mark |
|
From: Mark K. <mar...@co...> - 2004-01-12 15:15:43
|
On Mon, 2004-01-12 at 06:40, Peter E. Roos wrote: > I believe the same functionality was already mentioned here in the > ongoing discussions yesterday and today. > > Maybe it is an option to distinguish between SAME note stealing and > DIFFERENT note stealing, also... ;-) > I think this is related to GigaStudio's block chord note stealing. > > And, I believe this is probably already on the developers minds: treat > the notes differently based on where they are in the ADSR in the note > stealing process. > > I guess this can a rather intricate set of rules. > > Bruce is quite close to the developers, so some of his notes surely go > beyond being educated guesses. > > Regards, > > Peter Good points one and all. |
Thanks for helping keep SourceForge clean.
X