Not Richard, but responding anyway. On Mon, Sep 2, 2019 at 2:39 PM Ruud Mulder <[email protected]> wrote:
E.g. why is there no OSC in non-sequencer, > Well, for one thing it's a completely open question what OSC would even do in a sequencer. OSC is way more flexible and open-ended than MIDI. Anyway, It would be some kind of horrible hack to try any store the OSC events in a MIDI file (which is what non-sequencer reads and writes). If you have some coherent and sensible ideas for how this could work, the world may be listening. Might as well ask why there's no Tetris game built in. > there is someone who added LV2 plugins but it is not merged into the main > development (why?). > LV2 support was not missing in the first place due to lack of development resources. It was intentionally omitted because LV2 does not align with the goals of the project. In short, LV2 is a comparatively heavy-weight and heavy-handed dependency, but doesn't offer much, if anything, over LADSPA (unless you count hype as a pro). I see LV2 in the same general light as systemd, if that clears matters up any. > Also there are small but annoying 'features'. Open up a separate window > for the tracks and mute a track. In the main window the track status is not > updated. It is the way FLTK seems to work. There is too little separation > between the view and the model. This has nothing to do with speed. The > listener model is well known and updates all views fast enough and this can > be added to FLTK. > This description is not sufficient for me to understand the nature of the complaint. I can't even tell which application you're referring to. However, I can tell you that whatever it is you're describing is very unlikely to be due to a limitation of FLTK/NTK. The same issue applies to your CC event editor problem. The description of your workflow, i.e. what you're trying to do and how non-sequencer is preventing you from doing that is not sufficient for me (or anyone else, probably) to respond to it intelligently with anything other than a quiz. The event editor was never designed to be a primary input method, I'm sure there's room for improvement and it's likely that a minor tweak or better instructions would solve your problem. I'm just not sure what the problem is.
