On Thu, 14 Jul 2022 19:01:00 +0200
Ichthyostega <p...@ichthyostega.de> wrote:
>Am 12.07.22 um 13:14 schrieb Will Godfrey:
>> In other news...
>>
>> This September is another Yoshimi landmark - it becomes a teenager :P so I'm
>> wondering whether to make a fairly small release soon, then go flat out for
>> September, or just quietly carry on for a bumper one in September.
>
>We have accumulated some bugfixes, and we didn't roll a point release yet.
Yes, this is true. Maybe we should just push out 2.2.1 Monday week (25th). I
should be able to get that other GUI issue sorted by then.
>> Suggestions? Anyone got anything they want to push forward?
>
>Hadn't much time to contribute anything lately. But I can see two improvement
>efforts we wanted to push ahead gradually (memory management and float
>parameters). However, ideally these should be doable in small increments and
>without any user visible impacts, so these efforts not something to advertise
>for a major release.
Agreed. It would be nice to have this done, but not something to make a big
deal over. It would be quite meaningless to most of our users.
>For my own work, I am fighting with some problem for quite some time, but I'm
>not really sure how to approach that best. If I recall right, I have mentioned
>it several times in the past. The problem is: if you build an instrument based
>on some distinct sonic character, it often turns out that the result is either
>not balanced in itself over various octaves, and sometimes it also does not
>"run" well, again over a span of several octaves.
>
>This problem manifests itself with some obnoxious symptoms: if you play a
>chord, either the high-end or the low-end dominates. And the balance tends
>to slide away when the score moves up or down.
>
>Similar problems are known from conventional instruments, and there they
>are just considered as symptoms of inferior craftsmanship. A well made
>instrument is just expected to have a smooth "run" over various octaves
>and should have a similar "presence" in high as in low register, and
>should work well when played in ensemble, without requiring excessive
>tweaks or "stunts" by the musician.
>
>Some Ideas to alleviate such problems
>
> - possibility to define a volume adjustment based on the key,
> as part of the instrument itself (not a controller)
Yes. I agree it should be instrument specific, although where exactly? Would
this be a whole instrument setting, or per engine?
> - fading in/out and crossfading of layers, again based on volume, not
> velocity.
Confession time again :P
I originally set cross-fade as velocity, because at the time I couldn't work
out how to do volume without a lot of faffing about, and of course the actual
behaviour is rather different.
Also it is applied as a variation on 'multi' with its own 'yes/no' parameter.
I did this for (partial) backward compatibility. An older version of Yoshimi
will not recognise crossfade and just treats it as a multi. Had we stored a
higher menu number an older version would have reverted to 'single' mode.
I would suggest that a new entry could be added to the kit mode menu for
volume working in the same way with its own extra parameter.
--
Will J Godfrey {apparently now an 'elderly'}
https://willgodfrey.bandcamp.com/
http://yoshimi.github.io
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
_______________________________________________
Yoshimi-devel mailing list
Yoshimi-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
