Dear list,
here's a collection of suggestions that popped up during Will's
excellent workshop at LAC yesterday (with my remarks added in
parenthesis).
* Add the name of the current instrument to window titles of any of the
instrument's child windows.
(Good idea, especially useful if two instances of yosh are
simultaneously edited on the same workspace -- which is nothing I'd
recommend but it might happen.)
simultaneously edited on the same workspace -- which is nothing I'd
recommend but it might happen.)
* Reverse the order of panels in the 'Part's Insert Effects' window, so
that the effect number/type selection takes place at the top and the
selected effect's controls are at the bottom. It has been suggested
that this is more intuitive (to which I agree).
* For the harmonics faders, use something like logarithmic mapping of
fader position to value. With the currently implemented mapping, the
harmonics are audible fairly loud as soon as the fader is pulled up
by just one or two pixels.
(Great idea. One caveat I can see regarding compatibility with zyn:
the then achievable small values, while being loadable in zyn, would
probably not result in the faders being visibly set to any value < 0
and as soon as such a fader is moved, the small value will be lost and
not reproducible.)
the then achievable small values, while being loadable in zyn, would
probably not result in the faders being visibly set to any value < 0
and as soon as such a fader is moved, the small value will be lost and
not reproducible.)
* Missing tooltip on the global bandwidth fader in SUBsynth.
(Not mission critical as the label is quite explanatory. While we're
at it: the 'Drum mode' checkbox in the instrument kit window also
lacks a tooltip and is less self-explanatory. We'll probably find
more.)
at it: the 'Drum mode' checkbox in the instrument kit window also
lacks a tooltip and is less self-explanatory. We'll probably find
more.)
* An 'import samples' feature in PADsynth.
(Users of such a feature would have to know what they're doing, i.e.
load the correct number of perfectly loopable samples of appropriate
length, to get predictable results. Would anyone actually do this and
use such a feature? Alternatively, any single sufficiently long sample
could perhaps be automagically transformed into the required set of
samples but someone'd have to code that.)
load the correct number of perfectly loopable samples of appropriate
length, to get predictable results. Would anyone actually do this and
use such a feature? Alternatively, any single sufficiently long sample
could perhaps be automagically transformed into the required set of
samples but someone'd have to code that.)
* Optional "crossfades" along overlapping note ranges in instrument
kits, to achieve a smooth transition from one sound to another.
(Would hurt compatibility with zyn.)
If I've overlooked any suggestions during the workshop or if you have
others, just add them.
best,
-david
------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________ yoshimi-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/yoshimi-user
