You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For host application, JuceAAPAudioPluginHost and tracktion_engine can be seen as useful proof of concept apps. There should be some useful plugin that works well with the hosts.
An example can be fluidsynth-based plugin like juicysfplugin, but Android build needs non-trivial changes. And since we already have fluidsynth itself working on Android, there is not a lot of advantage over simple MIDI player. Especially, it makes little sense to have to instantiate ones for each track.
What I'm seeing good right now is to have SFZ working. sfizz supports LV2, and it actually involves not a few LV2 extension features. It also requires some complicated parameter bindings through Atom port as well as sfz loader through worker threads, so it would be a good dogfooding for LV2 wrapper.
sfizz needs UI support for file picker as well as other parameters. Therefore it could also be a good dogfooding for UI bindings. sfizz has no UI yet, and there is no UI binding generator, so it would also be required (or at least useful) to create UI binding automator in UI-framework-agnostic way.
Actually it does not have to be LV2 (it is rather difficult) so in practice it would be easy to use the library feature directly.
The text was updated successfully, but these errors were encountered:
For host application, JuceAAPAudioPluginHost and tracktion_engine can be seen as useful proof of concept apps. There should be some useful plugin that works well with the hosts.
An example can be fluidsynth-based plugin like juicysfplugin, but Android build needs non-trivial changes. And since we already have fluidsynth itself working on Android, there is not a lot of advantage over simple MIDI player. Especially, it makes little sense to have to instantiate ones for each track.
What I'm seeing good right now is to have SFZ working. sfizz supports LV2, and it actually involves not a few LV2 extension features. It also requires some complicated parameter bindings through Atom port as well as sfz loader through worker threads, so it would be a good dogfooding for LV2 wrapper.
sfizz needs UI support for file picker as well as other parameters. Therefore it could also be a good dogfooding for UI bindings. sfizz has no UI yet, and there is no UI binding generator, so it would also be required (or at least useful) to create UI binding automator in UI-framework-agnostic way.
Actually it does not have to be LV2 (it is rather difficult) so in practice it would be easy to use the library feature directly.
The text was updated successfully, but these errors were encountered: