Ok, let me just briefly my thoughts here, without providing any implementation.
on mac and windows
In the very long run yes. At the moment I think its ok to concentrate on making the linux version better first. We need not support the Gtk UI under Windows/Mac (see below).
vst 1 2 and 3 lv2 plugin support
I personally want to see this in BEAST, so I'll try to implement vst and lv2 support in the future. However, for now I'll probably not do vst3 support if only for the reason that I don't know it as well as I know lv2 and vst2.4.
the modular window gui to look more like a hardware something like this
Right. Tim is working on replacing the Gtk UI with Electron. So improvements for the look and feel should be made to the new UI in the future.
built in eq in the mixer channels like this
Yes, currently you have to use post processing networks for each track. The mixer should allow effects inside the channels directly. Probably something that makes sense once the Electron UI is more complete.
a built in drum machine something like this
Personally, I don't think there needs to be a "machine" here, its enough to write the drum note on events using the piano roll, and then using samples to play the track.
A mode where only note on events are visible could make this easier to use (as for instance hydrogen drums are displayed at the UI).
6.Multi Instruments aka keyboard splitting for live playing
Would be nice to have, but I am not personally interested in implementing it.
a built in multi sampler features something
Well, BEAST has two "multi samplers" built in. One is .bsewave file support (load retrokit for some drums). The other is sf2 support using libfluidsynth. I think linuxsampler provides a library that could be used for gigasampler playback.
Of course if you want to interactively edit which samples are used (and that is the feature request), yes that would be nice, and no that should not be implemented for the Gtk UI, but straight for Electron.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.