Conversation
Jarkko Sakkinen
jarkko
Edited 1 month ago
This would be great for #audio #plugins, as they don't need an enormous subset of Win32 API.
This could be realized in practical manner for instance in a future version of #CLAP, which could have up-calls whose API signatures would be along the lines with stuff commonly used for from Win32 API. I.e. basic graphics context stuff, file picker etc. Most of the plugins neither sample nor produce audio. They are just plain data processors with a fancy GUI.
A plugin using only those API's would be universal to all operating systems.
And since PE/COFF is widely know format and used across the operating systems for EFI support, DLL would be perfect format for the binary. That way one could have plugin binary that is cross-operating system compatible. I.e. host would implement the API and provide PE/COFF loader to initialize the plugin.
In addition to PE/COFF there should probably be target for wasm, which would enable plugin ecosystem for web daw's.a
https://www.youtube.com/watch?v=H5v0CK249rI
#MusicProduction
This could be realized in practical manner for instance in a future version of #CLAP, which could have up-calls whose API signatures would be along the lines with stuff commonly used for from Win32 API. I.e. basic graphics context stuff, file picker etc. Most of the plugins neither sample nor produce audio. They are just plain data processors with a fancy GUI.
A plugin using only those API's would be universal to all operating systems.
And since PE/COFF is widely know format and used across the operating systems for EFI support, DLL would be perfect format for the binary. That way one could have plugin binary that is cross-operating system compatible. I.e. host would implement the API and provide PE/COFF loader to initialize the plugin.
In addition to PE/COFF there should probably be target for wasm, which would enable plugin ecosystem for web daw's.a
https://www.youtube.com/watch?v=H5v0CK249rI
#MusicProduction
1
0
0
Raven667
raven667@hachyderm.io@jarkko random thought from a lay-person but the portal system for Flatpak covers some of these kinds of interactions (launching a file picker then passing the file back into the container) and maybe could be used as a template for the kind of plugin system you are describing
1
0
0