This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
changelog:drumgizmo-0.9.18 [2019/09/29 16:44] – [Release Notes for DrumGizmo-0.9.18] chaot | changelog:drumgizmo-0.9.18 [2019/10/16 07:21] – [Sample Normalization] deva | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | < | ||
======Release Notes for DrumGizmo-0.9.18====== | ======Release Notes for DrumGizmo-0.9.18====== | ||
+ | |||
+ | Released October 15th 2019. | ||
+ | |||
Roadmap: [[roadmap: | Roadmap: [[roadmap: | ||
- | < | + | |
- | NOTE TO AUTHORS: Insert video like this: | + | This release is primarily a bugfix release but a few new features also managed to sneak in. |
- | </code> | + | |
- | {{videogg> | + | Highlights: |
- | < | + | * Sample selection algorithm now behaves a lot better when using a small sample set. |
- | NOTE TO AUTHORS: Insert audio like this: | + | * Error reporting has been drastically improved when loading drum-kits. |
- | </ | + | * Sample normalization option has been added. |
- | {{videogg> | + | |
- | < | + | =====Sample Selection===== |
- | END OF NOTE | + | One of the main goals of this bugfix release is to fine-tune the sample selection algorithm. The things we changed are: |
+ | - Make the pDiverse parameter behave less extreme | ||
+ | - Make the pClose parameter behave less extreme | ||
+ | - Fine tune parameters and knob ranges of the sample selection algorithm | ||
+ | |||
+ | For pDiverse, we internally used a function which would attain very high values if the same sample is played twice in a very short time. Therefore, even samples with very different velocity from the input MIDI velocity would seem better. This lead to very loud/quiet samples to be chosen in scenarios where only few samples exist for a drum, which is obviously undesirable. By making the function values "less extreme", | ||
+ | |||
+ | This is what it sounded like, before the fix (ie. in version 0.9.17) - note; all notes have essentially the same velocity: | ||
+ | {{videogg> | ||
+ | |||
+ | And here is that same piece with the fix applied in version 0.9.18: | ||
+ | {{videogg> | ||
+ | |||
+ | =====Improved Error Reporting===== | ||
+ | First of all the drumkit loader is now able to tell the user what went wrong when an error occurs. This is printed in the status area of the plugin gui. | ||
+ | The dgvalidator tool inherited these same error reporting mechanisms so that now too is verbose about its findings when validating a drumkit. | ||
+ | |||
+ | =====Sample Normalization===== | ||
+ | A new tag '' | ||
+ | This feature makes it possible to create a sample containing audio files which is all normalized and still get something resembling different stroke powers based on the velocity. | ||
+ | |||
+ | An example of how to use it: | ||
+ | < | ||
+ | <?xml version=' | ||
+ | < | ||
+ | < | ||
+ | <sample name=" | ||
+ | < | ||
+ | ... | ||
+ | </ | ||
+ | ... | ||
+ | </ | ||
+ | </ | ||
</ | </ | ||
- | ==== Sample Selection | + | =====OSX improvements===== |
- | Sample selection was reworked: | + | On OSX it is now possible to compile and run DrumGizmo as an lv2 plugin with Cocoa UI. |
- | * fine tuning of parameters | + | It is still not entirely stable but at least now it works. |
- | * make diverse value less extrem for unusual values | + | |
- | * normalize | + | The MacOSX compilation instructions has been updated with the LV2 compilation and dependency installation: |
+ | =====CLI Improvements===== | ||
+ | The DrumGizmo command-line tool can control the remaining velocity humanizer | ||
+ | |||
+ | =====Other Bugs Fixes===== | ||
+ | | ||
+ | * A crash has been fixed on Windows when the plugin window was being close while the file-browser was still open. | ||
+ | * The plugin UI was not initially shown in Reaper on Windows until the UI was toggled off, then on. This has now been fixed. | ||
+ | * The file-browser | ||
+ | * The stddev sample spreading is now enabled/ | ||
+ | |||
+ | As always, if you still have issues or weird behavior: Please tell us! Your feedback is very valuable, always. |